Bug#905191: libecm1-dev: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Jerome BENOIT]

Hi Andreas,

I thought that I fixed this issue.

The difficulty here is that I am blind here:
how can I reproduce the issue on my own  ?

Thanks,
Jerome

--
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calcu...@rezozer.net
AE28 AE15 710D FF1D 87E5  A762 3F92 19A6 7F36 C68B



signature.asc
Description: OpenPGP digital signature

Bug#909350: marked as done (ell FTBFS with kernel 4.18 headers)

[Debian Bug Tracking System]

Your message dated Fri, 05 Oct 2018 04:49:04 +
with message-id 
and subject line Bug#909350: fixed in ell 0.10+git20181001.0b885d95-1
has caused the Debian Bug report #909350,
regarding ell FTBFS with kernel 4.18 headers
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.)


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

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

...
ell/key.c: In function 'kernel_dh_compute':
ell/key.c:205:38: error: 'struct keyctl_dh_params' has no member named 
'private'; did you mean 'dh_private'?
  struct keyctl_dh_params params = { .private = private,
  ^~~
  dh_private


The suggestion from gcc looks correct to me.
--- End Message ---
--- Begin Message ---
Source: ell
Source-Version: 0.10+git20181001.0b885d95-1

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

Debian distribution maintenance software
pp.
Nobuhiro Iwamatsu  (supplier of updated ell package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 02 Oct 2018 12:25:41 +0900
Source: ell
Binary: libell0 libell-dev
Architecture: source amd64
Version: 0.10+git20181001.0b885d95-1
Distribution: unstable
Urgency: medium
Maintainer: Nobuhiro Iwamatsu 
Changed-By: Nobuhiro Iwamatsu 
Description:
 libell-dev - development files for the Embedded Linux library
 libell0- Embedded Linux library
Closes: 909350
Changes:
 ell (0.10+git20181001.0b885d95-1) unstable; urgency=medium
 .
   * New upstream release.
   * Snapshot, taken from the master (20191001) (Closes: #909350).
   * Bump Standards-Version to 4.2.1.
   * Update libell0.symbols.
Checksums-Sha1:
 112769f8cf118a624181b1fd312ca96428158b14 1987 
ell_0.10+git20181001.0b885d95-1.dsc
 0bdae3d1beef7c7fca8b6e42d3e980e270ce 181432 
ell_0.10+git20181001.0b885d95.orig.tar.xz
 899f7e9826f9e6417262de7b3fcbc3c1fac646d1 3960 
ell_0.10+git20181001.0b885d95-1.debian.tar.xz
 1e1095f1c30e853c18edccbda251c584b823810a 6875 
ell_0.10+git20181001.0b885d95-1_amd64.buildinfo
 938887b09715d33e198e4b682373724331248c80 125716 
libell-dev_0.10+git20181001.0b885d95-1_amd64.deb
 1db83d74c6dc2757cd940eec99d0c5bf3d8b2813 363096 
libell0-dbgsym_0.10+git20181001.0b885d95-1_amd64.deb
 229f44b91ee6f54c2b766ec1ec06244bc026fa59 102364 
libell0_0.10+git20181001.0b885d95-1_amd64.deb
Checksums-Sha256:
 94452dcab356c8f889463213b1fd059bff4afee17b9209b75678dc9904a07787 1987 
ell_0.10+git20181001.0b885d95-1.dsc
 5db3303c4d5e676a91e23e30083975b974578e4a38fb21daa025d468659782a0 181432 
ell_0.10+git20181001.0b885d95.orig.tar.xz
 7a4bc9a07213c57bb7fbd9d98020fbe810f0e39db8d4d276f5463376247f25f6 3960 
ell_0.10+git20181001.0b885d95-1.debian.tar.xz
 fe0dc17806376cf6cced22e558df3e7bfbc36dcab3e3e1ae57963f958d32a636 6875 
ell_0.10+git20181001.0b885d95-1_amd64.buildinfo
 ae26c737805e650d9002f070457ce61782a3297103e925c69459c00cc005578e 125716 
libell-dev_0.10+git20181001.0b885d95-1_amd64.deb
 34b24a10aa8bb9f8c96f181f686fcc96e39e2bc43e042a15daec7238213517f8 363096 
libell0-dbgsym_0.10+git20181001.0b885d95-1_amd64.deb
 4db8a8e2ded525f7cec8b062aa0557d7eb157e04489b155e70c959c798a2578f 102364 
libell0_0.10+git20181001.0b885d95-1_amd64.deb
Files:
 fcfd085a53901190313fcb9a929a77d7 1987 devel optional 
ell_0.10+git20181001.0b885d95-1.dsc
 193182521dfe2584df6d2499841608df 181432 devel optional 
ell_0.10+git20181001.0b885d95.orig.tar.xz
 2d2ba9b964824d648da7abdc4143a1b7 3960 devel optional 
ell_0.10+git20181001.0b885d95-1.debian.tar.xz
 6447e57029c2744fd2b580842e172dcb 6875 devel optional 
ell_0.10+git20181001.0b885d95-1_amd64.buildinfo
 9a95e81dc9f786dc3ce557f9366ccd3c 125716 libdevel optional 
libell-dev_0.10+git20181001.0b885d95-1_amd64.deb
 b63b0e98ab09efa439f9f58bc3cd7322 363096 debug optional 
libell0-dbgsym_0.10+git20181001.0b885d95-1_amd64.deb
 eaa55883c4b1c048390c7efa00b18381 102364 libs optional 
libell0_0.10+git

Bug#910305: easyloggingpp FTBFS: configure: error: cannot find install-sh, install.sh, or shtool in build-aux ".."/build-aux

[Steve Robbins]

On Thursday, October 4, 2018 12:37:45 PM CDT Sven Joachim wrote:

> Almost certainly it is has been triggered by the recent upload of
> googletest, since the gtest-source directory is just a copy (via cp -a)
> of /usr/src/googletest/googletest.  Looks like that googletest upload
> broke out-of-tree builds.

Yes, it is triggered by new googletest; but the root cause is more subtle.  
The easyloggingpp package uses this rule to build gtest:

override_dh_auto_configure:
# We need to build googletest first
mkdir gtest-build
cp -a /usr/src/googletest/googletest gtest-source
dh_auto_configure -Dgtest-source -Bgtest-build
dh_auto_build -Dgtest-source -Bgtest-build

If you look at the "good" build log [1], you'll see that the above code was 
actually configuring & building with cmake.  With googletest 1.8.1, it flipped 
to using automake -- due to the presence of file "configure".  Unfortunately, 
the autoconf build is broken.

Suggest you add "--buildsystem=cmake" to the dh_auto_configure line.  Then it 
builds fine with googletest 1.8.1.

Best,
-Steve

[1] https://buildd.debian.org/status/fetch.php?
pkg=easyloggingpp&arch=all&ver=9.96.5%2Bdfsg-1&stamp=1536739463&raw=0

Bug#874727: closed by Anton Gladky (Bug#874727: fixed in coin3 3.1.4~abc9f50+dfsg2-1)

[markus]

Hi Christoph,

it's a packaging bug - libcoin is statically linked with libexpat, and
the version being used is outdated. So anything that uses libcoin and
libexpat will run into a segfault.

I am not aware of any other application that uses libcoin.

HTH,
Markus


On Tue, 2 Oct 2018 10:37:00 +0200
Christoph Berg  wrote:

> Control: tags -1 moreinfo
> 
> Re: mlampert 2018-01-06 <20180104145135.59a157e4@occ7>
> > Version libcoin89-dev 3.1.4-abc9f50+dfsg3-2 (in Debian Testing as
> > of yesterday) still has a statically linked version of libexpat -
> > and still causes any application using the system version libexpat
> > to segfault.  
> 
> Re: Vincas Dargis 2018-07-25
> 
> > Are there any workarounds for this issue? Seems same problem as
> > discovered on Kbuntu 18.04 that FreeCAD crashes when importing from
> > SVG file.  
> 
> Hi,
> 
> do we have any evidence that this is a bug in coin3, and not simply
> freecad being buggy? The freecad version currently in unstable crashes
> in all sorts of ways.
> 
> Markus: did you see the bug in any other application?
> 
> Christoph

Bug#910331: marked as done (libnbcompat: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Fri, 05 Oct 2018 02:39:31 +
with message-id 
and subject line Bug#910331: fixed in libnbcompat 20180822-2
has caused the Debian Bug report #910331,
regarding libnbcompat: Incomplete debian/copyright?
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.)


-- 
910331: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910331
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libnbcompat
Version: 20180822-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: John Goerzen , 
ftpmas...@debian.org

Hi,

I just ACCEPTed libnbcompat from NEW but noticed it was missing 
attribution in debian/copyright for at least Todd Miller, Henry
Spencer, Tobias Nygren, etc.

This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: libnbcompat
Source-Version: 20180822-2

We believe that the bug you reported is fixed in the latest version of
libnbcompat, 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.
John Goerzen  (supplier of updated libnbcompat package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 04 Oct 2018 20:34:13 -0500
Source: libnbcompat
Binary: libnbcompat-dev
Architecture: source amd64
Version: 20180822-2
Distribution: unstable
Urgency: low
Maintainer: John Goerzen 
Changed-By: John Goerzen 
Description:
 libnbcompat-dev - NetBSD pkgsrc compatibility library
Closes: 910331
Changes:
 libnbcompat (20180822-2) unstable; urgency=low
 .
   * Analyze licenses and note additional info in debian/copyright.
 Closes: #910331.
Checksums-Sha1:
 e6ca20266ef1d3cb4ab8dcae50dbade2a47aaba1 1920 libnbcompat_20180822-2.dsc
 59af3c8d58be30815dafebf27b3a2edb959c926f 4758 libnbcompat_20180822-2.diff.gz
 a727629f5cbdf717a116d577cbd869e5fff7e542 93462 
libnbcompat-dev_20180822-2_amd64.deb
 845eb6199b4cad70a8b19bdabd44dbd15566d687 6365 
libnbcompat_20180822-2_amd64.buildinfo
Checksums-Sha256:
 a964f30668ff7abfe0c25e5b599958550afa4d4587746815a02e20fe386865e3 1920 
libnbcompat_20180822-2.dsc
 08df9b9eb978da3e5b951294fe8574f7c940ffdfb7525798a09b8aded7d7596e 4758 
libnbcompat_20180822-2.diff.gz
 1278fe6b5c9981371c110aafc2edff60b95b2b13d00aac8e5b18ef60017683a7 93462 
libnbcompat-dev_20180822-2_amd64.deb
 b151dca2ee6f226115ebdb947d0c9d5b997a387e78dbe8dee189280e1ed8b8d8 6365 
libnbcompat_20180822-2_amd64.buildinfo
Files:
 0826ef12f4ba982394c1819dbf1a3db5 1920 libs optional libnbcompat_20180822-2.dsc
 d71782d7d4fe7029a2ee5e2ddcd94730 4758 libs optional 
libnbcompat_20180822-2.diff.gz
 650c3e37275ce642eb4426defa6013bd 93462 libdevel optional 
libnbcompat-dev_20180822-2_amd64.deb
 ad2d30195540a3d1723c69194605342b 6365 libs optional 
libnbcompat_20180822-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEJ217d7abdWx8toZp3Sn4hEKDntMFAlu2w6AACgkQ3Sn4hEKD
ntN58Q/+MsFEb8/TeRZuaNR7Wg0ENDGdQOhgszhgqb4xDhcs/XNRjxJjOTuZ9tR9
g3zh1nI5YEB0cWWYLxIVgObqbUp636odNF8ZwGl05V9J8iJUwxscAeZRGfLizbPy
q2Ka1BiejzxgrlxjzdhBZ7abTudShJ0vU2ZjazlDJUeVF4S7H9vA7S0nsCpD3tko
vfIdO2sA9BriyZ9kBgpRlwNaaaksMLVmmPV1OmmAo3VEKZUTVnEAD7++aO8szUsN
yD7Ok4hQAS+FhqRVW+VmdGtlK2rt3vQ0slG+l4vPIK996xMDaDR1+7ZWgPK5jSYs
y02xXVSAx8FHQuWJqHNJ4l4PC5gGBSW2hlhWtK4Fg385nLHqLexCkQcyD6gmFz8L
yt8aSffv6Oyidd8I38fWzv1GRleTMqTPhunfACio0eDeCc1FzwD9gvm/AlIBAhjr
ssZbZDrx+eEuNaABDXVU7EaWGpRSLSXDwReGmZFXcVM6/tU4ZVjr/A3SozEIt4xO
YpjMrUcAeOpisjUEbCYNJFyrQf7cxjHmHkFr6koAx6zoGKzInXfHDsRVCFOptpIs
mhn4IIV+yuvqTWafo40lcuaob+5fgAzpFCb+LcYBnPJel0O8xkjo74ykWMW8+uLT
qvUWFramsdVvgXsB5GcgoxxPlTICZ8jTDiQCt/yn4INX1DtqOLo=
=o2Id
-END PGP SIGNATURE End Message ---

Processed: (no subject)

[Debian Bug Tracking System]

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

> severity 910135 serious
Bug #910135 [xserver-xorg-core] xserver-xorg-core: Xserver crashes after update 
to 1.20.1-4
Severity set to 'serious' from 'important'
>
End of message, stopping processing here.

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

Bug#910110: aptitude: aptitude does not update libxapian30 during aptitude "self upgrade"

[Olly Betts]

On Tue, Oct 02, 2018 at 11:10:46PM +0200, Sven Joachim wrote:
> Indeed, but that needs to be fixed in libxapian30's shlibs file.

Fixed there by xapian-core 1.4.7-3.

> Then aptitude (and other reverse dependencies of libxapian30 that
> might be affected) can be rebuilt to pick up the changed dependency.

I've pulled out a list of the packages which need rebuilding from the
buildinfo files on mirror.ftp-master.d.o (anything built against
libxapian-dev 1.4.6-1 or higher which doesn't already have a suitably
versioned dependency):

07/10/pinot_1.05-2_kfreebsd-i386.buildinfo: libxapian-dev (= 1.4.6-1),
07/10/zeitgeist_1.0.1-0.2_kfreebsd-i386.buildinfo: libxapian-dev (= 1.4.6-1),
08/08/maildir-utils_1.0-6_amd64.buildinfo: libxapian-dev (= 1.4.7-2),
08/17/baloo-kf5_5.49.0-1_amd64.buildinfo: libxapian-dev (= 1.4.7-2),
08/28/recoll_1.24.1-3_amd64.buildinfo: libxapian-dev (= 1.4.7-2),
09/06/plasma-desktop_5.13.5-1_amd64.buildinfo: libxapian-dev (= 1.4.7-2),
09/06/plasma-workspace_5.13.5-1_amd64.buildinfo: libxapian-dev (= 1.4.7-2),
09/07/aptitude_0.8.11-3_amd64.buildinfo: libxapian-dev (= 1.4.7-2),
09/29/packagesearch_2.7.9_amd64.buildinfo: libxapian-dev (= 1.4.7-2),
10/02/cyrus-imapd_2.5.11-1_amd64.buildinfo: libxapian-dev (= 1.4.7-2),
10/03/akonadiconsole_18.08.1-1_amd64.buildinfo: libxapian-dev (= 1.4.7-2),
10/03/akonadi-search_18.08.1-1_amd64.buildinfo: libxapian-dev (= 1.4.7-2),
10/04/notmuch_0.28~rc0-1_amd64.buildinfo: libxapian-dev (= 1.4.7-2),
10/05/libsearch-xapian-perl_1.2.25.2-1_kfreebsd-amd64.buildinfo: libxapian-dev 
(= 1.4.7-2),

I'll request rebuilds once 1.4.7-3 has built on most architectures,
and recheck the latest buildinfo files in case anything gets built
against the current libxapian-dev before the new one propagates
everywhere.

Cheers,
Olly

Bug#910110: marked as done (libxapian30: needs to bump shlibs)

[Debian Bug Tracking System]

Your message dated Fri, 05 Oct 2018 01:50:09 +
with message-id 
and subject line Bug#910110: fixed in xapian-core 1.4.7-3
has caused the Debian Bug report #910110,
regarding libxapian30: needs to bump shlibs
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.)


-- 
910110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910110
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: aptitude
Version: 0.8.11-3
Severity: important
Tags: d-i

Dear Maintainer,

** IMPORTANT **
current report was not created on affected system, so do not take into account
"bugreport" automatic attached informations.
** /IMPORTANT **

Issue occure into a Debian Testing system.

I've to work on a not up-to-date system (about 1200 packages to update), so I
start to first update "aptitude" itself:
# aptitude install aptitude

This work fine.

But after, for any "aptitude" command, this fail with:

aptitude: symbol lookup error: aptitude: undefined symbol:
_ZN6Xapian4MSetC1EOS0_

Issue is that "aptitude" depends on "libxapian30", who was installed on the
past, but NOT upgraded by last "aptitude install aptitude"

OLD installed package:
ii  libxapian30:amd641.4.3-2amd64Search engine library

UP-TO-DATE package:
ii  libxapian30:amd641.4.7-2amd64Search engine library

In order to fix issue, I've to use "apt" to upgrade "libxapian30":

# apt-get install libxapian30


2018-10-02 21:31:15 upgrade libxapian30:amd64 1.4.3-2 1.4.7-2
2018-10-02 21:31:15 status half-configured libxapian30:amd64 1.4.3-2
2018-10-02 21:31:15 status unpacked libxapian30:amd64 1.4.3-2
2018-10-02 21:31:15 status half-installed libxapian30:amd64 1.4.3-2
2018-10-02 21:31:15 status half-installed libxapian30:amd64 1.4.3-2
2018-10-02 21:31:16 status unpacked libxapian30:amd64 1.4.7-2
2018-10-02 21:31:16 status unpacked libxapian30:amd64 1.4.7-2
2018-10-02 21:31:16 configure libxapian30:amd64 1.4.7-2 
2018-10-02 21:31:16 status unpacked libxapian30:amd64 1.4.7-2
2018-10-02 21:31:16 status half-configured libxapian30:amd64 1.4.7-2
2018-10-02 21:31:16 status installed libxapian30:amd64 1.4.7-2


Issue fixed, no more "undefined symbol" issue !

In order to definitively fix issue, "aptitude" package dependancies should be
modified:
- Currently, we have:
Dépend: [...], libxapian30

- Now, we should have something like:
Dépend: [...], libxapian30 (>=1.4.7-2)

Thanks for your help !

Best regards,

  Olivier



-- Package-specific info:
Terminal: xterm-256color
$DISPLAY is set.
which aptitude: /usr/bin/aptitude

aptitude version information:
aptitude 0.8.11
Compiler: g++ 8.2.0
Compiled against:
  apt version 5.0.2
  NCurses version 6.1
  libsigc++ version: 2.10.0
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.1.20180714
  cwidget version: 0.5.17
  Apt version: 5.0.2

aptitude linkage:
linux-vdso.so.1 (0x7ffdfc3f)
libapt-pkg.so.5.0 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 
(0x7fc80f377000)
libncursesw.so.6 => /lib/x86_64-linux-gnu/libncursesw.so.6 
(0x7fc80f33d000)
libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 
(0x7fc80f30f000)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7fc80f306000)
libcwidget.so.3 => /usr/lib/x86_64-linux-gnu/libcwidget.so.3 
(0x7fc80f20)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7fc80f0e)
libboost_iostreams.so.1.62.0 => 
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.62.0 (0x7fc80f0c1000)
libboost_system.so.1.62.0 => 
/usr/lib/x86_64-linux-gnu/libboost_system.so.1.62.0 (0x7fc80f0bc000)
libxapian.so.30 => /usr/lib/x86_64-linux-gnu/libxapian.so.30 
(0x7fc80ee96000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fc80ee75000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7fc80ecf2000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fc80eb5e000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7fc80eb42000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fc80e985000)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 
(0x7fc80e96c000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fc80e74e000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7fc80e73b000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7fc80e515000)
liblz4.so.1 => /usr/lib/x86_64-linux-gn

Bug#909846: libglib2.0-dev: absolute paths in gio-2.0.pc break reverse dependencies

[Simon McVittie]

On Sat, 29 Sep 2018 at 10:22:06 -0400, Jeremy Bicha wrote:
> I believe we don't consider this a bug in glib2.0.

It doesn't look as though this is going to be changed upstream, so
I don't think diverging is a good idea in the long term; and only
two packages seem to be affected, so fixing those packages seems a
reasonable short-term solution. I've opened RC bugs on tpm2-abrmd
(#910340, proposing the patch that its upstream already applied) and
playerctl (#910342, proposing a new patch that is equally straightforward)
and marked them as blocking this one.

I'm still trying to get clarification from the GLib upstream maintainers
on what their recommendation is for Autotools projects (other than
"stop using Autotools", which might be preferred in the long term but
scales poorly). The two reasonable possibilities seem to be:

PKG_CHECK_VAR([GDBUS_CODEGEN], [gio-2.0], [gdbus_codegen])

or

AC_PATH_PROG([GDBUS_CODEGEN], [gdbus-codegen])

(Neither is particularly better than the other for Debian systems; they
only have different characteristics in situations that Debian package
builds shouldn't encounter, such as GLib in a non-default $prefix.)

Either way, anyone with special requirements (e.g. cross-compiling on a
non-Debian system) can use "./configure GDBUS_CODEGEN=my-gdbus-codegen"
to override the default.

smcv

Processed: tagging 910340, tagging 910342

[Debian Bug Tracking System]

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

> tags 910340 + ftbfs
Bug #910340 [src:tpm2-abrmd] tpm2-abrmd: FTBFS with GLib 2.58.1: redundant use 
of AC_PATH_PROG
Warning: Unknown package 'src:tpm2-abrmd'
Added tag(s) ftbfs.
Warning: Unknown package 'src:tpm2-abrmd'
> tags 910342 + ftbfs
Bug #910342 [src:playerctl] playerctl: FTBFS with GLib 2.58.1: redundant use of 
AC_PATH_PROG
Warning: Unknown package 'src:playerctl'
Added tag(s) ftbfs.
Warning: Unknown package 'src:playerctl'
> thanks
Stopping processing here.

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

Bug#796400: [pkg-go] Bug#796400: Bug#796400: Bug#796400: golang-github-jacobsa-ratelimit: Non-determistically FTBFS due to unreliable timing in tests

[Alexandre Viau]

Should we fill a RM bug?

I'll do it if this bug stays inactive.

Cheers,

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature

Bug#910343: cowsay-off: What's the point of cowsay-off if you remove offensive ones?

[Salvo Tomaselli]

Package: cowsay-off
Version: 3.03+dfsg2-5
Severity: grave
Justification: renders package unusable

Dear Maintainer,
what is even the point of this package existing if the offensive ascii arts are
removed?

Please just drop this.

Best

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

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

Versions of packages cowsay-off depends on:
ii  cowsay  3.03+dfsg2-5

cowsay-off recommends no packages.

cowsay-off suggests no packages.

-- no debconf information

Processed: tagging 910340

[Debian Bug Tracking System]

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

> tags 910340 + fixed-upstream
Bug #910340 [src:tpm2-abrmd] tpm2-abrmd: FTBFS with GLib 2.58.1: redundant use 
of AC_PATH_PROG
Warning: Unknown package 'src:tpm2-abrmd'
Added tag(s) fixed-upstream.
Warning: Unknown package 'src:tpm2-abrmd'
> thanks
Stopping processing here.

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

Processed: playerctl: FTBFS with GLib 2.58.1: redundant use of AC_PATH_PROG

[Debian Bug Tracking System]

Processing control commands:

> block 909846 by -1
Bug #909846 [libglib2.0-dev] libglib2.0-dev: absolute paths in gio-2.0.pc break 
reverse dependencies that pass them to AC_PATH_PROG
909846 was blocked by: 910340
909846 was not blocking any bugs.
Added blocking bug(s) of 909846: 910342
Warning: Unknown package 'src:playerctl'

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

Bug#910342: playerctl: FTBFS with GLib 2.58.1: redundant use of AC_PATH_PROG

[Simon McVittie]

Source: playerctl
Version: 0.6.1-1
Severity: serious
Tags: patch upstream
Justification: fails to build from source
Control: block 909846 by -1

playerctl has this pattern in configure.ac:

AC_PATH_PROG([GDBUS_CODEGEN], [`$PKG_CONFIG --variable=gdbus_codegen 
gio-2.0`])

This doesn't work with recent versions of GLib, in which the pkg-config
call produces an absolute path. AC_PATH_PROG only accepts a basename for
its second argument.

There is some debate over whether the recommended way to check for tools
like these is to search the PATH:

AC_PATH_PROG([GDBUS_CODEGEN], [gdbus-codegen])

or to ask pkg-config:

PKG_CHECK_VAR([GDBUS_CODEGEN], [gio-2.0], [gdbus_codegen])

but combining AC_PATH_PROG with pkg-config certainly doesn't seem to be
what's intended. Either of those macro invocations would allow the location
to be overridden with "./configure GDBUS_CODEGEN=..." if required.

I have confirmed that the attached patch makes playerctl build
successfully in sbuild.

smcv
From: Simon McVittie 
Date: Thu, 4 Oct 2018 21:08:27 +0100
Subject: build: Use PKG_CHECK_VAR to check for gdbus-codegen

Recent versions of GLib define $gdbus_codegen to the absolute path to
gdbus-codegen, but AC_PATH_PROG doesn't work for an absolute path as
its second argument, causing configure to fail.

There's actually no need to use AC_PATH_PROG here, because
we don't need an absolute path to gdbus-codegen: if it's just a
basename that AC_PATH_PROG could find in the PATH, then the Makefile
can also find it in the PATH.

Using PKG_CHECK_VAR (from pkg-config 0.28+) preserves the ability for
a user to specify the path to a gdbus-codegen tool as a configure
argument, defaulting to the value of $gdbus_codegen from gio-2.0.pc.
---
 configure.ac | 6 ++
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/configure.ac b/configure.ac
index 21679fa..9a137c9 100644
--- a/configure.ac
+++ b/configure.ac
@@ -21,10 +21,8 @@ AC_PROG_INSTALL
 PKG_CHECK_MODULES([GOBJECT], [gobject-2.0 >= 2.38])
 PKG_CHECK_MODULES([GIO], [gio-unix-2.0])
 
-AC_PATH_PROG([GDBUS_CODEGEN], [`$PKG_CONFIG --variable=gdbus_codegen gio-2.0`])
-if test -z "$GDBUS_CODEGEN"; then
-AC_MSG_ERROR([*** gdbus-codegen is required to build playerctl])
-fi
+PKG_CHECK_VAR([GDBUS_CODEGEN], [gio-2.0], [gdbus_codegen], [],
+  [AC_MSG_ERROR([*** gdbus-codegen is required to build playerctl])])
 
 # Checks for typedefs, structures, and compiler characteristics
 AC_PROG_CC_STDC

Bug#910292: transition: libsrtp0-rm

[Mattia Rizzolo]

On Thu, Oct 04, 2018 at 11:54:12PM +0200, Bernhard Schmidt wrote:
> outdated auto tracker at
> https://release.debian.org/transitions/html/auto-srtp.html which is a
> bit confusing.

this will go away as soon as the package is removed from experimental…

> >  1 File a RC bug against src:srtp so the autoremoval clocks starts
> >ticking.  If the package is a key-package (not the case) or you want
> >it removed from testing sooner than you can get the releease team
> >involved of course.
> 
> I think it's transitively key due to being a rdep of kopete (which is
> core part of the KDE desktop).

bad me.  I wrote the "(not the case)" thinking I'd check before sending,
which obviously I didn't…
It seems the reason is not the dependency itself but "popcon" :)

> > Checking reverse dependencies...
> > # Broken Depends:
> > asterisk: asterisk-modules [hurd-i386]
> > gst-plugins-bad1.0: gstreamer1.0-plugins-bad [hurd-i386 kfreebsd-amd64 
> > kfreebsd-i386]
> 
> Those are non-release arches and they are just outdated. I guess those
> can be ignored?

They can be ignored (you should remember to mention this in the RM bug).
Of course if you could at least glance at why they are outdated, quite
often the fix is not that hard…  For asterisk the fix is asking for
removal of the binaries there, since an rdep is not building on hurd
anymore, for the other the work is in progress (I think #829570 is all
it will take…).

> > kopete: kopete [amd64 arm64 armel armhf i386 mips mips64el mipsel ppc64el 
> > s390x]
> 
> That's the blocker
> 
> > opal: libopal-dev [amd64 armel i386 mips mipsel]
> >   libopal3.10.10 [amd64 armel i386 mips mipsel]
> Only in unstable and RC-buggy for a while, we've already orphaned opal.

You haven't orphaned it, being a RFA.  Also, if that's the reaction to
RC bugs, then you should probably get the package removed instead, as
orphaning doesn't automagically fix bugs.

> > resiprocate: librecon-1.11 [amd64 arm64 armel armhf i386 mips mips64el 
> > mipsel ppc64el s390x]

Despite all the RC bugs and being unstable-only, it still builds.
Please consider patching that instead breaking it.

> I think that's a false positive. libsrtp0-dev (in unstable) provides
> libsrtp-dev. Also, I think src:qtwebengine-opensource-src isn't really
> using srtp at all, I've filed #910300 for that.

dak sadly still doesn't cope with virtual packages :(


Anyway, I saw you filed those bugs as whishlist/normal.  In my
experience, don't expect much traction with just wishlist bugs…  Also,
consider providing patches…


Considering that your rdep is indirectly kde-standard, you should imho
ask for removal from testing only once kopete is fixed…

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Processed: tpm2-abrmd: FTBFS with GLib 2.58.1: redundant use of AC_PATH_PROG

[Debian Bug Tracking System]

Processing control commands:

> block 909846 by -1
Bug #909846 [libglib2.0-dev] libglib2.0-dev: absolute paths in gio-2.0.pc break 
reverse dependencies that pass them to AC_PATH_PROG
909846 was not blocked by any bugs.
909846 was not blocking any bugs.
Added blocking bug(s) of 909846: 910340
Warning: Unknown package 'src:tpm2-abrmd'

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

Bug#910340: tpm2-abrmd: FTBFS with GLib 2.58.1: redundant use of AC_PATH_PROG

[Simon McVittie]

Source: tpm2-abrmd
Version: 1.3.1-1
Severity: serious
Tags: patch upstream
Justification: fails to build from source
Control: block 909846 by -1

tmp2-abrmd has this pattern in configure.ac:

AC_PATH_PROG([GDBUS_CODEGEN], [`$PKG_CONFIG --variable=gdbus_codegen 
gio-2.0`])

This doesn't work with recent versions of GLib, in which the pkg-config
call produces an absolute path. AC_PATH_PROG only accepts a basename for
its second argument.

There is some debate over whether the recommended way to check for tools
like these is to search the PATH:

AC_PATH_PROG([GDBUS_CODEGEN], [gdbus-codegen])

or to ask pkg-config:

PKG_CHECK_VAR([GDBUS_CODEGEN], [gio-2.0], [gdbus_codegen])

but combining AC_PATH_PROG with pkg-config certainly doesn't seem to be
what's intended. Either of those macro invocations would allow the location
to be overridden with "./configure GDBUS_CODEGEN=..." if required.

The upstream developer of tpm2-abrmd already applied a
patch to use AC_PATH_PROG([GDBUS_CODEGEN], [gdbus-codegen]):
https://github.com/tpm2-software/tpm2-abrmd/commit/b4036908dd067f8eadc9d53b1a2a39032aed109d
so I would suggest applying that (attached). I can confirm that applying
that patch fixes the build in sbuild.

smcv
From: Jonas Witschel 
Date: Tue, 11 Sep 2018 13:14:36 +0200
Subject: Fix gdbus-codegen lookup for recent versions of GLib

If GLib is built using Meson, the gdbus_codegen variable contains the
whole path to the binary instead of just the binary name. This cannot be
parsed by AC_PATH_PROG and leads to an error in the configure script.
According to https://gitlab.gnome.org/GNOME/glib/issues/1521#note_313402,
the recommended way to solve this is to look up gdbus-codegen directly
without using the pkg-config variable.

Origin: upstream, 2.0.3, commit:b4036908dd067f8eadc9d53b1a2a39032aed109d
---
 configure.ac | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/configure.ac b/configure.ac
index fe278e3..d1ea91b 100644
--- a/configure.ac
+++ b/configure.ac
@@ -32,7 +32,7 @@ PKG_CHECK_MODULES([GLIB], [glib-2.0])
 PKG_CHECK_MODULES([GOBJECT], [gobject-2.0])
 PKG_CHECK_MODULES([SAPI],[sapi < 2.0.0])
 AC_ARG_VAR([GDBUS_CODEGEN],[The gdbus-codegen executable.])
-AC_PATH_PROG([GDBUS_CODEGEN], [`$PKG_CONFIG --variable=gdbus_codegen gio-2.0`])
+AC_PATH_PROG([GDBUS_CODEGEN], [gdbus-codegen])
 if test -z "$GDBUS_CODEGEN"; then
 AC_MSG_ERROR([*** gdbus-codegen is required to build tpm2-abrmd])
 fi

Processed: Re: Bug#910292: transition: libsrtp0-rm

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:srtp
Bug #910292 [release.debian.org] transition: libsrtp0-rm
Bug reassigned from package 'release.debian.org' to 'src:srtp'.
Ignoring request to alter found versions of bug #910292 to the same values 
previously set
Ignoring request to alter fixed versions of bug #910292 to the same values 
previously set
> severity -1 serious
Bug #910292 [src:srtp] transition: libsrtp0-rm
Severity set to 'serious' from 'normal'
> retitle -1 Do not release srtp 1.x with Buster
Bug #910292 [src:srtp] transition: libsrtp0-rm
Changed Bug title to 'Do not release srtp 1.x with Buster' from 'transition: 
libsrtp0-rm'.

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

Processed: Re: Bug#909545: SSL CERTIFICATE_VERIFY_FAILED when using gs (Google Cloud Storage) backend.

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/boto/boto/pull/3836
Bug #909545 [python-boto] SSL CERTIFICATE_VERIFY_FAILED when using gs (Google 
Cloud Storage) backend.
Set Bug forwarded-to-address to 'https://github.com/boto/boto/pull/3836'.

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

Bug#909545: SSL CERTIFICATE_VERIFY_FAILED when using gs (Google Cloud Storage) backend.

[Sebastian Andrzej Siewior]

control: forwarded -1 https://github.com/boto/boto/pull/3836

On 2018-09-30 22:17:05 [+0200], Witold Baryluk wrote:
> Needed a small change to your patch:
> 
> Line 126 in boto/https_connection.py  in connect function needs to be
> protected by check::
> 
> 126 if self.key_file:
> 127 context.load_cert_chain(certfile=self.cert_file,
> keyfile=self.key_file)

Thank you. Attached the fixed version and forwarded upstream.

Sebastian
>From f5e7f6c98b46ff622f60a4661ffc9ce07216d109 Mon Sep 17 00:00:00 2001
From: Sebastian Andrzej Siewior 
Date: Sat, 29 Sep 2018 21:47:11 +0200
Subject: [PATCH] boto: try to add SNI support

Add SNI support. Newer OpenSSL (with TLS1.3) fail to connect if the
hostname is missing.

Link: https://bugs.debian.org/bug=909545
Tested-by: Witold Baryluk 
Signed-off-by: Sebastian Andrzej Siewior 
---
 boto/connection.py   | 19 ++-
 boto/https_connection.py | 22 +++---
 2 files changed, 21 insertions(+), 20 deletions(-)

diff --git a/boto/connection.py b/boto/connection.py
index 34b428f101df7..b4867a7657465 100644
--- a/boto/connection.py
+++ b/boto/connection.py
@@ -824,23 +824,24 @@ DEFAULT_CA_CERTS_FILE = os.path.join(os.path.dirname(os.path.abspath(boto.cacert
 h = http_client.HTTPConnection(host)
 
 if self.https_validate_certificates and HAVE_HTTPS_CONNECTION:
+context = ssl.create_default_context()
+context.verify_mode = ssl.CERT_REQUIRED
+context.check_hostname = True
+
 msg = "wrapping ssl socket for proxied connection; "
 if self.ca_certificates_file:
 msg += "CA certificate file=%s" % self.ca_certificates_file
+context.load_verify_locations(cafile=self.ca_certificates_file)
 else:
 msg += "using system provided SSL certs"
+context.load_default_certs()
 boto.log.debug(msg)
 key_file = self.http_connection_kwargs.get('key_file', None)
 cert_file = self.http_connection_kwargs.get('cert_file', None)
-sslSock = ssl.wrap_socket(sock, keyfile=key_file,
-  certfile=cert_file,
-  cert_reqs=ssl.CERT_REQUIRED,
-  ca_certs=self.ca_certificates_file)
-cert = sslSock.getpeercert()
-hostname = self.host.split(':', 0)[0]
-if not https_connection.ValidateCertificateHostname(cert, hostname):
-raise https_connection.InvalidCertificateException(
-hostname, cert, 'hostname mismatch')
+if key_file:
+context.load_cert_chain(certfile=cert_file, keyfile=key_file)
+
+sslSock = context.wrap_socket(sock, server_hostname=host)
 else:
 # Fallback for old Python without ssl.wrap_socket
 if hasattr(http_client, 'ssl'):
diff --git a/boto/https_connection.py b/boto/https_connection.py
index ddc31a152292e..a5076f6f9b261 100644
--- a/boto/https_connection.py
+++ b/boto/https_connection.py
@@ -119,20 +119,20 @@ from boto.compat import six, http_client
 sock = socket.create_connection((self.host, self.port), self.timeout)
 else:
 sock = socket.create_connection((self.host, self.port))
+
+context = ssl.create_default_context()
+context.verify_mode = ssl.CERT_REQUIRED
+context.check_hostname = True
+if self.key_file:
+context.load_cert_chain(certfile=self.cert_file, keyfile=self.key_file)
+
 msg = "wrapping ssl socket; "
 if self.ca_certs:
 msg += "CA certificate file=%s" % self.ca_certs
+context.load_verify_locations(cafile=self.ca_certs)
 else:
 msg += "using system provided SSL certs"
+context.load_default_certs()
 boto.log.debug(msg)
-self.sock = ssl.wrap_socket(sock, keyfile=self.key_file,
-certfile=self.cert_file,
-cert_reqs=ssl.CERT_REQUIRED,
-ca_certs=self.ca_certs)
-cert = self.sock.getpeercert()
-hostname = self.host.split(':', 0)[0]
-if not ValidateCertificateHostname(cert, hostname):
-raise InvalidCertificateException(hostname,
-  cert,
-  'remote hostname "%s" does not match '
-  'certificate' % hostname)
+
+self.sock = context.wrap_socket(sock, server_hostname=self.host)
-- 
2.19.0

Bug#910333: fontcustom: Incomplete debian/copyright?

[Chris Lamb]

Hi Alexandre,

> Fontcustom is a program that, amongst other things, parses the output of
> fontforge, which outputs this message. The string in spec_helper.rb is
> just for testing purposes, but does not apply to any file in fontcustom.
> 
> I'll close this bug.

Thanks for clarifying & checking!


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#910333: fontcustom: privacy breach

[Alexandre Viau]

Hello,

On 2018-10-04 4:55 p.m., Chris Lamb wrote:
> (It would also be nice to see privacy-breach-generic addressed.)

Done.

There was no use for this code unless you run browsers that you find in
museums anyways ;)

Cheers,

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature

Bug#910333: marked as done (fontcustom: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Thu, 4 Oct 2018 17:36:10 -0400
with message-id <3a57fbe8-1bf7-a1a7-200d-7895f40e4...@debian.org>
and subject line Re: Bug#910333: fontcustom: Incomplete debian/copyright?
has caused the Debian Bug report #910333,
regarding fontcustom: Incomplete debian/copyright?
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.)


-- 
910333: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910333
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fontcustom
Version: 2.0.0+ds4-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Alexandre Viau , ftpmas...@debian.org

Hi,

I just ACCEPTed fontcustom from NEW but noticed it was missing 
attribution in debian/copyright for at least the spec_helper.rb
Ruby script.

This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload.

(It would also be nice to see privacy-breach-generic addressed.)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
On 2018-10-04 4:55 p.m., Chris Lamb wrote:
> I just ACCEPTed fontcustom from NEW but noticed it was missing 
> attribution in debian/copyright for at least the spec_helper.rb
> Ruby script.

Fontcustom is a program that, amongst other things, parses the output of
fontforge, which outputs this message. The string in spec_helper.rb is
just for testing purposes, but does not apply to any file in fontcustom.

I'll close this bug.

Cheers,

-- 
Alexandre Viau
av...@debian.org



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

Bug#910336: sword: fails to build except on arch: all

[Jeremy Bicha]

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

Bug#910268: marked as done (dolphin-emu: FTBFS with googletest 1.8.1)

[Debian Bug Tracking System]

Your message dated Thu, 04 Oct 2018 21:19:43 +
with message-id 
and subject line Bug#910268: fixed in dolphin-emu 5.0+dfsg-4
has caused the Debian Bug report #910268,
regarding dolphin-emu: FTBFS with googletest 1.8.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.)


-- 
910268: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910268
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dolphin-emu
Version: 5.0+dfsg-3
Severity: serious
Tags: sid buster ftbfs fixed-upstream

dolphin-emu FTBFS with googletest 1.8.1:
> In file included from 
> /usr/src/gtest/include/gtest/internal/gtest-internal.h:40,
>  from /usr/src/gtest/include/gtest/gtest.h:59,
>  from 
> /<>/Source/UnitTests/VideoCommon/VertexLoaderTest.cpp:11:
> /usr/src/gtest/include/gtest/internal/gtest-port.h:891:57: error: 
> 'gtest_AllCombinationsVertexLoaderParamTest_dummy_' was declared 'extern' and 
> later 'static' [-fpermissive]
>  # define GTEST_ATTRIBUTE_UNUSED_ __attribute__ ((unused))
>  ^
> /usr/src/gtest/include/gtest/gtest-param-test.h:1421:54: note: in expansion 
> of macro 'GTEST_ATTRIBUTE_UNUSED_'
>static int gtest_##prefix##test_case_name##_dummy_ GTEST_ATTRIBUTE_UNUSED_ 
> = \
>   ^~~
> /<>/Source/UnitTests/VideoCommon/VertexLoaderTest.cpp:111:1: 
> note: in expansion of macro 'INSTANTIATE_TEST_CASE_P'
>  INSTANTIATE_TEST_CASE_P(
>  ^~~
> /<>/Source/UnitTests/VideoCommon/VertexLoaderTest.cpp:110:12: 
> note: previous declaration of 
> 'gtest_AllCombinationsVertexLoaderParamTest_dummy_'
>  extern int gtest_AllCombinationsVertexLoaderParamTest_dummy_;
> ^
> In file included from 
> /usr/src/gtest/include/gtest/internal/gtest-internal.h:40,
>  from /usr/src/gtest/include/gtest/gtest.h:59,
>  from 
> /<>/Source/UnitTests/VideoCommon/VertexLoaderTest.cpp:11:
> /usr/src/gtest/include/gtest/internal/gtest-port.h:891:57: error: 
> 'gtest_FormatsAndElementsVertexLoaderSpeedTest_dummy_' was declared 'extern' 
> and later 'static' [-fpermissive]
>  # define GTEST_ATTRIBUTE_UNUSED_ __attribute__ ((unused))
>  ^
> /usr/src/gtest/include/gtest/gtest-param-test.h:1421:54: note: in expansion 
> of macro 'GTEST_ATTRIBUTE_UNUSED_'
>static int gtest_##prefix##test_case_name##_dummy_ GTEST_ATTRIBUTE_UNUSED_ 
> = \
>   ^~~
> /<>/Source/UnitTests/VideoCommon/VertexLoaderTest.cpp:206:1: 
> note: in expansion of macro 'INSTANTIATE_TEST_CASE_P'
>  INSTANTIATE_TEST_CASE_P(
>  ^~~
> /<>/Source/UnitTests/VideoCommon/VertexLoaderTest.cpp:205:12: 
> note: previous declaration of 
> 'gtest_FormatsAndElementsVertexLoaderSpeedTest_dummy_'
>  extern int gtest_FormatsAndElementsVertexLoaderSpeedTest_dummy_;
> ^~~~
> make[5]: *** 
> [Source/UnitTests/VideoCommon/CMakeFiles/Test_VertexLoaderTest.dir/build.make:66:
>  
> Source/UnitTests/VideoCommon/CMakeFiles/Test_VertexLoaderTest.dir/VertexLoaderTest.cpp.o]
>  Error 1

Should be fixed by this upstream commit which I'll upload at some point:

https://github.com/dolphin-emu/dolphin/commit/ccf9ecbb03edbdd728738499dc5fae4d0631882a

James



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: dolphin-emu
Source-Version: 5.0+dfsg-4

We believe that the bug you reported is fixed in the latest version of
dolphin-emu, 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.
James Cowgill  (supplier of updated dolphin-emu package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 04 Oct 2018 21:49:21 +0100
Source: dolphin-emu
Binary: dolphin-emu dolphin-emu-data
Architecture: source
Version: 5.0+dfsg-4
Distribution: unstable
Urgency: medium
Ma

Bug#909995: Looks like LyX?

[Jonathan McDowell]

Weird. This built fine in my sbuild environment for upload to the
archive, but is now failing, so looks like one of the deps has changed.
The failing build log includes:

Traceback (most recent call last):
  File "/usr/share/lyx/configure.py", line 1886, in 
ret = checkLatexConfig(lyx_check_config and LATEX != '', bool_docbook)
  File "/usr/share/lyx/configure.py", line 1368, in checkLatexConfig
retval = processLayoutFile(file, bool_docbook)
  File "/usr/share/lyx/configure.py", line 1316, in processLayoutFile
% (classname, opt, desc, avai, prereq))
TypeError: %b requires a bytes-like object, or an object that implements 
__bytes__, not 'str'
support/Systemcall.cpp (294): Systemcall: 'python3 -tt 
"/usr/share/lyx/configure.py" --binary-dir="/usr/bin/"' finished with exit code 
1
LyX: Done!
LayoutFile.cpp (172): LayoutFileList::Read: no textclasses found!
Error: Document class not found

and later:

Error: Cannot convert file

No information for converting svg format files to eps.
Define a converter in the preferences.

which implies LyX wants something extra now. Will poke.

J.

-- 
They say that sex is like napalm.

Bug#910268: Bug #910268 in dolphin-emu marked as pending

[James Cowgill]

Control: tag -1 pending

Hello,

Bug #910268 in dolphin-emu 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/games-team/dolphin-emu/commit/a9b58c081e8d467352964b43e0a629f632700df3


d/patches: Add patch to fix FTBFS with googletest 1.8.1

Closes: #910268



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/910268

Processed: Bug #910268 in dolphin-emu marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #910268 [src:dolphin-emu] dolphin-emu: FTBFS with googletest 1.8.1
Added tag(s) pending.

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

Bug#910333: fontcustom: Incomplete debian/copyright?

[Chris Lamb]

Source: fontcustom
Version: 2.0.0+ds4-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Alexandre Viau , ftpmas...@debian.org

Hi,

I just ACCEPTed fontcustom from NEW but noticed it was missing 
attribution in debian/copyright for at least the spec_helper.rb
Ruby script.

This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload.

(It would also be nice to see privacy-breach-generic addressed.)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#910332: mtree-netbsd: Incomplete debian/copyright?

[Chris Lamb]

Source: mtree-netbsd
Version: 20180822-2
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: John Goerzen , 
ftpmas...@debian.org

Hi,

I just ACCEPTed mtree-netbsd from NEW but noticed it was missing 
attribution in debian/copyright for at least MIT, NetBSD, etc.

This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#910331: libnbcompat: Incomplete debian/copyright?

[Chris Lamb]

Source: libnbcompat
Version: 20180822-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: John Goerzen , 
ftpmas...@debian.org

Hi,

I just ACCEPTed libnbcompat from NEW but noticed it was missing 
attribution in debian/copyright for at least Todd Miller, Henry
Spencer, Tobias Nygren, etc.

This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#904653: python3-yowsup: fails to install with Python 3.7

[Hilmar Preusse]

On 26.07.18 Andreas Beckmann (a...@debian.org) wrote:

Hi Josué,

> 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...):
> 
AFAICT you have already the fix on salsa fro 2 month.  Would you be
so kind to upload the fixed package to Debian?

Thanks!
-- 
sigmentation fault


signature.asc
Description: PGP signature

Processed: tagging 910318

[Debian Bug Tracking System]

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

> tags 910318 + buster sid
Bug #910318 [src:factory-boy] factory-boy FTBFS: RuntimeError: generator raised 
StopIteration
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Bug#909004: marked as done (AttributeError: 'module' object has no attribute 'ignore')

[Debian Bug Tracking System]

Your message dated Thu, 04 Oct 2018 19:20:40 +
with message-id 
and subject line Bug#909004: fixed in mercurial-keyring 1.2.0-1
has caused the Debian Bug report #909004,
regarding AttributeError: 'module' object has no attribute 'ignore'
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.)


-- 
909004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909004
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mercurial-keyring
Version: 1.1.8-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

With Debian testing fully up-to-date, the 'hg pull' command fails to run:

user@debian-testing:~/src/hg/repo$ hg pull
pulling from https://bitbucket.org/someuser/someproject
** Unknown exception encountered with possibly-broken third-party extension
mercurial_keyring
** which supports versions unknown of Mercurial.
** Please disable mercurial_keyring and try your action again.
** If that fixes the bug please report it to
https://bitbucket.org/Mekk/mercurial_keyring/issues
** Python 2.7.15+ (default, Aug 31 2018, 11:56:52) [GCC 8.2.0]
** Mercurial Distributed SCM (version 4.7.1)
** Extensions loaded: gpg, convert, rebase, hgk, strip, mq, transplant, purge,
extdiff, histedit, shelve, mercurial_keyring
Traceback (most recent call last):
  File "/usr/bin/hg", line 41, in 
...
  File "/usr/lib/python2.7/dist-packages/mercurial_keyring.py", line 205, in
_read_password_from_keyring
keyring = import_keyring()
  File "/usr/lib/python2.7/dist-packages/mercurial_keyring.py", line 136, in
import_keyring
"fs.opener",
  File "/usr/lib/python2.7/dist-packages/mercurial_extension_utils.py", line
1013, in direct_import_ext
if blocked_module not in demandimport.ignore:
  File "/usr/lib/python2.7/dist-packages/hgdemandimport/demandimportpy2.py",
line 146, in __getattr__
return getattr(self._module, attr)
AttributeError: 'module' object has no attribute 'ignore'

The issue has been already marked as resolved in the upstream
https://bitbucket.org/Mekk/mercurial_keyring/issues/62/module-object-has-no-
attribute-ignore-with



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

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

Versions of packages mercurial-keyring depends on:
ii  mercurial  4.7.1-1
ii  mercurial-extension-utils  1.3.4-1
ii  python 2.7.15-3
ii  python-keyring 15.0.0-1

mercurial-keyring recommends no packages.

mercurial-keyring suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: mercurial-keyring
Source-Version: 1.2.0-1

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

Debian distribution maintenance software
pp.
Christoph Mathys  (supplier of updated mercurial-keyring 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 02 Oct 2018 21:58:40 +0200
Source: mercurial-keyring
Binary: mercurial-keyring
Architecture: source
Version: 1.2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Christoph Mathys 
Changed-By: Christoph Mathys 
Description:
 mercurial-keyring - Mercurial Keyring Extension
Closes: 909004
Changes:
 mercurial-keyring (1.2.0-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #909004)
   * Bump compat to 11 without changes.
   * Bump std version to 4.2.1 without changes.
Checksums-Sha1:
 b42ff3bf7e85310aef23ac3995a470e713179707 1636 mercurial-keyring_1.2.0-1.dsc
 64c71a5b2a3fce5c9163c5c91c352f7b9dff2900 23847 
mercurial-keyring_1.2.0.orig.tar.gz
 3b5653136c819f0d009f41e5d413f7b9a8d62b86 2400 
mercurial-keyring_1.2.0-1.debian.tar.xz
Checksums-Sha256:
 ccd156a9405ccd6538c8da8ae91f07dfebb3ff1829f155dc997036129ed75363 1636 
mercurial-keyring_1.2.0-1.d

Processed: [bts-link] source package src:lmfit-py

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:lmfit-py
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #906381 (http://bugs.debian.org/906381)
> # Bug title: lmfit-py: FTBFS in buster/sid (failing tests)
> #  * https://github.com/lmfit/lmfit-py/issues/502
> #  * remote status changed: closed -> open
> #  * reopen upstream
> tags 906381 - fixed-upstream
Bug #906381 [src:lmfit-py] lmfit-py: FTBFS in buster/sid (failing tests)
Removed tag(s) fixed-upstream.
> usertags 906381 - status-closed
Usertags were: status-closed.
Usertags are now: .
> usertags 906381 + status-open
There were no usertags set.
Usertags are now: status-open.
> thanks
Stopping processing here.

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

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

[Debian Bug Tracking System]

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

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

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

Processed: tagging 910306, tagging 910319

[Debian Bug Tracking System]

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

> tags 910306 + ftbfs
Bug #910306 [src:electrum] electrum FTBFS: mv: cannot stat 
'debian/python3-electrum/usr/share/applications': No such file or directory
Added tag(s) ftbfs.
> tags 910319 + ftbfs
Bug #910319 [src:fast-histogram] fast-histogram FTBFS: 
fast_histogram/_histogram_core.c:1:10: fatal error: Python.h: No such file or 
directory
Warning: Unknown package 'src:fast-histogram'
Added tag(s) ftbfs.
Warning: Unknown package 'src:fast-histogram'
> thanks
Stopping processing here.

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

Bug#910324: freebayes parallel FTBFS

[Helmut Grohne]

Source: freebayes
Version: 1.2.0-1
Severity: serious
Tags: ftbfs

freebayes fails to build from source in sbuild on unstable/amd64 when
performing a parallel build. The linker invocation is run before all
relevant objects are compiled. A build log ends with:

| g++ -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -I../ttmath  
-I/usr/include/bamtools `pkg-config --cflags libvcflib` `pkg-config --cflags 
libseqlib` `pkg-config --cflags htslib` `pkg-config --cflags jsoncpp` 
bamleftalign.o BedReader.o CNV.o fastlz.o Fasta.o Parameters.o Allele.o 
Sample.o Result.o AlleleParser.o Utility.o Genotype.o DataLikelihood.o 
Multinomial.o Ewens.o ResultData.o Dirichlet.o Marginals.o split.o LeftAlign.o 
IndelAllele.o Bias.o Contamination.o NonCall.o SegfaultHandler.o -o 
../bin/bamleftalign -lbamtools -ltabixpp -lz -lm -lpthread `pkg-config --libs 
libvcflib` `pkg-config --libs htslib` `pkg-config --libs libseqlib` `pkg-config 
--libs jsoncpp`
| g++: error: AlleleParser.o: No such file or directory
| g++: error: Genotype.o: No such file or directory
| g++: error: ResultData.o: No such file or directory
| make[2]: *** [Makefile:81: ../bin/bamleftalign] Error 1
| make[2]: *** Waiting for unfinished jobs
| make[2]: Leaving directory '/<>/src'
| make[1]: *** [Makefile:2: all] Error 2
| make[1]: Leaving directory '/<>'
| dh_auto_build: make -j12 "INSTALL=install --strip-program=true" returned exit 
code 2
| make: *** [debian/rules:6: build] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

The issue is also seen during reproducible builds:

https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/freebayes_1.2.0-1.rbuild.log.gz

Helmut

Bug#910255: libsane-common: error upgrading libsane-common (1.0.27-2) over (1.0.25-4.1)

[Jörg Frings-Fürst]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

tags 910255 + pending
thanks


Hello Michael,

thank you for spending your time helping to make Debian better with
this bug report. 

I have fixed your bug. The new release will be uploaded as soon as
possible.


CU
Jörg

- -- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema:  SYR8SJXB
Wire: @joergfringsfuerst
Skype:joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAlu2YqUACgkQCfifPIyh
0l32rw/7BHZKyptl5VkiBTgqWqYV1syKifZNjYOuU6k4Iavz2AYUSbRIWtP29jK1
EOaoL+qVWzSACGQaWmKYxKk59MnHKPVcuQOVaLdD9T704VOg/GUzzKOJ3+m5g8UE
ioH7fG1DEfV/wv2qv58Owuw9mmeAXW8Pe3wJDQxbrZglp+VX+JB5yfX542lnj80B
8ji5SR25mC+oIK6ubCT/YpTJauRtIE63ssWdjt/PpMM4O4zqdY/10A4hnXdA545M
5CI3lbgsTXQLH9smDX5XfbwqUwaGXgMEPJBqjvZUrSWfghXN4/lGt/K4MPdv2mDs
kO64/8oGqeeIKq/TiO4D+/ZUMHpJRfpgHSuXDa2hiMSXlwrfBbFw4NckCWcgTs2S
x65lud6FsKpejI54b4PQflW5BrNoOXUiFy/Wm5zptbWR0cCX6HNSMz78Io0ADqB4
UCw3kEQT+Pl8DBqyFOLZSaLbEgcdG8sKixBlHwNTvLX5C+uNtHNVgxcY1vDrA6p2
NqJllErDIAqKOytbFGYjBoGXTkN7hydlDSLFi2hXrPNww8b5EGxbzE63J2P063F/
yeR0Ce7jF9Qo18cclOolOvMc/IRfS4D7cG8hA80WHLOo4tJT8WWWRyTUANA/WQmi
L9Wy8CmoeJwx5+LI1NItgH/91ibmVlaF2ucqpGblJMx2cmFTmZ4=
=8hyb
-END PGP SIGNATURE-

Processed: Re: Bug#910255: libsane-common: error upgrading libsane-common (1.0.27-2) over (1.0.25-4.1)

[Debian Bug Tracking System]

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

> tags 910255 + pending
Bug #910255 [libsane-common] libsane-common: error upgrading libsane-common 
(1.0.27-2) over (1.0.25-4.1)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#910319: fast-histogram FTBFS: fast_histogram/_histogram_core.c:1:10: fatal error: Python.h: No such file or directory

[Helmut Grohne]

Source: fast-histogram
Version: 0.4-1
Severity: serious

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

|dh_auto_build -O--buildsystem=pybuild
| I: pybuild base:217: /usr/bin/python3.7 setup.py build 
| running build
| running build_py
| creating 
/<>/.pybuild/cpython3_3.7_fast-histogram/build/fast_histogram
| copying fast_histogram/__init__.py -> 
/<>/.pybuild/cpython3_3.7_fast-histogram/build/fast_histogram
| copying fast_histogram/histogram.py -> 
/<>/.pybuild/cpython3_3.7_fast-histogram/build/fast_histogram
| creating 
/<>/.pybuild/cpython3_3.7_fast-histogram/build/fast_histogram/tests
| copying fast_histogram/tests/test_histogram.py -> 
/<>/.pybuild/cpython3_3.7_fast-histogram/build/fast_histogram/tests
| copying fast_histogram/tests/__init__.py -> 
/<>/.pybuild/cpython3_3.7_fast-histogram/build/fast_histogram/tests
| running build_ext
| building 'fast_histogram._histogram_core' extension
| creating build
| creating build/temp.linux-amd64-3.7
| creating build/temp.linux-amd64-3.7/fast_histogram
| x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-I/usr/include/python3.7m -I/usr/lib/python3/dist-packages/numpy/core/include 
-c fast_histogram/_histogram_core.c -o 
build/temp.linux-amd64-3.7/fast_histogram/_histogram_core.o
| fast_histogram/_histogram_core.c:1:10: fatal error: Python.h: No such file or 
directory
|  #include 
|   ^~
| compilation terminated.
| error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
| E: pybuild pybuild:338: build: plugin distutils failed with: exit code=1: 
/usr/bin/python3.7 setup.py build 
| dh_auto_build: pybuild --build -i python{version} -p "3.7 3.6" returned exit 
code 13
| make: *** [debian/rules:9: build] Error 25
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

It also fails to build during reproducible tests:

https://tests.reproducible-builds.org/debian/rbuild/unstable/i386/fast-histogram_0.4-1.rbuild.log.gz

Helmut

Bug#910318: factory-boy FTBFS: RuntimeError: generator raised StopIteration

[Helmut Grohne]

Source: factory-boy
Version: 2.8.1-2
Severity: serious
Tags: ftbfs

factory-boy fails to build from source in sbuild on unstable/amd64. A
build ends with:

| ==
| ERROR: test_reset_after_end (tests.test_utils.ResetableIteratorTestCase)
| --
| Traceback (most recent call last):
|   File "/<>/factory/utils.py", line 158, in __iter__
| value = next(self.iterator)
| StopIteration
| 
| The above exception was the direct cause of the following exception:
| 
| Traceback (most recent call last):
|   File "/<>/tests/test_utils.py", line 343, in 
test_reset_after_end
| self.assertRaises(StopIteration, next, iterator)
|   File "/usr/lib/python3.7/unittest/case.py", line 743, in assertRaises
| return context.handle('assertRaises', args, kwargs)
|   File "/usr/lib/python3.7/unittest/case.py", line 178, in handle
| callable_obj(*args, **kwargs)
| RuntimeError: generator raised StopIteration
| 
| --
| Ran 381 tests in 0.311s
| 
| FAILED (errors=2, skipped=30)
| Test failed: 
| Creating test database for alias 'default'...
| Creating test database for alias 'replica'...
| Destroying test database for alias 'default'...
| Destroying test database for alias 'replica'...
| Creating test database for alias 'default'...
| Creating test database for alias 'replica'...
| Destroying test database for alias 'default'...
| Destroying test database for alias 'replica'...
| Creating test database for alias 'default'...
| Creating test database for alias 'replica'...
| Destroying test database for alias 'default'...
| Destroying test database for alias 'replica'...
| Creating test database for alias 'default'...
| Creating test database for alias 'replica'...
| Destroying test database for alias 'default'...
| Destroying test database for alias 'replica'...
| error: Test failed: 
| make[1]: *** [debian/rules:33: override_dh_auto_test] Error 1
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:12: build] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Wild guess: It didn't test on Python 3.7 earlier.

Helmut

Bug#910317: QtWebEngine in unstable is constantly crashing

[Boyuan Yang]

Package: python3-pyqt5.qtwebengine
Version: 5.11.2+dfsg-1
Severity: serious
X-Debbugs-CC: debian-qt-...@lists.debian.org
Control: affects -1 + libqt5webengine5

Dear Debian Qt/KDE maintainers and pyqt5.qtwebengine maintainers,

Current QtWebEngine in Debian Unstable would easily crash. That
happens after recent upgrade of libkf5.

For example, run the following script under python3:

$ export LC_ALL=C.UTF-8
$ export LANG=C
$ cat ./test.py
import sys

from PyQt5.QtWidgets import QApplication
from PyQt5.QtWidgets import QMainWindow
from PyQt5.QtWebEngineWidgets import QWebEngineView
from PyQt5.QtCore import QUrl

def main():
app = QApplication(sys.argv)
window = QMainWindow()
window.setWindowTitle('PyQt Demo')
window.setGeometry(320, 180, 960, 540)
view = QWebEngineView()
view.load(QUrl('http://leafletjs.com/')) # error here
window.setCentralWidget(view)
window.show()
sys.exit(app.exec_())

if __name__ == '__main__':
main()
$ python3 ./test.py
[1004/140404.438632:WARNING:stack_trace_posix.cc(699)] Failed to open
file: /tmp/.glBfSxZo (deleted)
  Error: No such file or directory
[8494:8515:1004/140404.647050:ERROR:nss_util.cc(727)] After loading
Root Certs, loaded==false: NSS error code: -8018
Received signal 11 SEGV_MAPERR 0010
#0 0x7fc98c03e76e 
#1 0x7fc98c03e880 
#2 0x7fc98c03eeb7 
#3 0x7fc9969db8e0 
#4 0x7fc990771604 
#5 0x7fc98aa8d660 
#6 0x7fc98aabde3c 
#7 0x7fc98a0af500 QQuickWindowPrivate::updateDirtyNode()
#8 0x7fc98a0af963 QQuickWindowPrivate::updateDirtyNodes()
#9 0x7fc98a0b0e22 QQuickWindowPrivate::syncSceneGraph()
#10 0x7fc98a16ce49 QQuickRenderControl::sync()
#11 0x7fc989c7e0c6 
#12 0x7fc989c7e2a6 
#13 0x7fc994b0003b QObject::event()
#14 0x7fc99548ac6b QWidget::event()
#15 0x7fc989c81e2d QQuickWidget::event()
#16 0x7fc990771bf0 
#17 0x7fc99544c4a1 QApplicationPrivate::notify_helper()
#18 0x7fc995453ae0 QApplication::notify()
#19 0x7fc995d1f11e 
#20 0x7fc994ad6589 QCoreApplication::notifyInternal2()
#21 0x7fc994b27648 QTimerInfoList::activateTimers()
#22 0x7fc994b27ea4 
#23 0x7fc9939acc3e g_main_context_dispatch
#24 0x7fc9939aced8 
#25 0x7fc9939acf6c g_main_context_iteration
#26 0x7fc994b28233 QEventDispatcherGlib::processEvents()
#27 0x7fc97df51ee1 
#28 0x7fc994ad525b QEventLoop::exec()
#29 0x7fc994add3d2 QCoreApplication::exec()
#30 0x7fc995ce214b 
#31 0x005068bf 
#32 0x0050a4e9 _PyEval_EvalFrameDefault
#33 0x00505d58 
#34 0x00506a8d 
#35 0x0050a4e9 _PyEval_EvalFrameDefault
#36 0x005088b8 
#37 0x0050a023 PyEval_EvalCode
#38 0x00635f82 
#39 0x0063603a PyRun_FileExFlags
#40 0x006397f8 PyRun_SimpleFileExFlags
#41 0x0063a38a Py_Main
#42 0x004ac090 main
#43 0x7fc996433b17 __libc_start_main
#44 0x005b35aa _start
  r8: 17281b04  r9: 017ae3e0 r10: 17281b04
r11: 0001
 r12:  r13: 017651c0 r14: 7fc994b91660
r15: 017650e0
  di: 01728da0  si:   bp: 7ffc01652bc0
bx: 01713dd0
  dx: 7fc994b91660  ax: 01082000  cx: 7fc994b91678
sp: 7ffc016527e0
  ip: 7fc990771604 efl: 00010202 cgf: 002b0033
erf: 0004
 trp: 000e msk:  cr2: 0010
[end of stack trace]
Calling _exit(1). Core file will not be generated.
$

--
Thanks,
Boyuan Yang

Bug#910316: erlang-ranch FTBFS: src/ranch_ssl.erl:128: ssl:ssl_accept/2: deprecated; use ssl:handshake/2 instead

[Helmut Grohne]

Source: erlang-ranch
Version: 1.3.0-1
Severity: serious
Tags: ftbfs

erlang-ranch fails to build from source using sbuild on unstable/amd64.
A build log ends with:

|debian/rules override_dh_auto_build
| make[1]: Entering directory '/<>'
| make SKIP_DEPS=yes
| make[2]: Entering directory '/<>'
|  DEPEND ranch.d
|  ERLC   ranch.erl ranch_acceptor.erl ranch_acceptors_sup.erl ranch_app.erl 
ranch_conns_sup.erl ranch_listener_sup.erl ranch_protocol.erl ranch_server.erl 
ranch_ssl.erl ranch_sup.erl ranch_tcp.erl ranch_transport.erl
| compile: warnings being treated as errors
| src/ranch_ssl.erl:128: ssl:ssl_accept/2: deprecated; use ssl:handshake/2 
instead
| make[3]: *** [erlang.mk:5069: ebin/ranch.app] Error 1
| make[2]: *** [erlang.mk:4872: app] Error 2
| make[2]: Leaving directory '/<>'
| make[1]: *** [debian/rules:10: override_dh_auto_build] Error 2
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:7: build] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

This is also seen by reproducible builds:

https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/erlang-ranch_1.3.0-1.rbuild.log.gz

Helmut

Processed: QtWebEngine in unstable is constantly crashing

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + libqt5webengine5
Bug #910317 [python3-pyqt5.qtwebengine] QtWebEngine in unstable is constantly 
crashing
Added indication that 910317 affects libqt5webengine5

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

Bug#901761: Not installable at amd64 because of libgcj17 dependency

[Andreas Beckmann]

On 2018-10-04 19:33, Johann Felix Soden wrote:
> On 03.10.2018 11:17 Andreas Beckmann wrote:
> 
>> Rather pdftk-java should take over the pdftk binary package, s.t. there
>> is an upgrade path. (A Provides: pdftk does not create an upgrade path).
>> That should make the old pdftk source package go away ...
> 
> My plan for the upgrade path was to release pdftk 2.02-3 as an
> transition package that depends on pdftk-java.

That would work as well, especially if you have some hope left that
pdktk upstream will resurrect it some day.

There just needs to be an installable pdftk package to provide a clean
upgrade path ...


Andrea

Bug#909864: marked as done (plotutils FTBFS on i386 with gcc 8)

[Debian Bug Tracking System]

Your message dated Thu, 04 Oct 2018 17:50:37 +
with message-id 
and subject line Bug#909864: fixed in plotutils 2.6-10
has caused the Debian Bug report #909864,
regarding plotutils FTBFS on i386 with gcc 8
to be marked as done.

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

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


-- 
909864: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909864
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: plotutils
Version: 2.6-9
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/plotutils.html

...
FAIL: plot2hpgl
===

FAIL plot2hpgl.test (exit status: 1)

FAIL: plot2pcl
==

FAIL plot2pcl.test (exit status: 1)


Testsuite summary for GNU plotutils 2.6

# TOTAL: 12
# PASS:  10
# SKIP:  0
# XFAIL: 0
# FAIL:  2
# XPASS: 0
# ERROR: 0

See test/test-suite.log
Please report to bug-plotut...@gnu.org

make[4]: *** [Makefile:531: test-suite.log] Error 1
--- End Message ---
--- Begin Message ---
Source: plotutils
Source-Version: 2.6-10

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

Debian distribution maintenance software
pp.
Andreas Metzler  (supplier of updated plotutils package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 04 Oct 2018 19:17:18 +0200
Source: plotutils
Binary: plotutils libplot2c2 libplot-dev
Architecture: source
Version: 2.6-10
Distribution: unstable
Urgency: medium
Maintainer: Andreas Metzler 
Changed-By: Andreas Metzler 
Closes: 909864
Description: 
 libplot2c2 - GNU plotutils libraries
 libplot-dev - GNU plotutils libraries (development files)
 plotutils  - GNU plotutils command line tools based on libplot
Changes:
 plotutils (2.6-10) unstable; urgency=medium
 .
   [ Andreas Metzler ]
   * Add -Wall to CXXFLAGS.
   * Build with -ffloat-store on i386 to fix a testsuite error (hpgl and pcl
 output) on i386. Thanks, Adrian Bunk! Closes: #909864
   * [lintian] Delete empty lines at the bottom of the changelog file.
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
Checksums-Sha1: 
 d5d45f9486dac324bd4f88c0d354ceafca51 2100 plotutils_2.6-10.dsc
 a1559e9d8bb2455c00450a9bf1413f69c017fc79 12544 plotutils_2.6-10.debian.tar.xz
Checksums-Sha256: 
 edda1dd46510b749b0e621e752d3e64a9872b1aa92854b947f0c54ce9c780175 2100 
plotutils_2.6-10.dsc
 15ff6541067f96a112fb688ec5a7a26aa707ced02d96b6a5cf7f8a20fd4804eb 12544 
plotutils_2.6-10.debian.tar.xz
Files: 
 0c3a04c0d1d7c5af0be72e740f956716 2100 math optional plotutils_2.6-10.dsc
 1fb318d57ea9f03fbbd5a2c526ed0a9a 12544 math optional 
plotutils_2.6-10.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAlu2TRgACgkQpU8BhUOC
FIRksRAAjwnrBjslDhd+JX/IUFVl0aCgc6aog1CGYWXjieiWr8CyS63SpFGkeP1S
DHgntvLP7b5DKaC2tabVmt063A04gGLcGYs9SEz8uDPZ8WDTzVF75W9X+4s2oYpu
XV8DGCep0k/GgJAGPlKJGwXgESDnUbnR1pbTUeCW2R6kHp/onGJ0ZU5FNL0ZJlqw
hUxXiYOmA8dj5Bb5BcIVPr1ZELlMNiEsNAQahC7Ok+HRDtT+xkzC0CSDw0KRL8tR
9GJTpLTSSPjOryhGri9NeQ4hEpNwlyW2V23FUZ84hlzxf0REsLwEecLZNXcjSUgw
B8jlyJnmVk4mbZddQU8MNwX1N9BbKwwgkmgYHJUNTSn9syEaLeOYh7vDjpOeZb3q
Wc9fllVNr5CgmeDTtFJeKdTM2D9sSFFOAAEuyf3CsctX1AFMxtHLDQbKC2W2UotH
SLDhRVQ+oMMocF5T9p/Gl+W9D8ytzxFdgar05pPzvtqETRoVBx6rv8bAl1E/qbaR
YGO+GkypYfnXDVM01LN1fOa3bkz4rBk5phwX9Rjcj2yDlLGPpKpavHpmbpWQIZWe
PY/89/60HdA3OAU3JG7L5PhAAcih9lmKvLGf9CpoFz9zHmeU3+/arLdi9PS10eKh
5ddQ7R9bAkNJ/J+XeomW/T9J8UdBqV5ik11VSOnN5d3JnfwKR5Y=
=s8OK
-END PGP SIGNATURE End Message ---

Bug#910312: erlang-jose FTBFS: erlang:get_stacktrace/0: deprecated; use the new try/catch syntax for retrieving the stack backtrace

[Helmut Grohne]

Source: erlang-jose
Version: 1.8.4-3
Severity: serious
Tags: ftbfs

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

| Compiled src/jose_server.erl
| Compiled src/jose_jwt.erl
| Compiled src/jose_sha3_keccakf1600_nif.erl
| Compiled src/jose_jwk_kty_oct.erl
| Compiled src/jose_jwk_kty_okp_ed448.erl
| src/jose_public_key.erl:44: erlang:get_stacktrace/0: deprecated; use the new 
try/catch syntax for retrieving the stack backtrace
| src/jose_public_key.erl:60: erlang:get_stacktrace/0: deprecated; use the new 
try/catch syntax for retrieving the stack backtrace
| src/jose_public_key.erl:84: erlang:get_stacktrace/0: deprecated; use the new 
try/catch syntax for retrieving the stack backtrace
| src/jose_public_key.erl:107: erlang:get_stacktrace/0: deprecated; use the new 
try/catch syntax for retrieving the stack backtrace
| src/jose_public_key.erl:122: erlang:get_stacktrace/0: deprecated; use the new 
try/catch syntax for retrieving the stack backtrace
| src/jose_public_key.erl:234: erlang:get_stacktrace/0: deprecated; use the new 
try/catch syntax for retrieving the stack backtrace
| Compiling src/jose_public_key.erl failed:
| DEBUG: Worker compilation failed: {{error,
| {error,[],
|  [["src/jose_public_key.erl:44: 
erlang:get_stacktrace/0: deprecated; use the new try/catch syntax for 
retrieving the stack backtrace\n",
|"src/jose_public_key.erl:60: 
erlang:get_stacktrace/0: deprecated; use the new try/catch syntax for 
retrieving the stack backtrace\n",
|"src/jose_public_key.erl:84: 
erlang:get_stacktrace/0: deprecated; use the new try/catch syntax for 
retrieving the stack backtrace\n",
|"src/jose_public_key.erl:107: 
erlang:get_stacktrace/0: deprecated; use the new try/catch syntax for 
retrieving the stack backtrace\n",
|"src/jose_public_key.erl:122: 
erlang:get_stacktrace/0: deprecated; use the new try/catch syntax for 
retrieving the stack backtrace\n",
|"src/jose_public_key.erl:234: 
erlang:get_stacktrace/0: deprecated; use the new try/catch syntax for 
retrieving the stack backtrace\n"]]}},
|{source,"src/jose_public_key.erl"}}
| ERROR: compile failed while processing /<>: rebar_abort
| make[1]: *** [/usr/share/dh-rebar/make/dh-rebar.Makefile:126: rebar_compile] 
Error 1
| dh_auto_build: make --no-print-directory -f 
/usr/share/dh-rebar/make/dh-rebar.Makefile build returned exit code 2
| make: *** [debian/rules:11: build] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Helmut

Bug#910305: easyloggingpp FTBFS: configure: error: cannot find install-sh, install.sh, or shtool in build-aux ".."/build-aux

[Sven Joachim]

Am 04.10.2018 um 18:53 schrieb Helmut Grohne:

> Source: easyloggingpp
> Version: 9.96.5+dfsg-1
> Severity: serious
> Tags: ftbfs
>
> easyloggingpp fails to build from source in unstable. The build log
> essentially looks like this:
>
> | dpkg-buildpackage: info: source package easyloggingpp
> | dpkg-buildpackage: info: source version 9.96.5+dfsg-1
> | dpkg-buildpackage: info: source distribution unstable
> | dpkg-buildpackage: info: source changed by Stephen Kitt 
> |  dpkg-source --before-build .
> | dpkg-buildpackage: info: host architecture amd64
> |  debian/rules clean
> | dh clean
> |dh_clean
> |  debian/rules binary
> | dh binary
> |dh_update_autotools_config
> |dh_autoreconf
> |debian/rules override_dh_auto_configure
> | make[1]: Entering directory '/<>'
> | mkdir gtest-build
> | cp -a /usr/src/googletest/googletest gtest-source
> | dh_auto_configure -Dgtest-source -Bgtest-build
> | cd gtest-build && ../gtest-source/configure 
> --build=x86_64-linux-gnu --prefix=/usr --includedir=\${prefix}/include 
> --mandir=\${prefix}/share/man --infodir=\${prefix}/share/info 
> --sysconfdir=/etc --localstatedir=/var --disable-silent-rules 
> --libdir=\${prefix}/lib/x86_64-linux-gnu 
> --libexecdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
> --disable-maintainer-mode --disable-dependency-tracking
> | configure: WARNING: unrecognized options: --disable-maintainer-mode
> | configure: error: cannot find install-sh, install.sh, or shtool in 
> build-aux ".."/build-aux
> | cd gtest-build && tail -v -n \+0 config.log
> | ==> config.log <==
> | ...
> | dh_auto_configure: cd gtest-build && ../gtest-source/configure 
> --build=x86_64-linux-gnu --prefix=/usr --includedir=\${prefix}/include 
> --mandir=\${prefix}/share/man --infodir=\${prefix}/share/info 
> --sysconfdir=/etc --localstatedir=/var --disable-silent-rules 
> --libdir=\${prefix}/lib/x86_64-linux-gnu 
> --libexecdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
> --disable-maintainer-mode --disable-dependency-tracking returned exit code 1
> | make[1]: *** [debian/rules:13: override_dh_auto_configure] Error 2
> | make[1]: Leaving directory '/<>'
> | make: *** [debian/rules:7: binary] Error 2
> | dpkg-buildpackage: error: debian/rules binary subprocess returned exit 
> status 2
>
> This looks like some dependency changed possibly debhelper or autoconf
> or something.

Almost certainly it is has been triggered by the recent upload of
googletest, since the gtest-source directory is just a copy (via cp -a)
of /usr/src/googletest/googletest.  Looks like that googletest upload
broke out-of-tree builds.

Cheers,
   Sven

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

[Helmut Grohne]

Source: elpy
Version: 1.24.0-1
Severity: serious
Tags: ftbfs

elpy fails to build from source randomly. A build log contains:

| Test elpy-promise-wait-should-return-early-for-resolved-promise backtrace:
|   (if (unwind-protect (setq value-774 (apply fn-772 args-773)) (setq f
|   (let (form-description-776) (if (unwind-protect (setq value-774 (app
|   (let ((value-774 (quote ert-form-evaluation-aborted-775))) (let (for
|   (let ((fn-772 (function elpy-promise-resolved-p)) (args-773 (list pr
|   (let ((start-time (current-time)) (promise (elpy-promise nil))) (run
|   (progn (let ((start-time (current-time)) (promise (elpy-promise nil)
|   (progn (setq elpy-rpc-timeout 100) (progn (let ((start-time (current
|   (unwind-protect (progn (setq elpy-rpc-timeout 100) (progn (let ((sta
|   (save-current-buffer (set-buffer temp-buffer) (unwind-protect (progn
|   (let ((temp-buffer (generate-new-buffer " *temp*"))) (save-current-b
|   (progn (let ((temp-buffer (generate-new-buffer " *temp*"))) (save-cu
|   (unwind-protect (progn (let ((temp-buffer (generate-new-buffer " *te
|   (let ((old-process-list (process-list)) (old-buffer-list (buffer-lis
|   (lambda nil (let ((old-process-list (process-list)) (old-buffer-list
|   ert--run-test-internal([cl-struct-ert--test-execution-info [cl-struc
|   ert-run-test([cl-struct-ert-test elpy-promise-wait-should-return-ear
|   ert-run-or-rerun-test([cl-struct-ert--stats t [[cl-struct-ert-test e
|   ert-run-tests(t #[385 "\306^B\307\"\203G^@\211\211G\310U\203^T^@\211@\20
|   ert-run-tests-batch(nil)
|   ert-run-tests-batch-and-exit()
|   eval((ert-run-tests-batch-and-exit))
|   command-line-1(("-l" "package" "--eval" "(add-to-list 'package-direc
|   command-line()
|   normal-top-level()
| Test elpy-promise-wait-should-return-early-for-resolved-promise condition:
| (ert-test-failed
|  ((should
|(elpy-promise-resolved-p promise))
|   :form
|   (elpy-promise-resolved-p
|[*elpy-promise* nil nil # nil])
|   :value nil))
|FAILED  222/362  elpy-promise-wait-should-return-early-for-resolved-promise

This happened in sbuild on unstable/amd64.

The reproducible builds folks encountered the same failure in one out of
two builds using pbuilder:

https://tests.reproducible-builds.org/debian/logs/unstable/amd64/elpy_1.24.0-1.build2.log.gz
https://tests.reproducible-builds.org/debian/rbuild/unstable/arm64/elpy_1.24.0-1.rbuild.log.gz
https://tests.reproducible-builds.org/debian/rbuild/unstable/armhf/elpy_1.24.0-1.rbuild.log.gz

For amd64, only the second build failed. When I tried it locally in
sbuild, three builds succeeded. I have no clue how the failure is
caused, but it is evident that it is not broken infrastructure.

Helmut

Bug#901761: Not installable at amd64 because of libgcj17 dependency

[Johann Felix Soden]

On 03.10.2018 11:17 Andreas Beckmann wrote:

> Rather pdftk-java should take over the pdftk binary package, s.t. there
> is an upgrade path. (A Provides: pdftk does not create an upgrade path).
> That should make the old pdftk source package go away ...

My plan for the upgrade path was to release pdftk 2.02-3 as an
transition package that depends on pdftk-java.

Currently, pdftk-java is the only working alternative, but maybe
upstream or someone else finds another way to solve the GCJ issue...

>From my perspective, providing the pdftk binary package in pdftk-java
seems to be a bit misleading, since the upstream is different.
(The pdftk binary itself is currently provided by update-alternatives in
pdftk-java)

What do you think, Andreas?

Best wishes,
 Johann Felix


-- 
Johann Felix Soden, joh...@debian.org, DD

Bug#909779: vows: Cannot find module 'glob'

[Petter Reinholdtsen]

Control: severity -1 wishlist
Control: retitle -1 vows: Should give more sensible error when unable to find 
/proc/self/fd/1

I got some help from Sunil, and we managed to track down this issue to
the simple fact that my chroot did not have /proc/ mounted, and this
caused vows to fail to find any javascript library.

It would be nice if vows mentioned its inability to find /proc/self/fd/1
instead of complaining that glob is missing.

-- 
Happy hacking
Petter Reinholdtsen

Processed: Re: Bug#909779 vows: Cannot find module 'glob'

[Debian Bug Tracking System]

Processing control commands:

> severity -1 wishlist
Bug #909779 [node-vows] vows: Cannot find module 'glob'
Severity set to 'wishlist' from 'serious'
> retitle -1 vows: Should give more sensible error when unable to find 
> /proc/self/fd/1
Bug #909779 [node-vows] vows: Cannot find module 'glob'
Changed Bug title to 'vows: Should give more sensible error when unable to find 
/proc/self/fd/1' from 'vows: Cannot find module 'glob''.

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

Bug#910307: elixir-lang FTBFS: tests fail: Killed

[Helmut Grohne]

Source: elixir-lang
Version: 1.6.5-1
Severity: serious
Tags: ftbfs

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

|   5) test translates :supervisor_bridge progress (Logger.TranslatorTest)
|  test/logger/translator_test.exs:751
|  Assertion with =~ failed
|  code:  assert capture_log(:info, fn ->
|   trap = Process.flag(:trap_exit, true)
|   {:ok, pid} = :supervisor_bridge.start_link(MyBridge, :normal)
|   receive() do
| {:EXIT, ^pid, _} ->
|   :ok
|   end
|   Process.flag(:trap_exit, trap)
| end) =~ ~r"\\[info\\]  Child of Supervisor 
#PID<\\d+\\.\\d+\\.\\d+> \\(Logger\\.TranslatorTest\\.MyBridge\\) started\nPid: 
#PID<\\d+\\.\\d+\\.\\d+>\nStart Call: 
Logger.TranslatorTest.MyBridge.init\\(:normal\\)\n"
|  left:  ""
|  right: ~r/\[info\]  Child of Supervisor #PID<\d+\.\d+\.\d+> 
\(Logger\.TranslatorTest\.MyBridge\) started\nPid: #PID<\d+\.\d+\.\d+>\nStart 
Call: Logger.TranslatorTest.MyBridge.init\(:normal\)\n/
|  stacktrace:
|test/logger/translator_test.exs:752: (test)
| 
| =INFO REPORT 4-Oct-2018::17:13:59.511859 ===
| application: logger
| exited: stopped
| type: temporary
| .
| 
| Finished in 0.7 seconds (0.3s on load, 0.4s on tests)
| 1 doctest, 109 tests, 5 failures
| 
| Randomized with seed 183795
| make[2]: *** [Makefile:92: test_logger] Error 1
| make[2]: Leaving directory '/<>'
| dh_auto_test: make -j18 test returned exit code 2
| epmd: Thu Oct  4 17:13:59 2018: got KILL_REQ - terminates normal
| 
| Killed
| make[1]: *** [debian/rules:12: override_dh_auto_test] Error 2
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:9: build] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

It also fails on the reproducible builds infrastructure:

https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/elixir-lang_1.6.5-1.rbuild.log.gz

Helmut

Bug#906382: marked as done (lombok-ast: FTBFS in buster/sid)

[Debian Bug Tracking System]

Your message dated Thu, 04 Oct 2018 17:06:01 +
with message-id 
and subject line Bug#906382: fixed in lombok-ast 0.2+ds-4
has caused the Debian Bug report #906382,
regarding lombok-ast: FTBFS in buster/sid
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.)


-- 
906382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906382
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:lombok-ast
Version: 0.2+ds-3
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with javahelper,maven_repo_helper
   dh_update_autotools_config -i
   dh_autoreconf -i
   dh_auto_configure -i
   debian/rules override_jh_linkjars
make[1]: Entering directory '/<>/lombok-ast-0.2+ds'
jh_linkjars
rm -f \
lib/runtime/ant* \
lib/runtime/jsch* \
lib/runtime/ecj* \
lib/runtime/eclipse* \
lib/runtime/asm* \

[... snipped ...]

[ivy:compile]   at 
jdk.compiler/com.sun.tools.javac.main.Main.compile(Main.java:165)
[ivy:compile]   at jdk.compiler/com.sun.tools.javac.Main.compile(Main.java:57)
[ivy:compile]   at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[ivy:compile]   at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[ivy:compile]   at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[ivy:compile]   at java.base/java.lang.reflect.Method.invoke(Method.java:564)
[ivy:compile]   at 
org.apache.tools.ant.taskdefs.compilers.Javac13.execute(Javac13.java:57)
[ivy:compile]   at org.apache.tools.ant.taskdefs.Javac.compile(Javac.java:1404)
[ivy:compile]   at org.apache.tools.ant.taskdefs.Javac.execute(Javac.java:1133)
[ivy:compile]   at com.zwitserloot.ivyplusplus.Compile.execute(Unknown Source)
[ivy:compile]   at 
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292)
[ivy:compile]   at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[ivy:compile]   at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[ivy:compile]   at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[ivy:compile]   at java.base/java.lang.reflect.Method.invoke(Method.java:564)
[ivy:compile]   at 
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:99)
[ivy:compile]   at org.apache.tools.ant.Task.perform(Task.java:350)
[ivy:compile]   at org.apache.tools.ant.Target.execute(Target.java:449)
[ivy:compile]   at org.apache.tools.ant.Target.performTasks(Target.java:470)
[ivy:compile]   at 
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1388)
[ivy:compile]   at org.apache.tools.ant.Project.executeTarget(Project.java:1361)
[ivy:compile]   at 
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
[ivy:compile]   at 
org.apache.tools.ant.Project.executeTargets(Project.java:1251)
[ivy:compile]   at org.apache.tools.ant.Main.runBuild(Main.java:834)
[ivy:compile]   at org.apache.tools.ant.Main.startAnt(Main.java:223)
[ivy:compile]   at org.apache.tools.ant.launch.Launcher.run(Launcher.java:284)
[ivy:compile]   at org.apache.tools.ant.launch.Launcher.main(Launcher.java:101)
[ivy:compile] Caused by: java.lang.ClassNotFoundException: 
com.sun.tools.javac.code.TypeTags
[ivy:compile]   at 
java.base/java.lang.ClassLoader.findClass(ClassLoader.java:711)
[ivy:compile]   at 
java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:566)
[ivy:compile]   at 
lombok.launch.ShadowClassLoader.loadClass(ShadowClassLoader.java:422)
[ivy:compile]   at 
java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:499)
[ivy:compile]   at java.base/java.lang.Class.forName0(Native Method)
[ivy:compile]   at java.base/java.lang.Class.forName(Class.java:291)
[ivy:compile]   at 
lombok.javac.JavacTreeMaker$SchroedingerType.getFieldCached(JavacTreeMaker.java:156)
[ivy:compile]   at 
lombok.javac.JavacTreeMaker$TypeTag.typeTag(JavacTreeMaker.java:244)
[ivy:compile]   at lombok.javac.Javac.(Javac.java:158)
[ivy:compile]   ... 47 more

BUILD FAILED
/<>/lombok-ast-0.2+ds/build.xml:94: Compile failed; see the compiler 
error output for details.

Total time: 2 seconds
make[1]: *** [debian/rules:17: override_dh_auto_build] Error 1
make[1]: Leaving directory '/<>/lombok-ast-0.2+ds'
make: *** [deb

Bug#910306: electrum FTBFS: mv: cannot stat 'debian/python3-electrum/usr/share/applications': No such file or directory

[Helmut Grohne]

Source: electrum
Version: 3.1.3-1
Severity: serious

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

| mkdir -p debian/electrum/usr/bin debian/electrum/usr/share
| mv debian/python3-electrum/usr/bin debian/electrum/usr
| mv debian/python3-electrum/usr/share/applications \
|debian/electrum/usr/share
| mv: cannot stat 'debian/python3-electrum/usr/share/applications': No such 
file or directory
| make[1]: *** [debian/rules:22: override_dh_auto_install] Error 1
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:9: binary] Error 2
| dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2

Helmut

Bug#910305: easyloggingpp FTBFS: configure: error: cannot find install-sh, install.sh, or shtool in build-aux ".."/build-aux

[Helmut Grohne]

Source: easyloggingpp
Version: 9.96.5+dfsg-1
Severity: serious
Tags: ftbfs

easyloggingpp fails to build from source in unstable. The build log
essentially looks like this:

| dpkg-buildpackage: info: source package easyloggingpp
| dpkg-buildpackage: info: source version 9.96.5+dfsg-1
| dpkg-buildpackage: info: source distribution unstable
| dpkg-buildpackage: info: source changed by Stephen Kitt 
|  dpkg-source --before-build .
| dpkg-buildpackage: info: host architecture amd64
|  debian/rules clean
| dh clean
|dh_clean
|  debian/rules binary
| dh binary
|dh_update_autotools_config
|dh_autoreconf
|debian/rules override_dh_auto_configure
| make[1]: Entering directory '/<>'
| mkdir gtest-build
| cp -a /usr/src/googletest/googletest gtest-source
| dh_auto_configure -Dgtest-source -Bgtest-build
| cd gtest-build && ../gtest-source/configure --build=x86_64-linux-gnu 
--prefix=/usr --includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking
| configure: WARNING: unrecognized options: --disable-maintainer-mode
| configure: error: cannot find install-sh, install.sh, or shtool in build-aux 
".."/build-aux
| cd gtest-build && tail -v -n \+0 config.log
| ==> config.log <==
| ...
| dh_auto_configure: cd gtest-build && ../gtest-source/configure 
--build=x86_64-linux-gnu --prefix=/usr --includedir=\${prefix}/include 
--mandir=\${prefix}/share/man --infodir=\${prefix}/share/info --sysconfdir=/etc 
--localstatedir=/var --disable-silent-rules 
--libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking returned exit code 1
| make[1]: *** [debian/rules:13: override_dh_auto_configure] Error 2
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:7: binary] Error 2
| dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2

This looks like some dependency changed possibly debhelper or autoconf
or something.

It's also seen by reproducible builds, but only in unstable:
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/easyloggingpp_9.96.5+dfsg-1.rbuild.log.gz

Helmut

Bug#907015: openssl version 1.1.1 breaks multiple reverse dependencies; versioned Breaks needed

[peter green]

> how is a versioned break helping anything? The minimal key limit, hash
> and TLS version can be overriden via config file and this what is
> causing the problems from what I can tell. So either the remote side
> upgrades their things or the users enabled "lower security" mode.
> Is there anything that skipped my mind?

There are also bugs in packages that actually break because of the
TLS 1.3 changes, for instance not sending the SNI and trying to
connect to google. Having a Breaks might be useful for those.

It seems the "blockers" for this bug can be split into the following categories.

Testsuite (either build-time or autopkgtest) failure (or hang), unknown whether 
it's an issue in testsuite or actual code:
907340: qtbase-opensource-src breaks purpose autopkgtest possibly due to new 
openssl (not clear if this actually is openssl related or just a coincidence)
907339: qtbase-opensource-src breaks kdeconnect autopkgtest possibly due to new 
openssl (not clear if this actually is openssl related or just a coincidence)
907118: error:141a318a:ssl routines:tls_process_ske_dhe:dh key too small
900152: nsca-ng: FTBFS against openssl 1.1.1
900158: python3.5: FTBFS against openssl 1.1.1 (sid-only)

Testsuite failure that appears to be a testsuite-specific issue.
900161: ruby-openssl: FTBFS against openssl 1.1.1 (sid-only, I tried to fix 
this but failed)
907028: ruby-openssl: autopkgtest needs update for new version of openssl 
(sid-only, probably same issue as build-time testsuite failure mentioned above)
907135: boxbackup FTBFS with OpenSSL 1.1.1
897651: u1db: FTBFS against openssl 1.1.1 (appears to be an undersized key in 
tesuitsuite)


Testsuite failure that appear to indicate an actual issue in the real code:
900160: ruby-eventmachine: FTBFS against openssl 1.1.1 (I tried to fix this but 
failed)
900156: puma: FTBFS against openssl 1.1.1 (sid-only, speculated cause has 
apparently been fixed on the openssl side but i'm not sure if the fix made it 
for 1.1.1 and the build still hangs according to the reproducible builds 
service)
898800: foolscap: FTBFS against openssl 1.1.1
907219: m2crypto: autopkgtest needs update for new version of openssl
897658: m2crypto: FTBFS against openssl 1.1.1
907427: (kimap) openssl 1.1.1 breaks ssl tests
907790: ruby2.5: FTBFS due to openssl 1.1.1
907022: puma: autopkgtest times out after update of openssl (presumablly the 
same as the build-time failure)
900154: pion: FTBFS against openssl 1.1.1

Server in stable that cannot be connected to by client in unstable:
907118: error:141a318a:ssl routines:tls_process_ske_dhe:dh key too small

Key generation script generates undersized keys:
907528: synergy: low grade TLS certificate generation, now unusable in unstable

Websites on the internet using outdated crypto:
907807: After upgrading to OpenSSL 1.1.1, many sites are unreachable

Non-web infrastructure using outdated crypto:
907518: (wpasupplicant) New libssl1.1 1.1.1~~pre9-1 in unstable breaks 
connecting to some wifi networks

SNI related troubles:
909545: SSL CERTIFICATE_VERIFY_FAILED when using gs (Google Cloud Storage) 
backend.

Bug#861361: marked as done (ruby-riddle: update build-depend to unversioned php-cli)

[Debian Bug Tracking System]

Your message dated Thu, 04 Oct 2018 15:06:47 +
with message-id 
and subject line Bug#861361: fixed in ruby-riddle 1.5.12-4.1
has caused the Debian Bug report #861361,
regarding ruby-riddle: update build-depend to unversioned php-cli
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.)


-- 
861361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861361
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-riddle
Version: 1.5.12-4
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu artful ubuntu-patch

Dear Maintainer,

Ubuntu 17.10 (and eventually Debian) are switching the default PHP to
7.1. To that end, it is better to depend on the php-cli metapackage,
unless explicit version-specific dependencies exist (for the CLI this
seems unlikely).

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


  * d/control: change b-d from php7.0 to php-cli, as there is no
specific need for PHP7.0.


Thanks for considering the patch.

*** /tmp/tmpOL60I7/ruby-riddle_1.5.12-4ubuntu1.debdiff
diff -Nru ruby-riddle-1.5.12/debian/control ruby-riddle-1.5.12/debian/control
--- ruby-riddle-1.5.12/debian/control   2017-01-04 00:34:26.0 -0800
+++ ruby-riddle-1.5.12/debian/control   2017-04-27 16:29:30.0 -0700
@@ -6,7 +6,7 @@
 Build-Depends: debhelper (>= 10~),
default-mysql-server | virtual-mysql-server,
gem2deb,
-   php7.0-cli,
+   php-cli,
procps,
rake,
ruby-mysql2,


-- System Information:
Debian Release: stretch/sid
  APT prefers zesty-updates
  APT policy: (500, 'zesty-updates'), (500, 'zesty-security'), (500, 'zesty')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

-- 
Nishanth Aravamudan
Ubuntu Server
Canonical Ltd
--- End Message ---
--- Begin Message ---
Source: ruby-riddle
Source-Version: 1.5.12-4.1

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated ruby-riddle package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 02 Oct 2018 15:51:21 +0200
Source: ruby-riddle
Binary: ruby-riddle
Architecture: source
Version: 1.5.12-4.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Mattia Rizzolo 
Description:
 ruby-riddle - Ruby API for Sphinx Search
Closes: 861361
Changes:
 ruby-riddle (1.5.12-4.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Update Vcs-* fields to point to salsa.d.o.
   * Change build-dep from php7.0 to php-cli, as there is no need for the
 specific 7.0 version.   Closes: #861361
   * Mark the ruby dependency with :any (from the m-a hinter).
   * Update watchfile to use gemwatch.debian.net.
Checksums-Sha1:
 87c326dbbfb89e2a519c194a9664d0ba5676b831 2148 ruby-riddle_1.5.12-4.1.dsc
 eb28de27169d8da6a7ed1a125ee65c61ed3efe09 3452 
ruby-riddle_1.5.12-4.1.debian.tar.xz
 16ec6fc92d7a6e896af7a56a9af4332937526c81 8703 
ruby-riddle_1.5.12-4.1_amd64.buildinfo
Checksums-Sha256:
 740cb0229c422c9950318f295e14298c5e1eae4bb25747d8c29c70b3d0baefee 2148 
ruby-riddle_1.5.12-4.1.dsc
 743cd9b89a0bdee5300010f3cf3487e59f02017bdd5152368f30bbfbb869099c 3452 
ruby-riddle_1.5.12-4.1.debian.tar.xz
 5e7ce0f934b5f6ced85f8fd208291ec1e3138f72aef0b60e53d5a94cedaef471 8703 
ruby-riddle_1.5.12-4.1_amd64.buildinfo
Files:
 2dea941c5bcfbce79e43d81fb176f7bb 2148 ruby optional ruby-riddle_1.5.12-4.1.dsc
 caf3578cdae16cda6a3eb013e74ad4e2 3452 ruby optional 
ruby-riddle_1.5.12-4.1.debian.tar.xz
 29b6f679537edadd5f31253fa7490f24 8703 ruby optional 
ruby-riddle_1.5.12-4.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAluzeKsACgkQCBa54Yx2
K62PEQ/+JxWa5i7h8Rjv4bzRPS6aihFYYiYNNf4WjnQ7f4vtvi4b0ok

Bug#907528: synergy: low grade TLS certificate generation, now unusable in unstable

[peter green]

(note: I'm just a guy taking a flyby look at bugs)


The following script is used to generate the key:
/usr/share/synergy/gen_ssl_pem.sh

Fixing that script is easy enough, but that is only the start of fixing the 
issue.

Firstly grepping the source finds a couple of other places where it seems to be 
choosing 1024 bit

res/openssl/synergy.conf:default_bits = 1024 # Size of keys
src/gui/src/SslCertificate.cpp: arguments.append("rsa:1024");

Again fixing those should be easy enough.

The final bit though is warning upgrading users, it seems these are manually 
set long term keys, so merely updating the generation script will not get the 
old keys out of service.

Bug#910295: dput FTBFS: tests fail: socket.gaierror: [Errno -2] Name or service not known

[Helmut Grohne]

Source: dput
Version: 1.0.2
Severity: serious
Tags: ftbfs

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

| ==
| ERROR: test_request_has_expected_fields 
(test.test_methods.http_upload_SuccessTestCase)
| 
test.test_methods.http_upload_SuccessTestCase.test_request_has_expected_fields 
(file-list-three,size-100k,incoming-has-trailing-slash,https,username,chatter)
| --
| testtools.testresult.real._StringException: Traceback (most recent call last):
|   File "/<>/test/test_methods.py", line 1003, in 
test_request_has_expected_fields
| self.function_to_test(**self.test_args)
|   File "/<>/dput/methods/https.py", line 16, in upload
| progress, protocol="https")
|   File "/<>/dput/methods/http.py", line 138, in upload
| conn.endheaders()
|   File "/usr/lib/python3.6/http/client.py", line 1234, in endheaders
| self._send_output(message_body, encode_chunked=encode_chunked)
|   File "/usr/lib/python3.6/http/client.py", line 1026, in _send_output
| self.send(msg)
|   File "/usr/lib/python3.6/http/client.py", line 964, in send
| self.connect()
|   File "/usr/lib/python3.6/http/client.py", line 1392, in connect
| super().connect()
|   File "/usr/lib/python3.6/http/client.py", line 936, in connect
| (self.host,self.port), self.timeout, self.source_address)
|   File "/usr/lib/python3/dist-packages/httpretty/core.py", line 617, in 
create_fake_connection
| s.connect(address)
|   File "/usr/lib/python3/dist-packages/httpretty/core.py", line 404, in 
connect
| self.truesock.connect(self._address)
| socket.gaierror: [Errno -2] Name or service not known
| 
| 
| --
| Ran 4791 tests in 70.582s
| 
| FAILED (errors=192, skipped=115)
| Test failed: 
| error: Test failed: 
| E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: 
python3.6 setup.py test 
| dh_auto_test: pybuild --test -i python{version} -p 3.6 returned exit code 13
| make: *** [debian/rules:22: build] Error 25
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

At least the vast majority of failures is due to a similar
socket.gaierror. Given that the chroot was created with
sbuild-createchroot, I'd expect that it should be "good enough". If that
isn't the case, we should fix sbuild. I've seen a discussion to make
netbase build-essential. Possibly that is related?

If you reassign the bug, make sure to "affects -1 + src:dput".

Helmut

Bug#907118: error:141a318a:ssl routines:tls_process_ske_dhe:dh key too small

[peter green]

I literally poked that patch into debian/patches{/series}, quilt
applied it and rebuilt, and it started working for me. Maybe there's
something different about our configs?

Strange, that patch seems to slightly change how the hardcoded dh params are 
loaded, but it doesn't seem to change the size of them or anything.

It seems that more recently commit 6b3844987509517dad6e41391d9142b867266b8b 
ripped out the hardcoded dh parameters and replaced them with a system for 
loading them from files, but that seems too intrusive for a stable update.

I am just taking a flyby look at rc bugs, but if this was my package I would 
propose a patch replacing the hardcoded 1024 bit parameters with hardcoded 4096 
bit parameters as a minimally intrusive fix for stable.

Bug#907873: marked as done (python3-jaraco.itertools,python-jaraco.itertools: ships /usr/lib/python*/dist-packages/.pytest_cache/v/cache/nodeids)

[Debian Bug Tracking System]

Your message dated Thu, 4 Oct 2018 16:30:19 +0200
with message-id 

and subject line 
has caused the Debian Bug report #907873,
regarding python3-jaraco.itertools,python-jaraco.itertools: ships 
/usr/lib/python*/dist-packages/.pytest_cache/v/cache/nodeids
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.)


-- 
907873: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907873
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-jaraco.itertools,python-jaraco.itertools
Version: 2.0.1-2
Severity: serious

Hi,

I'm just investigating file collisions of your packages with other
packages on the paths

  /usr/lib/python2.7/dist-packages/.pytest_cache/v/cache/nodeids
  /usr/lib/python3/dist-packages/.pytest_cache/v/cache/nodeids

which don't look like they should be shipped at all.


Andreas


python3-alembic=1.0.0-1_python3-jaraco.itertools=2.0.1-2.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 2.0.1-3

Fixed.
--- End Message ---

Processed: Re: Bug#907118: error:141a318a:ssl routines:tls_process_ske_dhe:dh key too small

[Debian Bug Tracking System]

Processing control commands:

> unblock 907015 by -1
Bug #907015 [src:openssl] openssl version 1.1.1 breaks multiple reverse 
dependencies; versioned Breaks needed
907015 was blocked by: 897643 900161 907340 900157 900982 891625 898804 898807 
907033 891665 907339 906981 900156 898800 907168 907215 906997 907219 898803 
897658 906955 907216 907135 907028 897652 898802 900160 898805 907278 907427 
907118 907049 897651 907055 907491 900152 898801 907790 907528 900158 907807 
907079 907022 907351 900154 900153 895959 907518 900159 909545 907031
907015 was blocking: 902557
Removed blocking bug(s) of 907015: 907118

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

Bug#907118: error:141a318a:ssl routines:tls_process_ske_dhe:dh key too small

[Antonio Terceiro]

Control: unblock 907015 by -1

On Sat, Sep 29, 2018 at 06:53:27PM +0200, Sebastian Andrzej Siewior wrote:
> On 2018-08-29 11:38:54 [-0600], dann frazier wrote:
> > > > error:141a318a:ssl routines:tls_process_ske_dhe:dh key too small
> > > > 
> > > > I found that backporting bip 0.9.0~rc3-1 to jessie worked. I further 
> > > > found
> > > > that just cherry-picking the following commit back to bip 0.8.9 seems 
> > > > to be
> > > > sufficient:
> > > > 
> > > >   39414f8 Handle OpenSSL version 1.1
> > > 
> > > I just tried backporting commit 39414f8 to the bip version in stretch,
> > > and it doesn't really fix the issue. There is probably some other commit
> > > that is needed.
> > 
> > I literally poked that patch into debian/patches{/series}, quilt
> > applied it and rebuilt, and it started working for me. Maybe there's
> > something different about our configs?

I'm not sure. I just tried it again with the same results. My config
file is attached, with just the sensitive parts obscured. It doesn't
seem to have anything related to this.

In the end, I solved my personal problem by building a backport of the
version in testing, and that just works.

> May I ask what is the problem here is? It looks like DH key is less than
> 1024bits in size. This is not per-se an openssl problem but "policy"
> (which could be changed but I suggest to update the key instead).

The problem is between clients with libssl 1.1.1 and bip from stable.
bip uses keys that are too small, which are rejected by default by those
clients due to the new default policy.

> If there is anything that needs to be fixed in bip in order to work
> (like missing SNI) then I would add a versioned BREAK to #907015 (after
> an upload so please let me know).

Since this is a problem between openssl on the client and bip on the
server, adding a Breaks: does not really help with anything.

> Otherwise I would unbreak this bug with #907015.

Yes, I don't think it makes sense to clock openssl on this; the version
of bip in testing/unstable is OK.

ip = "0.0.0.0";
port = 1;

client_side_ssl = true;
client_side_ssl_pem = "/var/lib/bip/bip.pem";

log_level = 3;

pid_file="/var/run/bip/bip.pid";
log_root = "/var/log/bip/";

backlog_lines = 0;# number of lines in backlog, 0 means no limit
backlog_msg_only = true;  # only include useful content in backlog

network {
name = "oftc";
ssl = true;
server { host = "irc.oftc.net"; port = 6697; };
};

network {
name = "freenode";
ssl = true;
server { host = "irc.freenode.net"; port = 6697; };
};

network {
name = "gimpnet";
ssl = true;
server { host = "irc.gimp.org"; port = 6697; };
};

user {
name = "terceiro";
password = "";

ssl_check_mode = "ca";
ssl_check_store = "/etc/ssl/certs";

default_nick = "terceiro";
default_user = "terceiro";
default_realname = "Antonio Terceiro";
connection {
name = "oftc";# used by bip only
network = "oftc"; # which ircnet to connect to

follow_nick = true;
ignore_first_nick = true;
no_client_away_msg = "currently disconnected";
on_connect_send = "PRIVMSG NickServ :IDENTIFY ";
};
connection {
name = "freenode";# used by bip only
network = "freenode"; # which ircnet to connect to

follow_nick = true;
ignore_first_nick = true;
no_client_away_msg = "currently disconnected";
on_connect_send = "PRIVMSG NickServ :IDENTIFY ";
};
connection {
name = "gimpnet"; # used by bip only
network = "gimpnet";  # which ircnet to connect to

follow_nick = true;
ignore_first_nick = true;
no_client_away_msg = "currently disconnected";
on_connect_send = "PRIVMSG NickServ :IDENTIFY ";
};
};

# vim: ft=conf


signature.asc
Description: PGP signature

Processed: openmpi: elpa builds hang on multiple architectures

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #905418 {Done: Alastair McKinstry } [src:openmpi] 
openmpi: elpa builds hang on multiple architectures
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions openmpi/3.1.2-5.

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

Bug#905418: openmpi: elpa builds hang on multiple architectures

[Graham Inggs]

Control: reopen -1

Recent builds of elpa continue to fail on armhf, i386 and ppc64el.

https://buildd.debian.org/status/package.php?p=elpa&suite=unstable

Bug#900160: ruby-eventmachine: FTBFS against openssl 1.1.1

[peter green]

It seems that ruby-eventmachine has a hardcoded 1024 bit CA certificate and 
key, I tried replacing this with a 4096 bit one but the testsuite still failed, 
I then tried replacing the client cert in the test with one signed by the new 
CA but that didn't fix things either.

Description:  Replace hardcoded cert/key with a 4096 bit one to keep recent openssl happy.
Author: Peter Michael Green 

---
The information above should follow the Patch Tagging Guidelines, please
checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
are templates for supplementary fields that you might want to add:

Origin: , 
Bug: 
Bug-Debian: https://bugs.debian.org/
Bug-Ubuntu: https://launchpad.net/bugs/
Forwarded: 
Reviewed-By: 
Last-Update: 2018-10-04

Index: ruby-eventmachine-1.0.7/ext/ssl.cpp
===
--- ruby-eventmachine-1.0.7.orig/ext/ssl.cpp
+++ ruby-eventmachine-1.0.7/ext/ssl.cpp
@@ -32,47 +32,96 @@ static EVP_PKEY *DefaultPrivateKey = NUL
 static X509 *DefaultCertificate = NULL;
 
 static char PrivateMaterials[] = {
-"-BEGIN RSA PRIVATE KEY-\n"
-"MIICXAIBAAKBgQDCYYhcw6cGRbhBVShKmbWm7UVsEoBnUf0cCh8AX+MKhMxwVDWV\n"
-"Igdskntn3cSJjRtmgVJHIK0lpb/FYHQB93Ohpd9/Z18pDmovfFF9nDbFF0t39hJ/\n"
-"AqSzFB3GiVPoFFZJEE1vJqh+3jzsSF5K56bZ6azz38VlZgXeSozNW5bXkQIDAQAB\n"
-"AoGALA89gIFcr6BIBo8N5fL3aNHpZXjAICtGav+kTUpuxSiaym9cAeTHuAVv8Xgk\n"
-"H2Wbq11uz+6JMLpkQJH/WZ7EV59DPOicXrp0Imr73F3EXBfR7t2EQDYHPMthOA1D\n"
-"I9EtCzvV608Ze90hiJ7E3guGrGppZfJ+eUWCPgy8CZH1vRECQQDv67rwV/oU1aDo\n"
-"6/+d5nqjeW6mWkGqTnUU96jXap8EIw6B+0cUKskwx6mHJv+tEMM2748ZY7b0yBlg\n"
-"w4KDghbFAkEAz2h8PjSJG55LwqmXih1RONSgdN9hjB12LwXL1CaDh7/lkEhq0PlK\n"
-"PCAUwQSdM17Sl0Xxm2CZiekTSlwmHrtqXQJAF3+8QJwtV2sRJp8u2zVe37IeH1cJ\n"
-"xXeHyjTzqZ2803fnjN2iuZvzNr7noOA1/Kp+pFvUZUU5/0G2Ep8zolPUjQJAFA7k\n"
-"xRdLkzIx3XeNQjwnmLlncyYPRv+qaE3FMpUu7zftuZBnVCJnvXzUxP3vPgKTlzGa\n"
-"dg5XivDRfsV+okY5uQJBAMV4FesUuLQVEKb6lMs7rzZwpeGQhFDRfywJzfom2TLn\n"
-"2RdJQQ3dcgnhdVDgt5o1qkmsqQh8uJrJ9SdyLIaZQIc=\n"
-"-END RSA PRIVATE KEY-\n"
+"-BEGIN PRIVATE KEY-\n"
+"MIIJQQIBADANBgkqhkiG9w0BAQEFAASCCSswggknAgEAAoICAQCemVhlidvoMwyR\n"
+"BRwAvYIFbfpZq9i/qbn+N14+imfNif9LzrLRRwyRQ08r2gNowMBieuN0RDap6fMP\n"
+"0f7Q3hgKpZ/5p3E2GqSw+xSiFJcFqCf0GtrH8UWKRsVwZFYfEPSyWzzuvgsCEh8d\n"
+"58vD8TKhdENSfoAI7wV9AifWFKPJwjt4cOi49JoW15aUODb87QvHdz84KoJ3vxN1\n"
+"X6u5ndp74vKhIhdL54heCHdaWG0B1EFong7QzWKn9k9LenopemyqHhCrfbil58ps\n"
+"a12wYgVpptY1up1PsgChfrRvGsp0eoe2fIxgXihsBUbszUeAdvo4evd54VIzcgP/\n"
+"8WBQknrFS0D/TJh3XWPKen36XGjSWxgPo4lc6gqYgf5EiUZM50M09nJ/zvEvBsGc\n"
+"wz1wNxRpQ8EJpUiz1gxGN6FMVvn7neS2LoDgKGmhplGanUhpYSswWr1NRJmY94aR\n"
+"0JRO5cvLriUAYhuj0vnUAfVMazlDg9bXI9KC57yNGg4UvtovdOBqxey5dVE//GG7\n"
+"/zAoHbPkPg7BdLMIolB7HXz/DOEGyzTIGYAFg3KUIl42PsbxtsPCKjKqb/T23mKc\n"
+"ZcbmdLhPOiGm4yVwM4LDUlW3nywtq7fcnJarTWz9B7tjszJYIMcAH95hnXIb6LQB\n"
+"wlY4F8ts+DzGfKGtZSifkTsKMzboxQIDAQABAoICAEla06/jG3tCYUWR/2m4PTMV\n"
+"sv1WpmG/tu8F3OlAStKeSR5e9AYnvoBRiYTWyUziGhlyjVFxW3crZeijUCB7GNOT\n"
+"13I5J/vGRvY0q05sB43uQMx+v0JLLcbPBPL+9XZY+VSlLoGeFKlYiFvkojJ2lNxo\n"
+"UdsN91oqc3dmT9aMpVTkKW2Di6BAQiTegh78ATLq0M/pL6xivQV1syJOpbasdClo\n"
+"xqAQjIXnCQO1Fr8KtyBpc/dXY7LfzAmzuulGNMqKfUgRr9Qhyg2yL8YFwseaDrbX\n"
+"G6yuK6R4yCHp4LqiwZEuOycEZEkOQ9PyfON57uBUJ1eISH5u4P46de8jTVD27yEn\n"
+"SezHd1TxzOl1pXMZfEOthRiDaXuEATxioJsxNVOp+boEXrtQ3k61goqs7JPWzi1g\n"
+"vLTK4YVlDHaCz8NTeqgnaMl1J04ourXJV/uTVcPjNiaof6f+tXS/PWEPef2mraDl\n"
+"PSdwpOThQvQbknl9sVKFpIyqUvHDZWm0lcn4eK2DAkux9nW4FBduqCRjtJej+nzw\n"
+"kTlyqaFhxvfwEwBq7by82a6wV86Qu1TyA3vRnGrB7u3/ZGvXbq25S2PvmB5BEctQ\n"
+"5qHL3bQxbGOqgHUo/E3y/zqwF5bSnwKNyy1DlPowQW9DkTcYqj/kdYTq9gxaCFpB\n"
+"6yr5tnsCBGil+sYdkhYBAoIBAQDMyi93tQT2sXV5+iK6ah5FsjIttNb10BMdqoI0\n"
+"UUJrjWIfbbx/BDAI4CWzQI4rVcdeNW4On/4wUFfeiNmwRYBQ7z26182gptNpEQFc\n"
+"dIn0hbv0Q7S/gkiqncpWRFCFu2/9QwD45SkcNOswTwis+YNFWUSTq2rJuFmDNHKj\n"
+"6W//OPK/b8Efq9pMqSdISXHmx2LCapgYiifqKy/PDeWnw+E07R7yLJE6AQceXLhd\n"
+"NHsWUR8O0ubTk8BwroocHw6VKM/9hVsEaXOemcMt4Ia7AbR3Qn13HbnJyQyDFd/9\n"
+"jUaAPpd8fspYk1KI9HVaA1JnZEWgyMvqCbd0XNEwScV83e1VAoIBAQDGQjZzFrDS\n"
+"G5G4bvVwAMEbvg1+diU5PScbhMLss5kMlunCm6LROsQLLiYOxynFMNkJvfa8X7z0\n"
+"1fsOYmDsCu7RTw2VO7nRiJP3AS6b9cvj4SpcjqvssC6L3GmXIvPlrYQAn/K6QMUe\n"
+"E3DnwT9Zn1op5C7H1Cid7AnAEYVWcSLzQd0QrBCaNVAK756ucop+7dls7YTgWz8T\n"
+"07rc1YWmZXFwhmXXv5DcpkU3sExQTro0ZhIg9iJe4A3j7lXCSmugL2JL7l0lNTIq\n"
+"1GsJvDQfRaSnizbiS2oY6FaRGPSelifyUn8pjSyR0HVV1pN/Z9kNzeHd3A24NuYg\n"
+"XbjOO2tJ1o2xAoIBAHvB77+iyFYg1gKZtCT9fj/WOVa/w2wXi4XRBhCBzubaMSMX\n"
+"GOOVb0Xd10qlR4VOuEXpehIig+VEmGVmRE+vIKVIfwCL67sbNgV3fmAWGUyJCRXL\n"
+"WM6m+C0LYDyT2imHJV1jAZJoQljGbh7qlC6cNsVQ9g1beRRgcM/GgUUnDESrcJ9Z\n"
+"9Naj7y+GxbN8lvXFJpyg+DtUOlzcLm8tUcz5pf5rEdl+L2FjP58Mn2nMDlplOaSm\n"
+"tVHFJ3WxNMtbxV9Eo7Tswx0+cN22xGnUFveqRxoPN20lrKIR+pq5PHyoxKM5sChP\n"
+"Iw82MJmNSeHUwhazVRSeZASSTKhocw6AdnVIVGUCggEAfm06y6lsmI98HWCkowfY\n"
+"HRjVAg/VLOsSRTokE010C9MwvikBautOmNKU8lePC3Ba9xtsfDORC5BoyINzyxIt\n"
+"uMvwnXm4xSWTNbBLSKk1m9u6Z8uTVxwCkq27p+ViItTDmKJm5t7m1IcROLjC7SPx\n"
+"G0Wnj0Z7oDkk/pYtsTH0V6tojXksHSpiIJ

Bug#893423: marked as done (thepeg FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Thu, 04 Oct 2018 13:39:32 +
with message-id 
and subject line Bug#893423: fixed in thepeg 1.8.0-4
has caused the Debian Bug report #893423,
regarding thepeg FTBFS with openjdk-9
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.)


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

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

...
checking for javac... /usr/bin/javac
checking for java... /usr/bin/java
checking for jar... /usr/bin/jar
checking if java works... no
configure: Java GUI disabled
...
   debian/rules override_dh_install-indep
make[1]: Entering directory '/build/1st/thepeg-1.8.0'
dh_install
dh_install: Cannot find (any matches for) "usr/bin/thepeg" (tried in ., 
debian/tmp)

dh_install: thepeg-gui missing files: usr/bin/thepeg
dh_install: Cannot find (any matches for) "usr/lib/*/ThePEG/ThePEG.jar" (tried 
in ., debian/tmp)

dh_install: thepeg-gui missing files: usr/lib/*/ThePEG/ThePEG.jar
dh_install: missing files, aborting
make[1]: *** [debian/rules:38: override_dh_install-indep] Error 25
--- End Message ---
--- Begin Message ---
Source: thepeg
Source-Version: 1.8.0-4

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated thepeg package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 04 Oct 2018 15:12:10 +0200
Source: thepeg
Binary: thepeg thepeg-gui libthepeg15 libthepeg-dev thepeg-reference
Architecture: source
Version: 1.8.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libthepeg-dev - Development library of ThePEG
 libthepeg15 - Run-time library of ThePEG
 thepeg - Toolkit for High Energy Physics Event Generation
 thepeg-gui - Java GUI of ThePEG
 thepeg-reference - Code reference of ThePEG
Closes: 893423
Changes:
 thepeg (1.8.0-4) unstable; urgency=medium
 .
   * Team upload.
   * Fixed the build failure with Java 9 (Closes: #893423)
Checksums-Sha1:
 4ae08197590f0e8d54f702f69b4e03f9fb3e8fc6 2387 thepeg_1.8.0-4.dsc
 ab497bdd5ce201f0c1ba5d117662d65c97d3368d 5152 thepeg_1.8.0-4.debian.tar.xz
 834c49cec5bb8d0dd27c559431aed5c3ce083bc0 11252 thepeg_1.8.0-4_source.buildinfo
Checksums-Sha256:
 1b91e079db7945e45ffc8da019b20dfa8a4cc4597c52649885fe7dd9adbbb1b9 2387 
thepeg_1.8.0-4.dsc
 39f99cf8ac7c3036859be35e4bd79677b2fbd853f0a5d38af2e741fcefe74307 5152 
thepeg_1.8.0-4.debian.tar.xz
 87c1bca5f5a2b7e5f9419b3a633816b0a62af1bce3091ef7ed235e807d9a872a 11252 
thepeg_1.8.0-4_source.buildinfo
Files:
 5807a2973e4af496859593c927b1cf68 2387 science optional thepeg_1.8.0-4.dsc
 861f77d4adfb07dabf5422618658d081 5152 science optional 
thepeg_1.8.0-4.debian.tar.xz
 60ac00ff09e680b4b60a99a491f6e191 11252 science optional 
thepeg_1.8.0-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAlu2EccSHGVib3VyZ0Bh
cGFjaGUub3JnAAoJEPUTxBnkudCssuoP+wV0H4Tjhv/PA14yKUS1Ye+UrHu0+zZp
d8w98ZatYl95MWBmawcqH3Wkj10IdRfJ0FfK+HzYs5I8Qq73DxyFLMQSwFYTymy1
9xb68YYRVgNAvFMG6CmrtuTqME8vrkjW+gcTEUo3kNYn8h/RT8Fr+6yeEv2yXjgy
ovyQ+9TijI0HKIgJfHEn+A92zqvgHNeO/jTkHmGAaJ4T23UuQyEQRI9pLCYgmrN2
iDXv0cv6769Xi4dJmkuXokCLpVVcvyP9whT4mRMoVVJMsiHTkPlPbPZThMgfONbD
ESx2S+Jq4yy1c/sYSdEl0pOjaNXHtuVzDYRtj/3OGJHM6kp6x6I/J3h+vSbfaBgk
uFVknVBUMcz13QdLDhB1E6ym+aNv434Ncg1NZqsDyrM/tZPJ+IHILatlL7up3dzy
xY/IP3+6CJVzp96HNXmHswEzIgfJ+/F+f01ZggJ1aOZH4bF0KMK2u6MyvRNoMc2i
0cPRx+3BR3sx7i3jvhAWpSkjdVbMx8sJSK76KyhgKeyJKBVrfBjJyf3YlFtE+qbK
3ltBSWg8pAyqUnHfrUi8ctGngy4Lnq4AZp8iSHmIdDsCk61zfPSn02kCJ1tJEdit
JhkBrMiqakGa+ieNXFc8SeDlC+oQ8gUqWnKHxbpo/xNwDcHkiD9z1tHGzB5FOySv
aHxLohjgAZdM
=A6lJ
-END PGP SIGNATURE End Message ---

Bug#909536: mozjs60: FTBFS on s390x: around 80% of tests crash

[Simon McVittie]

On Thu, 04 Oct 2018 at 11:24:14 +0200, Philipp Kern wrote:
> Running the revdep check for gjs (there are currently none on mozjs60):
> > Checking reverse dependencies...
> > # Broken Depends:
> > gnome-characters: gnome-characters
> > gnome-documents: gnome-documents
> > gnome-maps: gnome-maps
> > gnome-shell: gnome-shell
> > gnome-sound-recorder: gnome-sound-recorder
> > gnome-sushi: gnome-sushi
> > gnome-weather: gnome-weather
> > ostree: ostree-tests
> > polari: polari
> > 
> > # Broken Build-Depends:
> > gnome-characters: gjs (>= 1.49)
> >   libgjs-dev (>= 1.49)
> > gnome-documents: gjs (>= 1.48.0)
> >  libgjs-dev (>= 1.48)
> > gnome-maps: gjs (>= 1.50.0)
> > libgjs-dev (>= 1.44.0)
> > gnome-shell: libgjs-dev (>= 1.50.2-3~)
> > gnome-sound-recorder: gjs
> > gnome-sushi: libgjs-dev (>= 1.40)
> > gnome-weather: gjs (>= 1.49.4)
> >libgjs-dev (>= 1.39.91)
> > gpaste: libgjs-dev (>= 1.48.0)
> > libguestfs: gjs
> > libsecret: gjs
> > polari: libgjs-dev (>= 1.49.2)
> > seed-webkit2: libgjs-dev
> > 
> > Dependency problem found.
> 
> The main packages that are regrettable in this context are libguestfs
> and maybe also ostree. Would the gjs dependency be avoidable there?

I think we'll probably also want libsecret to survive, but that was
already fixed in unstable. (Maybe it showed up in your search as a result
of outdated binary packages on some architecture?)

ostree is fixed in git, I'll upload that soon: https://bugs.debian.org/910286

I've sent a patch for libguestfs, which is not a GNOME team package:
https://bugs.debian.org/910287

Both are marked as blockers for the transition bug
.

smcv

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

[Debian Bug Tracking System]

Your message dated Thu, 04 Oct 2018 12:21:59 +
with message-id 
and subject line Bug#899906: fixed in sword 1.7.3.1+dfsg-1
has caused the Debian Bug report #899906,
regarding sword: 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.)


-- 
899906: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899906
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:sword
Version: 1.7.3+dfsg-9.1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of sword,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package sword 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 ---
Source: sword
Source-Version: 1.7.3.1+dfsg-1

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

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

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

Debian distribution maintenance software
pp.
Teus Benschop  (supplier of updated sword package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 04 Oct 2018 13:52:16 +0200
Source: sword
Binary: libsword11v5 libsword-dev libsword-common libsword-utils libsword-dbg 
diatheke
Architecture: source
Version: 1.7.3.1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: CrossWire Packaging Team 

Changed-By: Teus Benschop 
Description:
 diatheke   - command line bible browsing and search tool
 libsword-common - common settings and module repository for libsword
 libsword-dbg - API/library for bible software - Debug Files
 libsword-dev - Development files for libsword
 libsword-utils - conversion utilities for bible documents in SWORD supported 
forma
 libsword11v5 - API/library for bible software
Closes: 899906
Changes:
 sword (1.7.3.1+dfsg-1) unstable; urgency=medium
 .
   [ Daniel Glassey ]
   * Imported Upstream version 1.7.3+dfsg
 .
   [ Teus Benschop ]
   * changelog
   * New upstream version 1.7.3.1+dfsg
   * debian/control: Updated maintainer email: Closes: #899906
   * debian/control: Updated Vcs-* for Salsa
Checksums-Sha1:
 8f4243af6a626c7bc7c8bfcdf3cc431f41f3611c 2498 sword_1.7.3.1+dfsg-1.dsc
 3841aec410c55aeec4adb303392cd2e16c51a28c 1845241 sword_1.7.3.1+dfsg.orig.tar.gz
 860734d9007728cf9115ecdc4d39c617a9ebf91a 27216 
sword_1.7.3.1+dfsg-1.debian.tar.xz
 55953f4b3a4a01e57

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

[Bert]

Same problem here, issue persists in 62.0.3-1 for me.

Processed: Bug #910233 in subversion marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #910233 [libsvn-dev,libsvn-java] libsvn-{dev,java}: unhandled symlink to 
directory conversion: /usr/share/doc/PACKAGE
Added tag(s) pending.

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

Bug#910233: Bug #910233 in subversion marked as pending

[James McCoy]

Control: tag -1 pending

Hello,

Bug #910233 in subversion 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/jamessan/subversion/commit/5ed1d9dfd96277d55e8e96eec6fe0c74d840254c


libsvn-{java,dev}: Use absolute target path for symlink_to_dir calls

Closes: #910233
Signed-off-by: James McCoy 



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/910233

Bug#910233: libsvn-{dev,java}: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[James McCoy]

On Thu, Oct 04, 2018 at 06:56:45AM +0200, Andreas Beckmann wrote:
> On 2018-10-04 02:53, James McCoy wrote:
> > On Wed, Oct 03, 2018 at 07:49:35PM +0200, Andreas Beckmann wrote:
> >> an upgrade test with piuparts revealed that your package installs files
> >> over existing symlinks and possibly overwrites files owned by other
> 
> > This is exactly what I did:
> > 
> > https://salsa.debian.org/jamessan/subversion/commit/d5e5e1c5c61b072974de5e0803deed669530e48c
> > https://salsa.debian.org/jamessan/subversion/commit/af236dd6de6239dff820d480206b4c92b8287be2
> 
> That looks good, except ...
> 
> The problematic links I observed are not normalized but use an absolute
> target:
> /usr/share/doc/libsvn-java -> /usr/share/doc/libsvn1
> (I didn't check where these originate from.)

Ack, you're right.  Thanks!

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Bug#910233: libsvn-{dev,java}: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Andreas Beckmann]

On 2018-10-04 02:53, James McCoy wrote:
> On Wed, Oct 03, 2018 at 07:49:35PM +0200, Andreas Beckmann wrote:
>> an upgrade test with piuparts revealed that your package installs files
>> over existing symlinks and possibly overwrites files owned by other

> This is exactly what I did:
> 
> https://salsa.debian.org/jamessan/subversion/commit/d5e5e1c5c61b072974de5e0803deed669530e48c
> https://salsa.debian.org/jamessan/subversion/commit/af236dd6de6239dff820d480206b4c92b8287be2

That looks good, except ...

The problematic links I observed are not normalized but use an absolute
target:
/usr/share/doc/libsvn-java -> /usr/share/doc/libsvn1
(I didn't check where these originate from.)

It should work if you replace the normalized relative target 'libsvn1'
with the absolute target '/usr/share/doc/libsvn1'.
dpkg-maintscript-helper will check both $(readink whatever) and
$(readlink -f whatever) against this target, so it will work with both
relative and absolute targets.
Don't forget to bump the .maintscript version.


Andreas

Processed: archiving 903802

[Debian Bug Tracking System]

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

> archive 903802
Bug #903802 {Done: Sylvestre Ledru } [libomp5-7] 
libomp5-7: missing Breaks+Replaces: libomp5
archived 903802 to archive/02 (from 903802)
> thanks
Stopping processing here.

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

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

[peter green]

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.



/ruby-openssl-2.0.5/test/envutil.rb:258:in `assert_join_threads'
Failure: test_tlsext_hostname(OpenSSL::TestSSL):
  exceptions on 2 threads:
#:
  /ruby-openssl-2.0.5/test/test_ssl.rb:654:in `connect': SSL_connect returned=1 
errno=0 state=error: sslv3 alert handshake failure (OpenSSL::SSL::SSLError)
from /ruby-openssl-2.0.5/test/test_ssl.rb:654:in `block in 
test_tlsext_hostname'
from /ruby-openssl-2.0.5/test/utils.rb:445:in `block (2 levels) in 
start_server'
  ---
#:
/ruby-openssl-2.0.5/debian/ruby-openssl/usr/lib/ruby/vendor_ruby/openssl/ssl.rb:382:in
 `accept': SSL_accept returned=1 errno=0 state=error: no suitable signature 
algorithm (OpenSSL::SSL::SSLError)
from 
/ruby-openssl-2.0.5/debian/ruby-openssl/usr/lib/ruby/vendor_ruby/openssl/ssl.rb:382:in
 `accept'
from /ruby-openssl-2.0.5/test/utils.rb:383:in `block in server_loop'
from /ruby-openssl-2.0.5/test/utils.rb:376:in `loop'
from /ruby-openssl-2.0.5/test/utils.rb:376:in `server_loop'
from /ruby-openssl-2.0.5/test/utils.rb:434:in `block (2 levels) in 
start_server'
=
: (0.010154)
test_unset_OP_ALL: .: (0.059083)
test_verify_certificate_identity: .: (0.008254)
test_verify_hostname: .: (0.007457)
test_verify_hostname_on_connect: .: (0.065102)
test_verify_result: .: (0.026004)
test_verify_wildcard: .: (0.005284)
OpenSSL::TestSSLSession:
test_client_session: 
# 
terminated with exception (report_on_exception is true):
Traceback (most recent call last):
9: from /ruby-openssl-2.0.5/test/utils.rb:445:in `block (2 levels) in 
start_server'
8: from /ruby-openssl-2.0.5/test/test_ssl_session.rb:158:in `block in 
test_client_session'
7: from /ruby-openssl-2.0.5/test/test_ssl_session.rb:158:in `times'
6: from /ruby-openssl-2.0.5/test/test_ssl_session.rb:168:in `block (2 
levels) in test_client_session'
5: from /usr/lib/ruby/vendor_ruby/test/unit/assertions.rb:130:in 
`assert'
4: from /usr/lib/ruby/vendor_ruby/test/unit/assertions.rb:1636:in 
`_wrap_assertion'
3: from /usr/lib/ruby/vendor_ruby/test/unit/assertions.rb:163:in `block 
in assert'
2: from /usr/lib/ruby/vendor_ruby/test/unit/assertions.rb:53:in 
`assert_block'
1: from /usr/lib/ruby/vendor_ruby/test/unit/assertions.rb:1631:in 
`_wrap_assertion'
/usr/lib/ruby/vendor_ruby/test/unit/assertions.rb:55:in `block in assert_block': 
 is not true. (Test::Unit::AssertionFailedError)


Description: Use stronger keys in tests to fix build with new openssl.
Author: Peter Michael Green 

---
The information above should follow the Patch Tagging Guidelines, please
checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
are templates for supplementary fields that you might want to add:

Origin: , 
Bug: 
Bug-Debian: https://bugs.debian.org/
Bug-Ubuntu: https://launchpad.net/bugs/
Forwarded: 
Reviewed-By: 
Last-Update: 2018-10-04

Index: ruby-openssl-2.0.5/test/utils.rb
===
--- ruby-openssl-2.0.5.orig/test/utils.rb
+++ ruby-openssl-2.0.5/test/utils.rb
@@ -64,6 +64,102 @@ gBoDG3WMPZoQj9pb7uMcrnvs4APj2FIhMU8U15Lc
 -END RSA PRIVATE KEY-
   _end_of_pem_
 
+  TEST_KEY_RSA3072 = OpenSSL::PKey::RSA.new <<-_end_of_pem_
+-BEGIN RSA PRIVATE KEY-
+MIIG4wIBAAKCAYEAuOfm5u9QvTVA3injjLlNQIdNEpkygrgeKF5yZDGndcsUTIap
+tdYW8e78rOFmt/LUHXZpiY/e0vo5WH6Lyp5/EGOCJqatKa21uDef3+bmsWNb9MOE
+XaIRjmcNjVim4aVJdGpjQzN/ysjR8KdqRwY3TDzVBsX7eNJpKS10NiMgSGvxxLwE
+00Z/YgM9RLKjtjjWLloP/cuiZcLplaXF+Tyi49u8P7yrlNheGGtU5eEZmx+XESES
+izsFyFC2zhDKpGlU+v9+oSbOPy6xNB9TjsxpG6QTtGdP9T8f990EcO/TC/JAr/uk
+RwoSqMZyeUT0lk+QzfkoVYsuzGjWlLnW+yLgnv4xb003sZCPa7llxhwZYajpZgdm
+/xhKBWg7x8u62aOR2pqNrV7aCRbI0AY2OphTuRIj1pwgX+t7RItrLHJ9Q0hVNQYL
+iJwwH7QhRcWBx4S07M1uR7u9tESqu1rm5W+AbpV/gWVZE8RGn6KHYndn1l7qjnWH
+z7bJYlLHm0AExp67AgMBAAECggGADacZ1n1fIclX08+V/KMGADi9SR1ErIA5wdNP
+cPR1n+3xvsDGsSVwpkZ2I7G06uokHVTL8BtOYZeWOmGFot1XFneyeXYfHQ+1djet
+N1QOPpTOimERWfSIhVI4nvInyEtzBASC9chMrEVtsu45m6rq1Fc9h3WA3ufyWdcA
+WKr5TD+kJ1mWpZ7z8uG4WWUzT1YdAmkl+yBZClh89M67sm52vIpR+QbOSHw9XmI2
+b47SXDDV767Ydq1R/PtwtABrZf5c5sm2ivRQG2xXUug+ykmTWLISQXqA+aWY46XL
+ymvwhna9wVNWlRrsVdWyl+O3u8rTS18Y817AraZpHnc049DXovVt3qRLKzuj+EfL
++2Ut00tfdHxrrVmqcncMeFCLphhjTLK8BA7Kxnd1F6mIkH2unYb0tB+yqElX/Zvp
+oDRiwpncCi0bnLq8Q+57+m5xn1dp6ebM710G3u9U63oPQAgeHHxYp5ZhvI8rgdUx
+nXkQ44SqqPeAKmIkV9cS0p+jp/1JAoHBAOYE+fyTZq4DwEWM3FxvbW+VPS/Fw1oF
+1ON3dSZP4UQFcubkUwZedVCdgbkXSHN4u7G7MzZw3SHaiTyCM8eBI7tc3MHo0F5W
+7bBAOLrwn9129D8D9ISZaEJejXfJG7aaE

Bug#910255: libsane-common: error upgrading libsane-common (1.0.27-2) over (1.0.25-4.1)

[Jeremy Bicha]

libsane-common should not provide the manpage for sane-config since
Debian doesn't provide sane-config any more.

Thanks,
Jeremy Bicha

Processed: Test failures

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #906381 [src:lmfit-py] lmfit-py: FTBFS in buster/sid (failing tests)
Ignoring request to alter tags of bug #906381 to the same tags previously set
> tags -1 upstream
Bug #906381 [src:lmfit-py] lmfit-py: FTBFS in buster/sid (failing tests)
Added tag(s) upstream.
> forwarded -1 https://github.com/lmfit/lmfit-py/issues/502
Bug #906381 [src:lmfit-py] lmfit-py: FTBFS in buster/sid (failing tests)
Changed Bug forwarded-to-address to 
'https://github.com/lmfit/lmfit-py/issues/502' from 
'https://github.com/lmfit/lmfit-py/pull/467'.

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

Processed: Test failures

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #906419 [src:lmfit-py] lmfit-py: FTBFS: test failure
Ignoring request to alter tags of bug #906419 to the same tags previously set
> tags -1 upstream
Bug #906419 [src:lmfit-py] lmfit-py: FTBFS: test failure
Added tag(s) upstream.
> forwarded -1 https://github.com/lmfit/lmfit-py/issues/502
Bug #906419 [src:lmfit-py] lmfit-py: FTBFS: test failure
Set Bug forwarded-to-address to 'https://github.com/lmfit/lmfit-py/issues/502'.

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

Bug#906381: Test failures

[Andreas Tille]

Control: tags -1 help
Control: tags -1 upstream
Control: forwarded -1 https://github.com/lmfit/lmfit-py/issues/502

Bug#909536: mozjs60: FTBFS on s390x: around 80% of tests crash

[Simon McVittie]

On Thu, 04 Oct 2018 at 11:24:14 +0200, Philipp Kern wrote:
> The main packages that are regrettable in this context are libguestfs
> and maybe also ostree. Would the gjs dependency be avoidable there?

ostree: definitely OK, the necessary changes are already staged
in git. gjs is only used for one test, which can be skipped on
non-mozjs-capable architectures.

libguestfs: it looks as though the B-D is for build-time tests of
GObject-Introspection bindings, which can be skipped (at a loss of
coverage).

smcv

Bug#909536: mozjs60: FTBFS on s390x: around 80% of tests crash

[Philipp Kern]

On 24.09.2018 22:18, Simon McVittie wrote:
> We can't upgrade gjs to a version that uses mozjs60 until either this is
> fixed somehow, or gjs and its dependencies (notably GNOME Shell) are
> removed from s390x. The architecture-specific removal seems a more likely
> short term solution; if this is done I'll downgrade this bug to important.

Running the revdep check for gjs (there are currently none on mozjs60):

> % dak rm -n -a s390x -R gjs
> W: -a/--architecture implies -p/--partial.
> Will remove the following packages from unstable:
> 
>gjs |   1.50.2-1 | source
>gjs |   1.52.3-2 | source, s390x
>  gjs-tests |   1.52.3-2 | s390x
> libgjs-dev |   1.52.3-2 | s390x
>   libgjs0g |   1.52.3-2 | s390x
> 
> Maintainer: Debian GNOME Maintainers 
> 
> 
> --- Reason ---
> 
> --
> 
> Checking reverse dependencies...
> # Broken Depends:
> gnome-characters: gnome-characters
> gnome-documents: gnome-documents
> gnome-maps: gnome-maps
> gnome-shell: gnome-shell
> gnome-sound-recorder: gnome-sound-recorder
> gnome-sushi: gnome-sushi
> gnome-weather: gnome-weather
> ostree: ostree-tests
> polari: polari
> 
> # Broken Build-Depends:
> gnome-characters: gjs (>= 1.49)
>   libgjs-dev (>= 1.49)
> gnome-documents: gjs (>= 1.48.0)
>  libgjs-dev (>= 1.48)
> gnome-maps: gjs (>= 1.50.0)
> libgjs-dev (>= 1.44.0)
> gnome-shell: libgjs-dev (>= 1.50.2-3~)
> gnome-sound-recorder: gjs
> gnome-sushi: libgjs-dev (>= 1.40)
> gnome-weather: gjs (>= 1.49.4)
>libgjs-dev (>= 1.39.91)
> gpaste: libgjs-dev (>= 1.48.0)
> libguestfs: gjs
> libsecret: gjs
> polari: libgjs-dev (>= 1.49.2)
> seed-webkit2: libgjs-dev
> 
> Dependency problem found.

The main packages that are regrettable in this context are libguestfs
and maybe also ostree. Would the gjs dependency be avoidable there?

Kind regards
Philipp Kern

Bug#906383: marked as done (lombok-patcher: FTBFS in buster/sid)

[Debian Bug Tracking System]

Your message dated Thu, 04 Oct 2018 09:04:24 +
with message-id 
and subject line Bug#906383: fixed in lombok-patcher 0.28-1
has caused the Debian Bug report #906383,
regarding lombok-patcher: FTBFS in buster/sid
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.)


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

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with javahelper
   dh_update_autotools_config -i
   dh_autoreconf -i
   dh_auto_configure -i
   jh_linkjars -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
mkdir -p build/packInjector
ant dist
Buildfile: /<>/build.xml

-pointlessCheck:


[... snipped ...]

[ivy:compile]   at 
jdk.compiler/com.sun.tools.javac.main.Main.compile(Main.java:165)
[ivy:compile]   at jdk.compiler/com.sun.tools.javac.Main.compile(Main.java:57)
[ivy:compile]   at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[ivy:compile]   at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[ivy:compile]   at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[ivy:compile]   at java.base/java.lang.reflect.Method.invoke(Method.java:564)
[ivy:compile]   at 
org.apache.tools.ant.taskdefs.compilers.Javac13.execute(Javac13.java:57)
[ivy:compile]   at org.apache.tools.ant.taskdefs.Javac.compile(Javac.java:1404)
[ivy:compile]   at org.apache.tools.ant.taskdefs.Javac.execute(Javac.java:1133)
[ivy:compile]   at com.zwitserloot.ivyplusplus.Compile.execute(Unknown Source)
[ivy:compile]   at 
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292)
[ivy:compile]   at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[ivy:compile]   at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[ivy:compile]   at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[ivy:compile]   at java.base/java.lang.reflect.Method.invoke(Method.java:564)
[ivy:compile]   at 
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:99)
[ivy:compile]   at org.apache.tools.ant.Task.perform(Task.java:350)
[ivy:compile]   at org.apache.tools.ant.Target.execute(Target.java:449)
[ivy:compile]   at org.apache.tools.ant.Target.performTasks(Target.java:470)
[ivy:compile]   at 
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1388)
[ivy:compile]   at org.apache.tools.ant.Project.executeTarget(Project.java:1361)
[ivy:compile]   at 
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
[ivy:compile]   at 
org.apache.tools.ant.Project.executeTargets(Project.java:1251)
[ivy:compile]   at org.apache.tools.ant.Main.runBuild(Main.java:834)
[ivy:compile]   at org.apache.tools.ant.Main.startAnt(Main.java:223)
[ivy:compile]   at org.apache.tools.ant.launch.Launcher.run(Launcher.java:284)
[ivy:compile]   at org.apache.tools.ant.launch.Launcher.main(Launcher.java:101)
[ivy:compile] Caused by: java.lang.ClassNotFoundException: 
com.sun.tools.javac.code.TypeTags
[ivy:compile]   at 
java.base/java.lang.ClassLoader.findClass(ClassLoader.java:711)
[ivy:compile]   at 
java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:566)
[ivy:compile]   at 
lombok.launch.ShadowClassLoader.loadClass(ShadowClassLoader.java:422)
[ivy:compile]   at 
java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:499)
[ivy:compile]   at java.base/java.lang.Class.forName0(Native Method)
[ivy:compile]   at java.base/java.lang.Class.forName(Class.java:291)
[ivy:compile]   at 
lombok.javac.JavacTreeMaker$SchroedingerType.getFieldCached(JavacTreeMaker.java:156)
[ivy:compile]   at 
lombok.javac.JavacTreeMaker$TypeTag.typeTag(JavacTreeMaker.java:244)
[ivy:compile]   at lombok.javac.Javac.(Javac.java:158)
[ivy:compile]   ... 47 more

BUILD FAILED
/<>/build.xml:112: Compile failed; see the compiler error output 
for details.

Total time: 2 seconds
make[1]: *** [debian/rules:14: override_dh_auto_build] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:6: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2
--

Bug#907880: marked as done (libomp5-8: missing Breaks+Replaces: libomp5-7)

[Debian Bug Tracking System]

Your message dated Thu, 4 Oct 2018 10:59:47 +0200
with message-id 
and subject line fixed
has caused the Debian Bug report #907880,
regarding libomp5-8: missing Breaks+Replaces: libomp5-7
to be marked as done.

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

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


-- 
907880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907880
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libomp5-8
Version: 1:8~svn340819-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
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/#overwriting-files-and-replacing-packages-replaces

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

  Preparing to unpack .../libomp5-8_1%3a8~svn340819-1_amd64.deb ...
  Unpacking libomp5-8:amd64 (1:8~svn340819-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libomp5-8_1%3a8~svn340819-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libomp.so.5', which is also 
in package libomp5-7:amd64 1:7~+rc2-1~exp2
  Errors were encountered while processing:
   /var/cache/apt/archives/libomp5-8_1%3a8~svn340819-1_amd64.deb


cheers,

Andreas


libomp5-7=1%7~+rc2-1~exp2_libomp5-8=1%8~svn340819-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
fixed 774295
fixed 907880

done

both are now fixed!

S--- End Message ---

Bug#910268: dolphin-emu: FTBFS with googletest 1.8.1

[James Cowgill]

Source: dolphin-emu
Version: 5.0+dfsg-3
Severity: serious
Tags: sid buster ftbfs fixed-upstream

dolphin-emu FTBFS with googletest 1.8.1:
> In file included from 
> /usr/src/gtest/include/gtest/internal/gtest-internal.h:40,
>  from /usr/src/gtest/include/gtest/gtest.h:59,
>  from 
> /<>/Source/UnitTests/VideoCommon/VertexLoaderTest.cpp:11:
> /usr/src/gtest/include/gtest/internal/gtest-port.h:891:57: error: 
> 'gtest_AllCombinationsVertexLoaderParamTest_dummy_' was declared 'extern' and 
> later 'static' [-fpermissive]
>  # define GTEST_ATTRIBUTE_UNUSED_ __attribute__ ((unused))
>  ^
> /usr/src/gtest/include/gtest/gtest-param-test.h:1421:54: note: in expansion 
> of macro 'GTEST_ATTRIBUTE_UNUSED_'
>static int gtest_##prefix##test_case_name##_dummy_ GTEST_ATTRIBUTE_UNUSED_ 
> = \
>   ^~~
> /<>/Source/UnitTests/VideoCommon/VertexLoaderTest.cpp:111:1: 
> note: in expansion of macro 'INSTANTIATE_TEST_CASE_P'
>  INSTANTIATE_TEST_CASE_P(
>  ^~~
> /<>/Source/UnitTests/VideoCommon/VertexLoaderTest.cpp:110:12: 
> note: previous declaration of 
> 'gtest_AllCombinationsVertexLoaderParamTest_dummy_'
>  extern int gtest_AllCombinationsVertexLoaderParamTest_dummy_;
> ^
> In file included from 
> /usr/src/gtest/include/gtest/internal/gtest-internal.h:40,
>  from /usr/src/gtest/include/gtest/gtest.h:59,
>  from 
> /<>/Source/UnitTests/VideoCommon/VertexLoaderTest.cpp:11:
> /usr/src/gtest/include/gtest/internal/gtest-port.h:891:57: error: 
> 'gtest_FormatsAndElementsVertexLoaderSpeedTest_dummy_' was declared 'extern' 
> and later 'static' [-fpermissive]
>  # define GTEST_ATTRIBUTE_UNUSED_ __attribute__ ((unused))
>  ^
> /usr/src/gtest/include/gtest/gtest-param-test.h:1421:54: note: in expansion 
> of macro 'GTEST_ATTRIBUTE_UNUSED_'
>static int gtest_##prefix##test_case_name##_dummy_ GTEST_ATTRIBUTE_UNUSED_ 
> = \
>   ^~~
> /<>/Source/UnitTests/VideoCommon/VertexLoaderTest.cpp:206:1: 
> note: in expansion of macro 'INSTANTIATE_TEST_CASE_P'
>  INSTANTIATE_TEST_CASE_P(
>  ^~~
> /<>/Source/UnitTests/VideoCommon/VertexLoaderTest.cpp:205:12: 
> note: previous declaration of 
> 'gtest_FormatsAndElementsVertexLoaderSpeedTest_dummy_'
>  extern int gtest_FormatsAndElementsVertexLoaderSpeedTest_dummy_;
> ^~~~
> make[5]: *** 
> [Source/UnitTests/VideoCommon/CMakeFiles/Test_VertexLoaderTest.dir/build.make:66:
>  
> Source/UnitTests/VideoCommon/CMakeFiles/Test_VertexLoaderTest.dir/VertexLoaderTest.cpp.o]
>  Error 1

Should be fixed by this upstream commit which I'll upload at some point:

https://github.com/dolphin-emu/dolphin/commit/ccf9ecbb03edbdd728738499dc5fae4d0631882a

James



signature.asc
Description: OpenPGP digital signature

Bug#891098: marked as done (python-gumbo: python-beautifulsoup is replaced with python-bs4)

[Debian Bug Tracking System]

Your message dated Thu, 04 Oct 2018 07:50:20 +
with message-id 
and subject line Bug#891098: fixed in gumbo-parser 0.10.1+dfsg-2.3
has caused the Debian Bug report #891098,
regarding python-gumbo: python-beautifulsoup is replaced with python-bs4
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.)


-- 
891098: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891098
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-gumbo
Version: 0.10.1+dfsg-2.1
Severity: important
Control: block 891087 by -1

beautifulsoup version 4 was replaced as a new package, bs4, which has
been in Debian for over 5 years now. beautfiulsoup (3.x) hasn't seen any
maintenance since then. It's high time to remove it from the archive.

Most code written against Beautiful Soup 3 will work against Beautiful
Soup 4 with one simple change. All you should have to do is change the
package name from BeautifulSoup to bs4, and depend on python-bs4 instead
of python-beautifulsoup.

There is some documentation on the migration here:
https://www.crummy.com/software/BeautifulSoup/bs4/doc/#porting-code-to-bs4

Thanks,

SR
--- End Message ---
--- Begin Message ---
Source: gumbo-parser
Source-Version: 0.10.1+dfsg-2.3

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

Debian distribution maintenance software
pp.
Sergei Golovan  (supplier of updated gumbo-parser package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 02 Oct 2018 07:50:58 +0300
Source: gumbo-parser
Binary: libgumbo-dev libgumbo1 python-gumbo python3-gumbo
Architecture: source amd64 all
Version: 0.10.1+dfsg-2.3
Distribution: unstable
Urgency: medium
Maintainer: Onur Aslan 
Changed-By: Sergei Golovan 
Description:
 libgumbo-dev - pure-C HTML5 parser development files
 libgumbo1  - pure-C HTML5 parser
 python-gumbo - pure-C HTML5 parser Python bindings
 python3-gumbo - pure-C HTML5 parser Python 3 bindings
Closes: 891098
Changes:
 gumbo-parser (0.10.1+dfsg-2.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Apply a patch by Stefano Rivera to port gumbo-parser to
 BeautifulSoup 4 (Closes: #891098)
Checksums-Sha1:
 3e6d06bedd5cb07a86b6b446372566b9862eb3f1 2200 gumbo-parser_0.10.1+dfsg-2.3.dsc
 a92f9588f78a1b52bd99a63b9d640c92264ed0e2 6540 
gumbo-parser_0.10.1+dfsg-2.3.debian.tar.xz
 ab06ad2f8c92530b00443c06e2c2ec873e3c502b 7849 
gumbo-parser_0.10.1+dfsg-2.3_amd64.buildinfo
 e8663324fea237db1599d29e6c287572c7a91aa2 133044 
libgumbo-dev_0.10.1+dfsg-2.3_amd64.deb
 0bec6601834c76045a2f20c7db84c534329d025b 175472 
libgumbo1-dbgsym_0.10.1+dfsg-2.3_amd64.deb
 e9ad780f717e7e5bc39b214a0074bf7f944dbd3c 105128 
libgumbo1_0.10.1+dfsg-2.3_amd64.deb
 6fc6939dbf0eecc7033c459c6770b4c5e8680f48 13596 
python-gumbo_0.10.1+dfsg-2.3_all.deb
 6038a40101eb47aef3f9c655f40b4690a018e5b4 13688 
python3-gumbo_0.10.1+dfsg-2.3_all.deb
Checksums-Sha256:
 c542362d448fd5c6da65a5f27ec1971fc91cc97bfcc0305486a3abf4af2173a1 2200 
gumbo-parser_0.10.1+dfsg-2.3.dsc
 36b44e9cde3b498fb635fc5d592bb3080aebef281175ab7c1fe68c2d3763210c 6540 
gumbo-parser_0.10.1+dfsg-2.3.debian.tar.xz
 eaf37e80d5c46e57f56aa4b540f7b0103a4161bfa69d5b43d4e154e313f3605a 7849 
gumbo-parser_0.10.1+dfsg-2.3_amd64.buildinfo
 7d6f592e16fe554a7944f16be28a310d787b288f6b8c9768f0d5d40f8080311e 133044 
libgumbo-dev_0.10.1+dfsg-2.3_amd64.deb
 44ce8a929e69fa842c85069e2e467ff189603995b92b567fd0cc49697a56b065 175472 
libgumbo1-dbgsym_0.10.1+dfsg-2.3_amd64.deb
 e58ac94458d935d46a3c819651c801f9c1f0eff9ccf2c05339c88923e520a432 105128 
libgumbo1_0.10.1+dfsg-2.3_amd64.deb
 88788fd1cbaea7881bd6e397c36875e99d03881816792f01f03c8f0907ae0bd8 13596 
python-gumbo_0.10.1+dfsg-2.3_all.deb
 0eca57323070b23cb5e0500338debbfaebafe7544cc7d804edef2857f0fcfe09 13688 
python3-gumbo_0.10.1+dfsg-2.3_all.deb
Files:
 4b4af0da2d834a7bfc8af0145f92a4ae 2200 libs optional 
gumbo-parser_0.10.1+dfsg-2.3.dsc
 b3bae92c18ff09631c55f37fbf1b5947 6540 libs optional 
gumbo-parser_0.10.1+dfsg-2.3.debian.tar.xz
 e9ba160f5ce05709f1c08b498470b204 7849 libs optional 
gumbo-parser_0.10.1+dfsg

Bug#908681: digikam, xsane are currently uninstaable

[Eric Valette]

apt-get install libsane1
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer 
required:
  enfuse libkf5calendarcore5abi1 libkf5mediawiki5 libkf5sane-data 
libpodofo0.9.5 libqtav1 libqtavwidgets1 xsane-common

Use 'apt autoremove' to remove them.
The following additional packages will be installed:
  libsane-common libsane-dev
The following packages will be REMOVED:
  digikam digikam-private-libs kipi-plugins kolourpaint kolourpaint4 
libkf5sane5 showfoto xsane

The following packages will be upgraded:
  libsane-common libsane-dev libsane1
3 upgraded, 0 newly installed, 8 to remove and 0 not upgraded.
Need to get 4902 kB of archives.
After this operation, 49.3 MB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.

-- eric

Bug#909659: marked as done (eztrace: armhf build hangs on arm64 machine)

[Debian Bug Tracking System]

Your message dated Thu, 04 Oct 2018 07:20:43 +
with message-id 
and subject line Bug#909659: fixed in eztrace 1.1-8-2
has caused the Debian Bug report #909659,
regarding eztrace: armhf build hangs on arm64 machine
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.)


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

Hi,

The armhf build hangs when building on an arm64 system:

make  check-TESTS
make[4]: Entering directory '/<>/build-mpich/test/automake'
make[5]: Entering directory '/<>/build-mpich/test/automake'
E: Build killed with signal TERM after 150 minutes of inactivity

See the pattern in
https://buildd.debian.org/status/logs.php?pkg=eztrace&arch=armhf

There should be an arm64 porterbox with armhf chroots to debug this.

Cheers,
Emilio

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

Kernel: Linux 4.17.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: eztrace
Source-Version: 1.1-8-2

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

Debian distribution maintenance software
pp.
Samuel Thibault  (supplier of updated eztrace package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 28 Sep 2018 11:08:02 +0200
Source: eztrace
Binary: eztrace libeztrace-dev libeztrace0
Architecture: source
Version: 1.1-8-2
Distribution: unstable
Urgency: medium
Maintainer: Samuel Thibault 
Changed-By: Samuel Thibault 
Description:
 eztrace- Automatic execution trace generation for HPC - tools
 libeztrace-dev - Automatic execution trace generation for HPC - development 
files
 libeztrace0 - Automatic execution trace generation for HPC - development files
Closes: 909659
Changes:
 eztrace (1.1-8-2) unstable; urgency=medium
 .
   * debian/patches/ptrace-arm: Disable ptrace on armhf, it seems to hang there
 (Closes: Bug#909659).
Checksums-Sha1:
 062164f59740027c083a04aeb8d0a797b535c6f6 2297 eztrace_1.1-8-2.dsc
 c0dcb3f1bfa87bb0a26f168a026c637102f93395 9396 eztrace_1.1-8-2.debian.tar.xz
Checksums-Sha256:
 9863373a245c0e69183a60d8d2cdabc822b0aab25a4a49932752a963c374c506 2297 
eztrace_1.1-8-2.dsc
 584bbd4de6ac32ff6ea0df595187c6f5ce99fe03c192a12266d0342ee73d11a1 9396 
eztrace_1.1-8-2.debian.tar.xz
Files:
 2393b55e95392a37e34de990b23aa8cb 2297 devel optional eztrace_1.1-8-2.dsc
 f2098dcfd5903169359060160764e1d9 9396 devel optional 
eztrace_1.1-8-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOjpdRkZg6GdhDKQnmWhJwc9WBHgFAlu1uOEACgkQmWhJwc9W
BHjbPQ/9G32qUUwTYd88Tg2noWM7MrYsCgt7KGwb/dNegbRYUBVd+r97Fp3Up5Qv
2OgVykYgyfWUauX27nWhWTi6qYvDqi6qecY8vZpmBKs4xtG1PYIZI/JC9z5+71ef
cdFCTDgmUmhMPiT+hBt8U8QqR8+jOIgHjU0XspiKWnD+8ADNcfmEdrEp+fcaqjmo
hSVx2UIHI4S58/gLFw7cecj0CbDwvwCXMOiPEX0TKe4S1htyC6lc8Cg5W6aw7TcC
blX/6s8+vQaf/ihV78foTOlb51AhDeMHfarlmdbIfmy9H5amKIH0sNeYxzV7TI0s
cdnEjX2aOuYnx6isp7pVN+tu28oBY80Q1MOLp8L1013jJ8egP5UNu7g+i4lHUHXC
smU3yCLUjTV7vBCnm8gY3J6Cm8RbdJmFUGrk+o+V02GkxMHdWtlAa//WvfzJStqx
FpIiV0zZgwpzbvBUNYYz9TkUKJidEMkfRtD2deDjSusEq4TwKWDPe9Qode8iHQ+/
2s8HLwoKehITW8llpbxg6lrDHh6FjJyBw2TVUNAKlDDhOYwJvW08fopzYFzH17Ce
K3dBvRIEhXTbfedF9EdCDFQDIbWVvDoOpYq4AFAuKnaiXYCnNCD4I7OUOk3zC/cm
rEeV2ISNcprtdgBjxx/RHiYGeXXPmP/6Rq/26panHZaJlzLMUTA=
=Mpls
-END PGP SIGNATURE End Message ---

Bug#909602: [Pkg-mailman-hackers] Bug#909602: mailmanclient causes python3-mailman-hyperkitty and mailman3-web to fail to install in buster

[Paul Gevers]

Hi Pierre,

On 04-10-18 00:47, Pierre-Elliott Bécue wrote:
> Would you prefer if we push a fix or if we wait for mailman-hyperkitty
> migration?

I don't think my preference matters here. Do what you think is best for
the mailman suite. I'll just quote [1] a statement from the release team
on this matter: "Therefore, we highly recommend that people work on
solving the underlying issue rather than wait it out."

Paul

[1] https://lists.debian.org/debian-devel-announce/2018/09/msg4.html



signature.asc
Description: OpenPGP digital signature