Bug#910485: libpsm2-2: times out on /dev/hfi1_0 device and causes test errors

[Drew Parsons]

Package: libpsm2-2
Version: 11.2.68-1
Severity: serious
Justification: causes other packages to fail tests; interferes with efficient 
execution; regression

Programs running with libpsm2-2 11.2.68-1 now emit the warning:
> ci-1538433288.12336hfi_wait_for_device: The /dev/hfi1_0 device failed to 
> appear after 15.0 seconds: Connection timed out

which registers as an error in tests (I presume the warning is sent
to stdout)

This causes some tests and debci tests to fail, for instance petsc
https://ci.debian.net/data/autopkgtest/unstable/amd64/p/petsc/1080389/log.gz

I think it must fail because of the new involvement of stderr. Some
other tests still pass, e.g. dolfin
https://ci.debian.net/data/autopkgtest/unstable/amd64/d/dolfin/1080544/log.gz


In any case, this bug holds up execution for 15 secs or more, which
itself is not good and is a regression from 10.3.58-2




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

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

Versions of packages libpsm2-2 depends on:
ii  libc6 2.27-6
ii  libnuma1  2.0.12-1

libpsm2-2 recommends no packages.

libpsm2-2 suggests no packages.

-- no debconf information

Bug#898705: #898705 android-platform-libcore FTBFS with debhelper v11

[Dmitry Smirnov]

It would be great to fix this bug in "unstable" to prevent auto-removal of 
Zabbix from "testing"...

Thanks.

-- 
All the best,
 Dmitry Smirnov

---

Moral courage is the most valuable and usually the most absent
characteristic in men.
-- George S. Patton


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

Bug#902759:

[Nicholas D Steeves]

Hello,

On Thu, Aug 02, 2018 at 09:22:12PM +1200, Michael Hudson-Doyle wrote:
>I cherry picked the attached patch from upstream to fix this in Ubuntu
>(it's just regenerating the .c files with a newer cython).

> From f4811786a50b95699b315169596a6090f4be3d65 Mon Sep 17 00:00:00 2001
> From: tomis007 
> Date: Tue, 3 Jul 2018 20:01:32 -0400
> Subject: [PATCH] regenerated with cython 0.28.3
> 
> ---
>  http_parser/parser.c | 10470 
> -
>  1 file changed, 6972 insertions(+), 3498 deletions(-)
> 

Just to confirm, none of the following is useful for the Debian
package, nor for correct DebCI functioning, right?
  
https://github.com/douban/pymesos/pull/109/commits/6ebaf93c2e76f49586faf1e6d5f7ca2cc9c7ee03

I'd like to see the patch Michael cherry picked applied to resolve
this bug :-)

Cheers,
Nicholas


signature.asc
Description: PGP signature

Bug#910226: closed by Georges Khaznadar (Bug#910226: fixed in expeyes 4.4.4+dfsg-2)

[Andreas Beckmann]

Control: found -1 4.4.4+dfsg-2

On 2018-10-05 17:54, Debian Bug Tracking System wrote:
>* added confilcts/replaces for python3-expeyes << 4.3. Closes: #910226

I don't see how this was supposed to fix the buggy maintainer script in
this package ...

Andreas

Processed: Re: Bug#910226 closed by Georges Khaznadar (Bug#910226: fixed in expeyes 4.4.4+dfsg-2)

[Debian Bug Tracking System]

Processing control commands:

> found -1 4.4.4+dfsg-2
Bug #910226 {Done: Georges Khaznadar } [expeyes-web] 
expeyes-web: fails to upgrade from 'stretch': Exception: cannot get content of 
python3-expeyes
Marked as found in versions expeyes/4.4.4+dfsg-2; no longer marked as fixed in 
versions expeyes/4.4.4+dfsg-2 and reopened.

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

Bug#910480: ghc: missing Breaks+Replaces+Provides for newly bundled libraries

[Andreas Beckmann]

Package: ghc
Version: 8.4.3+dfsg1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: block 910008 with -1
Control: block 910202 with -1

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

See the blocked bugs for the full logs, here are only excerpts:

---
  Preparing to unpack .../libghc-mtl-dev_2.2.2-2_amd64.deb ...
  Unpacking libghc-mtl-dev (2.2.2-2) over (2.2.2-1) ...
  Preparing to unpack .../gcc_4%3a8.2.0-1_amd64.deb ...
  Unpacking gcc (4:8.2.0-1) over (4:8.1.0-1) ...
  Preparing to unpack .../cpp_4%3a8.2.0-1_amd64.deb ...
  Unpacking cpp (4:8.2.0-1) over (4:8.1.0-1) ...
  Preparing to unpack .../ghc_8.4.3+dfsg1-2_amd64.deb ...
  Unpacking ghc (8.4.3+dfsg1-2) over (8.2.2-4) ...
  dpkg: error processing archive 
/var/cache/apt/archives/ghc_8.4.3+dfsg1-2_amd64.deb (--unpack):
   trying to overwrite '/var/lib/ghc/package.conf.d/mtl-2.2.2.conf', which is 
also in package libghc-mtl-dev 2.2.2-2
  update-alternatives: using /usr/bin/runghc to provide /usr/bin/runhaskell 
(runhaskell) in auto mode
  update-alternatives: using /usr/bin/ghc to provide /usr/bin/haskell-compiler 
(haskell-compiler) in auto mode
  There are problems in package mtl-2.2.2:
dependency "base-4.11.1.0" doesn't exist
dependency "transformers-0.5.5.0" doesn't exist
  
  The following packages are broken, either because they have a problem
  listed above, or because they depend on a broken package.
  mtl-2.2.2
  Preparing to unpack .../libgnutls30_3.5.19-1+b1_amd64.deb ...
  Unpacking libgnutls30:amd64 (3.5.19-1+b1) over (3.5.19-1) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/ghc_8.4.3+dfsg1-2_amd64.deb
---
  Selecting previously unselected package libghc-parsec3-dev.
  (Reading database ... 
(Reading database ... 10244 files and directories currently installed.)
  Preparing to unpack .../libghc-parsec3-dev_3.1.13.0-3_amd64.deb ...
  Unpacking libghc-parsec3-dev (3.1.13.0-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libghc-parsec3-dev_3.1.13.0-3_amd64.deb (--unpack):
   trying to overwrite '/var/lib/ghc/package.conf.d/parsec-3.1.13.0.conf', 
which is also in package ghc 8.4.3+dfsg1-2
  Errors were encountered while processing:
   /var/cache/apt/archives/libghc-parsec3-dev_3.1.13.0-3_amd64.deb
---


I think these bugs actually belong to ghc which started bundling more
libraries with the recent upload to unstable. 


I would suggest to add the following:

Breaks:
 libghc-mtl-dev (<< 2.2.2+),
 libghc-parsec3-dev (<< 3.1.13.0+),
Replaces:
 libghc-mtl-dev (<< 2.2.2+),
 libghc-parsec3-dev (<< 3.1.13.0+),
Provides:
 libghc-mtl-dev,
 libghc-parsec3-dev,

There may be more packages affected, but testing them is probably
blocked by libghc-mtl-dev

I used "${current_upstream_version}+" as version bound, since e.g.
"1.2.3+" sorts before new upstream versions like
  1.2.3+dfsg, 1.2.3.1
in addition to
  1.2.4, 1.5.3


cheers,

Andreas

Processed: ghc: missing Breaks+Replaces+Provides for newly bundled libraries

[Debian Bug Tracking System]

Processing control commands:

> block 910008 with -1
Bug #910008 [libghc-mtl-dev] haskell-mtl: Package libghc-mtl-dev not 
co-installable with ghc due to file conflicts
910008 was not blocked by any bugs.
910008 was not blocking any bugs.
Added blocking bug(s) of 910008: 910480
> block 910202 with -1
Bug #910202 [libghc-parsec3-dev] libghc-parsec3-dev: ships 
/var/lib/ghc/package.conf.d/parsec-3.1.13.0.conf which is now also in ghc
910202 was not blocked by any bugs.
910202 was not blocking any bugs.
Added blocking bug(s) of 910202: 910480

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

Processed: bug 906623 is forwarded to https://github.com/heimdal/heimdal/issues/435

[Debian Bug Tracking System]

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

> forwarded 906623 https://github.com/heimdal/heimdal/issues/435
Bug #906623 [src:heimdal] heimdal: FTBFS in buster/sid (hcrypto/engine.h: No 
such file or directory)
Set Bug forwarded-to-address to 'https://github.com/heimdal/heimdal/issues/435'.
> thanks
Stopping processing here.

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

Bug#910311: elpy FTBFS randomly: test elpy-promise-wait-should-return-early-for-resolved-promise fails

[Nicholas D Steeves]

Update 2: elpy-promise-wait-should-return-early-for-resolved-promise
fails 30% to 40% of the time in an schroot with Python 3.6.7rc1 as
/usr/bin/python3.  I changed the symlink to point to
/usr/bin/python3.7 (Python 3.7.1rc1) and this test passed 100% of the
time.  I ran the test 50 times.

I believe python3.6/3.6.7~rc1-1 is at fault (released Thu, 27 Sep 2018
11:51:25 +0200), because this test passes with 3.6.6-4 (from Sat, 01
Sep 2018 03:05:25 +0200).  This is the thing that changed in sid
(after Sept 4th) leading to the failure of
elpy-promise-wait-should-return-early-for-resolved-promise.

I'm contacting #debian-python about how to proceed.

Cheers,
Nicholas


signature.asc
Description: PGP signature

Bug#910443: gir-to-d FTBFS: Error: Expected argument to '-I'

[Helmut Grohne]

On Sat, Oct 06, 2018 at 08:35:44PM +0200, Matthias Klumpp wrote:
> This looks like a bug in Meson... I will take a look.

That wouldn't be the first one...

Though when comparing with the most recent logs from buildds, you spot:

... -I. -I.. -I../source/ -I -enable-color ...

This looks like meson recently added the = between flag and path and it
looks like you were trying to use ./-enable-color as an include
directory. So maybe it was buggy already, but it wasn't fatal until now.

If you reassign to meson, please don't forget "affects -1 +
src:gir-to-d".

Helmut

Bug#906315: spice: diff for NMU version 0.14.0-1.1

[Salvatore Bonaccorso]

Control: tags 906315 + pending


Dear maintainer,

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

Regards,
Salvatore
diff -Nru spice-0.14.0/debian/changelog spice-0.14.0/debian/changelog
--- spice-0.14.0/debian/changelog	2017-10-19 08:35:54.0 +0200
+++ spice-0.14.0/debian/changelog	2018-09-15 09:15:28.0 +0200
@@ -1,3 +1,10 @@
+spice (0.14.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix flexible array buffer overflow (CVE-2018-10873) (Closes: #906315)
+
+ -- Salvatore Bonaccorso   Sat, 15 Sep 2018 09:15:28 +0200
+
 spice (0.14.0-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru spice-0.14.0/debian/patches/Fix-flexible-array-buffer-overflow.patch spice-0.14.0/debian/patches/Fix-flexible-array-buffer-overflow.patch
--- spice-0.14.0/debian/patches/Fix-flexible-array-buffer-overflow.patch	1970-01-01 01:00:00.0 +0100
+++ spice-0.14.0/debian/patches/Fix-flexible-array-buffer-overflow.patch	2018-09-15 09:15:28.0 +0200
@@ -0,0 +1,68 @@
+From: Frediano Ziglio 
+Date: Fri, 18 May 2018 11:41:57 +0100
+Subject: Fix flexible array buffer overflow
+Origin: https://gitlab.freedesktop.org/spice/spice-common/commit/bb15d4815ab586b4c4a20f4a565970a44824c42c
+Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2018-10873
+Bug-Debian: https://bugs.debian.org/906315
+
+This is kind of a DoS, possibly flexible array in the protocol
+causes the network size check to be ignored due to integer overflows.
+
+The size of flexible array is computed as (message_end - position),
+then this size is added to the number of bytes before the array and
+this number is used to check if we overflow initial message.
+
+An example is:
+
+message {
+uint32 dummy[2];
+uint8 data[] @end;
+} LenMessage;
+
+which generated this (simplified remove useless code) code:
+
+{ /* data */
+data__nelements = message_end - (start + 8);
+
+data__nw_size = data__nelements;
+}
+
+nw_size = 8 + data__nw_size;
+
+/* Check if message fits in reported side */
+if (nw_size > (uintptr_t) (message_end - start)) {
+return NULL;
+}
+
+Following code:
+- data__nelements == message_end - (start + 8)
+- data__nw_size == data__nelements == message_end - (start + 8)
+- nw_size == 8 + data__nw_size == 8 + message_end - (start + 8) ==
+  8 + message_end - start - 8 == message_end -start
+- the check for overflow is (nw_size > (message_end - start)) but
+  nw_size == message_end - start so the check is doing
+  ((message_end - start) > (message_end - start)) which is always false.
+
+If message_end - start < 8 then data__nelements (number of element
+on the array above) computation generate an integer underflow that
+later create a buffer overflow.
+
+Add a check to make sure that the array starts before the message ends
+to avoid the overflow.
+
+Signed-off-by: Frediano Ziglio 
+Signed-off-by: Christophe Fergeau 
+[Salvatore Bonaccorso: Drop generated diff from commit messages causing
+ problem when applying with quilt. Remove addition to testsuite]
+---
+
+--- a/spice-common/python_modules/demarshal.py
 b/spice-common/python_modules/demarshal.py
+@@ -318,6 +318,7 @@ def write_validate_array_item(writer, co
+ writer.assign(nelements, array.size)
+ elif array.is_remaining_length():
+ if element_type.is_fixed_nw_size():
++writer.error_check("%s > message_end" % item.get_position())
+ if element_type.get_fixed_nw_size() == 1:
+ writer.assign(nelements, "message_end - %s" % item.get_position())
+ else:
diff -Nru spice-0.14.0/debian/patches/series spice-0.14.0/debian/patches/series
--- spice-0.14.0/debian/patches/series	1970-01-01 01:00:00.0 +0100
+++ spice-0.14.0/debian/patches/series	2018-09-15 09:15:28.0 +0200
@@ -0,0 +1 @@
+Fix-flexible-array-buffer-overflow.patch

Processed: spice: diff for NMU version 0.14.0-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 906315 + pending
Bug #906315 [src:spice] spice: CVE-2018-10873: Missing check in 
demarshal.py:write_validate_array_item() allows for buffer overflow and denial 
of service
Added tag(s) pending.

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

Bug#910448: mgetty: CVE-2018-16741

[Andreas Barth]

* Salvatore Bonaccorso (car...@debian.org) [181006 21:21]:
> FTR, I think if feasible best would be to go for unstable (and thus
> buster) directly to 1.2.1, which will adress as well the other CVEs
> (which were no-dsa or unimportant).

That's the plan, yes.


Andi

Bug#907998: gimp: Gimp does not load or crashes quickly

[Luis Mochan]

Package: gimp
Version: 2.10.6-3
Followup-For: Bug #907998

I rebooted my system (several update/upgrade cycles since previous
reboot) and my problem seems to have disappeared. I do get the same warnings
messages related to some missing blab conversions, but now gimp seems to
proceed with it's work. Sorry for the noise.

Regards,
Luis


-- 

  o
W. Luis Mochán,  | tel:(52)(777)329-1734 /<(*)
Instituto de Ciencias Físicas, UNAM  | fax:(52)(777)317-5388 `>/   /\
Apdo. Postal 48-3, 62251 |   (*)/\/  \
Cuernavaca, Morelos, México  | moc...@fis.unam.mx   /\_/\__/
GPG: 791EB9EB, C949 3F81 6D9B 1191 9A16  C2DF 5F0A C52B 791E B9EB

Bug#910448: mgetty: CVE-2018-16741

[Salvatore Bonaccorso]

Hi,

FTR, I think if feasible best would be to go for unstable (and thus
buster) directly to 1.2.1, which will adress as well the other CVEs
(which were no-dsa or unimportant).

Regards,
Salvatore

Processed: tagging 910466

[Debian Bug Tracking System]

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

> tags 910466 + ftbfs
Bug #910466 [src:quassel-irssi] quassel-irssi: FTBFS with gcc-8
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 910468

[Debian Bug Tracking System]

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

> tags 910468 + ftbfs
Bug #910468 [src:pluto-sat-code] pluto-sat-code: FTBFS: dh_installdocs: Cannot 
find (any matches for) "README.Debian" (tried in .)
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#907998: gimp: Gimp does not load or crashes quickly

[Luis Mochan]

Package: gimp
Version: 2.10.6-3
Followup-For: Bug #907998

It seems I have the same problem. Gimp seems to hang forever when I
start it either from a terminal or from the menu. I read about
removing my personal GIMP configuration directory, but it didn't change
anything, and about removing libopenblas, but I don't have openblas
installed. I do have blas, though:
$ aptitude search blas|grep -E ^i
i A libblas-dev - Basic Linear Algebra Subroutines 3, static library
i A libblas3 - Basic Linear Algebra Reference implementations, shared library
i A libgslcblas0 - GNU Scientific Library (GSL) -- blas library package

Regards,
Luis


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

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

Versions of packages gimp depends on:
ii  gimp-data2.10.6-3
ii  libaa1   1.4p5-44+b2
ii  libbabl-0.1-01:0.1.56-dmo1
ii  libbz2-1.0   1.0.6-9
ii  libc62.27-6
ii  libcairo21.15.12-1
ii  libfontconfig1   2.13.1-1
ii  libfreetype6 2.8.1-2
ii  libgcc1  1:8.2.0-7
ii  libgdk-pixbuf2.0-0   2.38.0+dfsg-6
ii  libgegl-0.4-01:0.4.8-dmo2
ii  libgexiv2-2  0.10.8-1
ii  libgimp2.0   2.10.6-3
ii  libglib2.0-0 2.58.1-2
ii  libgs9   9.25~dfsg-2
ii  libgtk2.0-0  2.24.32-3
ii  libgudev-1.0-0   232-2
ii  libharfbuzz0b1.9.0-1
ii  libheif1 1.3.2-1
ii  libilmbase23 2.2.1-2
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  liblcms2-2   2.9-3
ii  liblzma5 5.2.2-1.3
ii  libmng1  1.0.10+dfsg-3.1+b5
ii  libmypaint-1.3-0 1:1.3.0-dmo6
ii  libopenexr23 2.2.1-4
ii  libopenjp2-7 2.3.0-1
ii  libpango-1.0-0   1.42.4-3
ii  libpangocairo-1.0-0  1.42.4-3
ii  libpangoft2-1.0-01.42.4-3
ii  libpng16-16  1.6.34-2
ii  libpoppler-glib8 0.63.0-2
ii  librsvg2-2   2.40.20-3
ii  libstdc++6   8.2.0-7
ii  libtiff5 4.0.9-6
ii  libwebp6 0.6.1-2
ii  libwebpdemux20.6.1-2
ii  libwebpmux3  0.6.1-2
ii  libwmf0.2-7  0.2.8.4-12
ii  libx11-6 2:1.6.6-1
ii  libxcursor1  1:1.1.15-1
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-1
ii  libxmu6  2:1.1.2-2
ii  libxpm4  1:3.5.12-1
ii  xdg-utils1.1.3-1
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages gimp recommends:
ii  ghostscript  9.25~dfsg-2

Versions of packages gimp suggests:
pn  gimp-data-extras  
ii  gimp-help-en [gimp-help]  2.8.2-0.1
pn  gimp-python   
ii  gvfs-backends 1.38.0-2
ii  libasound21.1.6-1

-- no debconf information

-- 

  o
W. Luis Mochán,  | tel:(52)(777)329-1734 /<(*)
Instituto de Ciencias Físicas, UNAM  | fax:(52)(777)317-5388 `>/   /\
Apdo. Postal 48-3, 62251 |   (*)/\/  \
Cuernavaca, Morelos, México  | moc...@fis.unam.mx   /\_/\__/
GPG: 791EB9EB, C949 3F81 6D9B 1191 9A16  C2DF 5F0A C52B 791E B9EB

Bug#910443: gir-to-d FTBFS: Error: Expected argument to '-I'

[Matthias Klumpp]

Am Sa., 6. Okt. 2018 um 14:45 Uhr schrieb Helmut Grohne :
>
> Source: gir-to-d
> Version: 0.16.1-1
> Severity: serious
> Tags: ftbfs
>
> gir-to-d fails to build from source in sbuild on unstable/amd64. A build
> log ends with:
>
> | dh build --buildsystem=meson
> |dh_update_autotools_config -O--buildsystem=meson
> |dh_autoreconf -O--buildsystem=meson
> |dh_auto_configure -O--buildsystem=meson
> | cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
> --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
> --localstatedir=/var --libdir=lib/x86_64-linux-gnu 
> --libexecdir=lib/x86_64-linux-gnu
> | The Meson build system
> | Version: 0.48.0
> | Source dir: /<>
> | Build dir: /<>/obj-x86_64-linux-gnu
> | Build type: native build
> | Project name: GIR-to-D
> | Project version: 0.16.0
> | Appending DFLAGS from environment: '-O -g -release -wi'
> | Appending LDFLAGS from environment: '-Wl,-z,relro'
> | Native D compiler: ldc2 (llvm 1.11.0 "LDC - the LLVM D compiler (1.11.0):")
> | Build machine cpu family: x86_64
> | Build machine cpu: x86_64
> | Build targets in project: 2
> | Found ninja-1.8.2 at /usr/bin/ninja
> |dh_auto_build -O--buildsystem=meson
> | cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j1 -v
> | [1/20] /usr/bin/meson --internal vcstagger ../VERSION.in VERSION 0.16.0 
> /<> @VCS_TAG@ '(.*)' /<>/git describe --dirty=+ 
> --tags
> | [2/20] ldc2 -I=girtod@exe -I=. -I=.. -I=../source/ -I= -enable-color 
> -J/<>/obj-x86_64-linux-gnu -O -g -release -wi   
> -of='girtod@exe/source_girtod.d.o' -c ../source/girtod.d
> | FAILED: girtod@exe/source_girtod.d.o
> | ldc2 -I=girtod@exe -I=. -I=.. -I=../source/ -I= -enable-color 
> -J/<>/obj-x86_64-linux-gnu -O -g -release -wi   
> -of='girtod@exe/source_girtod.d.o' -c ../source/girtod.d
> | Error: Expected argument to '-I'
> | ninja: build stopped: subcommand failed.
> | dh_auto_build: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j1 -v 
> returned exit code 1
> | make: *** [debian/rules:8: build] Error 1
> | dpkg-buildpackage: error: debian/rules build subprocess returned exit 
> status 2

This looks like a bug in Meson... I will take a look.

Cheers,
Matthias

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

Bug#910468: pluto-sat-code: FTBFS: dh_installdocs: Cannot find (any matches for) "README.Debian" (tried in .)

[Andreas Beckmann]

Source: pluto-sat-code
Version: 0.0~git20180301-1
Severity: serious
Justification: fails to build from source

Hi,

pluto-sat-code FTBFS in an up-to-date sid+experimental pbuilder
environment, probably due to some changes in debhelper:

[...]
   dh_auto_test
   create-stamp debian/debhelper-build-stamp
 fakeroot debian/rules binary
dh binary
   dh_testroot
   dh_prep
   dh_installdirs
   debian/rules override_dh_auto_install
make[1]: Entering directory '/build/pluto-sat-code-0.0~git20180301'
Not invoking makefile's install target
make[1]: Leaving directory '/build/pluto-sat-code-0.0~git20180301'
   dh_install
   dh_installdocs
dh_installdocs: Cannot find (any matches for) "README.Debian" (tried in .)

make: *** [debian/rules:10: binary] Error 2


Andreas


pluto-sat-code_0.0~git20180301-1.log.gz
Description: application/gzip

Bug#910466: quassel-irssi: FTBFS with gcc-8

[Andreas Beckmann]

Source: quassel-irssi
Version: 0~git20180408-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

quassel-irssi FTBFS in an up-to-date sid+experimental pbuilder environment,
probably due to the switch of the default compiler to gcc-8.

 debian/rules build
dh build
   dh_update_autotools_config
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/quassel-irssi-0~git20180408'
/usr/bin/make -C core
make[2]: Entering directory '/build/quassel-irssi-0~git20180408/core'
cc -std=gnu11 -Wall -Wextra -Werror -g -O2 -I/usr/include/irssi//src/ 
-I/usr/include/irssi//src/core/ -I/usr/include/irssi//src/fe-common/ 
-I/usr/include/irssi//src/fe-common/core/ -I/usr/include/irssi//src/fe-tex
t/ -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-DUOFF_T_LONG -fPIC -DHAVE_OPENSSL -I/usr/include/quasselc -Wmissing-prototypes 
-Wmissing-declarations  -Wdate-time -D_FORTIFY_SOURCE=2  -c -
o quasselc-connector.o quasselc-connector.c
cc -std=gnu11 -Wall -Wextra -Werror -g -O2 -I/usr/include/irssi//src/ 
-I/usr/include/irssi//src/core/ -I/usr/include/irssi//src/fe-common/ 
-I/usr/include/irssi//src/fe-common/core/ -I/usr/include/irssi//src/fe-tex
t/ -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-DUOFF_T_LONG -fPIC -DHAVE_OPENSSL -I/usr/include/quasselc -Wmissing-prototypes 
-Wmissing-declarations  -Wdate-time -D_FORTIFY_SOURCE=2  -c -
o quassel-core.o quassel-core.c
cc -std=gnu11 -Wall -Wextra -Werror -g -O2 -I/usr/include/irssi//src/ 
-I/usr/include/irssi//src/core/ -I/usr/include/irssi//src/fe-common/ 
-I/usr/include/irssi//src/fe-common/core/ -I/usr/include/irssi//src/fe-text/ 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-DUOFF_T_LONG -fPIC -DHAVE_OPENSSL -I/usr/include/quasselc -Wmissing-prototypes 
-Wmissing-declarations  -Wdate-time -D_FORTIFY_SOURCE=2  -c -o quassel-net.o 
quassel-net.c
quassel-net.c: In function 'sig_connected':
quassel-net.c:110:8: error: cast between incompatible function types from 'void 
(*)(Quassel_SERVER_REC *)' {aka 'void (*)(struct Quassel_SERVER_REC_s *)'} to 
'void (*)(void *, GIOChannel *, int)' {aka 'void (*)(void *, struct _GIOChannel 
*, int)'} [-Werror=cast-function-type]
(GInputFunction) quassel_parse_incoming, r);
^
In file included from /usr/include/irssi//src/core/commands.h:4,
 from quassel-net.c:25:
quassel-net.c: In function 'quassel_net_init':
quassel-net.c:161:39: error: cast between incompatible function types from 
'void (*)(Quassel_SERVER_REC *)' {aka 'void (*)(struct Quassel_SERVER_REC_s 
*)'} to 'void (*)(const void *, const void *, const void *, const void *, const 
void *, const void *)' [-Werror=cast-function-type]
  signal_add_first("server connected", (SIGNAL_FUNC) sig_connected);
   ^
/usr/include/irssi//src/core/signals.h:23:78: note: in definition of macro 
'signal_add_first'
  signal_add_full(MODULE_NAME, SIGNAL_PRIORITY_HIGH, (signal), (SIGNAL_FUNC) 
(func), NULL)
  
^~~~
cc1: all warnings being treated as errors
make[2]: *** [: quassel-net.o] Error 1
make[2]: Leaving directory '/build/quassel-irssi-0~git20180408/core'
make[1]: *** [debian/rules:15: override_dh_auto_build] Error 2
make[1]: Leaving directory '/build/quassel-irssi-0~git20180408'
make: *** [debian/rules:12: build] Error 2


Andreas


quassel-irssi_0~git20180408-1.log.gz
Description: application/gzip

Bug#907227: marked as done (equalx: FTBFS with Qt 5.11)

[Debian Bug Tracking System]

Your message dated Sat, 06 Oct 2018 17:49:25 +
with message-id 
and subject line Bug#907227: fixed in equalx 0.7.1-4.1
has caused the Debian Bug report #907227,
regarding equalx: FTBFS with Qt 5.11
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.)


-- 
907227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907227
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:equalx
Version: 0.7.1-4
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 '/<>'
/usr/bin/qmake -qt5 -makefile -nocache QMAKE_LFLAGS_RELEASE="-Wl,-z,relro" 
QMAKE_CFLAGS_RELEASE="-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security" 
QMAKE_CXXFLAGS_RELEASE="-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security" 
QMAKE_CPPFLAGS_RELEASE="-Wdate-time -D_FORTIFY_SOURCE=2" PREFIX=/usr/bin
Info: creating stash file /<>/.qmake.stash
Project MESSAGE: Qt version: 5.11.1
WARNING: target.path is not defined: install target not created

make[1]: Leaving directory '/<>'
   dh_auto_build -a -O--parallel
make -j1
make[1]: Entering directory '/<>'
/usr/lib/qt5/bin/uic ui/mainwindow.ui -o ui_mainwindow.h
/usr/lib/qt5/bin/uic ui/dialogPreferences.ui -o ui_dialogPreferences.h
/usr/lib/qt5/bin/uic ui/dialogAbout.ui -o ui_dialogAbout.h
/usr/lib/qt5/bin/uic ui/dialogReplace.ui -o ui_dialogReplace.h
/usr/lib/qt5/bin/uic ui/widgetFind.ui -o ui_widgetFind.h
/usr/lib/qt5/bin/uic ui/BookmarksPanel/DialogPreferencesFolder.ui -o 
ui_DialogPreferencesFolder.h
/usr/lib/qt5/bin/uic ui/BookmarksPanel/DialogPreferencesBookmark.ui -o 
ui_DialogPreferencesBookmark.h
/usr/lib/qt5/bin/uic ui/BookmarksPanel/BookmarksWidget.ui -o 
ui_BookmarksWidget.h
/usr/lib/qt5/bin/uic ui/HistoryPanel/HistoryWidget.ui -o ui_HistoryWidget.h
g++ -c -pipe -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -D_REENTRANT -Wall -W 
-fPIC -DQT_NO_DEBUG_OUTPUT -DUNIX_PLATFORM -DQT_NO_DEBUG -DQT_WIDGETS_LIB 
-DQT_GUI_LIB -DQT_SQL_LIB -DQT_CORE_LIB -I. -isystem /usr/include/exempi-2.0 
-Iinclude -Iinclude/Library -Iinclude/BookmarksPanel -Iinclude/HistoryPanel 
-isystem /usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtSql -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -Itmp -isystem /usr/include/libdrm -I. 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o File.o src/File.cpp
g++ -c -pipe -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -D_REENTRANT -Wall -W 
-fPIC -DQT_NO_DEBUG_OUTPUT -DUNIX_PLATFORM -DQT_NO_DEBUG -DQT_WIDGETS_LIB 
-DQT_GUI_LIB -DQT_SQL_LIB -DQT_CORE_LIB -I. -isystem /usr/include/exempi-2.0 
-Iinclude -Iinclude/Library -Iinclude/BookmarksPanel -Iinclude/HistoryPanel 
-isystem /usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtSql -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -Itmp -isystem /usr/include/libdrm -I. 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o main.o src/main.cpp
g++ -c -pipe -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -D_REENTRANT -Wall -W 
-fPIC -DQT_NO_DEBUG_OUTPUT -DUNIX_PLATFORM -DQT_NO_DEBUG -DQT_WIDGETS_LIB 
-DQT_GUI_LIB -DQT_SQL_LIB -DQT_CORE_LIB -I. -isystem /usr/include/exempi-2.0 
-Iinclude -Iinclude/Library -Iinclude/BookmarksPanel -Iinclude/HistoryPanel 
-isystem /usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtSql -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -Itmp -isystem /usr/include/libdrm -I. 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o MainWindow.o 
src/MainWindow.cpp
g++ -c -pipe -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -D_REENTRANT -Wall -W 
-fPIC -DQT_NO_DEBUG_OUTPUT -DUNIX_PLATFORM -DQT_NO_DEBUG -DQT_WIDGETS_LIB 
-DQT_GUI_LIB -DQT_SQL_LIB -DQT_CORE_LIB -I. -isystem /usr/include/exempi-2.0 
-Iinclude -Iinclude/Library 

Bug#910458: gnome-user-docs FTBFS: 'NoneType' object has no attribute '__getitem__'

[Jeremy Bicha]

On Sat, Oct 6, 2018 at 11:27 AM Adrian Bunk  wrote:
> touch "zh_CN/zh_CN.stamp"
> Error: Could not merge translations:
> 'NoneType' object has no attribute '__getitem__'
> make[2]: *** [Makefile:851: ta/ta.stamp] Error 1

Could you request a give-back? Maybe there's a parallel building problem?

It's weird because we never used to have a problem here.

Thanks,
Jeremy Bicha

Bug#910464: octave-interval FTBFS: Makefile.am: error: required file './depcomp' not found

[Adrian Bunk]

Source: octave-interval
Version: 3.2.0-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=octave-interval=sid

...
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
(cd src/crlibm ; autoreconf)
Makefile.am: error: required file './depcomp' not found
Makefile.am:   'automake --add-missing' can install 'depcomp'
autoreconf: automake failed with exit status: 1
make[1]: *** [debian/rules:41: override_dh_auto_configure] Error 1

Bug#910463: os-autoinst FTBFS on !x86/ppc64{,el}: test failure

[Adrian Bunk]

Source: os-autoinst
Version: 4.5.1527308405.8b586d5-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=os-autoinst=sid

...
ok 1 - test executed fine
ok 2 - Snapshots are enabled
ok 3 - Wait idle waits for a second.
ok 4 - test type string and do not wait
ok 5 - test type string and wait for 5 seconds
ok 6 - test type string and wait for 10 seconds
ok 7 - test type string and wait for 20 seconds
ok 8 - get_test_data test
not ok 9 - save_tmp_file test
#   Failed test 'save_tmp_file test'
#   at ./99-full-stack.t line 68.
#  got: '256'
# expected: '0'
not ok 10 - Result in testresults/result-boot.json is ok
#   Failed test 'Result in testresults/result-boot.json is ok'
#   at ./99-full-stack.t line 73.
#  got: 'fail'
# expected: 'ok'
Bail out!  testresults/result-boot.json failed
FAIL 99-full-stack.t (exit status: 255)


Testsuite summary for os-autoinst 1.1.0

# TOTAL: 18
# PASS:  17
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See t/test-suite.log
Please report to https://github.com/os-autoinst/os-autoinst

make[5]: *** [Makefile:530: test-suite.log] Error 1

Bug#910412: marked as done (eric: broken symlink: /usr/share/eric/modules/WebBrowser/data/javascript/jquery-ui.js -> ../../../../../javascript/jquery/jquery-ui.js)

[Debian Bug Tracking System]

Your message dated Sat, 06 Oct 2018 16:07:18 +
with message-id 
and subject line Bug#910412: fixed in eric 18.10+ds1-3
has caused the Debian Bug report #910412,
regarding eric: broken symlink: 
/usr/share/eric/modules/WebBrowser/data/javascript/jquery-ui.js -> 
../../../../../javascript/jquery/jquery-ui.js
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.)


-- 
910412: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910412
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: eric
Version: 18.10+ds1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

>From the attached log (scroll to the bottom...):

1m30.6s ERROR: FAIL: Broken symlinks:
  /usr/share/eric/modules/WebBrowser/data/javascript/jquery-ui.js -> 
../../../../../javascript/jquery/jquery-ui.js (eric)


The target actually lives in .../javascript/jquery-ui/jquery-ui.js
  ^^^

cheers,

Andreas


eric_18.10+ds1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: eric
Source-Version: 18.10+ds1-3

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated eric package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 06 Oct 2018 10:53:13 -0400
Source: eric
Binary: eric eric-api-files
Architecture: source
Version: 18.10+ds1-3
Distribution: unstable
Urgency: high
Maintainer: Gudjon I. Gudjonsson 
Changed-By: Boyuan Yang 
Description:
 eric   - full featured Python IDE
 eric-api-files - API description files for use with eric
Closes: 910412
Changes:
 eric (18.10+ds1-3) unstable; urgency=high
 .
   * debian/rules: Fix broken symlink for jquery-ui (Closes: #910412).
   * debian/rules: Use uscan (debian/watch) for get-orig-source target.
   * debian/debian-manpages: Add eric6_browser(1).
Checksums-Sha1:
 57957fb3b880b7277a4d1556a065107d1e33a742 2173 eric_18.10+ds1-3.dsc
 d9a1bc3d31ea28b473f354c249e04c0ecab1ae50 25464 eric_18.10+ds1-3.debian.tar.xz
 d735a3686eeeaa3269d75014c0a543d35d6e78ef 10395 eric_18.10+ds1-3_amd64.buildinfo
Checksums-Sha256:
 638827a41326410e91bebbb58c328ede77fdaa8478160f0e1eaa1e5dd4b3a244 2173 
eric_18.10+ds1-3.dsc
 e43bf310f51056573ca49e4fa9223309ab60aa8c3fb93ac332c8a2fbfda1f889 25464 
eric_18.10+ds1-3.debian.tar.xz
 8c7b2863010cf307baf003d174170c1f7f2eb149b59b61e753f701f2487303ca 10395 
eric_18.10+ds1-3_amd64.buildinfo
Files:
 7ff670d43298b83b2f8a0f3c9957e82e 2173 devel optional eric_18.10+ds1-3.dsc
 d9019f5139e8522aba78a006ee23cabb 25464 devel optional 
eric_18.10+ds1-3.debian.tar.xz
 bb742a8f4de4599cbcbcea143ab174e5 10395 devel optional 
eric_18.10+ds1-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAlu4zpMACgkQwpPntGGC
Ws4QARAAukQSolu3X8bWB/zGvN5+bIXihSjkXlWBUaMaakhEChrEniRcU7geToj3
VGcz5f6HCTGD527NO5n15R9x3PG9V9U7s7X3qkD45bNaOKOG4TunWrAT7V2+VHXw
K7ddb0mhLY4HXy7OIw9BING7SipXR+COV7+07ghro2dF71t18XCwhRxc4G6ai6f7
Q+mEzTDpAykBsCKk2qIAI/NVtjGMdhS59LVdP/bl0XEU+r4hQae2Vp1V+pnYh0UF
lAH+23B9JbrE6/xmPbnfUExOZZEQ5Fdo1Z2iB8nZPUJbnxQ7eGml3WrePpwMnoJ9
C2uQMUQQ6cg5S1XmEH+KdaDQDCPAbPBNFZgYGlgaGLIZ3ftx8MVZDewD36ZpDpmK
prmtl+0zpvESL7udVMagRzKxAg9qbBIvugYev/HAFfQcw9JUCPya9nyY4ItFgJyI
kjW5uSwvbn+ziIy0iuvPTiWyuKn7R4Xe4C4v9JKCAQS5HPaN2gVUt319RTI6PIVb
fW8sG6urmJ/9WrQvIIOdWWixQYHG95TYO48DRALrbZZrcQ33Z0odkN/i4A89qtCy
flqF9EM/CFTviNUSIwtqKyDR/b6ojVwYZ7UcmuMqQRHbyXuhsfDS+oMFK7mH02zq
e2iWpVDM1oNPByv5Q3uSRaGEMHxt7rWT7qBbBrY90/0KD6NIcko=
=vT/7
-END PGP SIGNATURE End Message ---

Bug#902507: node-multiparty: FTBFS in buster/sid (TypeError: mime.lookup is not a function)

[Petter Reinholdtsen]

I had a closer look, and became more confused.  First some background
information: The mime library renamed lookup() to getType, while the
mime-types library in sid seem to still provide the lookup() method.

This build problemseem to be caused by a test depending on form-data.js in
the node-form-data package, which expect a mime library with the lookup()
function.  One way to fix this would be to convince form-data.js to use
the mime-types library, but I am unable to find out which library is
actually used and how it is pulled in.

A fix would be to change the code in node-form-data to use getType()
instead of lookup(), but it make more sense if a dependency of
node-form-data could be updated to reflect the changed requirement, to
version 2 of the node-mime library. The problem is that node-form-data
do not (build-)depend on any node-mime* library I can see.  What is
going on here?  What is the best fix for this?

In any case, I suspect this bug should be reassigned node-form-data or
split in two, one for node-multiparty and one for node-form-data.
But given that I have not been able to figure out exactly where
a mime* library is loaded, I do not know where the bug really is
located.

-- 
Happy hacking
Petter Reinholdtsen

Bug#910458: gnome-user-docs FTBFS: 'NoneType' object has no attribute '__getitem__'

[Adrian Bunk]

Source: gnome-user-docs FTBFS: Error: Could not merge translations: 
Version: 3.30.1-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=gnome-user-docs=all=3.30.1-1=1538768364=0

...
mo="zh_CN/zh_CN.mo"; \
if test -f "${mo}"; then mo="../${mo}"; else 
mo="/<>/gnome-help/${mo}"; fi; \
(cd "zh_CN/" && itstool -m "${mo}" ${d}/C/legal.xml ${d}/C/a11y-bouncekeys.page 
${d}/C/a11y-braille.page ${d}/C/a11y-contrast.page ${d}/C/a11y-dwellclick.page 
${d}/C/a11y-font-size.page ${d}/C/a11y-icon.page ${d}/C/a11y-mag.page 
${d}/C/a11y.page ${d}/C/a11y-right-click.page ${d}/C/a11y-screen-reader.page 
${d}/C/a11y-slowkeys.page ${d}/C/a11y-stickykeys.page 
${d}/C/a11y-visualalert.page ${d}/C/about-this-guide.page 
${d}/C/accounts-add.page ${d}/C/accounts-disable-service.page 
${d}/C/accounts-provider-not-available.page ${d}/C/accounts-remove.page 
${d}/C/accounts-which-application.page ${d}/C/accounts-whyadd.page 
${d}/C/accounts.page ${d}/C/backup-check.page ${d}/C/backup-frequency.page 
${d}/C/backup-how.page ${d}/C/backup-restore.page ${d}/C/backup-thinkabout.page 
${d}/C/backup-what.page ${d}/C/backup-where.page ${d}/C/backup-why.page 
${d}/C/bluetooth.page ${d}/C/bluetooth-connect-device.page 
${d}/C/bluetooth-problem-connecting.page 
${d}/C/bluetooth-remove-connection.page ${d}/C/bluetooth-send-file.page 
${d}/C/bluetooth-turn-on-off.page ${d}/C/bluetooth-visibility.page 
${d}/C/clock-calendar.page ${d}/C/clock-set.page ${d}/C/clock-timezone.page 
${d}/C/clock-world.page ${d}/C/clock.page ${d}/C/color.page 
${d}/C/color-assignprofiles.page ${d}/C/color-calibrate-camera.page 
${d}/C/color-calibrate-printer.page ${d}/C/color-calibrate-scanner.page 
${d}/C/color-calibrate-screen.page 
${d}/C/color-calibrationcharacterization.page 
${d}/C/color-calibrationdevices.page ${d}/C/color-calibrationtargets.page 
${d}/C/color-canshareprofiles.page ${d}/C/color-gettingprofiles.page 
${d}/C/color-howtoimport.page ${d}/C/color-missingvcgt.page 
${d}/C/color-notifications.page ${d}/C/color-notspecifiededid.page 
${d}/C/color-testing.page ${d}/C/color-whatisprofile.page 
${d}/C/color-whatisspace.page ${d}/C/color-why-calibrate.page 
${d}/C/color-whyimportant.page ${d}/C/contacts-add-remove.page 
${d}/C/contacts.page ${d}/C/contacts-connect.page 
${d}/C/contacts-edit-details.page ${d}/C/contacts-link-unlink.page 
${d}/C/contacts-search.page ${d}/C/contacts-setup.page 
${d}/C/disk-benchmark.page ${d}/C/disk-capacity.page ${d}/C/disk-check.page 
${d}/C/disk-format.page ${d}/C/disk-partitions.page ${d}/C/disk-repair.page 
${d}/C/disk-resize.page ${d}/C/disk.page ${d}/C/display-blank.page 
${d}/C/display-brightness.page ${d}/C/display-dual-monitors.page 
${d}/C/display-night-light.page ${d}/C/files-autorun.page 
${d}/C/files-browse.page ${d}/C/files-copy.page ${d}/C/files-delete.page 
${d}/C/files-disc-write.page ${d}/C/files-hidden.page ${d}/C/files-lost.page 
${d}/C/files-open.page ${d}/C/files-preview.page ${d}/C/files-recover.page 
${d}/C/files-removedrive.page ${d}/C/files-rename.page ${d}/C/files-search.page 
${d}/C/files-select.page ${d}/C/files-share.page ${d}/C/files-sort.page 
${d}/C/files-templates.page ${d}/C/files-tilde.page ${d}/C/files.page 
${d}/C/get-involved.page ${d}/C/gnome-classic.page ${d}/C/gnome-version.page 
${d}/C/hardware-auth.page ${d}/C/hardware-cardreader.page 
${d}/C/hardware-driver.page ${d}/C/hardware-problems-graphics.page 
${d}/C/hardware.page ${d}/C/help-irc.page ${d}/C/help-mailing-list.page 
${d}/C/index.page ${d}/C/keyboard-cursor-blink.page 
${d}/C/keyboard-key-menu.page ${d}/C/keyboard-key-super.page 
${d}/C/keyboard-layouts.page ${d}/C/keyboard-nav.page ${d}/C/keyboard-osk.page 
${d}/C/keyboard-repeat-keys.page ${d}/C/keyboard-shortcuts-set.page 
${d}/C/keyboard.page ${d}/C/look-background.page ${d}/C/look-display-fuzzy.page 
${d}/C/look-resolution.page ${d}/C/media.page ${d}/C/more-help.page 
${d}/C/mouse-doubleclick.page ${d}/C/mouse-lefthanded.page 
${d}/C/mouse-middleclick.page ${d}/C/mouse-mousekeys.page 
${d}/C/mouse-problem-notmoving.page ${d}/C/mouse-sensitivity.page 
${d}/C/mouse-touchpad-click.page ${d}/C/mouse-wakeup.page ${d}/C/mouse.page 
${d}/C/music-cantplay-drm.page ${d}/C/music-player-ipodtransfer.page 
${d}/C/music-player-newipod.page ${d}/C/nautilus-behavior.page 
${d}/C/nautilus-bookmarks-edit.page ${d}/C/nautilus-connect.page 
${d}/C/nautilus-display.page ${d}/C/nautilus-file-properties-basic.page 
${d}/C/nautilus-file-properties-permissions.page ${d}/C/nautilus-list.page 
${d}/C/nautilus-prefs.page ${d}/C/nautilus-preview.page 
${d}/C/nautilus-views.page ${d}/C/net-antivirus.page ${d}/C/net-browser.page 
${d}/C/net-default-browser.page ${d}/C/net-default-email.page 
${d}/C/net-email-virus.page ${d}/C/net-email.page ${d}/C/net-findip.page 
${d}/C/net-firewall-on-off.page ${d}/C/net-firewall-ports.page 
${d}/C/net-fixed-ip-address.page ${d}/C/net-general.page 
${d}/C/net-install-flash.page ${d}/C/net-macaddress.page ${d}/C/net-manual.page 

Bug#910457: syncany: FTBFS: dh_installman: Cannot find (any matches for) "/build/syncany-0.4.9~alpha/build/debian/syncany/debian/man/sy-cleanup.1" (tried in .)

[Andreas Beckmann]

Source: syncany
Version: 0.4.9~alpha-1
Severity: serious
Justification: fails to build from source

Hi,

syncany cannot be built in a current sid+experimental environment any
more:

[...]
 fakeroot debian/rules binary
dh binary --with bash-completion
   dh_testroot
   dh_prep
   dh_auto_install
   debian/rules override_dh_install
make[1]: Entering directory '/build/syncany-0.4.9~alpha'
rm -f build/install/syncany/bin/*.bat
dh_install
make[1]: Leaving directory '/build/syncany-0.4.9~alpha'
   dh_installdocs
   debian/rules override_dh_installchangelogs
make[1]: Entering directory '/build/syncany-0.4.9~alpha'
dh_installchangelogs build/install/syncany/CHANGELOG.md
make[1]: Leaving directory '/build/syncany-0.4.9~alpha'
   dh_installman
dh_installman: Cannot find (any matches for) 
"/build/syncany-0.4.9~alpha/build/debian/syncany/debian/man/sy-cleanup.1" 
(tried in .)

dh_installman: Aborting due to earlier error
make: *** [debian/rules:4: binary] Error 25
dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit 
status 2


Andreas


syncany_0.4.9~alpha-1.log.gz
Description: application/gzip

Bug#910455: bitcoin FTBFS on 32bit: test failure

[Adrian Bunk]

Source: bitcoin
Version: 0.17.0~dfsg-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=bitcoin=sid

...
make[5]: Leaving directory '/<>/src'
Running tests: compress_tests from test/compress_tests.cpp
test/test_bitcoin -l test_suite -t "`cat test/compress_tests.cpp | grep -E 
"(BOOST_FIXTURE_TEST_SUITE\\(|BOOST_AUTO_TEST_SUITE\\()" | cut -d '(' -f 2 | 
cut -d ',' -f 1 | cut -d ')' -f 1`" > test/compress_tests.cpp.log 2>&1 || (cat 
test/compress_tests.cpp.log && false)
Running tests: crypto_tests from test/crypto_tests.cpp
test/test_bitcoin -l test_suite -t "`cat test/crypto_tests.cpp | grep -E 
"(BOOST_FIXTURE_TEST_SUITE\\(|BOOST_AUTO_TEST_SUITE\\()" | cut -d '(' -f 2 | 
cut -d ',' -f 1 | cut -d ')' -f 1`" > test/crypto_tests.cpp.log 2>&1 || (cat 
test/crypto_tests.cpp.log && false)
Running tests: cuckoocache_tests from test/cuckoocache_tests.cpp
test/test_bitcoin -l test_suite -t "`cat test/cuckoocache_tests.cpp | grep -E 
"(BOOST_FIXTURE_TEST_SUITE\\(|BOOST_AUTO_TEST_SUITE\\()" | cut -d '(' -f 2 | 
cut -d ',' -f 1 | cut -d ')' -f 1`" > test/cuckoocache_tests.cpp.log 2>&1 || 
(cat test/cuckoocache_tests.cpp.log && false)
Running tests: denialofservice_tests from test/denialofservice_tests.cpp
test/test_bitcoin -l test_suite -t "`cat test/denialofservice_tests.cpp | grep 
-E "(BOOST_FIXTURE_TEST_SUITE\\(|BOOST_AUTO_TEST_SUITE\\()" | cut -d '(' -f 2 | 
cut -d ',' -f 1 | cut -d ')' -f 1`" > test/denialofservice_tests.cpp.log 2>&1 
|| (cat test/denialofservice_tests.cpp.log && false)
Running tests: descriptor_tests from test/descriptor_tests.cpp
test/test_bitcoin -l test_suite -t "`cat test/descriptor_tests.cpp | grep -E 
"(BOOST_FIXTURE_TEST_SUITE\\(|BOOST_AUTO_TEST_SUITE\\()" | cut -d '(' -f 2 | 
cut -d ',' -f 1 | cut -d ')' -f 1`" > test/descriptor_tests.cpp.log 2>&1 || 
(cat test/descriptor_tests.cpp.log && false)
Running tests: getarg_tests from test/getarg_tests.cpp
test/test_bitcoin -l test_suite -t "`cat test/getarg_tests.cpp | grep -E 
"(BOOST_FIXTURE_TEST_SUITE\\(|BOOST_AUTO_TEST_SUITE\\()" | cut -d '(' -f 2 | 
cut -d ',' -f 1 | cut -d ')' -f 1`" > test/getarg_tests.cpp.log 2>&1 || (cat 
test/getarg_tests.cpp.log && false)
Running tests: hash_tests from test/hash_tests.cpp
test/test_bitcoin -l test_suite -t "`cat test/hash_tests.cpp | grep -E 
"(BOOST_FIXTURE_TEST_SUITE\\(|BOOST_AUTO_TEST_SUITE\\()" | cut -d '(' -f 2 | 
cut -d ',' -f 1 | cut -d ')' -f 1`" > test/hash_tests.cpp.log 2>&1 || (cat 
test/hash_tests.cpp.log && false)
Running tests: key_io_tests from test/key_io_tests.cpp
test/test_bitcoin -l test_suite -t "`cat test/key_io_tests.cpp | grep -E 
"(BOOST_FIXTURE_TEST_SUITE\\(|BOOST_AUTO_TEST_SUITE\\()" | cut -d '(' -f 2 | 
cut -d ',' -f 1 | cut -d ')' -f 1`" > test/key_io_tests.cpp.log 2>&1 || (cat 
test/key_io_tests.cpp.log && false)
Running 11 test cases...
Entering test module "Bitcoin Test Suite"
test/crypto_tests.cpp(23): Entering test suite "crypto_tests"
test/crypto_tests.cpp(217): Entering test case "ripemd160_testvectors"
test/crypto_tests.cpp(217): Leaving test case "ripemd160_testvectors"; testing 
time: 346645us
test/crypto_tests.cpp(233): Entering test case "sha1_testvectors"
test/crypto_tests.cpp(233): Leaving test case "sha1_testvectors"; testing time: 
555499us
test/crypto_tests.cpp(249): Entering test case "sha256_testvectors"
test/crypto_tests.cpp(249): Leaving test case "sha256_testvectors"; testing 
time: 550873us
test/crypto_tests.cpp(271): Entering test case "sha512_testvectors"
test/crypto_tests.cpp(271): Leaving test case "sha512_testvectors"; testing 
time: 1591096us
test/crypto_tests.cpp(308): Entering test case "hmac_sha256_testvectors"
test/crypto_tests.cpp(308): Leaving test case "hmac_sha256_testvectors"; 
testing time: 46886us
test/crypto_tests.cpp(361): Entering test case "hmac_sha512_testvectors"
test/crypto_tests.cpp(361): Leaving test case "hmac_sha512_testvectors"; 
testing time: 62095us
test/crypto_tests.cpp(429): Entering test case "aes_testvectors"
test/crypto_tests.cpp(429): Leaving test case "aes_testvectors"; testing time: 
39761us
test/crypto_tests.cpp(445): Entering test case "aes_cbc_testvectors"
test/crypto_tests.cpp(445): Leaving test case "aes_cbc_testvectors"; testing 
time: 40189us
test/crypto_tests.cpp(497): Entering test case "chacha20_testvector"
test/crypto_tests.cpp(497): Leaving test case "chacha20_testvector"; testing 
time: 39479us
test/crypto_tests.cpp(527): Entering test case "countbits_tests"
test/crypto_tests.cpp(527): Leaving test case "countbits_tests"; testing time: 
91719us
test/crypto_tests.cpp(549): Entering test case "sha256d64"
test/crypto_tests.cpp(561): error: in "crypto_tests/sha256d64": check 
memcmp(out1, out2, 32 * i) == 0 has failed
test/crypto_tests.cpp(561): error: in "crypto_tests/sha256d64": check 
memcmp(out1, out2, 32 * i) == 0 has failed
test/crypto_tests.cpp(561): error: in "crypto_tests/sha256d64": check 
memcmp(out1, out2, 32 * i) == 0 has failed
test/crypto_tests.cpp(561): 

Bug#747046: marked as done (magicmaze: can't open ttf-isabella/Isabella.ttf; font now under isabella/Isabella.ttf)

[Debian Bug Tracking System]

Your message dated Sat, 06 Oct 2018 15:04:02 +
with message-id 
and subject line Bug#747046: fixed in magicmaze 1.4.3.6+dfsg-3
has caused the Debian Bug report #747046,
regarding magicmaze: can't open ttf-isabella/Isabella.ttf; font now under 
isabella/Isabella.ttf
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.)


-- 
747046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747046
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: magicmaze
Version: 1.4.3.6+dfsg-2
Severity: important

Dear Maintainer,

$ magicmaze 
Starting Magic Maze...
Setting up graphics...
/usr/lib/ruby/vendor_ruby/magicmaze/graphics.rb:170:in `open': Couldn't open 
font /usr/share/fonts/truetype/ttf-isabella/Isabella.ttf: Couldn't open 
/usr/share/fonts/truetype/ttf-isabella/Isabella.ttf (SDL::Error)
from /usr/lib/ruby/vendor_ruby/magicmaze/graphics.rb:170:in `font_init'
from /usr/lib/ruby/vendor_ruby/magicmaze/graphics.rb:86:in `initialize'
from /usr/lib/ruby/vendor_ruby/magicmaze/graphics.rb:73:in `new'
from /usr/lib/ruby/vendor_ruby/magicmaze/graphics.rb:73:in 
`get_graphics'
from /usr/lib/ruby/vendor_ruby/magicmaze/game.rb:47:in `init_graphics'
from /usr/lib/ruby/vendor_ruby/magicmaze/game.rb:32:in `initialize'
from /usr/games/magicmaze:110:in `new'
from /usr/games/magicmaze:110:in `'

solved by:

# ( cd /usr/share/fonts/truetype/ && ln -s isabella ttf-isabella )

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

Kernel: Linux 3.13-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages magicmaze depends on:
ii  fonts-isabella [ttf-isabella]  1.202-1
ii  ruby   1:2.0.0.2
ii  ruby-sdl   2.1.3-1+b1
ii  ruby1.9.1 [ruby-interpreter]   1.9.3.484-2
ii  ruby2.0 [ruby-interpreter] 2.0.0.484+really457-3
ii  ttf-isabella   1.202-1

magicmaze recommends no packages.

magicmaze suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: magicmaze
Source-Version: 1.4.3.6+dfsg-3

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated magicmaze package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 06 Oct 2018 16:18:35 +0200
Source: magicmaze
Binary: magicmaze
Architecture: source
Version: 1.4.3.6+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Description:
 magicmaze  - rescue the maiden while avoiding the monsters
Closes: 747046
Changes:
 magicmaze (1.4.3.6+dfsg-3) unstable; urgency=medium
 .
   [ Andreas Beckmann ]
   * QA upload.
   * Set Maintainer to Debian QA Group.  (See: #869294)
 .
   [ Hans Joachim Desserud ]
   * Depend on fonts-isabella now that ttf-isabella is a virtual package.
   * Update isabella path in patch to new location,
 closes: #747046, LP: #1360075.
Checksums-Sha1:
 fc92cceadc13e9f22db0e2e71d73603a856da286 1791 magicmaze_1.4.3.6+dfsg-3.dsc
 964e3d19c91d333d45091babfe8dd942b4179204 6100 
magicmaze_1.4.3.6+dfsg-3.debian.tar.xz
 dc76b6262a6c92cc396df4667ce96f4083eeea1f 5461 
magicmaze_1.4.3.6+dfsg-3_source.buildinfo
Checksums-Sha256:
 26cee4e79a1647acf7ef40e185cd78cbc3bf4e4097efe99a2232199f9eeff7d5 1791 
magicmaze_1.4.3.6+dfsg-3.dsc
 1ee9beacc4c962a6b32456b1d3aeadc0c1c9f3717b4a62a361623dbc2e24ad81 6100 
magicmaze_1.4.3.6+dfsg-3.debian.tar.xz
 813e3f3aa72e02eb3348f55bf1c4599d387e8f3811eb5908c41c85dd86b02a3c 5461 
magicmaze_1.4.3.6+dfsg-3_source.buildinfo
Files:
 258d44ae99d577ab1b5d9b4eb991865c 1791 games extra magicmaze_1.4.3.6+dfsg-3.dsc
 8a2838b0bec075ab3afba4e175cc1bf6 6100 games extra 
magicmaze_1.4.3.6+dfsg-3.debian.tar.xz
 189c603ed50ca4ca1b7db87dd20c773d 5461 games extra 
magicmaze_1.4.3.6+dfsg-3_source.buildinfo

-BEGIN PGP 

Bug#900161: marked as done (ruby-openssl: FTBFS against openssl 1.1.1)

[Debian Bug Tracking System]

Your message dated Sat, 06 Oct 2018 13:35:18 +
with message-id 
and subject line Bug#900161: fixed in ruby-openssl 2.1.1-1
has caused the Debian Bug report #900161,
regarding ruby-openssl: FTBFS against openssl 1.1.1
to be marked as done.

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

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


-- 
900161: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900161
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-openssl
Version: 2.0.5-1
Severity: important
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: openssl-1.1.1

The new openssl 1.1.1 is currently in experimental [0]. This package
failed to build against this new package [1] while it built fine against
the openssl version currently in unstable [2].
Could you please have a look?

The Error
|/<>/test/test_ssl.rb:1280:in `initialize': 
SSL_CTX_use_certificate: ee key too small (OpenSSL::SSL::SSLError)

is due to:
1.1.1~~pre6-1 changelog):
|   * Increase default security level from 1 to 2. This moves from the 80 bit
| security level to the 112 bit securit level and will require 2048 bit RSA
| and DHE keys.

[0] https://lists.debian.org/msgid-search/20180501211400.ga21...@roeckx.be
[1] 
https://breakpoint.cc/openssl-rebuild/2018-05-03-rebuild-openssl1.1.1-pre6/attempted/ruby-openssl_2.0.5-1_amd64-2018-05-01T21%3A05%3A24Z
[2] 
https://breakpoint.cc/openssl-rebuild/2018-05-03-rebuild-openssl1.1.1-pre6/successful/ruby-openssl_2.0.5-1_amd64-2018-05-02T18%3A51%3A30Z

Sebastian
--- End Message ---
--- Begin Message ---
Source: ruby-openssl
Source-Version: 2.1.1-1

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

Debian distribution maintenance software
pp.
Antonio Terceiro  (supplier of updated ruby-openssl 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 06 Oct 2018 10:24:43 -0300
Source: ruby-openssl
Binary: ruby-openssl
Architecture: source
Version: 2.1.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Antonio Terceiro 
Description:
 ruby-openssl - Ruby bindings for OpenSSL
Closes: 900161
Changes:
 ruby-openssl (2.1.1-1) unstable; urgency=medium
 .
   * New upstream version 2.1.1
 - Drop patches, not applicable anymore
   * Bump debhelper compatibility level to 11
   * Bump Standards-Version to 4.2.1; no changed needed otherwise
   * Update Vcs-* fields to point to salsa.debian.org
   * debian/rules: install upstream changelog
   * Fix building against openssl 1.1.1 (Closes: #900161)
 - Apply patches from upstream pull request #217
   https://github.com/ruby/openssl/pull/217/commits
 - debian/ruby-tests.rake: Add $TESTOPTS to ignore two tests that still
   crash against openssl 1.1.1
Checksums-Sha1:
 36740e83fe7d81fa5f35f4e0a540961069dbafb2 2045 ruby-openssl_2.1.1-1.dsc
 e1f229fec50e65e3d6e19272e6302a2a26ff15b2 254704 ruby-openssl_2.1.1.orig.tar.gz
 8a3fe9bb969e139929cb5e0db0916a253b3282c5 14096 
ruby-openssl_2.1.1-1.debian.tar.xz
 b3d388992aac65e1f62882654f87caad62c58619 6981 
ruby-openssl_2.1.1-1_source.buildinfo
Checksums-Sha256:
 ec55868a87bd0f929dc4600794d10d0c6d8110b2b91b6bf61cd8f304bf367f5d 2045 
ruby-openssl_2.1.1-1.dsc
 b70f5114116c214354d1084f85360c908d9801db8bba43944b265f15af11f2bb 254704 
ruby-openssl_2.1.1.orig.tar.gz
 747d97a01c039a65d39082b89bfb07c6930e227ea803859e1176854906005e06 14096 
ruby-openssl_2.1.1-1.debian.tar.xz
 4de9f196a0202b2b6418491040a0801311e1fb0d5afcfa23f07d9f2f63658e6a 6981 
ruby-openssl_2.1.1-1_source.buildinfo
Files:
 2701bce18d52022296172229f10b9c90 2045 ruby optional ruby-openssl_2.1.1-1.dsc
 cb539761e511af284b5ef68ff5ad6d6b 254704 ruby optional 
ruby-openssl_2.1.1.orig.tar.gz
 66033e2d8218f15d265612d7ff48f126 14096 ruby optional 
ruby-openssl_2.1.1-1.debian.tar.xz
 43cec4d9bd69f1546e8fe1b6eb39b6b5 6981 ruby optional 
ruby-openssl_2.1.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAlu4uFUACgkQ/A2xu81G
C96SXw/+PVNpOZSx6w9C1aUOu1tEgpZFLn9H0ZNKpeDqsYpe7zW1jJCeVyd1hcEi

Bug#900161: ruby-openssl: FTBFS against openssl 1.1.1

[Antonio Terceiro]

On Thu, Oct 04, 2018 at 12:10:53PM +0100, peter green wrote:
> i tried to modify the testsuite to use stronger keys (patch
> attatched), however after doing so the testsuite now hangs (relavent
> output pasted at end of message). Not sure what is going wrong here (I
> am neither a ruby expert or an openssl expert).
> 
> I have attached a patch with my changes so-far.

Thanks for looking into it.

There is an uptream pull request that fixes these issues:
https://github.com/ruby/openssl/pull/217

I have applied the patches from there, and with an extra change to
ignore 2 tests that crash due to the new policies in openssl 1.1.1, make
the package build.


signature.asc
Description: PGP signature

Processed: Bug #900161 in ruby-openssl marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #900161 [src:ruby-openssl] ruby-openssl: FTBFS against openssl 1.1.1
Added tag(s) pending.

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

Bug#900161: Bug #900161 in ruby-openssl marked as pending

[Antonio Terceiro]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/ruby-team/ruby-openssl/commit/ea057e19496a4b55235af5e869055c342fdbbf64


Fix building against openssl 1.1.1

Closes: #900161



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/900161

Processed: mgetty: CVE-2018-16741

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 1.1.36-3+deb9u1
Bug #910448 [src:mgetty] mgetty: CVE-2018-16741
Marked as fixed in versions mgetty/1.1.36-3+deb9u1.

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

Bug#910448: mgetty: CVE-2018-16741

[Salvatore Bonaccorso]

Source: mgetty
Version: 1.1.36-1
Severity: grave
Tags: patch security upstream
Control: fixed -1 1.1.36-3+deb9u1

Hi,

The following vulnerability was published for mgetty.

CVE-2018-16741[0]:
| An issue was discovered in mgetty before 1.2.1. In fax/faxq-helper.c,
| the function do_activate() does not properly sanitize shell
| metacharacters to prevent command injection. It is possible to use the
| ||, , or  characters within a file created by the "faxq-helper
| activate jobid" command.

The issue was fixed in DSA-4291-1 with 1.1.36-3+deb9u1 but not yet in
unstable and for buster, thus filling an RC bug to avoid the
regression for buster.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-16741
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16741

Regards,
Salvatore

Bug#910384: marked as done (libhandy-dev: Missing dependency on libgtk-3-dev)

[Debian Bug Tracking System]

Your message dated Sat, 06 Oct 2018 13:04:23 +
with message-id 
and subject line Bug#910384: fixed in libhandy 0.0.4-2
has caused the Debian Bug report #910384,
regarding libhandy-dev: Missing dependency on libgtk-3-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.)


-- 
910384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910384
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libhandy-0.0-dev
Version: 0.0.3-1
Severity: serious

I see that libhandy-0.0.pc has this line:
Requires: gtk+-3.0

That means that libhandy-0.0-dev needs a dependency on libgtk-3-dev

By the way, GNOME 3.32 components might start depending on libhandy.
(Buster will include GNOME 3.30 so Unstable is fine for now.) Thanks
for packaging this!

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: libhandy
Source-Version: 0.0.4-2

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

Debian distribution maintenance software
pp.
Guido Günther  (supplier of updated libhandy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 06 Oct 2018 14:25:32 +0200
Source: libhandy
Binary: libhandy-0.0-0 libhandy-0.0-dev gir1.2-handy-0.0
Architecture: source
Version: 0.0.4-2
Distribution: unstable
Urgency: medium
Maintainer: Guido Günther 
Changed-By: Guido Günther 
Description:
 gir1.2-handy-0.0 - GObject introspection files for libhandy
 libhandy-0.0-0 - Library with GTK+ widgets for mobile phones
 libhandy-0.0-dev - Development files for libhandy
Closes: 910384
Changes:
 libhandy (0.0.4-2) unstable; urgency=medium
 .
   [ Guido Günther ]
   * [9651d62] meson: Properly depend on the generated headers
 Fixes FTBFS.
   * [c48897d] d/control: Mark buil-deps for tests as 
 .
   [ Jeremy Bicha ]
   * [84d9e5c] Have libhandy-0.0-dev depend on libgtk-3-dev (Closes: #910384)
   * [b3ea207] Use dh --with gir
   * [3a82073] Simplify debian/rules
Checksums-Sha1:
 6d324ce53a35aa04da759da7343d13b60015c375 2132 libhandy_0.0.4-2.dsc
 ea705b20f8ae71c0a7523b5d160fa7fb917f41b0 4068 libhandy_0.0.4-2.debian.tar.xz
 f4fcd06905268e96a576f9c1085976425c27a8a7 17484 libhandy_0.0.4-2_amd64.buildinfo
Checksums-Sha256:
 7d7b0e20092588e7964d10192bde0c28de70996c5e9525a61389119c6fb06509 2132 
libhandy_0.0.4-2.dsc
 98f3a6192dbac04a01106f5c9897d0b6a9f69d5216c02d9d228b794482528530 4068 
libhandy_0.0.4-2.debian.tar.xz
 b3c495a19a8a6dc533a49d111628f9410056c4f26f70b51cea61eaa0de01ce1d 17484 
libhandy_0.0.4-2_amd64.buildinfo
Files:
 da657bb848d4a0713fee0450494081f6 2132 libs optional libhandy_0.0.4-2.dsc
 2b11695920eb53a69355ad7d8a60661c 4068 libs optional 
libhandy_0.0.4-2.debian.tar.xz
 844de8a69e98e714dee1ccf1e5e63885 17484 libs optional 
libhandy_0.0.4-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEvHzQcjh1660F3xzZB7i3sOqYEgsFAlu4q2cACgkQB7i3sOqY
Egu+mQ//Z1Lk8UKdeEY/yO2BPDiQoYs0pxql7Ue2zzBJlVajUbQ7eTxkOOPavmKl
RYibWicKhAoi5tL5UBRz3pAvYxnIXmQCRG61D9HIVJIZPwOoSVcJgzr3dTGmrDJu
f/D2x9Q8yMtOAWoTeh6lRY6P0JAPE/QYFJfv38lUZsmBDICQG6GR3AIJ0gE4Jz0C
Kv5P08zVQKi0qtij/ezV8UuTwN0b/NEOGS4qP2vAtALycyY5Dw3IQVJ3F2jIQhdF
QD6jFBxY3hogjjEOLkrOiXaTXViHOHIlNW8xp4Q8xOEzVyO+qSYgy+gE/BeRc6b8
Q+8Trxm1niH0+IH0PcAT2la6hKwOiK0u/RJTT7QRdHHWJrC+h6hpIGACa7bD1/Kz
aKmS4NpV2VYmwWlTRQinfpzK5jiFk2fTUNgyMG5loepEiqiHLziqTmbw8s4W2N10
EesSXaOQYVmtbVHVqR/OzptTqklicg4jrCbmPeHUJFcW8YI+RsV7ANonIkGs+C0t
OPMeuRFSpvWhAwBMdkz+koC3DMniYOWjRfiP21XXh1NcmUNIipKXklmugnZxMhs4
diMlctp0SihYGJ2I7WW4yISe4Vf7gWL0Czs+4VldPBoH7royusFBI1tGWMxyqWbA
lqNm9L9S+UdYAj5KioE4D48WBP5op+URGnWXQlwOWfb5AEakbhg=
=35Kr
-END PGP SIGNATURE End Message ---

Bug#910446: git-buildpackage FTBFS: flake8 fails

[Helmut Grohne]

Source: git-buildpackage
Version: 0.9.10
Severity: serious
Tags: ftbfs

git-buildpackage fails to build from source in sbuild on unstable/amd64.
A build log ends with:

|debian/rules override_dh_auto_test
| make[1]: Entering directory '/<>'
| make
| make[2]: Entering directory '/<>'
| flake8 
| ./.pybuild/cpython3_3.6/build/gbp/command_wrappers.py:286:26: W504 line break 
after binary operator
| ./.pybuild/cpython3_3.6/build/gbp/command_wrappers.py:301:26: W504 line break 
after binary operator
| ./.pybuild/cpython3_3.6/build/gbp/config.py:435:17: W504 line break after 
binary operator
| ./.pybuild/cpython3_3.6/build/gbp/config.py:436:17: W504 line break after 
binary operator
| ./.pybuild/cpython3_3.6/build/gbp/config.py:447:17: W504 line break after 
binary operator
| ./.pybuild/cpython3_3.6/build/gbp/config.py:524:17: W504 line break after 
binary operator
| ./.pybuild/cpython3_3.6/build/gbp/log.py:79:25: W504 line break after binary 
operator
| ./.pybuild/cpython3_3.6/build/gbp/patch_series.py:261:6: W605 invalid escape 
sequence '\s'
| ./.pybuild/cpython3_3.6/build/gbp/deb/dscfile.py:31:24: W605 invalid escape 
sequence '\s'
| ./.pybuild/cpython3_3.6/build/gbp/deb/dscfile.py:34:7: W605 invalid escape 
sequence '\.'
| ./.pybuild/cpython3_3.6/build/gbp/deb/dscfile.py:34:15: W605 invalid escape 
sequence '\.'
| ./.pybuild/cpython3_3.6/build/gbp/deb/dscfile.py:34:20: W605 invalid escape 
sequence '\.'
| ./.pybuild/cpython3_3.6/build/gbp/deb/dscfile.py:36:6: W605 invalid escape 
sequence '\.'
| ./.pybuild/cpython3_3.6/build/gbp/deb/dscfile.py:36:35: W605 invalid escape 
sequence '\.'
| ./.pybuild/cpython3_3.6/build/gbp/deb/dscfile.py:36:40: W605 invalid escape 
sequence '\.'
| ./.pybuild/cpython3_3.6/build/gbp/deb/dscfile.py:38:6: W605 invalid escape 
sequence '\.'
| ./.pybuild/cpython3_3.6/build/gbp/deb/dscfile.py:40:6: W605 invalid escape 
sequence '\.'
| ./.pybuild/cpython3_3.6/build/gbp/deb/dscfile.py:43:6: W605 invalid escape 
sequence '\.'
| ./.pybuild/cpython3_3.6/build/gbp/deb/dscfile.py:43:26: W605 invalid escape 
sequence '\.'
| ./.pybuild/cpython3_3.6/build/gbp/deb/dscfile.py:43:31: W605 invalid escape 
sequence '\.'
| ./.pybuild/cpython3_3.6/build/gbp/deb/git.py:35:6: W605 invalid escape 
sequence '\)'
| ./.pybuild/cpython3_3.6/build/gbp/deb/git.py:171:-37: W605 invalid escape 
sequence '\%'
| ./.pybuild/cpython3_3.6/build/gbp/deb/git.py:183:-54: W605 invalid escape 
sequence '\%'
| ./.pybuild/cpython3_3.6/build/gbp/deb/git.py:187:14: W605 invalid escape 
sequence '\%'
| ./.pybuild/cpython3_3.6/build/gbp/deb/git.py:210:14: W605 invalid escape 
sequence '\%'
| ./.pybuild/cpython3_3.6/build/gbp/deb/git.py:234:10: W605 invalid escape 
sequence '\.'
| ./.pybuild/cpython3_3.6/build/gbp/deb/git.py:234:15: W605 invalid escape 
sequence '\.'
| ./.pybuild/cpython3_3.6/build/gbp/deb/git.py:265:23: W605 invalid escape 
sequence '\w'
| ./.pybuild/cpython3_3.6/build/gbp/deb/policy.py:46:28: W605 invalid escape 
sequence '\.'
| ./.pybuild/cpython3_3.6/build/gbp/deb/policy.py:46:30: W605 invalid escape 
sequence '\+'
| ./.pybuild/cpython3_3.6/build/gbp/deb/policy.py:46:32: W605 invalid escape 
sequence '\-'
| ./.pybuild/cpython3_3.6/build/gbp/deb/policy.py:58:22: W605 invalid escape 
sequence '\.'
| ./.pybuild/cpython3_3.6/build/gbp/deb/policy.py:58:24: W605 invalid escape 
sequence '\+'
| ./.pybuild/cpython3_3.6/build/gbp/deb/policy.py:58:26: W605 invalid escape 
sequence '\-'
| ./.pybuild/cpython3_3.6/build/gbp/deb/policy.py:58:28: W605 invalid escape 
sequence '\:'
| ./.pybuild/cpython3_3.6/build/gbp/deb/policy.py:58:30: W605 invalid escape 
sequence '\~'
| ./.pybuild/cpython3_3.6/build/gbp/deb/pristinetar.py:39:14: W605 invalid 
escape sequence '\w'
| ./.pybuild/cpython3_3.6/build/gbp/deb/pristinetar.py:39:16: W605 invalid 
escape sequence '\+'
| ./.pybuild/cpython3_3.6/build/gbp/deb/pristinetar.py:43:15: W605 invalid 
escape sequence '\.'
| ./.pybuild/cpython3_3.6/build/gbp/deb/pristinetar.py:43:21: W605 invalid 
escape sequence '\.'
| ./.pybuild/cpython3_3.6/build/gbp/deb/pristinetar.py:43:26: W605 invalid 
escape sequence '\.'
| ./.pybuild/cpython3_3.6/build/gbp/git/repository.py:1189:18: W605 invalid 
escape sequence '\s'
| ./.pybuild/cpython3_3.6/build/gbp/git/repository.py:1189:26: W605 invalid 
escape sequence '\s'
| ./.pybuild/cpython3_3.6/build/gbp/git/repository.py:1189:33: W605 invalid 
escape sequence '\s'
| ./.pybuild/cpython3_3.6/build/gbp/git/repository.py:1189:37: W605 invalid 
escape sequence '\S'
| ./.pybuild/cpython3_3.6/build/gbp/git/repository.py:1192:18: W605 invalid 
escape sequence '\s'
| ./.pybuild/cpython3_3.6/build/gbp/git/repository.py:1192:25: W605 invalid 
escape sequence '\s'
| ./.pybuild/cpython3_3.6/build/gbp/git/repository.py:1192:32: W605 invalid 
escape sequence '\s'
| ./.pybuild/cpython3_3.6/build/gbp/git/repository.py:1192:36: W605 invalid 
escape sequence '\S'
| ./.pybuild/cpython3_3.6/build/gbp/git/repository.py:1890:5: E301 expected 1 
blank line, found 0
| 

Bug#910444: Filesystems listed in /etc/fstab are no more automatically mounted since switching to OpenRC

[Axel Beckert]

Package: openrc
Version: 0.34-3
Severity: grave
Justification: renders package unusable

Hi,

I just installed Debian Buster/Sid from scratch on a GPD Pocket 1 and
then switched from systemd to OpenRC.

Since then, /home (on LVM on LUKS), /boot and /boot/efi (i.e. anything
from /etc/fstab except the root file system) are no more mounted
automatically despite they're listed in /etc/fstab and "mount -a"
mounts them without issues.

Also swap is not used automatically despite it's listed in /etc/fstab,
too.

Content of my /etc/fstab:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
#
/dev/mapper/vgac-root /   ext4errors=remount-ro 0   1
# /boot was on /dev/mmcblk0p5 during installation
UUID=7e1e247c-ea51-444e-b183-0036de6e84f2 /boot   ext4defaults  
  0   2
# /boot/efi was on /dev/mmcblk0p1 during installation
UUID=C4FD-2BDD  /boot/efi   vfatumask=0077  0   1
/dev/mapper/vgac-home /home   ext4defaults0   2
/dev/mapper/vgac-swap noneswapsw  0   0

What was mounted after booting:

sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
udev /dev devtmpfs rw,nosuid,relatime,size=4032644k,nr_inodes=1008161,mode=755 
0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs rw,nosuid,noexec,relatime,size=807836k,mode=755 0 0
/dev/mapper/vgac-root / ext4 rw,relatime,errors=remount-ro 0 0
tmpfs /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0
pstore /sys/fs/pstore pstore rw,relatime 0 0
tmpfs /run/shm tmpfs rw,nosuid,nodev,noexec,relatime,size=1615660k 0 0
none /sys/kernel/security securityfs rw,relatime 0 0

What has been added by "mount -a":

/dev/mmcblk0p5 /boot ext4 rw,relatime 0 0
/dev/mmcblk0p1 /boot/efi vfat 
rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro
 0 0
/dev/mapper/vgac-home /home ext4 rw,relatime 0 0

Swap hasn't been activated by "mount -a", though. (Probably expected,
just wanted to mention it.)

P.S.: I have no idea if this is in OpenRC or one of its
dependencies. Feel free to reassign as needed.

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

Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages openrc depends on:
ii  init-system-helpers  1.54
ii  insserv  1.14.0-5.4+b1
ii  libaudit11:2.8.4-2
ii  libc62.27-6
ii  libeinfo10.34-3
ii  libpam0g 1.1.8-3.8
ii  librc1   0.34-3
ii  libselinux1  2.8-1+b1

openrc recommends no packages.

Versions of packages openrc suggests:
pn  policycoreutils  
ii  sysvinit-core2.88dsf-59.10

-- no debconf information

Bug#910443: gir-to-d FTBFS: Error: Expected argument to '-I'

[Helmut Grohne]

Source: gir-to-d
Version: 0.16.1-1
Severity: serious
Tags: ftbfs

gir-to-d fails to build from source in sbuild on unstable/amd64. A build
log ends with:

| dh build --buildsystem=meson
|dh_update_autotools_config -O--buildsystem=meson
|dh_autoreconf -O--buildsystem=meson
|dh_auto_configure -O--buildsystem=meson
| cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
--localstatedir=/var --libdir=lib/x86_64-linux-gnu 
--libexecdir=lib/x86_64-linux-gnu
| The Meson build system
| Version: 0.48.0
| Source dir: /<>
| Build dir: /<>/obj-x86_64-linux-gnu
| Build type: native build
| Project name: GIR-to-D
| Project version: 0.16.0
| Appending DFLAGS from environment: '-O -g -release -wi'
| Appending LDFLAGS from environment: '-Wl,-z,relro'
| Native D compiler: ldc2 (llvm 1.11.0 "LDC - the LLVM D compiler (1.11.0):")
| Build machine cpu family: x86_64
| Build machine cpu: x86_64
| Build targets in project: 2
| Found ninja-1.8.2 at /usr/bin/ninja
|dh_auto_build -O--buildsystem=meson
| cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j1 -v
| [1/20] /usr/bin/meson --internal vcstagger ../VERSION.in VERSION 0.16.0 
/<> @VCS_TAG@ '(.*)' /<>/git describe --dirty=+ --tags
| [2/20] ldc2 -I=girtod@exe -I=. -I=.. -I=../source/ -I= -enable-color 
-J/<>/obj-x86_64-linux-gnu -O -g -release -wi   
-of='girtod@exe/source_girtod.d.o' -c ../source/girtod.d
| FAILED: girtod@exe/source_girtod.d.o 
| ldc2 -I=girtod@exe -I=. -I=.. -I=../source/ -I= -enable-color 
-J/<>/obj-x86_64-linux-gnu -O -g -release -wi   
-of='girtod@exe/source_girtod.d.o' -c ../source/girtod.d
| Error: Expected argument to '-I'
| ninja: build stopped: subcommand failed.
| dh_auto_build: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j1 -v 
returned exit code 1
| make: *** [debian/rules:8: build] Error 1
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Helmut

Bug#910384: libhandy-dev: Missing dependency on libgtk-3-dev

[Guido Günther]

Hi,
On Fri, Oct 05, 2018 at 03:19:27PM -0400, Jeremy Bicha wrote:
> Package: libhandy-0.0-dev
> Version: 0.0.3-1
> Severity: serious
> 
> I see that libhandy-0.0.pc has this line:
> Requires: gtk+-3.0
> 
> That means that libhandy-0.0-dev needs a dependency on libgtk-3-dev
> 
> By the way, GNOME 3.32 components might start depending on libhandy.
> (Buster will include GNOME 3.30 so Unstable is fine for now.) Thanks
> for packaging this!

Yeah, I will unblock testing migrations once I did some more API
adjustments upstream.
Thanks for the patches,
 -- Guido

Bug#910442: genshi FTBFS: tests fail: RuntimeError: generator raised StopIteration

[Helmut Grohne]

Source: genshi
Version: 0.7-6
Severity: serious
Tags: ftbfs

genshi fails to build from source in sbuild on unstable/amd64. A build
log ends with:

| ==
| FAIL: replace (genshi.filters.transform.Transformer)
| Doctest: genshi.filters.transform.Transformer.replace
| --
| Traceback (most recent call last):
|   File "/usr/lib/python3.7/doctest.py", line 2198, in runTest
| raise self.failureException(self.format_failure(new.getvalue()))
| AssertionError: Failed doctest test for 
genshi.filters.transform.Transformer.replace
|   File 
"/<>/.pybuild/cpython3_3.7_genshi/build/genshi/filters/transform.py",
 line 368, in replace
| 
| --
| File 
"/<>/.pybuild/cpython3_3.7_genshi/build/genshi/filters/transform.py",
 line 374, in genshi.filters.transform.Transformer.replace
| Failed example:
| print((html | Transformer('.//title/text()').replace('New Title')))
| Exception raised:
| Traceback (most recent call last):
|   File 
"/<>/.pybuild/cpython3_3.7_genshi/build/genshi/filters/transform.py",
 line 118, in __iter__
| event = next(self.stream)
| StopIteration
| 
| The above exception was the direct cause of the following exception:
| 
| Traceback (most recent call last):
|   File "/usr/lib/python3.7/doctest.py", line 1329, in __run
| compileflags, 1), test.globs)
|   File "", line 
1, in 
| print((html | Transformer('.//title/text()').replace('New Title')))
|   File 
"/<>/.pybuild/cpython3_3.7_genshi/build/genshi/core.py", line 248, 
in __str__
| return self.render()
|   File 
"/<>/.pybuild/cpython3_3.7_genshi/build/genshi/core.py", line 184, 
in render
| return encode(generator, method=method, encoding=encoding, out=out)
|   File 
"/<>/.pybuild/cpython3_3.7_genshi/build/genshi/output.py", line 
57, in encode
| return _encode(''.join(list(iterator)))
|   File 
"/<>/.pybuild/cpython3_3.7_genshi/build/genshi/output.py", line 
241, in __call__
| for kind, data, pos in stream:
|   File 
"/<>/.pybuild/cpython3_3.7_genshi/build/genshi/output.py", line 
669, in __call__
| for kind, data, pos in stream:
|   File 
"/<>/.pybuild/cpython3_3.7_genshi/build/genshi/output.py", line 
774, in __call__
| for kind, data, pos in chain(stream, [(None, None, None)]):
|   File 
"/<>/.pybuild/cpython3_3.7_genshi/build/genshi/output.py", line 
594, in __call__
| for ev in stream:
|   File 
"/<>/.pybuild/cpython3_3.7_genshi/build/genshi/core.py", line 289, 
in _ensure
| for event in stream:
|   File 
"/<>/.pybuild/cpython3_3.7_genshi/build/genshi/core.py", line 289, 
in _ensure
| for event in stream:
|   File 
"/<>/.pybuild/cpython3_3.7_genshi/build/genshi/filters/transform.py",
 line 706, in _unmark
| for mark, event in stream:
|   File 
"/<>/.pybuild/cpython3_3.7_genshi/build/genshi/filters/transform.py",
 line 1076, in __call__
| for mark, event in stream:
| RuntimeError: generator raised StopIteration
| 
| 
| --
| Ran 861 tests in 0.443s
| 
| FAILED (failures=8, errors=56, skipped=1)
| Test failed: 
| error: Test failed: 
| E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: 
python3.7 setup.py test 
| dh_auto_test: pybuild --test -i python{version} -p "3.7 3.6" returned exit 
code 13
| make: *** [debian/rules:8: build] Error 25
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Could it be that this is due to Python 3.7 having become a supported
Python version?

Helmut

Processed: severity of 787603 is serious

[Debian Bug Tracking System]

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

> severity 787603 serious
Bug #787603 [src:genshi] [src:genshi] Some sources are not included in your 
package
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#910440: freediameter FTBFS: error: 'SCTP_SEND_FAILED_EVENT' undeclared

[Helmut Grohne]

Source: freediameter
Version: 1.2.1-6
Severity: serious
Tags: ftbfs

freediameter fails to build from source in sbuild on unstable/amd64. A
non-parallel build ends with:

| [ 34%] Building C object libfdcore/CMakeFiles/libfdcore.dir/sctp.c.o
| cd /<>/obj-x86_64-linux-gnu/libfdcore && /usr/bin/cc 
-D_GNU_SOURCE -Dlibfdcore_EXPORTS -I/<>/include 
-I/<>/obj-x86_64-linux-gnu/include -I/<>/libfdcore  
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC   -o 
CMakeFiles/libfdcore.dir/sctp.c.o   -c /<>/libfdcore/sctp.c
| /<>/libfdcore/sctp.c: In function 'fd_sctp_recvmeta':
| /<>/libfdcore/sctp.c:1262:9: error: 'SCTP_SEND_FAILED_EVENT' 
undeclared (first use in this function); did you mean 'SCTP_SEND_FAILED'?
| case SCTP_SEND_FAILED_EVENT:
|  ^~
|  SCTP_SEND_FAILED
| /<>/libfdcore/sctp.c:1262:9: note: each undeclared identifier is 
reported only once for each function it appears in
| /<>/libfdcore/sctp.c:1274:9: error: 
'SCTP_NOTIFICATIONS_STOPPED_EVENT' undeclared (first use in this function); did 
you mean 'SCTP_AUTHENTICATION_EVENT'?
| case SCTP_NOTIFICATIONS_STOPPED_EVENT:
|  ^~~~
|  SCTP_AUTHENTICATION_EVENT
| make[3]: *** [libfdcore/CMakeFiles/libfdcore.dir/build.make:402: 
libfdcore/CMakeFiles/libfdcore.dir/sctp.c.o] Error 1
| make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
| make[2]: *** [CMakeFiles/Makefile2:1096: 
libfdcore/CMakeFiles/libfdcore.dir/all] Error 2
| make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
| make[1]: *** [Makefile:144: all] Error 2
| make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu'
| dh_auto_build: cd obj-x86_64-linux-gnu && make -j1 "INSTALL=install 
--strip-program=true" returned exit code 2
| make: *** [debian/rules:19: build] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Helmut

Processed: affects 910119, found 861500 in 1.1.3-4, found 865399 in 2.2.0.1-3, tagging 910292

[Debian Bug Tracking System]

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

> affects 910119 + python-paste
Bug #910119 [python3-paste] python{,3}-paste: broken symlink: 
/usr/lib/python{2.7,3}/dist-packages/paste/evalexception/media/MochiKit.packed.js
Added indication that 910119 affects python-paste
> found 861500 1.1.3-4
Bug #861500 [graphite-api] graphite-api: broken symlinks: 
/usr/share/doc/graphite-api/html/_static/*/* -> 
../../../../../sphinx_rtd_theme/static/*/*
Marked as found in versions graphite-api/1.1.3-4.
> found 865399 2.2.0.1-3
Bug #865399 [libghc-cabal-dev] libghc-cabal-dev and ghc: error when trying to 
install together
Marked as found in versions haskell-cabal/2.2.0.1-3.
> tags 910292 + experimental
Bug #910292 [src:srtp] Do not release srtp 1.x with Buster
Added tag(s) experimental.
> thanks
Stopping processing here.

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

Bug#910429: grub-cloud-amd64: fails to install in a chroot

[Bastian Blank]

Hi

On Sat, Oct 06, 2018 at 09:15:13AM +0200, Andreas Beckmann wrote:
> during a test with piuparts I noticed your package failed to install.

This is more or less expected, as this package will break your
bootloader if it finds anything useful.

>   As
> per definition of the release team this makes the package too buggy for
> a release, thus the severity.

I don't see piuparts mentioned in
https://release.debian.org/buster/rc_policy.txt

Bastian

-- 
Beam me up, Scotty, there's no intelligent life down here!

Bug#910248: marked as done (kmymoney: KMyMoney needs to be recompiled against KDE PIM 18.08.)

[Debian Bug Tracking System]

Your message dated Sat, 06 Oct 2018 10:18:55 +
with message-id 
and subject line Bug#910248: fixed in kmymoney 5.0.1-3
has caused the Debian Bug report #910248,
regarding kmymoney: KMyMoney needs to be recompiled against KDE PIM 18.08.
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.)


-- 
910248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910248
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kmymoney
Version: 5.0.1-2
Severity: serious
Control: block 909288 by -1

Hey,

KDE PIM 18.08 changes ABI, so KMyMoney needs to recompiled against the
new version. But as KMyMoney 5.0.1 is currently in experimental, this
can't be done via the normal transition (so far as I unserstand.

hefee

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

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

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

Debian distribution maintenance software
pp.
Pino Toscano  (supplier of updated kmymoney package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 06 Oct 2018 12:07:03 +0200
Source: kmymoney
Binary: kmymoney kmymoney-common
Architecture: source
Version: 5.0.1-3
Distribution: experimental
Urgency: medium
Maintainer: Debian KDE Extras Team 
Changed-By: Pino Toscano 
Description:
 kmymoney   - personal finance manager for KDE
 kmymoney-common - KMyMoney architecture independent files
Closes: 910248
Changes:
 kmymoney (5.0.1-3) experimental; urgency=medium
 .
   * Team upload.
   * Switch Vcs-* fields to salsa.debian.org.
   * Backport upstream commit e5198a902996b27bf9abde0ad24af82d55ab5dc1 to fix
 build with Qt >= 5.11; patch upstream_Fix-build-with-Qt-5.11.patch.
   * The rebuild will make kmymoney use the new KDE PIM libraries.
 (Closes: #910248)
   * Bump Standards-Version to 4.2.1, no changes required.
   * Switch from --list-missing to dh_missing --fail-missing.
   * Remove empty line at the end of changelog.
Checksums-Sha1:
 0465e87be251eebd4884b57281787d9aa63be19c 2790 kmymoney_5.0.1-3.dsc
 b9a563631b8786cf75a949134568b82cc69c130b 12216 kmymoney_5.0.1-3.debian.tar.xz
 84084c4bd26b0507e4b3323a13d00ceff30e6dff 23269 
kmymoney_5.0.1-3_source.buildinfo
Checksums-Sha256:
 8399a7526bdd591ae187149eaf0488a6c1df6142c551710d56ba47fe13f2e8d3 2790 
kmymoney_5.0.1-3.dsc
 06a1622c03274a676b3d784bce8f3afcf9a77c1be2933a20c786f31f64476cc6 12216 
kmymoney_5.0.1-3.debian.tar.xz
 f2c84d328e8c793a19753989f4b2265c517bb4913e8c5207616a9033090c4366 23269 
kmymoney_5.0.1-3_source.buildinfo
Files:
 ce192fe605687a42eeb7429a7bd85568 2790 kde optional kmymoney_5.0.1-3.dsc
 ff6c8f0705f41dea1d09e4aed40a51be 12216 kde optional 
kmymoney_5.0.1-3.debian.tar.xz
 64b9f8da0c0135b7e78b6a7543bc3719 23269 kde optional 
kmymoney_5.0.1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEXyqfuC+mweEHcAcHLRkciEOxP00FAlu4iXcACgkQLRkciEOx
P02sow//RvcgY8EEutsuFhlHu9hiB5kgBhG1Rc/uUQEaR8wr4Bas/BkzEuTTxsW0
FIF8DkZDHUONsf8EZl8RQlpy5VQcxWzdHN3xPyb7eFSDJWQ/DzzU8k66OhbX6rlf
5ZHB2FvL+MMLdJQahSnrNiBXf6zaiMjokufCuQdB8QvIy4NehCBHPzpv/JhbsNvE
5EpYnvuRhbegqn2eEyyU9lG3Y2cnFRyZFWJpJxW3gKqI3PHfgpjqzpHZoh/Qjfa7
lbNmNi663R5J8hNOnO8DssnnZ6qSGcFHXBPAwq3JCo0aVUNmrZTB8+d02K0cxNir
z/JQyHZShLhHXqNpfCZA/Ge1joIqKIF66BN4lq05YZetuycBk8g7G7kpOJoPc5+p
65lohBXa6aTo3byg+E12wjBSIO0CRYE+VmhxoTNanXQFZqPfsbItrr8iKhLejBPA
G7g2BX6tUgPSxnGDDYHYThjEevwqrZeskDL+7yUF3yGZ31S+R5HzN0esXYtRh3KJ
7t8guhhJoJPcW/LPF7lhK1PlJnNXUEF6b4+00vRWMKNi1dp2gtbdENLr5YF31vHV
R3OcuxNzxpjDoLjcqiWJPfmw9WLO4ykYMc9TQA76v8Kqv6bkW+g5Z3E5XQUa9Z7k

Bug#896238: marked as done (python3-gphoto2cffi: gphoto2cffi fails to import)

[Debian Bug Tracking System]

Your message dated Sat, 06 Oct 2018 10:02:08 +
with message-id 
and subject line Bug#896238: fixed in gphoto2-cffi 0.3~a1-1.1~deb9u1
has caused the Debian Bug report #896238,
regarding python3-gphoto2cffi: gphoto2cffi fails to import
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.)


-- 
896238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896238
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-gphoto2cffi
Version: 0.3~a1-1+b1
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python3-gphoto2cffi importing the module gphoto2cffi
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/gphoto2cffi/__init__.py", line 1, in 

from .gphoto2 import (Camera, list_cameras, supported_cameras,
  File "/usr/lib/python3/dist-packages/gphoto2cffi/gphoto2.py", line 15, in 

from . import errors, backend
  File "/usr/lib/python3/dist-packages/gphoto2cffi/backend.py", line 56, in 

'extract_exif': _lib.GP_FILE_OPERATION_EXIF})
  File "/usr/lib/python3.6/enum.py", line 293, in __call__
return cls._create_(value, names, module=module, qualname=qualname, 
type=type, start=start)
  File "/usr/lib/python3.6/enum.py", line 399, in _create_
enum_class = metacls.__new__(metacls, class_name, bases, classdict)
  File "/usr/lib/python3.6/enum.py", line 153, in __new__
enum_class = super().__new__(metacls, cls, bases, classdict)
TypeError: type.__new__() argument 1 must be str, not bytes

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut
--- End Message ---
--- Begin Message ---
Source: gphoto2-cffi
Source-Version: 0.3~a1-1.1~deb9u1

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated gphoto2-cffi package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 16 Sep 2018 20:31:17 +0300
Source: gphoto2-cffi
Binary: python-gphoto2cffi python3-gphoto2cffi
Architecture: source
Version: 0.3~a1-1.1~deb9u1
Distribution: stretch
Urgency: high
Maintainer: Aigars Mahinovs 
Changed-By: Adrian Bunk 
Description:
 python-gphoto2cffi - GPhoto2 bindings with simpler API
 python3-gphoto2cffi - GPhoto2 bindings with simpler API
Closes: 896238
Changes:
 gphoto2-cffi (0.3~a1-1.1~deb9u1) stretch; urgency=medium
 .
   * Non-maintainer upload.
   * Rebuild for stretch.
 .
 gphoto2-cffi (0.3~a1-1.1) unstable; urgency=high
 .
   * Non-maintainer upload.
   * Add upstream fix to unbreak python3-gphoto2cffi. (Closes: #896238)
Checksums-Sha1:
 79b4c0ccedbe09c68b7919605fbc3ed8ea613e97 2016 
gphoto2-cffi_0.3~a1-1.1~deb9u1.dsc
 27e2b1bed27a208140e44154d875c1ae784974b4 2544 
gphoto2-cffi_0.3~a1-1.1~deb9u1.debian.tar.xz
Checksums-Sha256:
 fd942221124d5ff68294c19f09576b10e9f6cd99ab02235da15a4c55d6439b82 2016 
gphoto2-cffi_0.3~a1-1.1~deb9u1.dsc
 024ac3c297e2ea6e576c6b281fa5d022728678ef8913175a32da141e7f478822 2544 
gphoto2-cffi_0.3~a1-1.1~deb9u1.debian.tar.xz
Files:
 a041eaca89f7d241baff2c5ac0cc16b9 2016 python optional 
gphoto2-cffi_0.3~a1-1.1~deb9u1.dsc
 d7baa853d3e7204f93c940fbcffa9825 2544 python optional 
gphoto2-cffi_0.3~a1-1.1~deb9u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAluel5MACgkQiNJCh6LY
mLGEVQ//V5zKnDM73qn22pjZswyqDDlvYUcRRCS4hNugg1/89QAvA4avtidzHWri
U9vLEsgkrdgrV6hOFPz8ydnoa6ah0Cjwzc2VtF0heTbiaIv1NgDwzJ/wkoBoEw1h
nJz1LcgQkrsg9wTk+uYHysATHVpL2bj4CktEvNBV6uTMQJj1V1RJNi+TaIn+V0BX
eeCVsjXrXnFjmEbzXpmg2LFn0mKouSbksSDaZxDSOJXh8Cc9G1eoAz18xHgFBgcU

Bug#889740: marked as done (crashes when built with hardening)

[Debian Bug Tracking System]

Your message dated Sat, 06 Oct 2018 10:02:09 +
with message-id 
and subject line Bug#889740: fixed in xmotd 1.17.3b-9+deb9u1
has caused the Debian Bug report #889740,
regarding crashes when built with hardening
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.)


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

Package: xmotd
Version: 1.17.3b-9

Dear maintainers,

on several Debian 9 computers, the stretch version of xmotd crashed 
every time with the following error message:


xmotd: Bad address

Then, I installed version 1.17.3b-8 from oldstable, which did not crash. 
Then, I built from source, which gave the following results:


1. Neither 1.17.3b-8 nor 1.17.3b-9 work if compiled under stretch.

2. Version 1.17.3b-8 works if compiled under jessie.

3. Version 1.17.3b-9 works if compiled under jessie AND hardening flags 
are removed from debian/rules.


Regards
  Christoph
--- End Message ---
--- Begin Message ---
Source: xmotd
Source-Version: 1.17.3b-9+deb9u1

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated xmotd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 16 Sep 2018 21:30:35 +0300
Source: xmotd
Binary: xmotd
Architecture: source
Version: 1.17.3b-9+deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Hugo Lefeuvre 
Changed-By: Adrian Bunk 
Description:
 xmotd  - message of the day browser for X
Closes: 889740
Changes:
 xmotd (1.17.3b-9+deb9u1) stretch; urgency=medium
 .
   * Non-maintainer upload.
   * debian/patches/bugfix/fix-warnings-hardening-build.patch:
 - Fix most compile time warnings and avoid crash with hardening
   flags (acknowledgments to Christoph Pleger for the patch)
   (Closes: #889740).
 - Backported to stretch is a partial version of this patch
   sufficient to fix the crash.
Checksums-Sha1:
 16fe2dca0ca8795893bcb2c1ec39a35f0b4ba675 1876 xmotd_1.17.3b-9+deb9u1.dsc
 c90a60a408f7c74b7a3c01c5023baace7ffae766 10500 
xmotd_1.17.3b-9+deb9u1.debian.tar.xz
Checksums-Sha256:
 0452c72d22e862812c2ac05a57118b653d58ead106f3d1643c505c8d0105a300 1876 
xmotd_1.17.3b-9+deb9u1.dsc
 a129af389879ba99fd4964316a95f970f681e4a31ffdecd4940ddd67e2dd058a 10500 
xmotd_1.17.3b-9+deb9u1.debian.tar.xz
Files:
 f8f781be8c7a82bd09cd39af31118011 1876 x11 optional xmotd_1.17.3b-9+deb9u1.dsc
 501a38346743219a37219903e5b26e39 10500 x11 optional 
xmotd_1.17.3b-9+deb9u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAluepDMACgkQiNJCh6LY
mLE6Aw//TF71JUTXk3CCOk8hcmwlvL0zPuXZFySggMvQ3Oo7DpICsJIi/cH9IG0V
te2yPDVqMrOf7PX95gsW/Ux8TqmJdTXDBfldIat18qdFTBYQ0j/BBRSIhsVTRpwP
CPCD5bKNxtqEQqCQXuNakfiSQ7uCAJu4SQvHIzwWYqAsGk+vb4Z7bKtopsBzl087
Tu05PYCTOcceYajln/2AJTuxhpfKR1ykqAOxdH8VGOMXPIq86e/amV/+fI558OsD
t7F8HaLGfjTQUFPa7N7Zqm3zJy0pMryg+ncunhnEFeHclQ7EKfylhUbdu0wCHnar
cU4uLCUBoK5AfTabKNIi+3yYUUb+2TsnRp/mJrvNwaCkBxfoiHjjvHs2R8oD5pbv
mQeG64Pwf9H6HKOGObBp3SBKhppwsgxdnVynmWzkltLjSDbRrNDLLr1Nl7+8WVjN
Gw6hLeBXRqtGUudzMpLX1vhXpCpH1RSI64pDgJm42mphB5tVzsohpgpxbmsxJLKI
2krNUqtXFDwMz4LQ3HDU7UmVbXda7z0Ez8w4BJP4pJLIm+pEXM6ELTzPh9hJkson
wBN+HNF2AmPa8FFvy/tdC2vCy9AlQ3WsP4XI+KNoltFJcWABb5zP5/w/XegOpqt6
w0nk24ho7C0FFhECTNcrdWOxy7nkUsJfW6EnHYA4Yhqapl/GO9U=
=7Kif
-END PGP SIGNATURE End Message ---

Bug#910395: mediathekview: No longer works due to "missing" openjfx

[FPWild]

Hallo Hilko,

ich hatte das gleiche Problem, auch mit sid.
Ursache ist aber scheinbar das Paket "libopenjfx-java".
Ich habe es durch die stable Version ersetzt und nun startet
mediathekview wieder.
--> sudo apt-get install libopenjfx-java=8u111-b14-1

Gruß
Frank



On Fri, 05 Oct 2018 22:26:50 +0200 Hilko Bengen  wrote:

> Package: mediathekview
> Version: 13.0.6-1
> Severity: serious
>
> Dear Maintainer,
>
> when trying to start mediathekview, I get the following:
> ,
> | $ mediathekview
> | ===
> | JavaFX wurde nicht im klassenpfad gefunden.
> | Stellen Sie sicher, dass Sie ein Java JRE ab Version 8 benutzen.
> | Falls Sie Linux nutzen, installieren Sie das openjfx-Paket ihres
Package-Managers,
> | oder nutzen Sie eine eigene JRE-Installation.
> | ===
> `
>
> (Translated into English: JavaFX was not found in the classpah. Ensure
> that you are using JRE 8 or later. If you use Linux, install the openjfx
> package provided by your pacakge manager or use a seaparate JRE
> installation.)
>
> As you can see below, libopenjfx-java is installed.
>
> This is the version that is apparently selected by java_wrappers:
> ,
> | $ bash
> | $ . /usr/lib/java-wrappers/java-wrappers.sh
> | $ find_java_runtime java8
> | $ run_java --version
> | openjdk 10.0.2 2018-07-17
> | OpenJDK Runtime Environment (build 10.0.2+13-Debian-1)
> | OpenJDK 64-Bit Server VM (build 10.0.2+13-Debian-1, mixed mode)
> `
>
> Let's see... Selecting different JREs does not help:
> ,
> | $ JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/ mediathekview
> | ===
> | JavaFX wurde nicht im klassenpfad gefunden.
> | Stellen Sie sicher, dass Sie ein Java JRE ab Version 8 benutzen.
> | Falls Sie Linux nutzen, installieren Sie das openjfx-Paket ihres
Package-Managers,
> | oder nutzen Sie eine eigene JRE-Installation.
> | ===
> `
> ,
> | $ JAVA_HOME=/usr/lib/jvm/java-11-openjdk-amd64/ mediathekview
> | ===
> | JavaFX wurde nicht im klassenpfad gefunden.
> | Stellen Sie sicher, dass Sie ein Java JRE ab Version 8 benutzen.
> | Falls Sie Linux nutzen, installieren Sie das openjfx-Paket ihres
Package-Managers,
> | oder nutzen Sie eine eigene JRE-Installation.
> | ===
> `
>
> Unfortunately, the error message is made deliberately useless by
hiding the
> ClassNotFoundException:
> ,[ mediathekview-13.0.6/src/main/java/mediathek/Main.java ]
> | private static boolean hasJavaFx() {
> | try {

Bug#879034: pdfshuffler: port to gir1.2-poppler-0.18

[Jerome Robert]

On Tue, 12 Jun 2018 23:48:17 +0500 Andrey Rahmatullin  wrote:

> I wanted to try packaging this and I cannot find the upstream
> source. - https://github.com/jeromerobert/pdfshuffler, especially 
> https://github.com/jeromerobert/pdfshuffler/issues/9, say this is an 
> unofficial mirror, and it seems the porting work is not specific to 
> that repo.

I sent and e-mail to Konstantinos Poulios (the original upstream owner)
to ask about his plans. If he agree (or do not answer) I'll make
https://github.com/jeromerobert/pdfshuffler official and maintain
pdfshuffler there with the help of the community.

I also reopened https://github.com/jeromerobert/pdfshuffler/issues/9

Regards,

Jerome



signature.asc
Description: OpenPGP digital signature

Bug#909818: firefox: Web Content is eating nearly 100% CPU, several of them

[Martin Steigerwald]

Bert - 04.10.18, 13:38:
> Same problem here, issue persists in 62.0.3-1 for me.

I hesitated updating due to this bug reported by apt-listbugs, however 
today I did and I do not see this issue with Firefox 62.0.3-1 on Plasma 
desktop on ThinkPad T520 with Sandybridge Graphics.

Thanks,
-- 
Martin

Bug#899705: marked as done (sword-text-web: Invalid maintainer address pkg-crosswire-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Sat, 6 Oct 2018 09:38:01 +0200
with message-id 

and subject line done
has caused the Debian Bug report #899705,
regarding sword-text-web: Invalid maintainer address 
pkg-crosswire-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.)


-- 
899705: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899705
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:sword-text-web
Version: 3.1-2
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of sword-text-web,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package sword-text-web since the list address
pkg-crosswire-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-crosswire-de...@lists.alioth.debian.org is 16.

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 ---
the email address was fixed
-- 
Teus Benschop
teusjanne...@gmail.com
0318 712046
--- End Message ---

Bug#899702: marked as done (sword-comm-tdavid: Invalid maintainer address pkg-crosswire-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Sat, 6 Oct 2018 09:37:13 +0200
with message-id 

and subject line done
has caused the Debian Bug report #899702,
regarding sword-comm-tdavid: Invalid maintainer address 
pkg-crosswire-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.)


-- 
899702: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899702
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:sword-comm-tdavid
Version: 1.1-7
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of sword-comm-tdavid,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package sword-comm-tdavid since the list address
pkg-crosswire-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-crosswire-de...@lists.alioth.debian.org is 16.

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 ---
email was fixed
-- 
Teus Benschop
teusjanne...@gmail.com
0318 712046
--- End Message ---

Bug#899776: marked as done (sword-comm-mhcc: Invalid maintainer address pkg-crosswire-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Sat, 6 Oct 2018 09:35:01 +0200
with message-id 

and subject line Done
has caused the Debian Bug report #899776,
regarding sword-comm-mhcc: Invalid maintainer address 
pkg-crosswire-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.)


-- 
899776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899776
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:sword-comm-mhcc
Version: 1.1.0-2
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of sword-comm-mhcc,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package sword-comm-mhcc since the list address
pkg-crosswire-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-crosswire-de...@lists.alioth.debian.org is 16.

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 ---
Email address was fixed.
-- 
Teus Benschop
teusjanne...@gmail.com
0318 712046
--- End Message ---

Bug#899699: marked as done (sword-comm-scofield: Invalid maintainer address pkg-crosswire-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Sat, 6 Oct 2018 09:36:07 +0200
with message-id 

and subject line Done
has caused the Debian Bug report #899699,
regarding sword-comm-scofield: Invalid maintainer address 
pkg-crosswire-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.)


-- 
899699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899699
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:sword-comm-scofield
Version: 1.0-7
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of sword-comm-scofield,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package sword-comm-scofield since the list address
pkg-crosswire-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-crosswire-de...@lists.alioth.debian.org is 16.

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 ---
Email was fixed
-- 
Teus Benschop
teusjanne...@gmail.com
0318 712046
--- End Message ---

Processed: severity of 910430 is important

[Debian Bug Tracking System]

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

> severity 910430 important
Bug #910430 [src:clamav] clamav: CVE-2018-15378: denial-of-service in MEW 
unpacking feature
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#910430: clamav: CVE-2018-15378: denial-of-service in MEW unpacking feature

[Salvatore Bonaccorso]

Source: clamav
Version: 0.100.1+dfsg-1
Severity: grave
Tags: security upstream
Control: found -1 0.100.1+dfsg-0+deb9u1

Hi,

The following vulnerability was published for clamav.

CVE-2018-15378[0]:
denial-of-service in MEW unpacking feature

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-15378
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-15378
[1] https://blog.clamav.net/2018/10/clamav-01002-has-been-released.html
[2] http://lists.clamav.net/pipermail/clamav-announce/2018/33.html

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Processed: clamav: CVE-2018-15378: denial-of-service in MEW unpacking feature

[Debian Bug Tracking System]

Processing control commands:

> found -1 0.100.1+dfsg-0+deb9u1
Bug #910430 [src:clamav] clamav: CVE-2018-15378: denial-of-service in MEW 
unpacking feature
Marked as found in versions clamav/0.100.1+dfsg-0+deb9u1.

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

Bug#910429: grub-cloud-amd64: fails to install in a chroot

[Andreas Beckmann]

Package: grub-cloud-amd64
Version: 0.0.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package grub-cloud-amd64.
  (Reading database ... 
(Reading database ... 5367 files and directories currently installed.)
  Preparing to unpack .../grub-cloud-amd64_0.0.1_amd64.deb ...
  Unpacking grub-cloud-amd64 (0.0.1) ...
  Setting up grub-cloud-amd64 (0.0.1) ...
  grub-probe: error: cannot find a device for /boot/ (is /dev mounted?).
  Installing for i386-pc platform.
  grub-install: error: cannot find a device for /boot/grub (is /dev mounted?).
  dpkg: error processing package grub-cloud-amd64 (--configure):
   installed grub-cloud-amd64 package post-installation script subprocess 
returned error exit status 1
  Errors were encountered while processing:
   grub-cloud-amd64


cheers,

Andreas


grub-cloud-amd64_0.0.1.log.gz
Description: application/gzip

Bug#910336: marked as done (sword: fails to build except on arch: all)

[Debian Bug Tracking System]

Your message dated Sat, 6 Oct 2018 08:47:42 +0200
with message-id 

and subject line Fixed
has caused the Debian Bug report #910336,
regarding sword: fails to build except on arch: all
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.)


-- 
910336: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910336
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sword
Version: 1.7.3.1+dfsg-1
Severity: serious
Tags: ftbfs
X-Debbugs-CC: domini...@corbex.org, teusjanne...@gmail.com

sword fails to build:
https://buildd.debian.org/status/package.php?p=sword

It looks like the problem is that it doesn't handle builds where the
arch-independent package libsword-common isn't built.

By the way, sword 1.8.1 was released in January.

Build log excerpt
---
dh_install --list-missing
dh_install: Please use dh_missing --list-missing/--fail-missing instead
dh_install: This feature will be removed in compat 12.
# Fixes FTBFS if running binary-arch target only
chmod -x debian/libsword-common/usr/share/sword/locales.d/*
chmod: cannot access
'debian/libsword-common/usr/share/sword/locales.d/*': No such file or
directory
make[1]: [debian/rules:32: override_dh_install] Error 1 (ignored)
# Remove empty directory: usr/share/sword/modules
rmdir debian/libsword-common/usr/share/sword/modules
rmdir: failed to remove
'debian/libsword-common/usr/share/sword/modules': No such file or
directory
make[1]: *** [debian/rules:34: override_dh_install] Error 1


Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
The package built successfully on my local amd64 Sid box.
That is why I expected it would build in the Debian infrastructure too.
It didn't.
The build error has now been fixed.
A fixed package was uploaded.
It can now be seen that the fixed package builds fine in the Debian
infrastructure.
Now closing the bug again.
Thank you for spotting this.

-- 
Teus Benschop
teusjanne...@gmail.com
0318 712046
--- End Message ---

Bug#902507: node-multiparty: FTBFS in buster/sid (TypeError: mime.lookup is not a function)

[Petter Reinholdtsen]

The lookup() function in the mime library changed name to getType()
in the mime library version 2.  The dependency should be changed and
the name updated to solve this problem.

-- 
Happy hacking
Petter Reinholdtsen

Bug#908681: libsane1: nothing provides libsane so xsane uninstallable

[Ben Caradoc-Davies]

I was able to install libsane1 1.0.27-3 without removing xsane, so this 
aspect of the issue seems to be resolved in 1.0.27-3. Thanks very much.


Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Bug#910423: guacamole: broken symlink: /usr/share/guacamole/guacamole/WEB-INF/lib/stax-api.jar -> ../../../../java/stax-api.jar

[Andreas Beckmann]

Package: guacamole
Version: 0.9.9+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

>From the attached log (scroll to the bottom...):

1m22.8s ERROR: FAIL: Broken symlinks:
  /usr/share/guacamole/guacamole/WEB-INF/lib/stax-api.jar -> 
../../../../java/stax-api.jar (guacamole)


Is guacamole missing a dependency on libstax-java ?


cheers

Andreas


guacamole_0.9.9+dfsg-1.log.gz
Description: application/gzip

Bug#910422: grr-server: broken symlinks: /usr/share/grr-server/grr/artifacts/* -> debian/grr-server/usr/lib/python2.7/dist-packages/grr/artifacts/*

[Andreas Beckmann]

Package: grr-server
Version: 3.1.0.2+dfsg-6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

>From the attached log (scroll to the bottom...):

2m42.8s ERROR: FAIL: Broken symlinks:
  /usr/share/grr-server/grr/artifacts/wmi.yaml -> 
debian/grr-server/usr/lib/python2.7/dist-packages/grr/artifacts/wmi.yaml 
(grr-server)
  /usr/share/grr-server/grr/artifacts/windows_dll_hijacking.yaml -> 
debian/grr-server/usr/lib/python2.7/dist-packages/grr/artifacts/windows_dll_hijacking.yaml
 (grr-server)
  /usr/share/grr-server/grr/artifacts/windows.yaml -> 
debian/grr-server/usr/lib/python2.7/dist-packages/grr/artifacts/windows.yaml 
(grr-server)
  /usr/share/grr-server/grr/artifacts/webbrowser.yaml -> 
debian/grr-server/usr/lib/python2.7/dist-packages/grr/artifacts/webbrowser.yaml 
(grr-server)
  /usr/share/grr-server/grr/artifacts/unix_common.yaml -> 
debian/grr-server/usr/lib/python2.7/dist-packages/grr/artifacts/unix_common.yaml
 (grr-server)
  /usr/share/grr-server/grr/artifacts/ntfs.yaml -> 
debian/grr-server/usr/lib/python2.7/dist-packages/grr/artifacts/ntfs.yaml 
(grr-server)
  /usr/share/grr-server/grr/artifacts/macos.yaml -> 
debian/grr-server/usr/lib/python2.7/dist-packages/grr/artifacts/macos.yaml 
(grr-server)
  /usr/share/grr-server/grr/artifacts/linux_proc.yaml -> 
debian/grr-server/usr/lib/python2.7/dist-packages/grr/artifacts/linux_proc.yaml 
(grr-server)
  /usr/share/grr-server/grr/artifacts/linux.yaml -> 
debian/grr-server/usr/lib/python2.7/dist-packages/grr/artifacts/linux.yaml 
(grr-server)
  /usr/share/grr-server/grr/artifacts/legacy.yaml -> 
debian/grr-server/usr/lib/python2.7/dist-packages/grr/artifacts/legacy.yaml 
(grr-server)
  /usr/share/grr-server/grr/artifacts/kaspersky_careto.yaml -> 
debian/grr-server/usr/lib/python2.7/dist-packages/grr/artifacts/kaspersky_careto.yaml
 (grr-server)
  /usr/share/grr-server/grr/artifacts/java.yaml -> 
debian/grr-server/usr/lib/python2.7/dist-packages/grr/artifacts/java.yaml 
(grr-server)
  /usr/share/grr-server/grr/artifacts/installed_modules.yaml -> 
debian/grr-server/usr/lib/python2.7/dist-packages/grr/artifacts/installed_modules.yaml
 (grr-server)
  /usr/share/grr-server/grr/artifacts/config_files.yaml -> 
debian/grr-server/usr/lib/python2.7/dist-packages/grr/artifacts/config_files.yaml
 (grr-server)
  /usr/share/grr-server/grr/artifacts/cloud_services.yaml -> 
debian/grr-server/usr/lib/python2.7/dist-packages/grr/artifacts/cloud_services.yaml
 (grr-server)
  /usr/share/grr-server/grr/artifacts/applications.yaml -> 
debian/grr-server/usr/lib/python2.7/dist-packages/grr/artifacts/applications.yaml
 (grr-server)
  /usr/share/grr-server/grr/artifacts/antivirus.yaml -> 
debian/grr-server/usr/lib/python2.7/dist-packages/grr/artifacts/antivirus.yaml 
(grr-server)


The targets contain build-time paths.


cheers,

andreas


grr-server_3.1.0.2+dfsg-6.log.gz
Description: application/gzip