Processed: Bug #907431 in cppo marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #907431 [cppo] cppo's testsuite fails on arm{el,hf} and ppc64el
Added tag(s) pending.

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

Bug#907431: Bug #907431 in cppo marked as pending

[Mehdi Dogguy]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/ocaml-team/cppo/commit/416abc291f17f06e40d0bbc9e2d3cd6ba20e265c


Fix issue on arm{el,hf} and ppc64el (Closes: #907431)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/907431

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 907432 https://github.com/cloudflare/redoctober/issues/193
Bug #907432 [src:golang-github-cloudflare-redoctober] 
golang-github-cloudflare-redoctober: FTBFS (too many arguments in call to 
activation.Listeners)
Set Bug forwarded-to-address to 
'https://github.com/cloudflare/redoctober/issues/193'.
> thanks
Stopping processing here.

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

Processed: tagging 907764

[Debian Bug Tracking System]

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

> tags 907764 + help
Bug #907764 [src:golang-github-hashicorp-raft] golang-github-hashicorp-raft: 
FTBFS in buster/sid (failing tests)
Added tag(s) help.
> thanks
Stopping processing here.

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

Bug#908800: nautilus: can't use nautilus without tracker

[Youhei SASAKI]

Package: nautilus
Version: 3.30.0-4
Severity: grave

Dear Maintainer,

* What led up to the situation?

I can't use nautilus without tracker:

  % nautilus
  (nautilus:8): Tracker-ERROR **: 13:24:19.460: Unable to find default 
domain ontology rule /usr/share/tracker/domain-ontologies/default.rule

But nautilus dependencies said...
  ...
  Suggests: eog, evince | pdf-viewer, nautilus-extension-brasero, 
nautilus-sendto, totem | mp3-decoder, tracker, xdg-user-dirs
  ...

So, nautilus should "Depends" tracker, not "Suggests".

Best Wishes,
Youhei

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

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

Versions of packages nautilus depends on:
ii  bubblewrap 0.3.0-1
ii  desktop-file-utils 0.23-3
ii  gsettings-desktop-schemas  3.28.0-1
ii  gvfs   1.38.0-2
ii  libatk1.0-02.30.0-1
ii  libc6  2.27-6
ii  libcairo-gobject2  1.15.12-1
ii  libcairo2  1.15.12-1
ii  libgdk-pixbuf2.0-0 2.38.0+dfsg-5
ii  libgexiv2-20.10.8-1
ii  libglib2.0-0   2.58.0-3
ii  libglib2.0-data2.58.0-3
ii  libgnome-autoar-0-00.2.3-1
ii  libgtk-3-0 3.24.0-3
ii  libnautilus-extension1a3.30.0-4
ii  libpango-1.0-0 1.42.4-3
ii  libpangocairo-1.0-01.42.4-3
ii  libseccomp22.3.3-3
ii  libselinux12.8-1+b1
ii  libtracker-sparql-2.0-02.1.4-1
ii  nautilus-data  3.30.0-4
ii  shared-mime-info   1.9-2

Versions of packages nautilus recommends:
pn  gnome-sushi  
pn  gvfs-backends
ii  librsvg2-common  2.40.20-3

Versions of packages nautilus suggests:
ii  eog 3.28.3-1
ii  evince [pdf-viewer] 3.30.0-2
pn  nautilus-extension-brasero  
pn  nautilus-sendto 
ii  tracker 2.1.4-1
ii  vlc [mp3-decoder]   1:3.0.4-dmo3
ii  xdg-user-dirs   0.17-1

-- no debconf information

Processed: fixed 901912 in 2.2.2-1+deb9u1

[Debian Bug Tracking System]

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

> # will be in upcoming DSA
> fixed 901912 2.2.2-1+deb9u1
Bug #901912 {Done: Alessandro Ghedini } [src:discount] 
CVE-2018-11468 CVE-2018-11503 CVE-2018-11504 CVE-2018-12495
The source 'discount' and version '2.2.2-1+deb9u1' do not appear to match any 
binary packages
Marked as fixed in versions discount/2.2.2-1+deb9u1.
> thanks
Stopping processing here.

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

Processed: severity of 903149 is serious

[Debian Bug Tracking System]

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

> severity 903149 serious
Bug #903149 [clipit] ClipIt crashes with segmentation fault on start
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#908671: marked as done (glib-d: ftbfs on armhf and i386)

[Debian Bug Tracking System]

Your message dated Thu, 13 Sep 2018 23:49:09 +
with message-id 
and subject line Bug#907947: fixed in gir-to-d 0.16.1-1
has caused the Debian Bug report #907947,
regarding glib-d: ftbfs on armhf and 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.)


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

hello, recent ldc made the package FTBFS.

snippet of the build log on armhf
[1/327] ldc2 -Iglibd-2.0@sha -I. -I.. -Igenerated -I../generated 
-I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include 
-enable-color -O -g -release -wi -mattr=-neon -relocation-model=pic   -of 
'glibd-2.0@sha/obj-arm-linux-gnueabihf_generated_glib_c_functions.d.o' -c 
../obj-arm-linux-gnueabihf/generated/glib/c/functions.d
FAILED: glibd-2.0@sha/obj-arm-linux-gnueabihf_generated_glib_c_functions.d.o 
ldc2 -Iglibd-2.0@sha -I. -I.. -Igenerated -I../generated 
-I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include 
-enable-color -O -g -release -wi -mattr=-neon -relocation-model=pic   -of 
'glibd-2.0@sha/obj-arm-linux-gnueabihf_generated_glib_c_functions.d.o' -c 
../obj-arm-linux-gnueabihf/generated/glib/c/functions.d
../obj-arm-linux-gnueabihf/generated/glib/c/functions.d(1163): Error: found 
`const` when expecting `)`
../obj-arm-linux-gnueabihf/generated/glib/c/functions.d(1163): Error: semicolon 
expected following function declaration
../obj-arm-linux-gnueabihf/generated/glib/c/functions.d(1163): Error: 
declaration expected, not `*`
../obj-arm-linux-gnueabihf/generated/glib/c/functions.d(1187): Error: found 
`const` when expecting `)`
../obj-arm-linux-gnueabihf/generated/glib/c/functions.d(1187): Error: semicolon 
expected following function declaration
../obj-arm-linux-gnueabihf/generated/glib/c/functions.d(1187): Error: 
declaration expected, not `*`
[2/327] ldc2 -Iglibd-2.0@sha -I. -I.. -Igenerated -I../generated 
-I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include 
-enable-color -O -g -release -wi -mattr=-neon -relocation-model=pic   -of 
'glibd-2.0@sha/obj-arm-linux-gnueabihf_generated_gtkd_paths.d.o' -c 
../obj-arm-linux-gnueabihf/generated/gtkd/paths.d
[3/327] ldc2 -Iglibd-2.0@sha -I. -I.. -Igenerated -I../generated 
-I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include 
-enable-color -O -g -release -wi -mattr=-neon -relocation-model=pic   -of 
'glibd-2.0@sha/obj-arm-linux-gnueabihf_generated_glib_BookmarkFile.d.o' -c 
../obj-arm-linux-gnueabihf/generated/glib/BookmarkFile.d
FAILED: glibd-2.0@sha/obj-arm-linux-gnueabihf_generated_glib_BookmarkFile.d.o 
ldc2 -Iglibd-2.0@sha -I. -I.. -Igenerated -I../generated 
-I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include 
-enable-color -O -g -release -wi -mattr=-neon -relocation-model=pic   -of 
'glibd-2.0@sha/obj-arm-linux-gnueabihf_generated_glib_BookmarkFile.d.o' -c 
../obj-arm-linux-gnueabihf/generated/glib/BookmarkFile.d
generated/glib/c/functions.d(1163): Error: found `const` when expecting `)`
generated/glib/c/functions.d(1163): Error: semicolon expected following 
function declaration
generated/glib/c/functions.d(1163): Error: declaration expected, not `*`
generated/glib/c/functions.d(1187): Error: found `const` when expecting `)`
generated/glib/c/functions.d(1187): Error: semicolon expected following 
function declaration
generated/glib/c/functions.d(1187): Error: declaration expected, not `*`
[4/327] ldc2 -Iglibd-2.0@sha -I. -I.. -Igenerated -I../generated 
-I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include 
-enable-color -O -g -release -wi -mattr=-neon -relocation-model=pic   -of 
'glibd-2.0@sha/obj-arm-linux-gnueabihf_generated_glib_AsyncQueue.d.o' -c 
../obj-arm-linux-gnueabihf/generated/glib/AsyncQueue.d
FAILED: glibd-2.0@sha/obj-arm-linux-gnueabihf_generated_glib_AsyncQueue.d.o 
ldc2 -Iglibd-2.0@sha -I. -I.. -Igenerated -I../generated 
-I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include 
-enable-color -O -g -release -wi -mattr=-neon -relocation-model=pic   -of 
'glibd-2.0@sha/obj-arm-linux-gnueabihf_generated_glib_AsyncQueue.d.o' -c 
../obj-arm-linux-gnueabihf/generated/glib/AsyncQueue.d
generated/glib/c/functions.d(1163): Error: found `const` when expecting `)`
generated/glib/c/functions.d(1163): Error: semicolon expected following 
function declaration
generated/glib/c/functions.d(1163): Error: declaration expected, not `*`
generated/glib/c/functions.d(1187): Error: found `const` when expecting `)`

Bug#907947: marked as done (glib-d FTBFS with glib 2.58)

[Debian Bug Tracking System]

Your message dated Thu, 13 Sep 2018 23:49:09 +
with message-id 
and subject line Bug#907947: fixed in gir-to-d 0.16.1-1
has caused the Debian Bug report #907947,
regarding glib-d FTBFS with glib 2.58
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.)


-- 
907947: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907947
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glib-d
Version: 2.0.0-1
Severity: serious
Tags: ftbfs

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

...
FAILED: glibd-2.0@sha/obj-x86_64-linux-gnu_generated_glib_c_functions.d.o 
ldc2 -Iglibd-2.0@sha -I. -I.. -Igenerated -I../generated 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-enable-color -O -g -release -wi -relocation-model=pic   -of 
'glibd-2.0@sha/obj-x86_64-linux-gnu_generated_glib_c_functions.d.o' -c 
../obj-x86_64-linux-gnu/generated/glib/c/functions.d
../obj-x86_64-linux-gnu/generated/glib/c/functions.d(1163): Error: found 
`const` when expecting `)`
../obj-x86_64-linux-gnu/generated/glib/c/functions.d(1163): Error: semicolon 
expected following function declaration
../obj-x86_64-linux-gnu/generated/glib/c/functions.d(1163): Error: declaration 
expected, not `*`
../obj-x86_64-linux-gnu/generated/glib/c/functions.d(1187): Error: found 
`const` when expecting `)`
../obj-x86_64-linux-gnu/generated/glib/c/functions.d(1187): Error: semicolon 
expected following function declaration
../obj-x86_64-linux-gnu/generated/glib/c/functions.d(1187): Error: declaration 
expected, not `*`
...
--- End Message ---
--- Begin Message ---
Source: gir-to-d
Source-Version: 0.16.1-1

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

Debian distribution maintenance software
pp.
Matthias Klumpp  (supplier of updated gir-to-d 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, 14 Sep 2018 09:22:45 +0200
Source: gir-to-d
Binary: gir-to-d
Architecture: source amd64
Version: 0.16.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian D Language Group 
Changed-By: Matthias Klumpp 
Description:
 gir-to-d   - Create D bindings from GObject introspection files
Closes: 907947
Changes:
 gir-to-d (0.16.1-1) unstable; urgency=medium
 .
   * New upstream version: 0.16.1
 - Fixes GLib >= 2.58 function prototype generation (Closes: #907947)
Checksums-Sha1:
 a9df581e15c62ae548a0eeb1cdbdafcf42dc860e 1965 gir-to-d_0.16.1-1.dsc
 9a4c5d82aa3eef81ff239e17d05c6b26b704bf23 41095 gir-to-d_0.16.1.orig.tar.gz
 e639f000628a9cd98f253f144f5052226cdf7b7e 2332 gir-to-d_0.16.1-1.debian.tar.xz
 e88868c8492898fe7a749121674880685eab9d97 1342168 
gir-to-d-dbgsym_0.16.1-1_amd64.deb
 5d018ac4f07c1857864cf94f90e0abfbd6c12b6a 6528 gir-to-d_0.16.1-1_amd64.buildinfo
 7051c99715d0db1e29ea1ff72b45ed57b35073ff 284708 gir-to-d_0.16.1-1_amd64.deb
Checksums-Sha256:
 6ac9d44b8ddcbcb2d4f6dd4b0e37419359c7de7700b255ab8e14e2f00086266a 1965 
gir-to-d_0.16.1-1.dsc
 5917c33abf57bef042978e51b4bd0b36fc4ec45c0f5a7830a3881c10957d6a8a 41095 
gir-to-d_0.16.1.orig.tar.gz
 fa85fea5a9e9a24b1c2f0b7052971e28e4bdf8a74c14b6b7e51cff1f2be41f9d 2332 
gir-to-d_0.16.1-1.debian.tar.xz
 11a062ef83e12ea003e5feb59f1cc63152ab3585a859d021cf89ff8cfe1ded24 1342168 
gir-to-d-dbgsym_0.16.1-1_amd64.deb
 8b2fbcf5babc84019f564966be30b914b34e695dcd48acddbc9bb32689a5e65c 6528 
gir-to-d_0.16.1-1_amd64.buildinfo
 faf337ad77e0faee5e7d73d79863abb4bdaf6c66378332f43e08c42da1c83f0f 284708 
gir-to-d_0.16.1-1_amd64.deb
Files:
 953706d55efb4887807846b7645efe22 1965 devel optional gir-to-d_0.16.1-1.dsc
 abf67a099a855e14df88b1ec363b3f00 41095 devel optional 
gir-to-d_0.16.1.orig.tar.gz
 91ab2337963cd997e0182856578b54a6 2332 devel optional 
gir-to-d_0.16.1-1.debian.tar.xz
 a8bd5edc4ed5b90824b19de769bf4ca7 1342168 debug optional 
gir-to-d-dbgsym_0.16.1-1_amd64.deb
 849a90cb7c08ad9adfe6085897516003 6528 devel optional 
gir-to-d_0.16.1-1_amd64.buildinfo
 90b787ab266d67345ab01e7b7a3f7c90 284708 devel optional 
gir-to-d_0.16.1-1_amd64.deb

-BEGIN PGP SIGNATURE-

Bug#888549: chrome-gnome-shell: Please don't use /etc/opt, it's not FHS-compliant

[Russ Allbery]

Jonathan Nieder  writes:
> Jeremy Bicha wrote:

>> chrome-gnome-shell (in this case) is an addon for the Google Chrome web
>> browser. Since Chrome installs to /opt/ (which is encouraged by FHS),
>> /etc/opt/ is the only standards-compliant location for
>> chrome-gnome-shell to ship the configuration files it needs to provide
>> its core functionality.

>> There is no reason this functionality cannot be offered in Debian. We
>> got complaints when we supported other browsers but not Google Chrome.

> Since Google Chrome is not part of Debian, shouldn't this
> functionality be offered in contrib, not Debian?

chrome-gnome-shell supports all of Chromium, Chrome, and Firefox in the
same package, two of which are in Debian.  It only installs one file in
/etc/opt for Chrome, namely:

/etc/opt/chrome/native-messaging-hosts/org.gnome.chrome_gnome_shell.json

Splitting that single config file into a separate contrib package feels
like overkill here.  It shouldn't hurt anything on a system without Chrome
and it doesn't create any sort of dependency on Chrome, which is the
normal case for contrib.

-- 
Russ Allbery (r...@debian.org)   

Bug#906488: marked as done (lifeograph: FTBFS in buster/sid (static assertion failed))

[Debian Bug Tracking System]

Your message dated Thu, 13 Sep 2018 22:52:16 +
with message-id 
and subject line Bug#906488: fixed in lifeograph 1.4.2-2
has caused the Debian Bug report #906488,
regarding lifeograph: FTBFS in buster/sid (static assertion 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.)


-- 
906488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906488
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:lifeograph
Version: 1.4.2-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-arch
dh build-arch --parallel
   dh_update_autotools_config -a -O--parallel
   dh_auto_configure -a -O--parallel
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles" ..
-- The C compiler identification is GNU 8.2.0
-- The CXX compiler identification is GNU 8.2.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++

[... snipped ...]

 from /<>/src/app_window.cpp:32:
/usr/include/gtk-3.0/gtk/deprecated/gtkstatusicon.h:74:8: warning: unnecessary 
parentheses in declaration of '__gtk_reserved1' [-Wparentheses]
   void (*__gtk_reserved1);
^
/usr/include/gtk-3.0/gtk/deprecated/gtkstatusicon.h:75:8: warning: unnecessary 
parentheses in declaration of '__gtk_reserved2' [-Wparentheses]
   void (*__gtk_reserved2);
^
/usr/include/gtk-3.0/gtk/deprecated/gtkstatusicon.h:76:8: warning: unnecessary 
parentheses in declaration of '__gtk_reserved3' [-Wparentheses]
   void (*__gtk_reserved3);
^
/usr/include/gtk-3.0/gtk/deprecated/gtkstatusicon.h:77:8: warning: unnecessary 
parentheses in declaration of '__gtk_reserved4' [-Wparentheses]
   void (*__gtk_reserved4);
^
In file included from /usr/include/c++/8/map:60,
 from /usr/include/glibmm-2.4/glibmm/variant.h:32,
 from 
/usr/include/glibmm-2.4/glibmm/containerhandle_shared.h:23,
 from /usr/include/glibmm-2.4/glibmm/arrayhandle.h:21,
 from /usr/include/glibmm-2.4/glibmm.h:92,
 from /usr/include/gtkmm-3.0/gtkmm.h:87,
 from /<>/src/lifeograph.hpp:27,
 from /<>/src/app_window.cpp:32:
/usr/include/c++/8/bits/stl_tree.h: In instantiation of 'class 
std::_Rb_tree, bool 
(*)(LIFEO::DiaryElement*, LIFEO::DiaryElement*), std::allocator >':
/usr/include/c++/8/bits/stl_set.h:133:17:   required from 'class 
std::set >'
/<>/src/diarydata.hpp:351:7:   required from 'class 
LIFEO::DiaryElementReferrer'
/<>/src/diarydata.hpp:519:29:   required from here
/usr/include/c++/8/bits/stl_tree.h:452:21: error: static assertion failed: 
comparison object must be invocable with two arguments of key type
   static_assert(__is_invocable<_Compare&, const _Key&, const _Key&>{},
 ^
/usr/include/c++/8/bits/stl_tree.h: In instantiation of 'class 
std::_Rb_tree, 
std::_Select1st >, bool 
(*)(LIFEO::DiaryElement*, LIFEO::DiaryElement*), 
std::allocator > >':
/usr/include/c++/8/bits/stl_map.h:151:17:   required from 'class 
std::map > 
>'
/<>/src/diarydata.hpp:371:7:   required from 'class 
LIFEO::DiaryElementMapper'
/<>/src/diarydata.hpp:585:63:   required from here
/usr/include/c++/8/bits/stl_tree.h:452:21: error: static assertion failed: 
comparison object must be invocable with two arguments of key type
/usr/include/c++/8/bits/stl_tree.h: In instantiation of 'class 
std::_Rb_tree, bool 
(*)(LIFEO::DiaryElement*, LIFEO::DiaryElement*), std::allocator 
>':
/usr/include/c++/8/bits/stl_set.h:133:17:   required from 'class 
std::set >'
/<>/src/diarydata.hpp:351:7:   required from 'class 
LIFEO::DiaryElementReferrer'
/<>/src/diarydata.hpp:707:62:   required from here
/usr/include/c++/8/bits/stl_tree.h:452:21: error: static assertion failed: 
comparison object must be invocable with two arguments of key type
make[3]: *** [CMakeFiles/lifeograph.dir/build.make:66: 
CMakeFiles/lifeograph.dir/src/app_window.cpp.o] Error 1
make[3]: Leaving directory 

Bug#908786: mothur-mpi contains the same binary as mothur

[Adrian Bunk]

Package: mothur-mpi
Version: 1.40.5-1
Severity: serious

$ sha256sum /usr/bin/mothur*
316ea8bcabce032371788425c98c5da62a353de20a1b6174582cad5a49a06153  
/usr/bin/mothur
316ea8bcabce032371788425c98c5da62a353de20a1b6174582cad5a49a06153  
/usr/bin/mothur-mpi
$ 


USEMPI seems to be no longer an upstream option,
so both builds produce the same binary.

Bug#908323: marked as done (libgtk3-perl: FTBFS: t/overrides.t failure)

[Debian Bug Tracking System]

Your message dated Thu, 13 Sep 2018 22:35:43 +
with message-id 
and subject line Bug#908323: fixed in libgtk3-perl 0.034-2
has caused the Debian Bug report #908323,
regarding libgtk3-perl: FTBFS: t/overrides.t failure
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.)


-- 
908323: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908323
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgtk3-perl
Version: 0.034-1
Severity: serious
User: debian-p...@lists.debian.org
Usertags: autopkgtest
Control: block 902557 with -1

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

  
https://ci.debian.net/data/autopkgtest/unstable/amd64/libg/libgtk3-perl/953602/log.gz

  Undefined subroutine ::Gdk::PIXDATA_HEADER_LENGTH called at 
/<>/blib/lib/Gtk3.pm line 2119.
  # Looks like your test exited with 255 just after 162.

  [...]

  Test Summary Report
  ---
  t/overrides.t(Wstat: 65280 Tests: 162 Failed: 0)
Non-zero exit status: 255
Parse errors: Bad plan.  You planned 233 tests but ran 162.
  Files=22, Tests=843,  5 wallclock secs ( 0.18 usr  0.03 sys +  4.58 cusr  
0.46 csys =  5.25 CPU)
  Result: FAIL
 
I'm guessing this regressed with gdk-pixbuf 2.38.0+dfsg-1 or so, but I
haven't verified that (and the ci.debian.net machinery doesn't seem to
have pinpointed it yet either.)
-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: libgtk3-perl
Source-Version: 0.034-2

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

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

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libgtk3-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 14 Sep 2018 00:14:03 +0200
Source: libgtk3-perl
Binary: libgtk3-perl
Architecture: source
Version: 0.034-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 908323
Description: 
 libgtk3-perl - Perl bindings for the GTK+ graphical user interface library
Changes:
 libgtk3-perl (0.034-2) unstable; urgency=medium
 .
   * Team upload.
   * Add patch to adjust for changes in gdk-pixbuf 2.38.
 Thanks to Iain Lane for his help from the GNOME side.
 (Closes: #908323)
   * Add a versioned build dependency on gir1.2-gdkpixbuf-2.0
 (>= 2.38.0+dfsg-5~) which fixes #908673, as the second part of
 the fix for the failures in #908323.
   * Drop useless ${shlibs:Depends} from Depends.
   * Declare compliance with Debian Policy 4.2.1.
Checksums-Sha1: 
 2e771c3223f3f57397a58257cdd5d3d4068e4ffe 2364 libgtk3-perl_0.034-2.dsc
 91a498e2af238718560775f2797c79d6bbcf0981 5352 
libgtk3-perl_0.034-2.debian.tar.xz
Checksums-Sha256: 
 26342e500620b67100ee30506c4fea5ae98f20362490c5cafb419235f8fe5ed3 2364 
libgtk3-perl_0.034-2.dsc
 6ba994c284a6842f58a8406e9864c14cfd9725bb0fc924327ceae79681d260ca 5352 
libgtk3-perl_0.034-2.debian.tar.xz
Files: 
 19b2dd70ac3ab4e177896a08d7a69fe0 2364 perl optional libgtk3-perl_0.034-2.dsc
 7da9e7a8e35fc8f2509701ed270d200f 5352 perl optional 
libgtk3-perl_0.034-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAlua4ftfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgYfWQ/+LXg/5Pb+P5FtBzw1lSanTxrCCC/dbmDlyPIWk/9gzRB9rfGwNAYIOxAp
i8D9hXJXte/kLtNlTuuLv5kD7Ju4DsTtKjDmeD1YHdHO3if6oV/auL/BIRZpGoqM
BEKQlh9f/U7oOhKQwMTVNxxNMToZDIN3LKaSDMNY6T5sC5DwrsOpwILkSpqm/Lb4
XIH5mKOIOMCJYuYzTP29qajSrQwhqKdSvrolevGEZK4mIK1PFXgoBFN8Zv9STNQf
6ScSsZshcyIuSZ7Xa23cJsMpHr1YA1RxssB4pDars/gFnwpneqO6ikyFVgiOLAqn
u6R/pj7lNpqagBaR7lZnBKNyJm5AxpVbf3hWzxkrJdnGIC80apwhN5Pe9PWMyIDs
bKZdRhMTCJ8hw1/qi/RCDgOyXQsNQlP1WxJlSfKsq+kVk07DFHbjKTmUq+e65hIu
8t40LQozDnjWRLNEXCGYdRJuvLNgseBO7ekgyDlTZXuTjmRNUfy/AVe5UE1vzJ06
z2J4O85QuYNBoJAQ5ypKYdgL6bCgsTRNwTBJyDwqvIoZPxEg9wpEmbbFB3unUqys

Bug#888549: chrome-gnome-shell: Please don't use /etc/opt, it's not FHS-compliant

[Simon McVittie]

On Thu, 13 Sep 2018 at 14:57:47 -0700, Jonathan Nieder wrote:
> Jeremy Bicha wrote:
> > There is no reason this functionality cannot be offered in Debian. We
> > got complaints when we supported other browsers but not Google Chrome.
> 
> Since Google Chrome is not part of Debian, shouldn't this
> functionality be offered in contrib, not Debian?

That would be appropriate if chrome-gnome-shell *only* integrated with
Chrome, but it does the same things for Chromium and Firefox, which
are in main. The name only starts with "chrome" because that's what its
upstream developer calls it (and the binary package would probably be
webext-gnome-shell if it was packaged today).

smcv

Bug#888549: chrome-gnome-shell: Please don't use /etc/opt, it's not FHS-compliant

[Jeremy Bicha]

On Thu, Sep 13, 2018 at 6:18 PM Jonathan Nieder  wrote:
> Then I'm confused.  Why are browsers in main unable to support a
> location other than /etc/opt for this?

Because the app in /opt/ is not allowed by the FHS to store its
configuration anywhere other /etc/opt/ .

> Could there be a package in contrib that installs a symlink to
> /etc/opt, with the rest of the functionality in main?

Honestly, that would make things much worse for GNOME users who happen
to enjoy using Google Chrome than to just have the full-featured gnome
metapackage install chrome-gnome-shell with support for all major
browsers.

Unless someone proposes a working patch for something better, I'll
probably just implement the simple mkdir workaround in
chrome-gnome-shell's postrm which will satisfy piuparts.

Thanks,
Jeremy Bicha

Bug#908323: Bug #908323 in libgtk3-perl marked as pending

[gregor herrmann]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/perl-team/modules/packages/libgtk3-perl/commit/e994b7b78d10d45ed2e881693f3ff3a8906fdbe2


Add patch to adjust for changes in gdk-pixbuf 2.38.

Closes: #908323
Thanks: Iain Lane for his help from the GNOME side.



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/908323

Bug#888549: chrome-gnome-shell: Please don't use /etc/opt, it's not FHS-compliant

[Jonathan Nieder]

Jeremy Bicha wrote:
> On Thu, Sep 13, 2018 at 5:57 PM Jonathan Nieder  wrote:

>>> There is no reason this functionality cannot be offered in Debian. We
>>> got complaints when we supported other browsers but not Google Chrome.
>>
>> Since Google Chrome is not part of Debian, shouldn't this
>> functionality be offered in contrib, not Debian?
>
> No. Despite its name, chrome-gnome-shell also supports Chromium and
> Firefox, both of which are in main.

Then I'm confused.  Why are browsers in main unable to support a
location other than /etc/opt for this?

Could there be a package in contrib that installs a symlink to
/etc/opt, with the rest of the functionality in main?

Thanks,
Jonathan

Processed: Bug #908323 in libgtk3-perl marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #908323 [src:libgtk3-perl] libgtk3-perl: FTBFS: t/overrides.t failure
Added tag(s) pending.

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

Bug#908323: libgtk3-perl: FTBFS: t/overrides.t failure

[gregor herrmann]

On Thu, 13 Sep 2018 13:16:46 +0100, Iain Lane wrote:

> On Wed, Sep 12, 2018 at 11:59:49PM +0200, gregor herrmann wrote:
> > That's great news, thanks.
> > Please give us a short ping once the fixed package is available.
> I've just uploaded gdk-pixbuf 2.38.0+dfsg-5. There will be the normal
> delay, but hopefully this fixes the issue for you.

Thanks!

Indeed libgtk3-perl now seems to work with my previous patch and
gir1.2-gdkpixbuf-2.0 2.38.0+dfsg-5.
I'll upload in a second.


Cheers,
gregor

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


signature.asc
Description: Digital Signature

Bug#888549: chrome-gnome-shell: Please don't use /etc/opt, it's not FHS-compliant

[Jeremy Bicha]

Dropping the other CC's for courtesy.

On Thu, Sep 13, 2018 at 5:57 PM Jonathan Nieder  wrote:
> > There is no reason this functionality cannot be offered in Debian. We
> > got complaints when we supported other browsers but not Google Chrome.
>
> Since Google Chrome is not part of Debian, shouldn't this
> functionality be offered in contrib, not Debian?

No. Despite its name, chrome-gnome-shell also supports Chromium and
Firefox, both of which are in main.

chrome-gnome-shell is expected to be installed by default in a
full-featured GNOME installation. Requiring users to manually enable
contrib and install a package they don't know they need in order for
https://extensions.gnome.org/ to work isn't very user-friendly.

Thanks,
Jeremy Bicha

Bug#888549: Bug#888243: Bug#888549: chrome-gnome-shell: Please don't use /etc/opt, it's not FHS-compliant

[Santiago Vila]

unmerge 888546
reassign 888546 chrome-gnome-shell
thanks

With this unmerge and reassign, I'm keeping each bug where they were
originally reported.

Holger, this one (#888546) is the bug that you reported. If you think
it is really a bug in piuparts, feel free to reassign again.

[ After this I will close #888243 (the bug in base-files) ].

You can still Cc: me if you want (but other than "mkdir -p directory"
in postrm, I don't have any better idea).

Thanks.

Bug#888549: chrome-gnome-shell: Please don't use /etc/opt, it's not FHS-compliant

[Jonathan Nieder]

Hi,

Jeremy Bicha wrote:
> On Thu, Sep 13, 2018 at 4:40 PM Santiago Vila  wrote:

>> What I said is that no sane package in Debian/main should need to put
>> files directly in /etc/opt. That's an oddity, a very unorthodox thing,
>> it would be like a Debian package in main putting stuff directly in /opt.
>
> chrome-gnome-shell (in this case) is an addon for the Google Chrome
> web browser. Since Chrome installs to /opt/ (which is encouraged by
> FHS), /etc/opt/ is the only standards-compliant location for
> chrome-gnome-shell to ship the configuration files it needs to provide
> its core functionality.
>
> There is no reason this functionality cannot be offered in Debian. We
> got complaints when we supported other browsers but not Google Chrome.

Since Google Chrome is not part of Debian, shouldn't this
functionality be offered in contrib, not Debian?

[...]
>  But if
> that can't be done, I think we would be happy enough to apply a patch
> to implement the trigger workaround.

For what it's worth (especially since this is about integrating with a
non-Debian package), makes sense to me.

Thanks,
Jonathan

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

[James Cowgill]

Source: nethack
Version: 3.4.3-14
Severity: serious
X-Debbugs-CC: vch...@debian.org

Hi,

While reviewing the copyright file for the NetHack 3.6.1 upload, I
noticed that the debian directory (and its patches) are marked as under
the GPL-2.0. Unfortunately NetHack's special NGPL license is not
compatible with the GPL (both are copyleft with some conflicting terms),
so I have come to the conclusion that Debian's version of NetHack is not
distributable in binary form at all.

Thankfully I think this can be resolved fairly smoothly. If I look at
the package history, I see that before 3.4.3-14 everything was licensed
under the NGPL (except for the lisp patches). In this version, the
copyright file was changed to relicense(?!) the debian/ directory under
the GPL. Vincent and I are the only people who have claimed copyright
since that point, and I am fine with licensing my stuff under the NGPL,
so Vincent is the only person who needs asking.

Vincent, can all your changes to the nethack package be licensed under
the NGPL instead of the GPL-2.0?

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#907687: buildbot: FTBFS fix

[Santiago Vila]

On Thu, 13 Sep 2018, Robin Jarry wrote:

> Package: src:buildbot
> Version: 1.4.0-1
> 
> This should be fixed by the latest version. I forgot to mention it in
> the changelog.
> 
> However, there are still errors in the rb page:
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/buildbot.html
> 
> But I cannot manage to "reproduce" them :) The package builds fine on my
> machine (I use sbuild). I even tried building several times in a row.
> 
> Could you give me some guidance on how should I approach this?

Hmm, difficult question. I don't really know.

Usually, what works (or what people try) is to change one variable at
a time. For example, I can't reproduce this anymore using sbuild and
you say you can't either. In reproducible builds they are using
pbuilder, so one variable that you could change is to test the build
using pbuilder too.

But that was just an example, my feeling is that this is not related
to using sbuild/pbuilder but maybe something related to different CPU
speed or alike.

I would ask in the reproducible builds mailing list:

https://lists.reproducible-builds.org/listinfo/rb-general

Thanks.

Bug#888549: Bug#888243: Bug#888549: chrome-gnome-shell: Please don't use /etc/opt, it's not FHS-compliant

[Santiago Vila]

On Thu, Sep 13, 2018 at 08:59:39PM +, Holger Levsen wrote:

> a.) using /opt/etc and shipping files there is fine today and piuparts
> should not complain here

Could you briefly explain in which way the most recent FHS is more
permissive than previous releases?

If we allow using /etc/opt in Debian packages, I would like to think
that it would be only to support packages not in Debian already using
it, (like the present case), not an open door to use /etc/opt widely.

(In other words, IMHO, a warning from piuparts would still be desirable).

Thanks.

Bug#888549: chrome-gnome-shell: Please don't use /etc/opt, it's not FHS-compliant

[Santiago Vila]

On Thu, Sep 13, 2018 at 05:15:48PM -0400, Jeremy Bicha wrote:
> On Thu, Sep 13, 2018 at 4:40 PM Santiago Vila  wrote:
> > What I said is that no sane package in Debian/main should need to put
> > files directly in /etc/opt. That's an oddity, a very unorthodox thing,
> > it would be like a Debian package in main putting stuff directly in /opt.
> 
> chrome-gnome-shell (in this case) is an addon for the Google Chrome
> web browser. Since Chrome installs to /opt/ (which is encouraged by
> FHS), /etc/opt/ is the only standards-compliant location for
> chrome-gnome-shell to ship the configuration files it needs to provide
> its core functionality.
> 
> There is no reason this functionality cannot be offered in Debian. We
> got complaints when we supported other browsers but not Google Chrome.

Ok, please feel free to close the bug about FHS compliance that I filed.

> > I filed the bug because I believe it's the root of the problem you
> > have with piuparts, but in either case, feel free to disagree on that
> > one and claim FHS compliance, as far as you don't ask other people to
> > fix the consequences of putting files in /etc/opt.
> 
> I am asking for help. I have never created or dealt with noawait
> triggers so I don't know how to implement Guillem's suggested
> workaround.
> 
> We talked about this a week ago in the Debian GNOME team. I believe
> the team generally thinks it would be a lot simpler for base-files or
> a similar package to just provides these directories and stop
> encouraging sysadmins to delete directories they don't like.

Oh, I don't really encourage deleting directories, I just allow it,
that's all.

> But if
> that can't be done, I think we would be happy enough to apply a patch
> to implement the trigger workaround.

Have you considered a simple mkdir -p involved-opt-directory
in the postrm?

Thanks.

Bug#888549: chrome-gnome-shell: Please don't use /etc/opt, it's not FHS-compliant

[Jeremy Bicha]

On Thu, Sep 13, 2018 at 4:40 PM Santiago Vila  wrote:
> What I said is that no sane package in Debian/main should need to put
> files directly in /etc/opt. That's an oddity, a very unorthodox thing,
> it would be like a Debian package in main putting stuff directly in /opt.

chrome-gnome-shell (in this case) is an addon for the Google Chrome
web browser. Since Chrome installs to /opt/ (which is encouraged by
FHS), /etc/opt/ is the only standards-compliant location for
chrome-gnome-shell to ship the configuration files it needs to provide
its core functionality.

There is no reason this functionality cannot be offered in Debian. We
got complaints when we supported other browsers but not Google Chrome.

> I filed the bug because I believe it's the root of the problem you
> have with piuparts, but in either case, feel free to disagree on that
> one and claim FHS compliance, as far as you don't ask other people to
> fix the consequences of putting files in /etc/opt.

I am asking for help. I have never created or dealt with noawait
triggers so I don't know how to implement Guillem's suggested
workaround.

We talked about this a week ago in the Debian GNOME team. I believe
the team generally thinks it would be a lot simpler for base-files or
a similar package to just provides these directories and stop
encouraging sysadmins to delete directories they don't like. But if
that can't be done, I think we would be happy enough to apply a patch
to implement the trigger workaround.

Thanks,
Jeremy Bicha

Bug#908732: marked as done (libboost1.62-dev: please drop dependency on libstdc++-4.8-dev / libstdc++-dev)

[Debian Bug Tracking System]

Your message dated Thu, 13 Sep 2018 21:05:13 +
with message-id 
and subject line Bug#908732: fixed in boost1.62 1.62.0+dfsg-9
has caused the Debian Bug report #908732,
regarding libboost1.62-dev: please drop dependency on libstdc++-4.8-dev / 
libstdc++-dev
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.)


-- 
908732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908732
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libboost1.62-dev
Version: 1.62.0+dfsg-8
Severity: serious
Justification: depends on non-existing package
X-Debbugs-CC: debian...@packages.debian.org
User: debian...@packages.debian.org
Usertags: breaks

While investigating the reason why several autopkgtest fail [1, 2, 3]
when run in testing with some package from unstable we [4] found that
this is caused by libc++-8-dev being installed. I believe this is pulled
in because:

a) libc++8-dev provides libstdc++-dev (I'll file a separate bug about
that) and

b) libboost1.62-dev depends on "libstdc++-4.8-dev | libstdc++-dev"

libstdc++-4.8-dev is only available in oldstable now. Please drop the
dependency and leave the dependency on libstdc++-dev to the c++ compiler.

Paul

[1] https://ci.debian.net/packages/a/akonadi-calendar/testing/amd64/
[2] https://ci.debian.net/packages/k/kf5-kdepim-apps-libs/testing/amd64/
[3] https://ci.debian.net/packages/libk/libkf5calendarsupport/testing/amd64/
[4] https://lists.debian.org/debian-ci/2018/09/msg00010.html

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

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

Versions of packages libboost1.62-dev depends on:
ii  libstdc++-8-dev [libstdc++-dev]  8.2.0-4

libboost1.62-dev recommends no packages.

Versions of packages libboost1.62-dev suggests:
pn  libboost-atomic1.62-dev   
pn  libboost-chrono1.62-dev   
pn  libboost-context1.62-dev  
pn  libboost-coroutine1.62-dev
pn  libboost-date-time1.62-dev
pn  libboost-exception1.62-dev
pn  libboost-fiber1.62-dev
pn  libboost-filesystem1.62-dev   
pn  libboost-graph-parallel1.62-dev   
pn  libboost-graph1.62-dev
pn  libboost-iostreams1.62-dev
pn  libboost-locale1.62-dev   
pn  libboost-log1.62-dev  
pn  libboost-math1.62-dev 
pn  libboost-mpi-python1.62-dev   
pn  libboost-mpi1.62-dev  
pn  libboost-program-options1.62-dev  
pn  libboost-python1.62-dev   
pn  libboost-random1.62-dev   
pn  libboost-regex1.62-dev
pn  libboost-serialization1.62-dev
pn  libboost-signals1.62-dev  
pn  libboost-system1.62-dev   
pn  libboost-test1.62-dev 
pn  libboost-thread1.62-dev   
pn  libboost-timer1.62-dev
pn  libboost-type-erasure1.62-dev 
pn  libboost-wave1.62-dev 
pn  libboost1.62-doc  
pn  libboost1.62-tools-dev
pn  libmpfrc++-dev
pn  libntl-dev



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: boost1.62
Source-Version: 1.62.0+dfsg-9

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated boost1.62 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: Thu, 13 Sep 2018 22:40:44 +0200
Source: boost1.62
Binary: libboost1.62-dev libboost1.62-tools-dev libboost1.62-all-dev 
libboost1.62-doc libboost-atomic1.62.0 libboost-atomic1.62-dev 
libboost-chrono1.62.0 libboost-chrono1.62-dev libboost-context1.62.0 
libboost-context1.62-dev libboost-coroutine1.62.0 

Bug#892390: marked as done (boost1.62: build-depends on GCC 6)

[Debian Bug Tracking System]

Your message dated Thu, 13 Sep 2018 21:05:13 +
with message-id 
and subject line Bug#892390: fixed in boost1.62 1.62.0+dfsg-9
has caused the Debian Bug report #892390,
regarding boost1.62: build-depends on GCC 6
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.)


-- 
892390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892390
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: boost1.62
Severity: serious
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: gcc-6-rm

Hi,

boost1.62 build-depends on GCC 6. We now have GCC 7 (default) and GCC
8 in the archive, so please make your package build with a newer
compiler (preferably the default one) again, since we'd like to
remove GCC 6 from testing before the buster release.

Cheers, Emilio 
--- End Message ---
--- Begin Message ---
Source: boost1.62
Source-Version: 1.62.0+dfsg-9

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated boost1.62 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: Thu, 13 Sep 2018 22:40:44 +0200
Source: boost1.62
Binary: libboost1.62-dev libboost1.62-tools-dev libboost1.62-all-dev 
libboost1.62-doc libboost-atomic1.62.0 libboost-atomic1.62-dev 
libboost-chrono1.62.0 libboost-chrono1.62-dev libboost-context1.62.0 
libboost-context1.62-dev libboost-coroutine1.62.0 libboost-coroutine1.62-dev 
libboost-date-time1.62.0 libboost-date-time1.62-dev libboost-exception1.62-dev 
libboost-fiber1.62.0 libboost-fiber1.62-dev libboost-filesystem1.62.0 
libboost-filesystem1.62-dev libboost-graph1.62.0 libboost-graph1.62-dev 
libboost-graph-parallel1.62.0 libboost-graph-parallel1.62-dev 
libboost-iostreams1.62.0 libboost-iostreams1.62-dev libboost-locale1.62.0 
libboost-locale1.62-dev libboost-log1.62.0 libboost-log1.62-dev 
libboost-math1.62.0 libboost-math1.62-dev libboost-mpi1.62.0 
libboost-mpi1.62-dev libboost-mpi-python1.62.0 libboost-mpi-python1.62-dev 
libboost-program-options1.62.0 libboost-program-options1.62-dev 
libboost-python1.62.0 libboost-python1.62-dev libboost-random1.62.0
 libboost-random1.62-dev libboost-regex1.62.0 libboost-regex1.62-dev 
libboost-serialization1.62.0 libboost-serialization1.62-dev 
libboost-signals1.62.0 libboost-signals1.62-dev libboost-system1.62.0 
libboost-system1.62-dev libboost-test1.62.0 libboost-test1.62-dev 
libboost-thread1.62.0 libboost-thread1.62-dev libboost-timer1.62.0 
libboost-timer1.62-dev libboost-type-erasure1.62.0 
libboost-type-erasure1.62-dev libboost-wave1.62.0
 libboost-wave1.62-dev
Architecture: source
Version: 1.62.0+dfsg-9
Distribution: unstable
Urgency: medium
Maintainer: Debian Boost Team 
Changed-By: Anton Gladky 
Description:
 libboost-atomic1.62-dev - atomic data types, operations, and memory ordering 
constraints
 libboost-atomic1.62.0 - atomic data types, operations, and memory ordering 
constraints
 libboost-chrono1.62-dev - C++ representation of time duration, time point, and 
clocks
 libboost-chrono1.62.0 - C++ representation of time duration, time point, and 
clocks
 libboost-context1.62-dev - provides a sort of cooperative multitasking on a 
single thread
 libboost-context1.62.0 - provides a sort of cooperative multitasking on a 
single thread
 libboost-coroutine1.62-dev - provides a sort of cooperative multitasking on a 
single thread
 libboost-coroutine1.62.0 - provides a sort of cooperative multitasking on a 
single thread
 libboost-date-time1.62-dev - set of date-time libraries based on generic 
programming concepts
 libboost-date-time1.62.0 - set of date-time libraries based on generic 
programming concepts
 libboost-exception1.62-dev - library to help write exceptions and handlers
 libboost-fiber1.62-dev - cooperatively-scheduled micro-/userland-threads
 libboost-fiber1.62.0 - cooperatively-scheduled micro-/userland-threads
 libboost-filesystem1.62-dev - filesystem operations (portable paths, iteration 
over directories
 libboost-filesystem1.62.0 - filesystem operations (portable 

Bug#888549: Bug#888243: Bug#888549: chrome-gnome-shell: Please don't use /etc/opt, it's not FHS-compliant

[Holger Levsen]

On Thu, Sep 13, 2018 at 10:47:16PM +0200, Santiago Vila wrote:
> On Thu, Sep 13, 2018 at 08:41:49PM +, Holger Levsen wrote:
> > On Thu, Sep 13, 2018 at 10:28:18PM +0200, Santiago Vila wrote:
> 
> > > Can we reassing this already, please?
> > 
> > for those watching along:
> > - #93390 is closed.
> > - #888549 is assigned to chrome-gnome-shell
> 
> I was referring to #888243, which is not a bug in base-files.

thanks for pointing this out. I guess this is because we are cc:ing #888549 
and #888546 here, and #888546 is merged with #888243, #888549 is not merged
with anything.

Anyhow,

- #888243/#888546 is assigned to base-files and in 888243 is called " Lack of 
/opt in
  base-files causes piuparts issues for in-house packages" while 888546
  is called "gnome-chrom-shell: After purging files have disappeared:
  /etc/opt/ owned by: chrome-gnome-shell"
- #888549 is assigned to gnome-chrome-shell and is called
  "chrome-gnome-shell: Please don't use /etc/opt, it's not
  FHS-compliant"

So it seems to me, that 

a.) using /opt/etc and shipping files there is fine today and piuparts
should not complain here
b.) thus #888243/#888546 should be reassigned to piuparts
c.) #888549 should be closed or merged with #888243/#888546

Am I missing something?


on a related note, why do merged bugs have different titles?

-- 
cheers,
Holger

---
   holger@(debian|reproducible-builds|layer-acht).org
   PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C


signature.asc
Description: PGP signature

Bug#863283: marked as done (cantor-backend-r: Cantor fails to start R server/session)

[Debian Bug Tracking System]

Your message dated Thu, 13 Sep 2018 22:51:13 +0200
with message-id <20180913205111.3ppuztri24zid...@debian.org>
and subject line Re: cantor-backend-r: Cantor fails to start R server/session
has caused the Debian Bug report #863283,
regarding cantor-backend-r: Cantor fails to start R server/session
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.)


-- 
863283: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863283
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cantor-backend-r
Version: 4:16.08.3-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

When I try to select R engine with Cantor, R fails to start and Cantor
is freeze on "starting session" window.

I paste console exit:

 Start Cantor from console ---
$ cantor
dir:  "/usr/lib/x86_64-linux-gnu/qt5/plugins/cantor/backends"
Error while loading plugin:  "."
Error while loading plugin:  ".."
Creating MaximaBackend
Creating NullBackend
Creating PythonBackend
Creating RBackend
dir:  "/usr/bin/cantor/backends"
Created a CantorPart
Backend  "R"  offers extensions:  ("ScriptExtension", "AdvancedPlotExtension")
Spawning a new R session
new worksheetaccess interface
()
()
()
()
()
()
()
()
()
()
()
()
(QKeySequence("Ctrl+Shift+S"))
(QKeySequence("Ctrl+S"))
()
(QKeySequence("Ctrl+Z"))
(QKeySequence("Ctrl+Shift+Z"))
(QKeySequence("Ctrl+X"), QKeySequence("Shift+Del"))
(QKeySequence("Ctrl+C"), QKeySequence("Ctrl+Ins"))
(QKeySequence("Ctrl+V"), QKeySequence("Shift+Ins"))
(QKeySequence("Ctrl+F"))
(QKeySequence("Ctrl+R"))
(QKeySequence("F3"))
(QKeySequence("Shift+F3"))
()
(QKeySequence("Ctrl+P"))
()
(QKeySequence("Ctrl++"), QKeySequence("Ctrl+="))
(QKeySequence("Ctrl+-"))
()
()
()
()
()
()
()
(QKeySequence("Shift+Return"))
(QKeySequence("Ctrl+Return"))
()
()
()
()
(QKeySequence("Shift+Del"))
()
()
()
()
loading assistants...
dir:  "/usr/lib/x86_64-linux-gnu/qt5/plugins/cantor/assistants"
Error while loading assistant:  "."
Error while loading assistant:  ".."
plugin  "Gráficos avanzados"  requires  ("AdvancedPlotExtension")
plugin  "Gráficos avanzados"  issupported by  "R"
KXMLGUI file found at deprecated location 
("/usr/share/cantor/cantor_advancedplot_assistant.rc") -- please use 
${KXMLGUI_INSTALL_DIR} to install this file instead.
plugin  "Crear matriz"  requires  ("LinearAlgebraExtension")
plugin  "Crear matriz"  is   not   supported by  "R"
plugin  "Diferenciar"  requires  ("CalculusExtension")
plugin  "Diferenciar"  is   not   supported by  "R"
plugin  "Eigenvalores"  requires  ("LinearAlgebraExtension", "HistoryExtension")
plugin  "Eigenvalores"  is   not   supported by  "R"
plugin  "Eigenvectores"  requires  ("LinearAlgebraExtension", 
"HistoryExtension")
plugin  "Eigenvectores"  is   not   supported by  "R"
plugin  "Importar paquete"  requires  ("PackagingExtension")
plugin  "Importar paquete"  is   not   supported by  "R"
plugin  "Integrar"  requires  ("CalculusExtension")
plugin  "Integrar"  is   not   supported by  "R"
plugin  "Invertir matriz"  requires  ("LinearAlgebraExtension", 
"HistoryExtension")
plugin  "Invertir matriz"  is   not   supported by  "R"
plugin  "Plot2d"  requires  ("PlotExtension")
plugin  "Plot2d"  is   not   supported by  "R"
plugin  "Plot3d"  requires  ("PlotExtension")
plugin  "Plot3d"  is   not   supported by  "R"
plugin  "QalculatePlot"  requires  ("QalculatePlotExtension")
plugin  "QalculatePlot"  is   not   supported by  "R"
plugin  "RunScript"  requires  ("ScriptExtension")
plugin  "RunScript"  issupported by  "R"
KXMLGUI file found at deprecated location 
("/usr/share/cantor/cantor_runscript_assistant.rc") -- please use 
${KXMLGUI_INSTALL_DIR} to install this file instead.
plugin  "Resolver"  requires  ("CASExtension")
plugin  "Resolver"  is   not   supported by  "R"
dir:  "/usr/bin/cantor/assistants"
loading panel plugins for session of type  "R"
dir:  "/usr/lib/x86_64-linux-gnu/qt5/plugins/cantor/panels"
Error while loading panel:  "."
Error while loading panel:  ".."
plugin  "Ayuda"  requires  ("")
Requesting capabilities of RSession
plugin  "Ayuda"  issupported
setting session to  0x55efb3b16c80
plugin  "Gestor de variables"  requires  ("VariableManagementExtension")
plugin  "Gestor de variables"  is   not   supported
dir:  "/usr/bin/cantor/panels"
Requesting capabilities of RSession
Requesting capabilities of RSession
login
wsStatusChange 1
storing plots at  "/tmp/cantor/rserver-29302"

R version 3.4.0 (2017-04-21) -- "You Stupid Darkness"
Copyright (C) 2017 The R Foundation for Statistical Computing
Platform: x86_64-pc-linux-gnu (64-bit)

Bug#908670: libundead: ftbfs on armhf

[Andreas Tille]

Hi Peter,

thanks a lot for your analysis.

On Thu, Sep 13, 2018 at 01:27:58PM +0100, peter green wrote:
> 4. Simply get libundead removed on armhf/raspbian. libundead seems to only 
> have two reverse build-dependencies neither of which has ever successfully 
> built on armhf. libbiod previously failed with a testsuite failure (probablly 
> related to the miscompilation discussed above) and now fails with the same 
> error that libundead does. sambamba is blocked by a dependency on libbiod

I think this solution makes the least effort for all involved parties
and is in line with the practical use of this package on armhf.

Kind regards

 Andreas.

-- 
http://fam-tille.de

Bug#888549: Bug#888243: Bug#888549: chrome-gnome-shell: Please don't use /etc/opt, it's not FHS-compliant

[Santiago Vila]

On Thu, Sep 13, 2018 at 08:41:49PM +, Holger Levsen wrote:
> On Thu, Sep 13, 2018 at 10:28:18PM +0200, Santiago Vila wrote:

> > Can we reassing this already, please?
> 
> for those watching along:
> - #93390 is closed.
> - #888549 is assigned to chrome-gnome-shell

I was referring to #888243, which is not a bug in base-files.

Thanks.

Bug#851771: php-gettext: CVE-2016-6175

[Ivo De Decker]

Hi,

On Wed, Jan 18, 2017 at 05:23:43PM +0100, Salvatore Bonaccorso wrote:
> the following vulnerability was published for php-gettext.
> 
> CVE-2016-6175[0]:
> Use of eval too unrestrictive 

The packages using php-gettext in buster are:

cacti: cacti
kopano-webapp: kopano-webapp-common
phpmyadmin: phpmyadmin
tt-rss: tt-rss

Only phpmyadmin is a key package.

For phpmyadmin, php-gettext was replaced by motranslator
(https://github.com/phpmyadmin/motranslator/) in 4.7. Buster currently has
4.6, but a newer version might be uploaded at some point (see
https://bugs.debian.org/879741).

Cheers,

Ivo

Bug#899842: marked as done (fcitx-table-other: Invalid maintainer address pkg-ime-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Thu, 13 Sep 2018 20:42:27 +
with message-id 
and subject line Bug#899842: fixed in fcitx-table-other 0.2.4-2
has caused the Debian Bug report #899842,
regarding fcitx-table-other: Invalid maintainer address 
pkg-ime-de...@lists.alioth.debian.org
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.)


-- 
899842: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899842
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:fcitx-table-other
Version: 0.2.4-1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of fcitx-table-other,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package fcitx-table-other since the list address
pkg-ime-de...@lists.alioth.debian.org used in the Maintainer: field was
not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-ime-de...@lists.alioth.debian.org is 68.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: fcitx-table-other
Source-Version: 0.2.4-2

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated fcitx-table-other 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: Thu, 13 Sep 2018 15:02:31 -0400
Source: fcitx-table-other
Binary: fcitx-table-amharic fcitx-table-arabic fcitx-table-cns11643 
fcitx-table-compose fcitx-table-emoji fcitx-table-ipa-x-sampa fcitx-table-latex 
fcitx-table-malayalam-phonetic fcitx-table-rustrad fcitx-table-tamil-remington 
fcitx-table-thai fcitx-table-translit fcitx-table-translit-ua fcitx-table-viqr 
fcitx-table-yawerty
Architecture: source
Version: 0.2.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Input Method Team 
Changed-By: Boyuan Yang 
Description:
 fcitx-table-amharic - Flexible Input Method Framework - Amharic table
 fcitx-table-arabic - Flexible Input Method Framework - Arabic table
 fcitx-table-cns11643 - Flexible Input Method Framework - Cns11643 table
 fcitx-table-compose - Flexible Input Method Framework - Compose table
 fcitx-table-emoji - Flexible Input Method Framework - Emoji table
 fcitx-table-ipa-x-sampa - Flexible Input Method Framework - IPA-X-SAMPA table
 fcitx-table-latex - Flexible Input Method Framework - LaTeX table
 fcitx-table-malayalam-phonetic - Flexible Input Method Framework - Malayalam 
phonetic table
 fcitx-table-rustrad - Flexible Input Method Framework - Rustrad table
 

Bug#888549: chrome-gnome-shell: Please don't use /etc/opt, it's not FHS-compliant

[Santiago Vila]

On Thu, Sep 13, 2018 at 01:38:19PM -0400, Jeremy Bicha wrote:
> On Thu, Sep 13, 2018 at 1:31 PM Santiago Vila  wrote:
> > Please reassign. This is not a bug in base-files.
> 
> Let's specifically talk about https://bugs.debian.org/888549 . You
> opened that bug claiming that chrome-gnome-shell wasn't compliant with
> FHS but it is compliant.

What I said is that no sane package in Debian/main should need to put
files directly in /etc/opt. That's an oddity, a very unorthodox thing,
it would be like a Debian package in main putting stuff directly in /opt.

I filed the bug because I believe it's the root of the problem you
have with piuparts, but in either case, feel free to disagree on that
one and claim FHS compliance, as far as you don't ask other people to
fix the consequences of putting files in /etc/opt.

Thanks.

Bug#888549: Bug#888243: Bug#888549: chrome-gnome-shell: Please don't use /etc/opt, it's not FHS-compliant

[Holger Levsen]

On Thu, Sep 13, 2018 at 10:28:18PM +0200, Santiago Vila wrote:
> On Thu, Sep 13, 2018 at 01:23:32PM -0400, Jeremy Bicha wrote:
> 
> > References
> > 
> > [...]
> > - https://bugs.debian.org/93390
> 
> Are you serious?
[...]
> Can we reassing this already, please?

for those watching along:
- #93390 is closed.
- #888549 is assigned to chrome-gnome-shell

Please let's all calm down and find the right technical solution for
#888549, which is titled "chrome-gnome-shell: Please don't use /etc/opt,
it's not FHS-compliant" which doesnt seem to be correct anymore with
todays version of FHS which debian-policy mandates.

So, close #888549 or retitle to what?


-- 
cheers,
Holger

---
   holger@(debian|reproducible-builds|layer-acht).org
   PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C


signature.asc
Description: PGP signature

Bug#908737: marked as done (libboost1.67-dev: drop dependency on libstdc++(-4.8|)-dev)

[Debian Bug Tracking System]

Your message dated Thu, 13 Sep 2018 20:40:59 +
with message-id 
and subject line Bug#908737: fixed in boost1.67 1.67.0-7
has caused the Debian Bug report #908737,
regarding libboost1.67-dev: drop dependency on libstdc++(-4.8|)-dev
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.)


-- 
908737: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908737
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libboost1.62-dev
Version: 1.62.0+dfsg-8
Severity: serious
Justification: depends on non-existing package
X-Debbugs-CC: debian...@packages.debian.org
User: debian...@packages.debian.org
Usertags: breaks

While investigating the reason why several autopkgtest fail [1, 2, 3]
when run in testing with some package from unstable we [4] found that
this is caused by libc++-8-dev being installed. I believe this is pulled
in because:

a) libc++8-dev provides libstdc++-dev (I'll file a separate bug about
that) and

b) libboost1.62-dev depends on "libstdc++-4.8-dev | libstdc++-dev"

libstdc++-4.8-dev is only available in oldstable now. Please drop the
dependency and leave the dependency on libstdc++-dev to the c++ compiler.

Paul

[1] https://ci.debian.net/packages/a/akonadi-calendar/testing/amd64/
[2] https://ci.debian.net/packages/k/kf5-kdepim-apps-libs/testing/amd64/
[3] https://ci.debian.net/packages/libk/libkf5calendarsupport/testing/amd64/
[4] https://lists.debian.org/debian-ci/2018/09/msg00010.html

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

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

Versions of packages libboost1.62-dev depends on:
ii  libstdc++-8-dev [libstdc++-dev]  8.2.0-4

libboost1.62-dev recommends no packages.

Versions of packages libboost1.62-dev suggests:
pn  libboost-atomic1.62-dev   
pn  libboost-chrono1.62-dev   
pn  libboost-context1.62-dev  
pn  libboost-coroutine1.62-dev
pn  libboost-date-time1.62-dev
pn  libboost-exception1.62-dev
pn  libboost-fiber1.62-dev
pn  libboost-filesystem1.62-dev   
pn  libboost-graph-parallel1.62-dev   
pn  libboost-graph1.62-dev
pn  libboost-iostreams1.62-dev
pn  libboost-locale1.62-dev   
pn  libboost-log1.62-dev  
pn  libboost-math1.62-dev 
pn  libboost-mpi-python1.62-dev   
pn  libboost-mpi1.62-dev  
pn  libboost-program-options1.62-dev  
pn  libboost-python1.62-dev   
pn  libboost-random1.62-dev   
pn  libboost-regex1.62-dev
pn  libboost-serialization1.62-dev
pn  libboost-signals1.62-dev  
pn  libboost-system1.62-dev   
pn  libboost-test1.62-dev 
pn  libboost-thread1.62-dev   
pn  libboost-timer1.62-dev
pn  libboost-type-erasure1.62-dev 
pn  libboost-wave1.62-dev 
pn  libboost1.62-doc  
pn  libboost1.62-tools-dev
pn  libmpfrc++-dev
pn  libntl-dev



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: boost1.67
Source-Version: 1.67.0-7

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated boost1.67 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: Thu, 13 Sep 2018 20:57:27 +0200
Source: boost1.67
Binary: libboost1.67-dev libboost1.67-tools-dev libboost1.67-all-dev 
libboost1.67-doc libboost-atomic1.67.0 libboost-atomic1.67-dev 
libboost-chrono1.67.0 libboost-chrono1.67-dev libboost-container1.67.0 
libboost-container1.67-dev libboost-context1.67.0 libboost-context1.67-dev 

Bug#888549: Bug#888243: Bug#888549: chrome-gnome-shell: Please don't use /etc/opt, it's not FHS-compliant

[Santiago Vila]

On Thu, Sep 13, 2018 at 01:23:32PM -0400, Jeremy Bicha wrote:

> References
> 
> [...]
> - https://bugs.debian.org/93390

Are you serious?

Such bug was in 2001-04-10, but in 2001-11-09 I modified base-files
to provide the opt directories, this is from the changelog:

base-files (2.2.14) unstable; urgency=low

  * Created /opt, /etc/opt and /var/opt in the first install.
They are mentioned in FHS 2.1 and required in FHS 2.2 (Closes: #118505).

You can check that those directories exist in any newly installed Debian system.

Creating directories in the postinst is a completely acceptable way to
provide FHS compliance, and in fact, it is sometimes necessary to
accomodate for mount points and similar things, see this changelog
entry for example:

base-files (7.7) unstable; urgency=low

  * The directory /mnt is not included inside base-files.deb anymore.
Instead, it is created by postinst the very first time base-files
is installed (by debootstrap), or when upgrading from an earlier
base-files version. This should make the usual upgrade at every point
release to work even if /mnt is a stale mount point. Closes: #763405.


So, to summarize again: No, this is not a bug in base-files. I'm very
sorry that this implementation detail causes trouble for you, but I
firmly believe that whatever problem you have with it does not require a
modification in base-files to be solved, or a restriction in the freedom
to remove a directory when you don't need it.

Can we reassing this already, please?

Thanks.

Bug#908580: ibus-table-createdb fails with nonexisting $HOME

[Adrian Bunk]

On Thu, Sep 13, 2018 at 02:39:58PM -0400, Boyuan Yang wrote:
> I'm wondering why reproducible-builds project has to use a nonexistant $HOME 
> value. It seems to be reasonable for a program to function correctly only 
> with 
> a valid (existing) $HOME directory available.

https://www.debian.org/doc/debian-policy/ch-opersys.html#non-existent-home-directories

> What do you think would be the best solution? Should we export $HOME as /tmp 
> explicitly prior to the build?

Ideally it should work without requiring $HOME to exist.

HOME=/tmp opens a bunch of potential security and other problems on 
machines with more than one user - sorry if my example was misleading 
for that.


< plugwash> basically there are three bits to "home inside the builddir"
< plugwash> 1. "export HOME :=$(CURDIR)/fakehome" at the top-level of the rules 
file.
< plugwash> 2. "mkdir fakehome" at the start of the build target
< plugwash> 3. "rm -rf fakehome" at the end of the clean target
< plugwash> exactly how you do 2 and 3 will depend on what style of rules file 
the package uses.


> Regards,
> Boyuan Yang

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#908775: reportbug crash

[Sandro Tosi]

please upgrade python3-simplesoap to the latest version

On Thu, Sep 13, 2018 at 3:45 PM Alice Vixie  wrote:

> Package: reportbug
> Version: 7.5.0
>
> When I invoke `reportbug' without arguments from an ordinary shell
> prompt it correctly opens the dialog.
>
> I press Next and I am asked to enter the name of the package to report.
>
> I answer: linux-image-4.17.0-1-amd64 and press Next.
>
> It says Checking for new version at madison, then some very short message I 
> can't even read and then I am confronted with a message
>
> Traceback (most recent call last):
>
>   File "/usr/lib/python3/dist-packages/reportbug/ui/gtk2_ui.py", line 1049, 
> in sync_pre_operation
>
> http_proxy=http_proxy, archived=archived, source=source)
>
>   File "/usr/lib/python3/dist-packages/reportbug/debbugs.py", line 1072, in 
> get_reports
>
> bugs = debianbts.get_bugs(pkg_filter, package)
>
>   File "/usr/lib/python3/dist-packages/debianbts/debianbts.py", line 410, in 
> get_bugs
>
> reply = soap_client.call('get_bugs', method_el)
>
>   File "/usr/lib/python3/dist-packages/pysimplesoap/client.py", line 260, in 
> call
>
> self.xml_response = self.send(method, self.xml_request)
>
>   File "/usr/lib/python3/dist-packages/pysimplesoap/client.py", line 313, in 
> send
>
> location, http_method, body=xml, headers=headers)
>
>   File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1395, in 
> request
>
> self.disable_ssl_certificate_validation)
>
>   File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 978, in 
> __init__
>
> timeout=timeout, context=context)
>
> TypeError: fixer() missing 1 required positional argument: 'check_hostname'
>
>
> During handling of the above exception, another exception occurred:
>
>
> Traceback (most recent call last):
>
>   File "/usr/bin/reportbug", line 2266, in 
>
> main()
>
>   File "/usr/bin/reportbug", line 1109, in main
>
> return iface.user_interface()
>
>   File "/usr/bin/reportbug", line 1722, in user_interface
>
> latest_first=self.options.latest_first)
>
>   File "/usr/lib/python3/dist-packages/reportbug/ui/gtk2_ui.py", line 1763, 
> in func
>
> args, kwargs = op.sync_pre_operation(*args, **kwargs)
>
>   File "/usr/lib/python3/dist-packages/reportbug/ui/gtk2_ui.py", line 1051, 
> in sync_pre_operation
>
> error_dialog("Unable to connect to %s BTS." % sysinfo['name'])
>
>   File "/usr/lib/python3/dist-packages/reportbug/ui/gtk2_ui.py", line 137, in 
> error_dialog
>
> _assert_context(ui_context)
>
>   File "/usr/lib/python3/dist-packages/reportbug/ui/gtk2_ui.py", line 92, in 
> _assert_context
>
> (_describe_context(really), _describe_context(expected)))
>
> AssertionError: Function should be called in  thread> but was called in 
>
>
>
>
> vixie@x201:~$ cat /etc/issue
>
> Debian GNU/Linux buster/sid \n \l
>
> vixie@x201:~$ uname -a
>
> Linux x201 4.17.0-1-amd64 #1 SMP Debian 4.17.8-1 (2018-07-20) x86_64 GNU/Linux
>
> vixie@x201:~$ hostname
>
> x201
>
> I do have network connectivity.
>
>

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

Processed: forcibly merging 908087 908775

[Debian Bug Tracking System]

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

> forcemerge 908087 908775
Bug #908087 [reportbug] reportbug: Fails with: TypeError: fixer() missing 1 
required positional argument: 'check_hostname'
Bug #908131 [reportbug] reportbug: TypeError("fixer() missing 1 required 
positional argument… (plus some warnings)
Bug #908578 [reportbug] reportbug: crash on requesting madison
Bug #908619 [reportbug] reportbug: Crash when reporting bug: TypeError: fixer() 
missing argument: 'check_hostname'
Bug #908775 [reportbug] reportbug crash
Severity set to 'grave' from 'normal'
908775 was not blocked by any bugs.
908775 was not blocking any bugs.
Added blocking bug(s) of 908775: 906127
Bug #908131 [reportbug] reportbug: TypeError("fixer() missing 1 required 
positional argument… (plus some warnings)
Bug #908578 [reportbug] reportbug: crash on requesting madison
Bug #908619 [reportbug] reportbug: Crash when reporting bug: TypeError: fixer() 
missing argument: 'check_hostname'
Merged 908087 908131 908578 908619 908775
> thanks
Stopping processing here.

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

Processed: found 908682 in 1:2.12+dfsg-3

[Debian Bug Tracking System]

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

> found 908682 1:2.12+dfsg-3
Bug #908682 [src:qemu] qemu: (CVE-2018-3639 SSB) qemu should be able to pass 
the ssbd cpu flag
Marked as found in versions qemu/1:2.12+dfsg-3.
> thanks
Stopping processing here.

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

Processed: found 908682 in 1:2.8+dfsg-6

[Debian Bug Tracking System]

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

> found 908682 1:2.8+dfsg-6
Bug #908682 [src:qemu] qemu: (CVE-2018-3639 SSB) qemu should be able to pass 
the ssbd cpu flag
Marked as found in versions qemu/1:2.8+dfsg-6.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:curl

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:curl
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #908327 (http://bugs.debian.org/908327)
> # Bug title: curl: CVE-2018-14618: NTLM password overflow via integer overflow
> #  * https://github.com/curl/curl/issues/2756
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 908327 + fixed-upstream
Bug #908327 [src:curl] curl: CVE-2018-14618: NTLM password overflow via integer 
overflow
Added tag(s) fixed-upstream.
> usertags 908327 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: tagging 908682

[Debian Bug Tracking System]

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

> tags 908682 + upstream
Bug #908682 [src:qemu] qemu: (CVE-2018-3639 SSB) qemu should be able to pass 
the ssbd cpu flag
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package cppo

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package cppo
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #907431 (http://bugs.debian.org/907431)
> # Bug title: cppo's testsuite fails on arm{el,hf} and ppc64el
> #  * https://github.com/mjambon/cppo/issues/61
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 907431 + fixed-upstream
Bug #907431 [cppo] cppo's testsuite fails on arm{el,hf} and ppc64el
Added tag(s) fixed-upstream.
> usertags 907431 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 907431 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package docker.io

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package docker.io
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #908057 (http://bugs.debian.org/908057)
> # Bug title: docker.io: CVE-2018-10892
> #  * https://github.com/moby/moby/pull/37404
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 908057 + fixed-upstream
Bug #908057 [docker.io] docker.io: CVE-2018-10892
Added tag(s) fixed-upstream.
> usertags 908057 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#908580: ibus-table-createdb fails with nonexisting $HOME

[Boyuan Yang]

I'm wondering why reproducible-builds project has to use a nonexistant $HOME 
value. It seems to be reasonable for a program to function correctly only with 
a valid (existing) $HOME directory available.

What do you think would be the best solution? Should we export $HOME as /tmp 
explicitly prior to the build?

--
Regards,
Boyuan Yang

在 2018年9月11日星期二 EDT 上午9:53:39，您写道：
> Package: ibus-table
> Version: 1.9.21-1
> Severity: serious
> Control: affects -1 src:ibus-table-others
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ibus-tabl
> e-others.html
> 
> ...
> /usr/bin/ibus-table-createdb  -n compose.db -s compose.txt
> Traceback (most recent call last):
>   File "/usr/share/ibus-table/engine/tabcreatedb.py", line 455, in 
> main()
>   File "/usr/share/ibus-table/engine/tabcreatedb.py", line 175, in main
> create_database=True)
>   File "/usr/share/ibus-table/engine/tabsqlitedb.py", line 262, in __init__
> import ibus_table_location
>   File "/usr/share/ibus-table/engine/ibus_table_location.py", line 102, in
>  __module_init = __ModuleInitializer()
>   File "/usr/share/ibus-table/engine/ibus_table_location.py", line 96, in
> __init__ _init()
>   File "/usr/share/ibus-table/engine/ibus_table_location.py", line 76, in
> _init os.makedirs(IBUS_TABLE_LOCATION['data_home'])
>   File "/usr/lib/python3.6/os.py", line 210, in makedirs
> makedirs(head, mode, exist_ok)
>   File "/usr/lib/python3.6/os.py", line 210, in makedirs
> makedirs(head, mode, exist_ok)
>   File "/usr/lib/python3.6/os.py", line 210, in makedirs
> makedirs(head, mode, exist_ok)
>   File "/usr/lib/python3.6/os.py", line 220, in makedirs
> mkdir(name, mode)
> PermissionError: [Errno 13] Permission denied: '/nonexistent'
> make[2]: *** [Makefile:519: compose.db] Error 1
> 
> 
> This can be reproduced with:
> 
> # works
> $ HOME=/tmp /usr/bin/ibus-table-createdb -n compose.db -s compose.txt
> 
> # fails
> $ HOME=/doesnotexist /usr/bin/ibus-table-createdb -n compose.db -s
> compose.txt



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

Processed: Already forwarded by maintainer before this bug was even filed

[Debian Bug Tracking System]

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

> forwarded 908696 https://lab.civicrm.org/dev/core/issues/270
Bug #908696 [civicrm-common] civicrm-common: please remove dependency on 
libjs-swfobject, which is going away
Set Bug forwarded-to-address to 'https://lab.civicrm.org/dev/core/issues/270'.
>
End of message, stopping processing here.

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

Bug#907687: marked as done (buildbot: FTBFS (buildbot_worker.test.unit.test_runprocess.TestRunProcess.testPipeString fails))

[Debian Bug Tracking System]

Your message dated Thu, 13 Sep 2018 19:57:52 +0200
with message-id <20180913175751.2iofpy63yirkt...@jarry.cc>
and subject line buildbot: FTBFS fix
has caused the Debian Bug report #907687,
regarding buildbot: FTBFS 
(buildbot_worker.test.unit.test_runprocess.TestRunProcess.testPipeString fails)
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.)


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

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with python3,bash-completion,sphinxdoc
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure --buildsystem=pybuild --sourcedirectory=master \
--package=python3-buildbot -- --name=buildbot
pybuild --configure -i python{version} -p 3.6 --name=buildbot --dir 
master
I: pybuild base:217: python3.6 setup.py config 
running config
/usr/lib/python3/dist-packages/setuptools/dist.py:398: UserWarning: Normalizing 
'1.2.0-1' to '1.2.0.post1'
  normalized_version,
dh_auto_configure --buildsystem=pybuild --sourcedirectory=worker \

[... snipped ...]

===
[SKIPPED]
Flaky test (https://github.com/buildbot/buildbot/issues/3936) - set 
$RUN_FLAKY_TESTS to run anyway

buildbot.test.unit.test_worker_ec2.TestEC2LatentWorker.test_get_image_owners
===
[SKIPPED]
ViewBuildsEndpointMatcher is not implemented yet

buildbot.test.unit.test_www_endpointmatchers.ViewBuildsEndpointMatcherBranch.test_build
===
[SKIPPED]
not a win32 platform

buildbot_worker.test.unit.test_runprocess.TestRunProcess.testPipeString
===
[ERROR]
Traceback (most recent call last):
  File 
"/<>/debian/python3-buildbot/usr/lib/python3.6/dist-packages/buildbot/process/properties.py",
 line 459, in getRenderingFor
rv = yield build.render(value[index])
  File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 1418, 
in _inlineCallbacks
result = g.send(result)
  File 
"/<>/debian/python3-buildbot/usr/lib/python3.6/dist-packages/buildbot/process/properties.py",
 line 495, in getRenderingFor
raise KeyError(error_message)
builtins.KeyError: "secrets service not started, need to configure 
SecretManager in c['services'] to use 'secrets'in Interpolate"

buildbot.test.unit.test_master.StartupAndReconfig.test_reconfig
---
Ran 5510 tests in 59.016s

FAILED (skips=303, errors=1, successes=5206)
Exception ignored in: 
RuntimeError: generator ignored GeneratorExit
Exception ignored in: 
RuntimeError: generator ignored GeneratorExit
Exception ignored in: 
RuntimeError: generator ignored GeneratorExit
Exception ignored in: <_io.FileIO name='/dev/null' mode='rb' closefd=True>
ResourceWarning: unclosed file <_io.TextIOWrapper name='/dev/null' mode='r' 
encoding='UTF-8'>
E: pybuild pybuild:338: test: plugin custom failed with: exit code=1: 
PYTHONPATH=/<>/pkg:/<>/debian/python3-buildbot//usr/lib/python3.6/dist-packages:/<>/debian/python3-buildbot-worker//usr/lib/python3.6/dist-packages
 LC_ALL=C.UTF-8 trial3 --reporter=text buildbot.test buildbot_worker.test
dh_auto_test: pybuild --test -i python{version} -p 3.6 --system=custom 
"--test-args=PYTHONPATH=/<>/pkg:/<>/debian/python3-buildbot/{install_dir}:/<>/debian/python3-buildbot-worker/{install_dir}
 LC_ALL=C.UTF-8 trial3 --reporter=text buildbot.test buildbot_worker.test" 
returned exit code 13
make[1]: *** [debian/rules:31: override_dh_auto_install] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:55: binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


The build was made in my autobuilder with "dpkg-buildpackage -A"
but it also fails here:

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

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

If this is really a bug in one of the build-depends, 

Bug#888549: chrome-gnome-shell: Please don't use /etc/opt, it's not FHS-compliant

[Jeremy Bicha]

On Thu, Sep 13, 2018 at 1:31 PM Santiago Vila  wrote:
> Please reassign. This is not a bug in base-files.

Let's specifically talk about https://bugs.debian.org/888549 . You
opened that bug claiming that chrome-gnome-shell wasn't compliant with
FHS but it is compliant.

> We pass the FHS compliance tests, for newly installed systems, which is
> where the tests should be performed, base-files *provides* those
> directories, but if you remove them (either directly or indirectly),
> then it is your duty to restore them, not mine.

Respectfully, chrome-gnome-shell isn't removing anything. The
pipuparts issue preventing chrome-gnome-shell from migrating to
Testing is a bug caused by your unusual interpretation of the word
"required" in FHS.

Thanks,
Jeremy Bicha

Bug#888549: chrome-gnome-shell: Please don't use /etc/opt, it's not FHS-compliant

[Santiago Vila]

On Thu, Sep 13, 2018 at 01:23:32PM -0400, Jeremy Bicha wrote:
> Santiago, can we revisit this?
> 
> Debian Policy § 9.1.1 since 4.1.5.0 requires compliance with FHS 3.0
> and I don't see any listed exception for /etc/opt/ .
> 
> FHS 3.0 § 3.7.2 requires /etc/opt/ . (§ 3.2 also requires /opt)

We pass the FHS compliance tests, for newly installed systems, which is
where the tests should be performed, base-files *provides* those
directories, but if you remove them (either directly or indirectly),
then it is your duty to restore them, not mine.

Please reassign. This is not a bug in base-files.

Thanks.

Bug#888549: chrome-gnome-shell: Please don't use /etc/opt, it's not FHS-compliant

[Jeremy Bicha]

Santiago, can we revisit this?

Debian Policy § 9.1.1 since 4.1.5.0 requires compliance with FHS 3.0
and I don't see any listed exception for /etc/opt/ .

FHS 3.0 § 3.7.2 requires /etc/opt/ . (§ 3.2 also requires /opt)

References

- https://www.debian.org/doc/debian-policy/ch-opersys.html#file-system-structure
- 
https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.html#etcHostspecificSystemConfiguration
- https://bugs.debian.org/93390

Thanks,
Jeremy Bicha

Bug#865851: Bug #865851 in drf-extensions marked as pending

[Michael Fladischer]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/modules/drf-extensions/commit/902c253df920908f2b01016a7f682de7364bc332


New upstream release (Closes: #865851).



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/865851

Processed: Bug #865851 in drf-extensions marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #865851 [src:drf-extensions] drf-extensions FTBFS with Django 1.11
Added tag(s) pending.

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

Processed (with 1 error): Xen things

[Debian Bug Tracking System]

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

> tags 853710 + pending
Bug #853710 [src:xen] xen: ftbfs with GCC-7
Added tag(s) pending.
> tags 852545 + pending
Bug #852545 [xen] Config file in xen-hypervisor package likely causes problems 
on upgrade
Added tag(s) pending.
> tags 879751 + pending
Failed to alter tags of Bug 879751: Not altering archived bugs; see unarchive.

> tags 858962 + pending
Bug #858962 [src:xen] Request: enable OVMF at build time in 4.8 as it does not 
require non-free anymore
Added tag(s) pending.
>
End of message, stopping processing here.

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

Processed: RM: libjs-swfupload -- RoQA; obsolete

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 905602
Bug #908768 [ftp.debian.org] RM: libjs-swfupload -- RoQA; obsolete
908768 was not blocked by any bugs.
908768 was not blocking any bugs.
Added blocking bug(s) of 908768: 905602

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

Bug#908766: liblog-dispatch-message-passing-perl: FTBFS (test failures) with liblog-dispatch-perl 2.68-1

[gregor herrmann]

Source: liblog-dispatch-message-passing-perl
Version: 0.009-3
Severity: serious
Tags: upstream ftbfs sid buster
Justification: fails to build from source

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

As first seen on ci.debian.net, liblog-dispatch-perl 2.68-1 breaks
liblog-dispatch-message-passing-perl('s test suite):


t/00_compile.t .. 
ok 1 - use Log::Dispatch::Message::Passing;
1..1
ok
t/basic.t ... 
ok 1
not ok 2

#   Failed test at t/basic.t line 23.
# Structures begin differing at:
#  $got->[0]{name} = Does not exist
# $expected->[0]{name} = 'myapp_logstash'
1..2
# Looks like you failed 1 test of 2.
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/2 subtests 
t/log_message_structured.t .. skipped: Broken currently

Test Summary Report
- ---
t/basic.t (Wstat: 256 Tests: 2 Failed: 1)
  Failed test:  2
  Non-zero exit status: 1
Files=3, Tests=3,  0 wallclock secs ( 0.02 usr  0.01 sys +  0.36 cusr  0.05 
csys =  0.44 CPU)
Result: FAIL


I'm not sure if the changes in Log::Dispatch::Output 2.68 are (not
only the cause but also) the actual problem, or if
Log::Dispatch::Message::Passing somehow needs to adapt ...
Hence not forwarding upstream yet; maybe someone gets a clearer
picture of this issue?


Cheers,
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAluaegxfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgYTWg//bhffDM2qSgZCCyaoV3x24l93LS4JL0O/Nf9nI1y4jdLSHxQtKpWmEp1y
T0umYjUUvoDBXUV3kpyxF0xSd3qFsXz9jNts26R4/tmbClF5bqjHDsRrgxdE8J0t
Ejb4gQW1s9icCrYVdAY2GQ6q8H0kXfJaophgfVJZiTwHiqvbMlKTbBbkAIvqoyRQ
K86CqjzjMbG1bxYR4JDR2rz1SQQVFd1MFA3YU1LhFT/g5zC8LwDwE3CpfJQaWirP
3pUb58ScLf+C2VT1UIOwIFS0JR/QychFkwDkRBlHAuLJimXN2wPeGYu3oMoMXkFj
Efw1q3MErjEKaNMWYj1BnOR1iga/5jSxtZc9B5aSw567A5Mcutt6ck/6khJqVWaf
hmguTekFij14cbqke5Dovm3kX3Sl3VkFeaLXpgR0TnbTikGgSeY1XLh8PllaaO09
ssERnA9XqK0UmIhaLwy9lP5B08fvC9B9M3g/3Rt+lYIcvzhvLHDfAvba2gweYseb
AK5YFUWsJNFtKGv56Nk6NkjH0TW3iQiv8A0kqO9I3AaXbKELIyWlv6ETbwfC5vJV
DAB6CM0yzRXhyYBKhmPfZuyqPZpPeGPaEaup1okwNA45X9R0/2WwWsfRI3mDwS0j
sGG4Beszwa4O96wBZXoaeBhFykF2wqdvDENcjZSLP6XU7HgKfwM=
=msdK
-END PGP SIGNATURE-

Bug#906969: marked as done (cb2bib: FTBFS in buster/sid (invalid use of incomplete type 'class QAction'))

[Debian Bug Tracking System]

Your message dated Thu, 13 Sep 2018 14:49:13 +
with message-id 
and subject line Bug#906969: fixed in cb2bib 1.9.9-1
has caused the Debian Bug report #906969,
regarding cb2bib: FTBFS in buster/sid (invalid use of incomplete type 'class 
QAction')
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.)


-- 
906969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906969
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:cb2bib
Version: 1.9.7-2
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-arch
dh build-arch --parallel
   dh_update_autotools_config -a -O--parallel
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
mkdir -p /<>/debian/build && \
cp -rpf c2bscripts  c2btools  cb2bib.pro  cb2bib.rc data src testPDFImport xpdf 
/<>/debian/build && \
cd /<>/debian/build && \
qtchooser -run-tool=qmake -qt=5 ../../
Info: creating stash file /<>/debian/build/.qmake.stash
make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
convert src/icons/cb2bib.png -resize 32x32 debian/cb2bib.xpm

[... snipped ...]

/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:228:43: error: no type named 
'Object' in 'struct QtPrivate::FunctionPointer'
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:260:13: note: candidate: 
'template static typename 
std::enable_if<((int)(QtPrivate::FunctionPointer::ArgumentCount) >= 0), 
QMetaObject::Connection>::type QObject::connect(const typename 
QtPrivate::FunctionPointer::Object*, Func1, Func2)'
 connect(const typename QtPrivate::FunctionPointer::Object 
*sender, Func1 signal, Func2 slot)
 ^~~
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:260:13: note:   template 
argument deduction/substitution failed:
../../../src/findDialog.cpp:47:80: note:   candidate expects 3 arguments, 4 
provided
 connect(findPreviousAction, SIGNAL(triggered()), this, 
SLOT(findPrevious()));

^
In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qvariant.h:51,
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/QVariant:1,
 from ./ui_findDialog.h:12,
 from ../../../src/findDialog.h:12,
 from ../../../src/findDialog.cpp:9:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:269:13: note: candidate: 
'template static typename 
std::enable_if<(((int)(QtPrivate::FunctionPointer::ArgumentCount) >= 0) 
&& (! QtPrivate::FunctionPointer::IsPointerToMemberFunction)), 
QMetaObject::Connection>::type QObject::connect(const typename 
QtPrivate::FunctionPointer::Object*, Func1, const QObject*, Func2, 
Qt::ConnectionType)'
 connect(const typename QtPrivate::FunctionPointer::Object 
*sender, Func1 signal, const QObject *context, Func2 slot,
 ^~~
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:269:13: note:   template 
argument deduction/substitution failed:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h: In substitution of 
'template static typename 
std::enable_if<(((int)(QtPrivate::FunctionPointer::ArgumentCount) >= 0) 
&& (! QtPrivate::FunctionPointer::IsPointerToMemberFunction)), 
QMetaObject::Connection>::type QObject::connect(const typename 
QtPrivate::FunctionPointer::Object*, Func1, const QObject*, Func2, 
Qt::ConnectionType) [with Func1 = const char*; Func2 = const char*]':
../../../src/findDialog.cpp:47:80:   required from here
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:269:13: error: no type named 
'type' in 'struct std::enable_if'
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:300:13: note: candidate: 
'template static typename 
std::enable_if<(QtPrivate::FunctionPointer::ArgumentCount == -1), 
QMetaObject::Connection>::type QObject::connect(const typename 
QtPrivate::FunctionPointer::Object*, Func1, Func2)'
 connect(const typename QtPrivate::FunctionPointer::Object 
*sender, Func1 signal, Func2 slot)
 ^~~
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:300:13: note:   template 
argument deduction/substitution failed:
../../../src/findDialog.cpp:47:80: note:   candidate expects 3 arguments, 4 
provided
 connect(findPreviousAction, SIGNAL(triggered()), this, 
SLOT(findPrevious()));

^
In file included from 

Processed: Re: Bug#908752: r-cran-stan: epends on version of libgdal-dev that doesn't exist

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #908752 [r-cran-rstan] r-cran-stan: epends on version of libgdal-dev that 
doesn't exist
Added tag(s) pending.
> block -1 by 898704
Bug #908752 [r-cran-rstan] r-cran-stan: epends on version of libgdal-dev that 
doesn't exist
908752 was not blocked by any bugs.
908752 was not blocking any bugs.
Added blocking bug(s) of 908752: 898704

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

Bug#908752: r-cran-stan: epends on version of libgdal-dev that doesn't exist

[Andreas Tille]

Control: tags -1 pending
Control: block -1 by 898704

The package r-cran-rstan was accepted by ftpmaster before r-cran-stanheaders
so it does not even build.  I'll ping ftpmaster about this.

On Thu, Sep 13, 2018 at 04:03:36PM +0300, Adrian Bunk wrote:
> > 
> > The package depends on libgdal-dev >= 2.17.2 which I think is a typo.  The 
> > highest version of libgdal that is available in both Debian and at the gdal 
> > site is 2.3.1.

That's just caused by a broken dh-r which is fixed.  Rebuilding the
package is the only thing that's needed.

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#908670: libundead: ftbfs on armhf

[Matthias Klumpp]

Am Mi., 12. Sep. 2018 um 14:33 Uhr schrieb Andreas Tille :
>
> Control: tags -1 help
>
> Sorry, I have no idea what to do.  Any help is welcome.

This is a bug in LLVM that is now being tracked at
https://bugs.llvm.org/show_bug.cgi?id=38931

Cheers,
Matthias

-- 
I welcome VSRE emails. See http://vsre.info/

Bug#908762: marked as done (npm: Missing dependency: node-readable-stream)

[Debian Bug Tracking System]

Your message dated Thu, 13 Sep 2018 19:48:19 +0530
with message-id <1ac0ed8e-8ebe-55b9-7a60-b6a51d15d...@onenetbeyond.org>
and subject line Re: [Pkg-javascript-devel] Bug#908762: npm: Missing 
dependency: node-readable-stream
has caused the Debian Bug report #908762,
regarding npm: Missing dependency: node-readable-stream
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.)


-- 
908762: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908762
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: npm
Version: 5.8.0+ds-3
Severity: grave
Tags: patch

Dear Maintainer,

while trying to install a bunch of Node packages demanded by a valid
package.json, npm gives me error message "Cannot find module
'readable-stream'". Here's the npm logfile:

,
| 0 info it worked if it ends with ok
| 1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'install' ]
| 2 info using npm@5.8.0
| 3 info using node@v8.11.2
| 4 verbose stack Error: Cannot find module 'readable-stream'
| 4 verbose stack at Function.Module._resolveFilename
| (module.js:547:15)
| 4 verbose stack at Function.Module._load (module.js:474:25)
| 4 verbose stack at Module.require (module.js:596:17)
| 4 verbose stack at require (internal/module.js:11:18)
| 4 verbose stack at Object.
| 
(/usr/share/npm/node_modules/cacache/node_modules/mississippi/node_modules/duplexify/index.js:1:76)
| 4 verbose stack at Module._compile (module.js:652:30)
| 4 verbose stack at Object.Module._extensions..js (module.js:663:10)
| 4 verbose stack at Module.load (module.js:565:32)
| 4 verbose stack at tryModuleLoad (module.js:505:12)
| 4 verbose stack at Function.Module._load (module.js:497:3)
| 4 verbose stack at Module.require (module.js:596:17)
| 4 verbose stack at require (internal/module.js:11:18)
| 4 verbose stack at Object.
| 
(/usr/share/npm/node_modules/cacache/node_modules/mississippi/node_modules/pumpify/index.js:3:17)
| 4 verbose stack at Module._compile (module.js:652:30)
| 4 verbose stack at Object.Module._extensions..js (module.js:663:10)
| 4 verbose stack at Module.load (module.js:565:32)
| 5 verbose cwd /home/bengen/src/deb/grr/node-modules
| 6 verbose Linux 4.17.0-0.bpo.3-amd64
| 7 verbose argv "/usr/bin/node" "/usr/bin/npm" "install"
| 8 verbose node v8.11.2
| 9 verbose npm  v5.8.0
| 10 error code MODULE_NOT_FOUND
| 11 error Cannot find module 'readable-stream'
| 12 verbose exit [ 1, true ]
`

Installing node-readable-stream fixes this for me, so here's a patch.

Cheers,
-Hilko
>From f0817f5de0e66a2dad5258578f550b200c69e7fe Mon Sep 17 00:00:00 2001
From: Hilko Bengen 
Date: Thu, 13 Sep 2018 16:07:52 +0200
Subject: [PATCH] Add readable-stream dependency

---
 debian/control | 1 +
 1 file changed, 1 insertion(+)

diff --git a/debian/control b/debian/control
index a191fff..564de80 100644
--- a/debian/control
+++ b/debian/control
@@ -150,6 +150,7 @@ Depends: nodejs,
  node-performance-now,
  node-promise-inflight,
  node-read,
+ node-readable-stream,
  node-read-package-json (>= 1.1.0),
  node-request (>= 2.25.0),
  node-retry,
-- 
2.18.0

--- End Message ---
--- Begin Message ---
fixed 908762 5.8.0+ds1-1

thanks

The idea was to remove readable-stream dependency so its easy to
backport to stretch, but I missed removing the dependency from embedded
modules in previous upload, which was fixed in last upload.--- End Message ---

Processed: Re: [Pkg-javascript-devel] Bug#908762: npm: Missing dependency: node-readable-stream

[Debian Bug Tracking System]

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

> fixed 908762 5.8.0+ds1-1
Bug #908762 [npm] npm: Missing dependency: node-readable-stream
Marked as fixed in versions npm/5.8.0+ds1-1.
> thanks
Stopping processing here.

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

Bug#908762: npm: Missing dependency: node-readable-stream

[Hilko Bengen]

Package: npm
Version: 5.8.0+ds-3
Severity: grave
Tags: patch

Dear Maintainer,

while trying to install a bunch of Node packages demanded by a valid
package.json, npm gives me error message "Cannot find module
'readable-stream'". Here's the npm logfile:

,
| 0 info it worked if it ends with ok
| 1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'install' ]
| 2 info using npm@5.8.0
| 3 info using node@v8.11.2
| 4 verbose stack Error: Cannot find module 'readable-stream'
| 4 verbose stack at Function.Module._resolveFilename
| (module.js:547:15)
| 4 verbose stack at Function.Module._load (module.js:474:25)
| 4 verbose stack at Module.require (module.js:596:17)
| 4 verbose stack at require (internal/module.js:11:18)
| 4 verbose stack at Object.
| 
(/usr/share/npm/node_modules/cacache/node_modules/mississippi/node_modules/duplexify/index.js:1:76)
| 4 verbose stack at Module._compile (module.js:652:30)
| 4 verbose stack at Object.Module._extensions..js (module.js:663:10)
| 4 verbose stack at Module.load (module.js:565:32)
| 4 verbose stack at tryModuleLoad (module.js:505:12)
| 4 verbose stack at Function.Module._load (module.js:497:3)
| 4 verbose stack at Module.require (module.js:596:17)
| 4 verbose stack at require (internal/module.js:11:18)
| 4 verbose stack at Object.
| 
(/usr/share/npm/node_modules/cacache/node_modules/mississippi/node_modules/pumpify/index.js:3:17)
| 4 verbose stack at Module._compile (module.js:652:30)
| 4 verbose stack at Object.Module._extensions..js (module.js:663:10)
| 4 verbose stack at Module.load (module.js:565:32)
| 5 verbose cwd /home/bengen/src/deb/grr/node-modules
| 6 verbose Linux 4.17.0-0.bpo.3-amd64
| 7 verbose argv "/usr/bin/node" "/usr/bin/npm" "install"
| 8 verbose node v8.11.2
| 9 verbose npm  v5.8.0
| 10 error code MODULE_NOT_FOUND
| 11 error Cannot find module 'readable-stream'
| 12 verbose exit [ 1, true ]
`

Installing node-readable-stream fixes this for me, so here's a patch.

Cheers,
-Hilko
>From f0817f5de0e66a2dad5258578f550b200c69e7fe Mon Sep 17 00:00:00 2001
From: Hilko Bengen 
Date: Thu, 13 Sep 2018 16:07:52 +0200
Subject: [PATCH] Add readable-stream dependency

---
 debian/control | 1 +
 1 file changed, 1 insertion(+)

diff --git a/debian/control b/debian/control
index a191fff..564de80 100644
--- a/debian/control
+++ b/debian/control
@@ -150,6 +150,7 @@ Depends: nodejs,
  node-performance-now,
  node-promise-inflight,
  node-read,
+ node-readable-stream,
  node-read-package-json (>= 1.1.0),
  node-request (>= 2.25.0),
  node-retry,
-- 
2.18.0

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

[殷啟聰 | Kai-Chung Yan]

> Who are the DD in the team? Are there other contributors currently
> following the process to become a DD?

Mostly Hans (eighthave) is the DD involved a lot, and Markus (apo) occasionally 
helps. I am currently going through the process of becoming a DD but it is 
going very slowly.

> It would have helped if you had given me the URL of the repository.
> Anyway, I'm willing to sponsor the update (even though I don't know much
> about Android Tools) but I have a few comments:

Thank you for the sponsor, it will help us a lot!

The repository is at 
. 
Sorry about that, I thought it was too trivial.

> 1/ your RFS mentions the need to do a "stage1" upload but you actually
> manually dropped the package and the build dependencies that were tagged
> stage1, why did you do that?

"stage1" is everything but "fastboot". "fastboot" depends on some libraries in 
"android-platform-system-extras" which also depend on libraries in this source 
package, making a circular dependency. We are going to upload the full version 
after "android-platform-system-extras" gets uploaded.

"buildd" does not support staged uploads, so we have to manually remove 
"fastboot", hence the "~stage1" part of the version.

> 2/ I don't understand why you replace "android-tools-mkbootimg" with
> "mkbootimg". The latter package has a very generic name while the former
> was rather explicit. It looks like a step backwards. Yes, now it matches
> the name of the executable inside the package, but I'm not sure it
> justifies introducing a new package and dealing with a transitional
> package. What was your rationale? And you should have documented your
> rationale in the commit messages and in the changelog entry.

We have renamed "adb" and "fastboot" as well, and we are doing the same for 
"mkbootimg" this time. For the moment, the names of these programs have been 
well-known and exclusive in the society, so I don't think the "android-tools-" 
prefix is necessary. For a name, they seem not that generic to me as I've seen 
something more so (e.g. "docker" and "node", which did caused name conflicts in 
Debian).

Another reason has been mentioned by you: They match the executables.

There are other executables built by this package with names more generic, like 
"img2simg" and "append2simg". We put them together in a single package (as you 
can see in the changelog") because they belong to the same subproject 
"libsparse". Unfortunately "mkbootimg" lives on its own so I just make it its 
own package.



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#908752: r-cran-stan: epends on version of libgdal-dev that doesn't exist

[Debian Bug Tracking System]

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

> reassign 908752 r-cran-rstan 2.17.3+dfsg-1
Bug #908752 [r-cran-stan] r-cran-stan: epends on version of libgdal-dev that 
doesn't exist
Warning: Unknown package 'r-cran-stan'
Bug reassigned from package 'r-cran-stan' to 'r-cran-rstan'.
No longer marked as found in versions 2.17.3+dfsg-1.
Ignoring request to alter fixed versions of bug #908752 to the same values 
previously set
Bug #908752 [r-cran-rstan] r-cran-stan: epends on version of libgdal-dev that 
doesn't exist
Marked as found in versions r-cran-rstan/2.17.3+dfsg-1.
> severity 908752 serious
Bug #908752 [r-cran-rstan] r-cran-stan: epends on version of libgdal-dev that 
doesn't exist
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#908693: marked as done (novnc: please remove dependency on libjs-swfobject, which is going away)

[Debian Bug Tracking System]

Your message dated Thu, 13 Sep 2018 13:00:13 +
with message-id 
and subject line Bug#908693: fixed in novnc 1:1.0.0-1
has caused the Debian Bug report #908693,
regarding novnc: please remove dependency on libjs-swfobject, which is going 
away
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.)


-- 
908693: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908693
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: novnc
version: 1:0.4+dfsg+1+20131010+gitf68af8af3d-7
severity: serious
Control: block 900106 -1

Hi,

Please remove the dependency on libjs-swfobject, which is scheduled to be
removed from buster. See https://bugs.debian.org/900106 for more info.

Cheers,

Ivo
--- End Message ---
--- Begin Message ---
Source: novnc
Source-Version: 1:1.0.0-1

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 15 May 2018 11:28:13 +0200
Source: novnc
Binary: novnc python-novnc python3-novnc
Architecture: source all
Version: 1:1.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Description:
 novnc  - HTML5 VNC client - daemon and programs
 python-novnc - HTML5 VNC client - Python 2.7 libraries
 python3-novnc - HTML5 VNC client - Python 3.x libraries
Closes: 847122 908693
Changes:
 novnc (1:1.0.0-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/copyright: Use https in Format
   * Removing gbp.conf, not used anymore or should be specified in the
 developers dotfiles
   * d/control: Use team+openst...@tracker.debian.org as maintainer
 .
   [ David Rabel ]
   * d/changelog: Fix wrong entry.
   * d/copyright: Fixed. Was totally broken.
   * d/novnc.install: Don't install extra license file.
   * d/patches/ : Fix typo.
   * d/control, d/watch: Update upstream URL.
 .
   [ Thomas Goirand ]
   * New upstream release (Closes: #847122):
 - Drop now useless patches: utils-launch.patch and
   adds_support_for_secure_attribute_on_token_cookie.patch
   * Do not override dh_clean anymore.
   * Fixed patch to package novnc as python package.
   * Rewrite debian/novnc.install and part of debian/rules to adapt to the new
 upstream release..
   * Add patch for Python 3 compat (print statements).
   * Hack po/po2js to use debian/getopt.js.
   * Update debian/copyright file to reality of 1.0.0.
   * Fixed debian/rules to use new upstream URL.
   * Add Python 3 support.
   * Document license for vendor/pako/lib/zlib/.
   * Removed runtime dependency on libjs-swfobject, which is only for old web
 browsers anyway (Closes: #908693).
   * Add compatibility symlink to vnc_auto.html so that it works with old Nova
 setup without any modification.
   * Delete /usr/share/novnc/vendor/browser-es-module-loader/.npmignore during
 the file install.
   * Fixed shebang for b64-to-binary.pl.
Checksums-Sha1:
 f3af38bb22d7fb03a509baebfb5a182b1a27b559 2123 novnc_1.0.0-1.dsc
 66368b005d115824a299a8835a3803a6c72db74b 1131408 novnc_1.0.0.orig.tar.xz
 f5bdeebc8772b731fd6651ba3786b8fed9b9c18e 37628 novnc_1.0.0-1.debian.tar.xz
 252f87cacd3464938fbae00b301238312c0e7775 819952 novnc_1.0.0-1_all.deb
 10ce9097e17833db51fe8f7e929af2dda4da8521 7574 novnc_1.0.0-1_amd64.buildinfo
 dd27732a618519f02b52900ece54e9cba1421f6a 16864 python-novnc_1.0.0-1_all.deb
 558fa87b12b9c25e5eedcd724dc3099398e7adba 16948 python3-novnc_1.0.0-1_all.deb
Checksums-Sha256:
 e3a5460178831deffef71ac0939d10a1250cd7cbc55e7b442754a9264a9139bd 2123 
novnc_1.0.0-1.dsc
 c2749036f75a8ceeb38d07c5b22194bf089f767887d893955226130f879a75b2 1131408 
novnc_1.0.0.orig.tar.xz
 20c56f3003123e30e7627c9b1e275f18b48601a7469df0c76b03d9771cce06fe 37628 
novnc_1.0.0-1.debian.tar.xz
 eee7945260bf7de2210e7d506c4d5b36aaffc62bdd0af7a35df0dc5904e75445 819952 
novnc_1.0.0-1_all.deb
 201a9bd0c5f29887dde95db2501cfebff7e7d38e07b540cff510945a4ce71ce4 7574 
novnc_1.0.0-1_amd64.buildinfo
 

Bug#906307: clsync: pre-depends on multiarch-support in buster

[Aurelien Jarno]

tag: reopen -1

On 2018-09-13 15:35, Adrian Bunk wrote:
> Version: 0.4.2-1 
> 
> On Thu, Aug 16, 2018 at 10:50:17PM +0200, Aurelien Jarno wrote:
> > Source: clsync
> > Version: 0.4.1-1
> > Severity: serious
> > Tags: buster
> > 
> > The multiarch-support package is scheduled for removal in buster.
> > clsync is one of the last package in buster that still depends on
> > it. The dependency is added by old versions of debhelper, so in theory
> > the package would just need to get rebuild and migrated to testing.
> > Unfortunately it's not something possible as the package doesn't build
> > on most architectures due to bug#844778 which is opened for more almost
> > two years now.
> 
> I'm closing this with the version in unstable.

The version in unstable still doesn't build on most architectures, so it
won't migrate to testing.

> Version tracking will handle this correctly.

Closing this bug will prevent the autoremoval to work, which was exactly
the purpose of this bug, as discussed in #905996. Reopening it.

Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Processed: found 907079 in 2.57-4

[Debian Bug Tracking System]

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

> found 907079 2.57-4
Bug #907079 [python-imaplib2] Not using SNI
Marked as found in versions python-imaplib2/2.57-4.
> thanks
Stopping processing here.

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

Bug#906307: marked as done (clsync: pre-depends on multiarch-support in buster)

[Debian Bug Tracking System]

Your message dated Thu, 13 Sep 2018 15:35:38 +0300
with message-id <20180913123538.GA8703@localhost>
and subject line Re: Bug#906307: clsync: pre-depends on multiarch-support in 
buster
has caused the Debian Bug report #906307,
regarding clsync: pre-depends on multiarch-support in buster
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.)


-- 
906307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906307
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: clsync
Version: 0.4.1-1
Severity: serious
Tags: buster

The multiarch-support package is scheduled for removal in buster.
clsync is one of the last package in buster that still depends on
it. The dependency is added by old versions of debhelper, so in theory
the package would just need to get rebuild and migrated to testing.
Unfortunately it's not something possible as the package doesn't build
on most architectures due to bug#844778 which is opened for more almost
two years now.

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

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

On Thu, Aug 16, 2018 at 10:50:17PM +0200, Aurelien Jarno wrote:
> Source: clsync
> Version: 0.4.1-1
> Severity: serious
> Tags: buster
> 
> The multiarch-support package is scheduled for removal in buster.
> clsync is one of the last package in buster that still depends on
> it. The dependency is added by old versions of debhelper, so in theory
> the package would just need to get rebuild and migrated to testing.
> Unfortunately it's not something possible as the package doesn't build
> on most architectures due to bug#844778 which is opened for more almost
> two years now.

I'm closing this with the version in unstable.

Version tracking will handle this correctly.

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#908673: marked as done (gdk_pixbuf_new_from_inline introspection metadata is broken)

[Debian Bug Tracking System]

Your message dated Thu, 13 Sep 2018 12:34:12 +
with message-id 
and subject line Bug#908673: fixed in gdk-pixbuf 2.38.0+dfsg-5
has caused the Debian Bug report #908673,
regarding gdk_pixbuf_new_from_inline introspection metadata is broken
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.)


-- 
908673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908673
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgtk3-perl
Version: 0.034-1
Severity: serious
User: debian-p...@lists.debian.org
Usertags: autopkgtest
Control: block 902557 with -1

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

  
https://ci.debian.net/data/autopkgtest/unstable/amd64/libg/libgtk3-perl/953602/log.gz

  Undefined subroutine ::Gdk::PIXDATA_HEADER_LENGTH called at 
/<>/blib/lib/Gtk3.pm line 2119.
  # Looks like your test exited with 255 just after 162.

  [...]

  Test Summary Report
  ---
  t/overrides.t(Wstat: 65280 Tests: 162 Failed: 0)
Non-zero exit status: 255
Parse errors: Bad plan.  You planned 233 tests but ran 162.
  Files=22, Tests=843,  5 wallclock secs ( 0.18 usr  0.03 sys +  4.58 cusr  
0.46 csys =  5.25 CPU)
  Result: FAIL
 
I'm guessing this regressed with gdk-pixbuf 2.38.0+dfsg-1 or so, but I
haven't verified that (and the ci.debian.net machinery doesn't seem to
have pinpointed it yet either.)
-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: gdk-pixbuf
Source-Version: 2.38.0+dfsg-5

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

Debian distribution maintenance software
pp.
Iain Lane  (supplier of updated gdk-pixbuf 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: Thu, 13 Sep 2018 12:50:53 +0100
Source: gdk-pixbuf
Binary: libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-bin libgdk-pixbuf2.0-common 
libgdk-pixbuf2.0-dev libgdk-pixbuf2.0-doc libgdk-pixbuf2.0-0-udeb 
gir1.2-gdkpixbuf-2.0
Architecture: source
Version: 2.38.0+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Iain Lane 
Description:
 gir1.2-gdkpixbuf-2.0 - GDK Pixbuf library - GObject-Introspection
 libgdk-pixbuf2.0-0 - GDK Pixbuf library
 libgdk-pixbuf2.0-0-udeb - GDK Pixbuf library - minimal runtime (udeb)
 libgdk-pixbuf2.0-bin - GDK Pixbuf library (thumbnailer)
 libgdk-pixbuf2.0-common - GDK Pixbuf library - data files
 libgdk-pixbuf2.0-dev - GDK Pixbuf library (development files)
 libgdk-pixbuf2.0-doc - GDK Pixbuf library (documentation)
Closes: 908673
Changes:
 gdk-pixbuf (2.38.0+dfsg-5) unstable; urgency=medium
 .
   [ Jeremy Bicha ]
   * debian/rules: Use meson test --print-errorlogs
 dh_auto_test normally does that for us
 .
   [ Iain Lane ]
   * Add new patch to include gdk-pixdata.c when building the GdkPixbuf gir.
 This fixes broken introspection metadata that at least would have broken
 libgtk3-perl. (Closes: #908673)
Checksums-Sha1:
 38143c97dcabc3ce95f1c724c960d43dd725961d 2903 gdk-pixbuf_2.38.0+dfsg-5.dsc
 068acdc773aa0605cd087eff94e3687b135da154 17564 
gdk-pixbuf_2.38.0+dfsg-5.debian.tar.xz
 8574f3d65f987e00d60df3d8f73ea2d39536eff6 12695 
gdk-pixbuf_2.38.0+dfsg-5_source.buildinfo
Checksums-Sha256:
 42afe6c7db589970f55dcae27a58bf315eae1d055777f58a44071ea4765b3060 2903 
gdk-pixbuf_2.38.0+dfsg-5.dsc
 30c732c4e9e9220467abdad34247a15c6b4b422c7c34c34dffd3eaa71d8a6307 17564 
gdk-pixbuf_2.38.0+dfsg-5.debian.tar.xz
 865aa6e92ca6b5b4e9d5c206a06fc92ae317e955953c68806dee05e57a6cf51c 12695 
gdk-pixbuf_2.38.0+dfsg-5_source.buildinfo
Files:
 36856b6a426cdb4f2696af2f6caaa6e0 2903 libs optional 
gdk-pixbuf_2.38.0+dfsg-5.dsc
 95ed0c4953660ac1799ce120efdfca35 17564 libs optional 
gdk-pixbuf_2.38.0+dfsg-5.debian.tar.xz
 699c12f84464e5558cd4a8dc0688b0f4 12695 libs optional 
gdk-pixbuf_2.38.0+dfsg-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEPQ77lee1I38W6CJY41LVxRxQQdQFAluaU/cACgkQ41LVxRxQ

Bug#908670: libundead: ftbfs on armhf

[peter green]

I (with my raspbian maintainer hat on) reported this to ldc upstream at 
https://github.com/ldc-developers/ldc/issues/2848 and some digging has been 
done. The short version is that we know what commit caused the build failures. 
However that commit was a fix for mis compilation, so I don't think we should 
just back it out. The proper fix is in llvm itself though a workaround may be 
possible in ldc.

The long version as I understand it.

ldc generates "thunks", these thunks adjust the "this" pointer before calling 
the original function. I understand they are related to multiple inheritance.

It was discovered that "thunks" for variadic functions were being miscompiled 
https://github.com/ldc-developers/ldc/issues/2613 , the variadic arguments were not being 
passed on correctly to the original function. It turns out that variadic functions can 
only be passed on correctly in a tail call (most ABIs don't pass on any meta-information 
about the number of variadics, so there is no real way to copy the variadics).

The fix was to make ldc specify "musttail" (which is an order) rather than 
"tail" (which is a hint) when generating thunks for variadic functions 
https://github.com/kinke/ldc/commit/1dda15a76272cdb3963754fa815d96bacc989852.

Unfortunately it seems that llvm sometimes fails to compile such thunks on arm, 
I did some playing around with different parameter lists and it seems that it 
fails to compile them if a non-variadic structure parameter overflows on to the 
stack.

So what are our options.

1. Back out the upstream fix, this would fix the build but would almost 
certainly result in miscompiled code, I don't think that is acceptable.
2. Get the issue fixed in llvm, I have filed a bug report ( 
https://bugs.llvm.org/show_bug.cgi?id=38931 ) but I don't know when and if it 
will be actioned.
3. Hack ldc to generate variadic thunks in native assembler on arm, the thunks 
are trivial to express in native arm asm, but i'm not sure what calls to the 
llvm api are needed to insert a procedure written in native asm.
4. Simply get libundead removed on armhf/raspbian. libundead seems to only have 
two reverse build-dependencies neither of which has ever successfully built on 
armhf. libbiod previously failed with a testsuite failure (probablly related to 
the miscompilation discussed above) and now fails with the same error that 
libundead does. sambamba is blocked by a dependency on libbiod

Processed: linpsk: diff for NMU version 1.3.5-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 906253 + pending
Bug #906253 [src:linpsk] linpsk: FTBFS: invalid use of incomplete type 'class 
QButtonGroup'
Added tag(s) pending.

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

Bug#906253: linpsk: diff for NMU version 1.3.5-1.1

[Adrian Bunk]

Control: tags 906253 + pending

Dear maintainer,

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

cu
Adrian

-- 

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

diff -Nru linpsk-1.3.5/debian/changelog linpsk-1.3.5/debian/changelog
--- linpsk-1.3.5/debian/changelog	2017-07-18 19:34:40.0 +0300
+++ linpsk-1.3.5/debian/changelog	2018-09-13 15:09:59.0 +0300
@@ -1,3 +1,11 @@
+linpsk (1.3.5-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add patch from Reiner Herrmann for FTBFS with Qt 5.11.
+(Closes: #906253)
+
+ -- Adrian Bunk   Thu, 13 Sep 2018 15:09:59 +0300
+
 linpsk (1.3.5-1) unstable; urgency=medium
 
   * New upstream version 1.3.5
diff -Nru linpsk-1.3.5/debian/patches/qt5.11.patch linpsk-1.3.5/debian/patches/qt5.11.patch
--- linpsk-1.3.5/debian/patches/qt5.11.patch	1970-01-01 02:00:00.0 +0200
+++ linpsk-1.3.5/debian/patches/qt5.11.patch	2018-09-13 15:09:57.0 +0300
@@ -0,0 +1,13 @@
+Author: Reiner Herrmann 
+Description: Include missing header for QButtonGroup
+
+--- a/gui/modemenu.cpp
 b/gui/modemenu.cpp
+@@ -23,6 +23,7 @@
+ #include "parameter.h"
+ #include "crxchannel.h"
+ 
++#include 
+ 
+ extern Parameter settings;
+ 
diff -Nru linpsk-1.3.5/debian/patches/series linpsk-1.3.5/debian/patches/series
--- linpsk-1.3.5/debian/patches/series	2017-07-18 19:24:41.0 +0300
+++ linpsk-1.3.5/debian/patches/series	2018-09-13 15:09:57.0 +0300
@@ -1,3 +1,4 @@
 we_have_hamlib.patch
 typo.patch
 ftbfs-clang.patch
+qt5.11.patch

Bug#908323: libgtk3-perl: FTBFS: t/overrides.t failure

[Iain Lane]

On Wed, Sep 12, 2018 at 11:59:49PM +0200, gregor herrmann wrote:
> That's great news, thanks.
> Please give us a short ping once the fixed package is available.

I've just uploaded gdk-pixbuf 2.38.0+dfsg-5. There will be the normal
delay, but hopefully this fixes the issue for you.

Cheers,

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]


signature.asc
Description: PGP signature

Bug#908673: Bug #908673 in gdk-pixbuf marked as pending

[Iain Lane]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/gnome-team/gdk-pixbuf/commit/d5d2f6aa96cf8c309c22e29d558cef487dd2567c


Add new patch to include gdk-pixdata.c when building the GdkPixbuf gir

This fixes broken introspection metadata that at least would have broken
libgtk3-perl.

Closes: #908673



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/908673

Processed: Bug #908673 in gdk-pixbuf marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #908673 [gir1.2-gdkpixbuf-2.0] gdk_pixbuf_new_from_inline introspection 
metadata is broken
Added tag(s) pending.

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

Processed: affects 908580

[Debian Bug Tracking System]

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

> affects 908580 src:ibus-table-chinese
Bug #908580 [ibus-table] ibus-table-createdb fails with nonexisting $HOME
Added indication that 908580 affects src:ibus-table-chinese
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 908670 https://github.com/ldc-developers/ldc/issues/2848
Bug #908670 [src:libundead] libundead: ftbfs on armhf
Set Bug forwarded-to-address to 
'https://github.com/ldc-developers/ldc/issues/2848'.
> forwarded 908671 https://github.com/gtkd-developers/gir-to-d/issues/19
Bug #908671 [src:gir-to-d] glib-d: ftbfs on armhf and i386
Bug #907947 [src:gir-to-d] glib-d FTBFS with glib 2.58
Set Bug forwarded-to-address to 
'https://github.com/gtkd-developers/gir-to-d/issues/19'.
Set Bug forwarded-to-address to 
'https://github.com/gtkd-developers/gir-to-d/issues/19'.
>
End of message, stopping processing here.

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

Bug#908213: marked as done (node-regjsparser: Build against node-unicode-11.0.0)

[Debian Bug Tracking System]

Your message dated Thu, 13 Sep 2018 12:04:08 +
with message-id 
and subject line Bug#908213: fixed in node-regjsparser 0.4.0+ds-2
has caused the Debian Bug report #908213,
regarding node-regjsparser: Build against node-unicode-11.0.0
to be marked as done.

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

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


-- 
908213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908213
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-regjsparser
Version: 0.4.0+ds-1
Severity: serious
Tags: ftbfs

node-regjsparaser build-depend on node-unicode-10.0.0 but that package
is no longer built from source. Please build against
node-unicode-11.0.0 instead.

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: node-regjsparser
Source-Version: 0.4.0+ds-2

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

Debian distribution maintenance software
pp.
Julien Puydt  (supplier of updated node-regjsparser 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: Thu, 13 Sep 2018 13:33:14 +0200
Source: node-regjsparser
Binary: node-regjsparser
Architecture: source all
Version: 0.4.0+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Julien Puydt 
Description:
 node-regjsparser - Parser for JavaScript's RegExp for Node.js
Closes: 908213
Changes:
 node-regjsparser (0.4.0+ds-2) unstable; urgency=medium
 .
   * Build-depend on node-unicode-11.0.0 (Closes: #908213).
Checksums-Sha1:
 50474e8e93c592809c8ff1efdb836046c3944d9e 2134 node-regjsparser_0.4.0+ds-2.dsc
 8e0cdcf1f164c37bc94760af8de7964bdc8c1204 6004 
node-regjsparser_0.4.0+ds-2.debian.tar.xz
 1512dbeb98027228758fe9073a6df69d9439b191 15760 
node-regjsparser_0.4.0+ds-2_all.deb
 f95e6b01c22ae1c13700b82580e04c27edb73e37 6120 
node-regjsparser_0.4.0+ds-2_amd64.buildinfo
Checksums-Sha256:
 f77196825803517cc70214048063af791bdd8fe590c3126398b63c68538c3adc 2134 
node-regjsparser_0.4.0+ds-2.dsc
 8ee7912582be7b75e5c5f8e1a3f705c23a525ce78f9edb23dc346202a0ef12b1 6004 
node-regjsparser_0.4.0+ds-2.debian.tar.xz
 1ab70a5c2c170ae0f043e94bf765df252a761c863c93a1b6c3f1e866856cbff2 15760 
node-regjsparser_0.4.0+ds-2_all.deb
 3ec396d5a7e8cde91b975a8f3187e486fe6d190f9b53b6111f4205266a19d05b 6120 
node-regjsparser_0.4.0+ds-2_amd64.buildinfo
Files:
 5e2c3efb8db28e9f78b137749572e746 2134 javascript optional 
node-regjsparser_0.4.0+ds-2.dsc
 a90ee5cdf87cc687080f5f201dbf4091 6004 javascript optional 
node-regjsparser_0.4.0+ds-2.debian.tar.xz
 9ceaf1b1775ee26445b418b98578f373 15760 javascript optional 
node-regjsparser_0.4.0+ds-2_all.deb
 d49dc5d899319fccd7596936980fccbc 6120 javascript optional 
node-regjsparser_0.4.0+ds-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJNBAEBCgA3FiEEgS7v2KP7pKzk3xFLBMU71/4DBVEFAluaTAAZHGp1bGllbi5w
dXlkdEBsYXBvc3RlLm5ldAAKCRAExTvX/gMFUZHVD/9kzUmlSjqSYWE4ivHYVVsL
y+OIgPNWEFR59/VZqEtkFbhqkLbNRifYOCFs4aNyQfmnPAw2IH+GSeyNdXg48eKe
dJy1OU+K+Ea1xmuaKfwBfcFXt+eeQWyrQ9ysfLzYU+DTBCfzC8pjHfDQ2Yn0QHiv
yv3P0q2puA72YBbB/+1hhOVBykWb0bLMw8dKjOBY+8d66JFgr6bsO4Wst0e4trS8
tEv17Tm/blDA8bMXX5EqlJT8Hp/mHZTh78EDEiUCAr3i/THdwAaklsP9491Q0M/9
MIQBmpPEb58AGPEhm+jEE1GVACXztR4p0et/zT+zDISkOYveE2is5OJ9531wBuqH
gImO9Nhgu55l+tE7wAcFdr8YKOpfxPPvSqVEROzxXCPyZL6EGHxEoEmXUBUBNcVS
rESEmrZfWYu6uGj3aTewWiqNbjHlGY30dWmT53OYLz595KRZcXIXhb434mMaleSn
6tibNvMyj29Ut9/VWq5OqC9Ck3swwhctDL41K/hfwgt8LI119RbI+t2z8+Evmizu
aqTd0vBuLNxe04K2XreNeXQN11m+n2HxsreoNYBzElo4HS18PfzDGFtbI0R3FePC
4Q//8cgB7tWAjeCrOBY6GRBaxoc4eaKPXMrgJKnNzAE1dM895YTDZ5PM9egJlCjz
8UEnRefEwpEO+Rtj1XU1Sw==
=RG1s
-END PGP SIGNATURE End Message ---

Bug#896991: marked as done (libtrapperkeeper-clojure is not installable)

[Debian Bug Tracking System]

Your message dated Thu, 13 Sep 2018 14:45:18 +0300
with message-id <20180913114517.GA27524@localhost>
and subject line Re: Bug#896991: libtrapperkeeper-clojure is not installable
has caused the Debian Bug report #896991,
regarding libtrapperkeeper-clojure is not installable
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.)


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

There is a conflict between the dependencies
  libclojure-java
and
  libtools-nrepl-clojure -> libclojure1.8-java
--- End Message ---
--- Begin Message ---
On Thu, Apr 26, 2018 at 06:45:12PM +0300, Adrian Bunk wrote:
> Package: libtrapperkeeper-clojure
> Version: 4.4.1-1
> Severity: serious
> 
> There is a conflict between the dependencies
>   libclojure-java
> and
>   libtools-nrepl-clojure -> libclojure1.8-java

This seems to be fixed now.

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#908678: security-tracker - Breaks salsa.d.o

[Paul Wise]

On Thu, Sep 13, 2018 at 7:37 PM, Salvatore Bonaccorso wrote:

> Do you have any hints at us on what we could look at to faciliate/help
> more salsa maintainers?

I think I read on IRC that the main thing is that the design of git is
not optimised for having large and growing files that change on every
commit. So splitting them up into to one file per CVE/DSA/DLA/etc
might help? Or switching from git to a database or something like
restic or borg.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#908678: security-tracker - Breaks salsa.d.o

[Salvatore Bonaccorso]

Hi Bastian,

On Wed, Sep 12, 2018 at 03:10:56PM +0200, Bastian Blank wrote:
> Package: security-tracker
> Severity: critical
> 
> The security tracker git repository is in a state which git does not
> really like.  git clone takes ages, fsck takes ages, repack is reported
> to be impossible.
> 
> The GitLab on salsa.d.o also chokes on it some times during git
> operations.  Some may be attributed to the old diff formatter problem,
> which I hope gets fixed soon.  But lately it even caused stalls on git
> operation.
> 
> As the problems caused by the state of this repo now causes user visible
> outages, this needs to be fixed.

Do you have any hints at us on what we could look at to faciliate/help
more salsa maintainers?

What is actually this old diff formater problem you mentioned which
going to be solved? Would it in the meantime help to make the access
only for logged in users/restricted?

Regards,
Salvatore

Bug#908741: libjpeg9: do not hardcode automake version

[Gianfranco Costamagna]

Source: libjpeg9
Version: 1:9c-1
Severity: serious
tags: patch
Justification: prevents removal of old automake-1.15

Hello, please stop using the old automake-1.15, and use the unversioned one.
(you are the last user of automake-1.15, this is why I'm setting the severity 
to serious, I presume
the maintainer will try to remove the package soon now that 1.16 is in testing)

Patch following:

diff -Nru libjpeg9-9c/debian/changelog libjpeg9-9c/debian/changelog
--- libjpeg9-9c/debian/changelog2018-07-28 14:35:23.0 +0200
+++ libjpeg9-9c/debian/changelog2018-09-13 12:44:08.0 +0200
@@ -1,3 +1,10 @@
+libjpeg9 (1:9c-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Do not export and include a specific automake version (Closes: #-1)
+
+ -- Gianfranco Costamagna   Thu, 13 Sep 2018 
12:44:08 +0200
+
 libjpeg9 (1:9c-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru libjpeg9-9c/debian/control libjpeg9-9c/debian/control
--- libjpeg9-9c/debian/control  2018-07-26 14:18:35.0 +0200
+++ libjpeg9-9c/debian/control  2018-09-13 12:44:08.0 +0200
@@ -2,7 +2,7 @@
 Maintainer: Bill Allombert 
 Section: graphics
 Priority: optional
-Build-Depends: debhelper (>= 9), autotools-dev, dh-autoreconf, automake-1.15
+Build-Depends: debhelper (>= 9), dh-autoreconf
 Standards-Version: 4.1.5
 
 Package: libjpeg9
diff -Nru libjpeg9-9c/debian/rules libjpeg9-9c/debian/rules
--- libjpeg9-9c/debian/rules2018-07-26 14:18:15.0 +0200
+++ libjpeg9-9c/debian/rules2018-09-13 12:44:08.0 +0200
@@ -18,8 +18,6 @@
 CFLAGS += -O2
 endif
 
-export AUTOMAKE = automake-1.15
-export ACLOCAL = aclocal-1.15
 export AUTOHEADER = true
 
 build: build-stamp 

Processed: libboost1.*-dev

[Debian Bug Tracking System]

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

> # although not impacting autopkgtest libboost1*-dev are affected as well
> clone 908732 -1 -2
Bug #908732 [libboost1.62-dev] libboost1.62-dev: please drop dependency on 
libstdc++-4.8-dev / libstdc++-dev
Bug 908732 cloned as bugs 908736-908737
> reassign -1 libboost1.63-dev 1.63.0+dfsg-1.1
Bug #908736 [libboost1.62-dev] libboost1.62-dev: please drop dependency on 
libstdc++-4.8-dev / libstdc++-dev
Bug reassigned from package 'libboost1.62-dev' to 'libboost1.63-dev'.
No longer marked as found in versions boost1.62/1.62.0+dfsg-8.
Ignoring request to alter fixed versions of bug #908736 to the same values 
previously set
Bug #908736 [libboost1.63-dev] libboost1.62-dev: please drop dependency on 
libstdc++-4.8-dev / libstdc++-dev
Marked as found in versions boost1.63/1.63.0+dfsg-1.1.
> reassign -2 libboost1.67-dev 1.67.0-6
Bug #908737 [libboost1.62-dev] libboost1.62-dev: please drop dependency on 
libstdc++-4.8-dev / libstdc++-dev
Bug reassigned from package 'libboost1.62-dev' to 'libboost1.67-dev'.
No longer marked as found in versions boost1.62/1.62.0+dfsg-8.
Ignoring request to alter fixed versions of bug #908737 to the same values 
previously set
Bug #908737 [libboost1.67-dev] libboost1.62-dev: please drop dependency on 
libstdc++-4.8-dev / libstdc++-dev
Marked as found in versions boost1.67/1.67.0-6.
> retitle -1 libboost1.63-dev: drop dependency on libstdc++(-4.8|)-dev
Bug #908736 [libboost1.63-dev] libboost1.62-dev: please drop dependency on 
libstdc++-4.8-dev / libstdc++-dev
Changed Bug title to 'libboost1.63-dev: drop dependency on 
libstdc++(-4.8|)-dev' from 'libboost1.62-dev: please drop dependency on 
libstdc++-4.8-dev / libstdc++-dev'.
> retitle -2 libboost1.67-dev: drop dependency on libstdc++(-4.8|)-dev
Bug #908737 [libboost1.67-dev] libboost1.62-dev: please drop dependency on 
libstdc++-4.8-dev / libstdc++-dev
Changed Bug title to 'libboost1.67-dev: drop dependency on 
libstdc++(-4.8|)-dev' from 'libboost1.62-dev: please drop dependency on 
libstdc++-4.8-dev / libstdc++-dev'.
> thanks
Stopping processing here.

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

Bug#908735: colord: need to build-depend on argyll

[Jonas Smedegaard]

Package: colord
Version: 1.4.3-2
Severity: serious
Tags: ftbfs

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Build-daemons all fail with a buildlog indicating that "spotread" is
missing.  That command is provided by the package argyll.

Please build-depend on argyll.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAluaMmgACgkQLHwxRsGg
ASEyThAAm1PA1pH3xmNKqlsgmTlLDUG2XmPaSrmzm8L8vkOCpqa4mBNQGE6AA8gs
deVtovq6OuC/5oGcP45MSEXJOsdJ17UPBen/omKcae3Wb7NY8g9OYF2u9vyHyKL5
BRimQmZo8qvPpl9ns89nycpLjxG34EPvGu1ApHo0NhTU0RQaq9PJRBCtnDtok7Jd
Lk29VsfKzGdNLTsRiGZxT4Hf1z4wFN1ckXLAuIWm4dwRZ2rTQpV8iPs1XWbKy+2x
BSFeq/ERSzVdnokj2tLwkIEmef21hKM/3ukfWMcEz2gb9hKDkj9rWyY9SDO42KPO
bi9+JrguiCK04hXu/Ls+Y0mDf/2/IFocGwtKvI6+TZYvj3bLBc/Iiq/J+HhYs6RL
hxmUrbTFZVLDKPNfHabZE2k2ZfRMbshA7tZCMsQ1GwfWKPv0Z3AyCzQcIdP+uMxr
H9+yA9Y0qPXa2ZgLMhRH84UGz5xxsa1xz5mzjZL51e4ps+BdyK5TomZaw7sf5nAM
q0U2GHngcd2GrVyu7WgJEICciZ5hwKf73J1XaiIinN5jL1NR6VS3yO8A5lO+HZlq
nL0tuHr9aWi+EUwoq8QIPvH1ybhYjTNL58dIPYtjaXpTEn+d2Wb9uR1DNlynVuK1
Ys9MB/jQFXGjVpnpIxy6OBxsGcUQnkKlA3yGu2orn4bbiO+W8sw=
=haGi
-END PGP SIGNATURE-

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

[Ervin]

Package: redshift
Version: 1.11-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

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

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

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



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

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

Versions of packages redshift depends on:
ii  libc6   2.24-11+deb9u3
ii  libdrm2 2.4.74-1
ii  libglib2.0-02.50.3-2
ii  libx11-62:1.6.4-3
ii  libxcb-randr0   1.12-1
ii  libxcb-render0  1.12-1
ii  libxcb1 1.12-1
ii  libxxf86vm1 1:1.1.4-1+b2

Versions of packages redshift recommends:
ii  geoclue-2.0  2.4.5-1

redshift suggests no packages.

-- no debconf information

Bug#908449: firefox-esr_60.2.0esr-1~deb9u2.1_i386.deb not working

[Mike Hommey]

On Thu, Sep 13, 2018 at 09:04:54PM +1200, Tim Makarios wrote:
> On 13/09/18 18:42, Mike Hommey wrote:
> > Can you install the firefox-esr-dbgsym package from
> > https://people.debian.org/~glandium/firefox-esr-dbgsym_60.2.0esr-1~deb9u2.1_i386.deb
> > 
> > and run the following command:
> > 
> > gdb firefox-esr
> > 
> > At the gdb prompt, type the following commands:
> > 
> >set pagination off
> >run
> 
> When I get to this point, it gives the output:
> > Starting program: /usr/bin/firefox-esr [Thread debugging using
> > libthread_db enabled]
> > Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
> and then thrashes my hard drive for a very long time.  I left it going for a
> while (over half an hour, maybe closer to three quarters of an hour), and in
> the end it seemed to have frozen the computer entirely.
> 
> I only have about three quarters of a gigabyte of RAM, which may have
> something to do with it...

Huh. Can you then try ulimit -c unlimited, and upload the resulting core
file somewhere?

Mike

Bug#908732: libboost1.62-dev: please drop dependency on libstdc++-4.8-dev / libstdc++-dev

[Paul Gevers]

Package: libboost1.62-dev
Version: 1.62.0+dfsg-8
Severity: serious
Justification: depends on non-existing package
X-Debbugs-CC: debian...@packages.debian.org
User: debian...@packages.debian.org
Usertags: breaks

While investigating the reason why several autopkgtest fail [1, 2, 3]
when run in testing with some package from unstable we [4] found that
this is caused by libc++-8-dev being installed. I believe this is pulled
in because:

a) libc++8-dev provides libstdc++-dev (I'll file a separate bug about
that) and

b) libboost1.62-dev depends on "libstdc++-4.8-dev | libstdc++-dev"

libstdc++-4.8-dev is only available in oldstable now. Please drop the
dependency and leave the dependency on libstdc++-dev to the c++ compiler.

Paul

[1] https://ci.debian.net/packages/a/akonadi-calendar/testing/amd64/
[2] https://ci.debian.net/packages/k/kf5-kdepim-apps-libs/testing/amd64/
[3] https://ci.debian.net/packages/libk/libkf5calendarsupport/testing/amd64/
[4] https://lists.debian.org/debian-ci/2018/09/msg00010.html

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

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

Versions of packages libboost1.62-dev depends on:
ii  libstdc++-8-dev [libstdc++-dev]  8.2.0-4

libboost1.62-dev recommends no packages.

Versions of packages libboost1.62-dev suggests:
pn  libboost-atomic1.62-dev   
pn  libboost-chrono1.62-dev   
pn  libboost-context1.62-dev  
pn  libboost-coroutine1.62-dev
pn  libboost-date-time1.62-dev
pn  libboost-exception1.62-dev
pn  libboost-fiber1.62-dev
pn  libboost-filesystem1.62-dev   
pn  libboost-graph-parallel1.62-dev   
pn  libboost-graph1.62-dev
pn  libboost-iostreams1.62-dev
pn  libboost-locale1.62-dev   
pn  libboost-log1.62-dev  
pn  libboost-math1.62-dev 
pn  libboost-mpi-python1.62-dev   
pn  libboost-mpi1.62-dev  
pn  libboost-program-options1.62-dev  
pn  libboost-python1.62-dev   
pn  libboost-random1.62-dev   
pn  libboost-regex1.62-dev
pn  libboost-serialization1.62-dev
pn  libboost-signals1.62-dev  
pn  libboost-system1.62-dev   
pn  libboost-test1.62-dev 
pn  libboost-thread1.62-dev   
pn  libboost-timer1.62-dev
pn  libboost-type-erasure1.62-dev 
pn  libboost-wave1.62-dev 
pn  libboost1.62-doc  
pn  libboost1.62-tools-dev
pn  libmpfrc++-dev
pn  libntl-dev



signature.asc
Description: OpenPGP digital signature

Bug#908449: firefox-esr_60.2.0esr-1~deb9u2.1_i386.deb not working

[Tim Makarios]

On 13/09/18 18:42, Mike Hommey wrote:

Can you install the firefox-esr-dbgsym package from
https://people.debian.org/~glandium/firefox-esr-dbgsym_60.2.0esr-1~deb9u2.1_i386.deb

and run the following command:

gdb firefox-esr

At the gdb prompt, type the following commands:

   set pagination off
   run


When I get to this point, it gives the output:
Starting program: /usr/bin/firefox-esr 
[Thread debugging using libthread_db enabled]

Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
and then thrashes my hard drive for a very long time.  I left it going 
for a while (over half an hour, maybe closer to three quarters of an 
hour), and in the end it seemed to have frozen the computer entirely.


I only have about three quarters of a gigabyte of RAM, which may have 
something to do with it...



   bt full
   x/i $eip

And attach the output.

Thanks

Mike


Cheers,

Tim
<><

Bug#908722: marked as done (invesalius: Fails to upgrade: SyntaxError: Missing parentheses in call to 'print'. Did you mean print("Comecei")?)

[Debian Bug Tracking System]

Your message dated Thu, 13 Sep 2018 09:04:05 +
with message-id 
and subject line Bug#908722: fixed in invesalius 3.1.2-2
has caused the Debian Bug report #908722,
regarding invesalius: Fails to upgrade: SyntaxError: Missing parentheses in 
call to 'print'. Did you mean print("Comecei")?
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.)


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

Hi,

when tying to upgrade invesalius from 3.1.1-1 to 3.1.2-1, it
failed for me as follows:

[…]
Preparing to unpack .../5-invesalius_3.1.2-1_all.deb ...
Unpacking invesalius (3.1.2-1) over (3.1.1-1) ...
[…]
Preparing to unpack .../6-invesalius-bin_3.1.2-1_amd64.deb ...
Unpacking invesalius-bin (3.1.2-1) over (3.1.1-1) ...
[…]
Setting up invesalius-bin (3.1.2-1) ...
[…]
Setting up invesalius (3.1.2-1) ...
  File "/usr/share/invesalius/invesalius/data/editor.py", line 120
print "Comecei"
  ^
SyntaxError: Missing parentheses in call to 'print'. Did you mean 
print("Comecei")?

  File "/usr/share/invesalius/invesalius/data/orientation.py", line 37
print "AXIAL"
^
SyntaxError: Missing parentheses in call to 'print'. Did you mean 
print("AXIAL")?

  File "/usr/share/invesalius/invesalius/data/volume_widgets.py", line 68
print "send signal - update slice info in panel and in 2d"
 ^
SyntaxError: Missing parentheses in call to 'print'. Did you mean print("send 
signal - update slice info in panel and in 2d")?

dpkg: error processing package invesalius (--configure):
 installed invesalius package post-installation script subprocess returned 
error exit status 1
Errors were encountered while processing:
 invesalius

This can also be seen in this piuparts log:
https://piuparts.debian.org/sid/fail/invesalius_3.1.2-1.log

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

Kernel: Linux 4.17.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages invesalius depends on:
ii  invesalius-bin3.1.2-1
ii  python3   3.6.6-1
ii  python3-gdcm  2.8.7-2
ii  python3-nibabel   2.3.0-1
ii  python3-numpy 1:1.14.5-1+b1
ii  python3-pil   5.2.0-2
ii  python3-psutil5.4.6-1+b1
ii  python3-scipy 1.1.0-1+b1
ii  python3-serial3.4-4
ii  python3-skimage   0.14.0-1
ii  python3-vtk7  7.1.1+dfsg1-5
ii  python3-vtkgdcm   2.8.7-2
ii  python3-wxgtk4.0  4.0.1+dfsg-6

invesalius recommends no packages.

invesalius suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: invesalius
Source-Version: 3.1.2-2

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

Debian distribution maintenance software
pp.
Thiago Franco de Moraes  (supplier of updated invesalius 
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: Wed, 12 Sep 2018 10:54:57 -0300
Source: invesalius
Binary: invesalius invesalius-examples invesalius-bin
Architecture: source
Version: 3.1.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Thiago Franco de Moraes 
Description:
 invesalius - 3D medical imaging reconstruction software
 invesalius-bin - Implementation of MIDA and contour based visualizations
 invesalius-examples - examples for 3D medical imaging reconstruction software
Closes: 908722
Changes:
 invesalius (3.1.2-2) unstable; urgency=medium
 .
   * Patch to remove python2 prints
 Closes: 

Processed: tagging 908678

[Debian Bug Tracking System]

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

> tags 908678 + confirmed
Bug #908678 [security-tracker] security-tracker - Breaks salsa.d.o
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Processed: Re: Bug#907079: offlineimap: Not using SNI

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 python-imaplib2
Bug #907079 [offlineimap] offlineimap: Not using SNI
Bug reassigned from package 'offlineimap' to 'python-imaplib2'.
Ignoring request to alter found versions of bug #907079 to the same values 
previously set
Ignoring request to alter fixed versions of bug #907079 to the same values 
previously set
> retitle -1 Not using SNI
Bug #907079 [python-imaplib2] offlineimap: Not using SNI
Changed Bug title to 'Not using SNI' from 'offlineimap: Not using SNI'.
> affects -1 offlineimap
Bug #907079 [python-imaplib2] Not using SNI
Added indication that 907079 affects offlineimap
> forwarded -1 https://github.com/imaplib2/imaplib2/issues/5
Bug #907079 [python-imaplib2] Not using SNI
Set Bug forwarded-to-address to 'https://github.com/imaplib2/imaplib2/issues/5'.

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

Bug#907079: offlineimap: Not using SNI

[Ilias Tsitsimpis]

Control: reassign -1 python-imaplib2
Control: retitle -1 Not using SNI
Control: affects -1 offlineimap
Control: forwarded -1 https://github.com/imaplib2/imaplib2/issues/5

On Sat, Aug 25, 2018 at 08:24PM, Kurt Roeckx wrote:
> This is most likely caused by offlineimap not using SNI and
> google sending an invalid in case you use TLS 1.3 without SNI. I'm
> cloning this bug issue for that.
> [...]
> For more information about this, see:
> https://wiki.openssl.org/index.php/TLS1.3#Server_Name_Indication

Hi Kurt,

Thanks for pointing out the solution.

This should be fixed in python-imaplib2, so I'm reassigning it there.

As a work-around, one could force OfflineIMAP to use TLS 1.2, by setting
the `ssl_version` configuration option to `tls1_2`.

-- 
Ilias

Bug#908708: marked as done (networking-l2gw: FTBFS (ImportError: cannot import name 'topics'))

[Debian Bug Tracking System]

Your message dated Thu, 13 Sep 2018 08:37:24 +
with message-id 
and subject line Bug#908708: fixed in networking-l2gw 1:13.0.0-2
has caused the Debian Bug report #908708,
regarding networking-l2gw: FTBFS (ImportError: cannot import name 'topics')
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.)


-- 
908708: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908708
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:networking-l2gw
Version: 1:12.0.1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
dh build-indep --buildsystem=python_distutils --with python3
   dh_update_autotools_config -i -O--buildsystem=python_distutils
   dh_autoreconf -i -O--buildsystem=python_distutils
   dh_auto_configure -i -O--buildsystem=python_distutils
dh_auto_configure: Please use the third-party "pybuild" build system instead of 
python-distutils
dh_auto_configure: This feature will be removed in compat 12.
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions

[... snipped ...]

from neutron.common import topics as neutron_topics
ImportError: cannot import name 'topics'

Failed to import test module: 
networking_l2gw.tests.unit.services.l2gateway.service_drivers.test_rpc_l2gw
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File 
"/<>/networking_l2gw/tests/unit/services/l2gateway/service_drivers/test_rpc_l2gw.py",
 line 26, in 
from networking_l2gw.services.l2gateway.ovsdb import data
  File "/<>/networking_l2gw/services/l2gateway/ovsdb/data.py", 
line 21, in 
from networking_l2gw.services.l2gateway.common import tunnel_calls
  File 
"/<>/networking_l2gw/services/l2gateway/common/tunnel_calls.py", 
line 16, in 
from neutron.common import topics as neutron_topics
ImportError: cannot import name 'topics'

Failed to import test module: 
networking_l2gw.tests.unit.services.l2gateway.test_agent_scheduler
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File 
"/<>/networking_l2gw/tests/unit/services/l2gateway/test_agent_scheduler.py",
 line 26, in 
from neutron.common import topics
ImportError: cannot import name 'topics'

--
Ran 0 tests in 2.641s

OK
+ subunit-stats
+ subunit-filter -s --no-passthrough
+ cat /tmp/tmp.p2QwnkCvrS
Total tests:   0
Passed tests:  0
Failed tests:  0
Skipped tests: 0
Seen tags: 
+ rm -f /tmp/tmp.p2QwnkCvrS
+ testr-python3 slowest
make[1]: *** [debian/rules:26: override_dh_install] Error 3
make[1]: Leaving directory '/<>'
make: *** [debian/rules:6: binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


The build was made in my autobuilder with "dpkg-buildpackage -A"
but it also fails here:

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

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Unfortunately, I can't compare build logs with the official ones at
buildd.debian.org because they do not exist:

https://buildd.debian.org/status/package.php?p=networking%2dl2gw

Please reconsider uploading in source-only form.

Thanks.
--- End Message ---
--- Begin Message ---
Source: networking-l2gw
Source-Version: 1:13.0.0-2

We believe that the bug you reported is fixed in the latest version of
networking-l2gw, which is due to be installed 

Bug#908014: marked as done (libldm FTBFS with glib 2.58)

[Debian Bug Tracking System]

Your message dated Thu, 13 Sep 2018 08:37:13 +
with message-id 
and subject line Bug#908014: fixed in libldm 0.2.4-2
has caused the Debian Bug report #908014,
regarding libldm FTBFS with glib 2.58
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.)


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

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

...
ldm.c: In function 'ldm_class_init':
ldm.c:303:5: error: 'g_type_class_add_private' is deprecated 
[-Werror=deprecated-declarations]
 g_type_class_add_private(klass, sizeof(LDMPrivate));
 ^~~~
In file included from /usr/include/glib-2.0/gobject/gobject.h:24,
 from /usr/include/glib-2.0/gobject/gbinding.h:29,
 from /usr/include/glib-2.0/glib-object.h:23,
 from ldm.h:21,
 from ldm.c:40:
/usr/include/glib-2.0/gobject/gtype.h:1303:10: note: declared here
 void g_type_class_add_private   (gpointerg_class,
  ^~~~
...
--- End Message ---
--- Begin Message ---
Source: libldm
Source-Version: 0.2.4-2

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

Debian distribution maintenance software
pp.
Hilko Bengen  (supplier of updated libldm 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: Thu, 13 Sep 2018 09:35:45 +0200
Source: libldm
Binary: libldm-dev libldm-1.0-0 ldmtool
Architecture: source
Version: 0.2.4-2
Distribution: unstable
Urgency: medium
Maintainer: Hilko Bengen 
Changed-By: Hilko Bengen 
Description:
 ldmtool- tool for managing Microsoft Windows dynamic disks
 libldm-1.0-0 - library for managing Microsoft Windows dynamic disks
 libldm-dev - library for managing Microsoft Windows dynamic disks
Closes: 908014
Changes:
 libldm (0.2.4-2) unstable; urgency=medium
 .
   * Fix FTBFS due to use of deprecated glib function (Closes: #908014)
   * Bump Standards-Version
   ' Add .symbols file
Checksums-Sha1:
 10251c997c02ba6ea257b375f6d8103e119fc491 2065 libldm_0.2.4-2.dsc
 cd3ca2871be1176f6b78e6dd79a4415c6badf947 3768 libldm_0.2.4-2.debian.tar.xz
 0a845fc40bec68c49a8dbad8cec424cc3d3b3ad5 7455 libldm_0.2.4-2_source.buildinfo
Checksums-Sha256:
 c38b4aab4806f6d8af45db6214f1d37ab424b88205b117e74694f73711e79d99 2065 
libldm_0.2.4-2.dsc
 b500cf83460be56bc8f91cc2ff6ca823eec0166b4e52ec004c70bfeb0898363d 3768 
libldm_0.2.4-2.debian.tar.xz
 53b58fda997f3bc43b8fa10cf2101bcce641b0193c55ce7fe5af9bb07f8900d9 7455 
libldm_0.2.4-2_source.buildinfo
Files:
 9e1b334e3f5a238679286b4fef0b4865 2065 libs optional libldm_0.2.4-2.dsc
 d210027ef2d5d82367a9c0edab912b9d 3768 libs optional 
libldm_0.2.4-2.debian.tar.xz
 4a2657072de87ca5e80bf60d2b2c5a59 7455 libs optional 
libldm_0.2.4-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCAAwFiEErnMQVUQqHZbPTUx4dbcQY1whOn4FAluaG4oSHGJlbmdlbkBk
ZWJpYW4ub3JnAAoJEHW3EGNcITp+ZDEP/3FnWe+9rl4IWcp7p+lHIRrat/3O2GZE
OtV1aRgw1Mq4iA6pCQj9WV2y5zwHRelMw53K3Qrsbt6VsF6wCGX1dOtbSIsfkhBL
1OeLuOoY3zQxk4VGVriffNLOUupc8AU7QfJQnStrynfeS++OuLiC/uDtW7TKHcuU
R/2G+haZh4cYucZJbGQx/u2uItPl+IA4ycYS23wMOjV/+WNphidrR7L7DvlyWgO/
Bi253iwifkqXrasqL04p+x39s+55m7LNnURpbWo/9YLcNWVLkSK2Is6QrXZ5BQz3
Fw+P+WZATvh8UJs5jUPyx5Rhuo3D5NlfaGF9kXPRjR9xRJ3a8jXNvMeJVVQ9TRg5
Oj56EUeV/8m+LW3S2c+dpti06co/u8CXwNEslL6fBBpx4lRtPUrywq9ZhWlojlxh
AZjXBDY6yyIxlwTr5x94Nb1vFqQFPlbhJe5r7jb8fw1L7vY+jhmJ9sNB38QGpfMy
gGABAZGQW5D19wD5bW9hByJDpnGr2rXhyfhB7e30mXDE30p35S4G2+66SHhfk1eQ
ENRsP2UizFtn9inDzYIdAYif3KiYz6V8W5dvtzDK7w/8TF2t3KoufwPmOXQeV84q
A5sG75ABAq5t+juS1TqD1+qP3UzTKc09OgrVuirXpW8aVz2DFMiMtboMRrqs+b0D
6IZTRMMeax4N
=34vk
-END PGP SIGNATURE End Message ---

Bug#908708: [PKG-Openstack-devel] Bug#908708: networking-l2gw: FTBFS (ImportError: cannot import name 'topics')

[Thomas Goirand]

On 09/13/2018 02:50 AM, Santiago Vila wrote:
> reopen 908708
> thanks
> 
> On Thu, 13 Sep 2018, Thomas Goirand wrote:
> 
>> Feel free to open a new bug for the Sid
>> version, that would help a way more.
> 
> Ok, here it is the bug for the sid version.
> 
> I reported against 1:12.0.1-1 which is already the sid version.
> When built under sid it fails in exactly the same way it failed
> for me under buster.
> 
> However:
> 
> $ rmadison networking-l2gw
> networking-l2gw | 1:1.0.0+git20160927.29cb4fe3-1 | stable   | source
> networking-l2gw | 1:12.0.1-1 | testing  | source
> networking-l2gw | 1:12.0.1-1 | unstable | source
> networking-l2gw | 1:13.0.0-1 | experimental | source
> 
> Maybe you forgot to upload 1:13.0.0-1 for unstable?
> 
> For the record, I only report bugs against packages having the same
> version in buster and sid (as in this case), and only when the package
> fails in sid according to reproducible builds (as in this case).
> 
> Sometimes the package fails in buster and sid for completely different
> reasons and that would be a false positive, but that's not what it
> happened here.
> 
> (And no, I'm not going to build packages in experimental, I'm not a
> cyborg either :-).
> 
> Thanks.

Oh, Santiago, now I feel very much sorry with the way I replied. Indeed,
I forgot to upload, and the version from Experimental failed in a
slightly different way, because one test was missing a new parameter
from ovs.jsonrpc.Session(). I added the parameter in the unit test, and
now it works. I uploaded the package, it should be all good now.

Thanks for your bug report, and checking the Sid version as well.

Cheers,

Thomas Goirand (zigo)

Bug#906050: Just waiting for octave...

[Ole Streicher]

Control: block -1 by 906047
Control: tags -1 pending

I just wait for the new Octave to be uploaded to unstable -- #906047 is
fixed in experimental, but not there.

Cheers

Ole