Bug#803526: marked as done (scilab-minimal-bin: built with old TCL/TK on purpose?)

[Debian Bug Tracking System]

Your message dated Fri, 04 May 2018 05:05:48 +
with message-id 
and subject line Bug#803526: fixed in scilab 6.0.1-2
has caused the Debian Bug report #803526,
regarding scilab-minimal-bin: built with old TCL/TK on purpose?
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.)


-- 
803526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803526
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: scilab-minimal-bin
Version: 5.5.2-2
Severity: minor


Hey.

scilab 5.5.2-2 seems to be built with TCL/TK 8.5, instead of 8.6 as
the previous version.

Was that on purpose?

Cheers,
Chris.
--- End Message ---
--- Begin Message ---
Source: scilab
Source-Version: 6.0.1-2

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

Debian distribution maintenance software
pp.
Julien Puydt  (supplier of updated scilab 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, 03 May 2018 09:06:16 +0200
Source: scilab
Binary: scilab-cli scilab scilab-data scilab-include scilab-minimal-bin 
scilab-full-bin scilab-doc scilab-doc-fr scilab-doc-pt-br scilab-doc-ja 
scilab-test
Architecture: source all amd64
Version: 6.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Julien Puydt 
Description:
 scilab - Scientific software package for numerical computations
 scilab-cli - Scientific software package - Command Line Interpreter
 scilab-data - Scientific software package for numerical computations (data file
 scilab-doc - Scientific software package (English documentations)
 scilab-doc-fr - Scientific software package (French documentation)
 scilab-doc-ja - Scientific software package (Japanese documentation)
 scilab-doc-pt-br - Scientific software package (Brazilian Portuguese 
documentation)
 scilab-full-bin - Scientific software package for numerical computations (all 
binar
 scilab-include - Scientific software package for numerical computations 
(include f
 scilab-minimal-bin - Scientific software package for numerical computations 
(minimal b
 scilab-test - Scientific software package for numerical computations (test file
Closes: 803526 875790
Changes:
 scilab (6.0.1-2) unstable; urgency=medium
 .
   [ Emmanuel Bourg ]
   * Fixed the build failure with Java 9 (Closes: #875790)
 .
   [ Julien Puydt ]
   * Depend on unversioned tcl/tk (Closes: #803526)
   * Force use of java 8 since later versions aren't supported (Closes: #875790)
Checksums-Sha1:
 1f446de3cedf02fd56e250d0da64e10ae6623d69 3723 scilab_6.0.1-2.dsc
 54fdd3bc308aeaf63245ce7e07980da2b03cb422 70660 scilab_6.0.1-2.debian.tar.xz
 bdc97a6266c4adcb61df55842cec5f393c652f3c 501300 scilab-cli_6.0.1-2_all.deb
 aaeb6961c46ef7c1b9b4c1c9ad6b33c51e22b3e8 37490120 scilab-data_6.0.1-2_all.deb
 f00651e4cef5a298c3a1f06288ac303c811766a7 7489180 scilab-doc-fr_6.0.1-2_all.deb
 2abf460e313ccde9f06c5949a218f9f6d7842111 7697756 scilab-doc-ja_6.0.1-2_all.deb
 c021ad045b811189cdee7ebf63abefc401e61bb6 7337276 
scilab-doc-pt-br_6.0.1-2_all.deb
 77d68f1a6f3b36acb8567e761aaf80624f9ecbca 8774648 scilab-doc_6.0.1-2_all.deb
 aa129640c9996a96829be82d6ac57fb37521faf3 19833748 
scilab-full-bin-dbgsym_6.0.1-2_amd64.deb
 59614ca6481c63a5cce1adf8f7554e8cc0caa7d6 1985996 
scilab-full-bin_6.0.1-2_amd64.deb
 aa28d28eb5fc571847b589f748df26781300a4c8 228500 
scilab-include_6.0.1-2_amd64.deb
 137b973595758cb74d9a6c17b115648993ce19c9 75670184 
scilab-minimal-bin-dbgsym_6.0.1-2_amd64.deb
 71bf2224e21ad090e2b7bb015456b5997f87f58c 4039096 
scilab-minimal-bin_6.0.1-2_amd64.deb
 bb3afef732a793e1024c5e26675b7c219a59520f 12309876 scilab-test_6.0.1-2_all.deb
 c7d07c8257fea2683dd3b9195f444e87706b3b64 75484 scilab_6.0.1-2_all.deb
 6913965d5fe4be36f093ca2277be382dfb5550af 21714 scilab_6.0.1-2_amd64.buildinfo
Checksums-Sha256:
 05f72d30192ffbb47dc092dc2867549aaf11cf1162365db18b66ec9f6aa40834 3723 
scilab_6.0.1-2.dsc
 

Bug#875790: marked as done (FTBFS with Java 9: configure fails to detect Java)

[Debian Bug Tracking System]

Your message dated Fri, 04 May 2018 05:05:48 +
with message-id 
and subject line Bug#875790: fixed in scilab 6.0.1-2
has caused the Debian Bug report #875790,
regarding FTBFS with Java 9: configure fails to detect Java
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.)


-- 
875790: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875790
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scilab
Version: 5.5.2-5
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.
The wiki has some common problems and their solutions:
https://wiki.debian.org/Java/Java9Pitfalls

The "/jre" part of the install path is gone. Also, many of the libraries
have moved. I'm not sure why configure cares so much about the actual
locations.

Build log:

checking type of jvm... jdk
checking java API version... 1.8
Using the following JNI include flags 
-I/usr/lib/jvm/java-9-openjdk-amd64/include 
-I/usr/lib/jvm/java-9-openjdk-amd64/include/linux
checking if jni.h can be included... yes
Looking for JNI libs with x86_64 as machine hardware name
Looking for /usr/lib/jvm/java-9-openjdk-amd64/jre/lib/x86_64/libjava.so
Looking for /usr/lib/jvm/java-9-openjdk-amd64/jre/lib/amd64/libjava.so
Looking for /usr/lib/jvm/java-9-openjdk-amd64/jre/lib/i386/client/libjvm.so
Looking for /usr/lib/jvm/java-9-openjdk-amd64/jre/bin/classic/libjvm.so
Looking for /usr/lib/jvm/java-9-openjdk-amd64/lib/jvm.lib
Looking for /usr/lib/jvm/java-9-openjdk-amd64/jre/lib/mipsel/libjava.so
configure: error: Could not detect the location of the Java
shared library. You will need to update java.m4
to add support for this JVM configuration.
make: *** [debian/stamp-autotools] Error 1
/usr/share/cdbs/1/class/autotools.mk:44: recipe for target 
'debian/stamp-autotools' failed
dpkg-buildpackage: error: debian/rules build gave error exit status 2




Cheers,
Chris.
--- End Message ---
--- Begin Message ---
Source: scilab
Source-Version: 6.0.1-2

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

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

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

Debian distribution maintenance software
pp.
Julien Puydt  (supplier of updated scilab 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, 03 May 2018 09:06:16 +0200
Source: scilab
Binary: scilab-cli scilab scilab-data scilab-include scilab-minimal-bin 
scilab-full-bin scilab-doc scilab-doc-fr scilab-doc-pt-br scilab-doc-ja 
scilab-test
Architecture: source all amd64
Version: 6.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Julien Puydt 
Description:
 scilab - Scientific software package for numerical computations
 scilab-cli - Scientific software package - Command Line Interpreter
 scilab-data - Scientific software package for numerical computations (data file
 scilab-doc - Scientific software package (English documentations)
 scilab-doc-fr - Scientific software package (French documentation)
 scilab-doc-ja - Scientific software package (Japanese documentation)
 scilab-doc-pt-br - Scientific software package (Brazilian Portuguese 
documentation)
 scilab-full-bin - Scientific software package for numerical computations (all 
binar
 scilab-include - Scientific software package for numerical computations 
(include f
 scilab-minimal-bin - Scientific software package for numerical computations 
(minimal b
 scilab-test - Scientific software package for numerical computations (test file
Closes: 803526 875790
Changes:
 scilab (6.0.1-2) unstable; urgency=medium
 .
   [ Emmanuel Bourg ]
   * Fixed the build failure with Java 9 (Closes: #875790)
 .
   [ Julien Puydt ]
   * Depend on unversioned tcl/tk (Closes: #803526)
   * Force use of java 8 since later versions aren't supported (Closes: #875790)
Checksums-Sha1:
 

Bug#825647: marked as done (ocsinventory-server: prompting due to modified conffiles which were not modified by the user: /etc/apache2/conf-available/ocsinventory-server.conf)

[Debian Bug Tracking System]

Your message dated Fri, 4 May 2018 06:54:29 +0200
with message-id <2faf7c2d-f3f2-acbb-df4e-3e876c327...@free.fr>
and subject line Fixed
has caused the Debian Bug report #825647,
regarding ocsinventory-server: prompting due to modified conffiles which were 
not modified by the user: /etc/apache2/conf-available/ocsinventory-server.conf
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.)


-- 
825647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825647
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ocsinventory-server
Version: 2.1.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed the piuparts
upgrade test because dpkg detected a conffile as being modified and then
prompted the user for an action. As there is no user input, this fails.
But this is not the real problem, the real problem is that this prompt
shows up in the first place, as there was nobody modifying this conffile
at all, the package has just been installed and upgraded...

This is a violation of policy 10.7.3, see
https://www.debian.org/doc/debian-policy/ch-files.html#s10.7.3,
which says "[These scripts handling conffiles] must not ask unnecessary
questions (particularly during upgrades), and must otherwise be good
citizens."

https://wiki.debian.org/DpkgConffileHandling should help with figuring
out how to do this properly.

In https://lists.debian.org/debian-devel/2009/08/msg00675.html and
followups it has been agreed that these bugs are to be filed with
severity serious.

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

  Setting up ocsinventory-server (2.1.2-1) ...
  
  Configuration file '/etc/apache2/conf-available/ocsinventory-server.conf'
   ==> Modified (by you or by a script) since installation.
   ==> Package distributor has shipped an updated version.
 What would you like to do about it ?  Your options are:
  Y or I  : install the package maintainer's version
  N or O  : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
   The default action is to keep your current version.
  *** ocsinventory-server.conf (Y/I/N/O/D/Z) [default=N] ? dpkg: error 
processing package ocsinventory-server (--configure):
   end of file on stdin at conffile prompt

This was observed on a squeeze => wheezy => jessie => stretch
upgrade test. The installation and upgrades up to jessie worked
fine, but the final upgrade to stretch showed this prompt.

cheers,

Andreas


ocsinventory-server_2.1.2-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
fixed 825647 2.4.1+dfsg-1

stop

postinst script no more modify /etc/ocsinventory/ocsinventory.conf--- End Message ---

Processed: Fixed

[Debian Bug Tracking System]

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

> fixed 825647 2.4.1+dfsg-1
Bug #825647 [ocsinventory-server] ocsinventory-server: prompting due to 
modified conffiles which were not modified by the user: 
/etc/apache2/conf-available/ocsinventory-server.conf
There is no source info for the package 'ocsinventory-server' at version 
'2.4.1+dfsg-1' with architecture ''
Unable to make a source version for version '2.4.1+dfsg-1'
Marked as fixed in versions 2.4.1+dfsg-1.
> stop
Stopping processing here.

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

Bug#825647: Unable to reproduce

[Xavier]

Hi all,

I've packaged OCSinventory-Server 2.4.1. I'm unable to reproduce this
bug. COuld you give me the script of this scenario ?

Regards,
Xavier

Bug#897671: u-boot does not work on sheevaplug

[Markus Krebs]

Package: u-boot
Version: 2018.03+dfsg1-2
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

flashing the newest u-boot.kwb on sheevaplug makes the system unbootable. I 
tried flashing out of Debian as well as from u-boot - no difference. One must 
flash a different u-boot via OpenOCD to bring the system back to life again.
The u-boot.kwb provided at https://forum.doozan.com/read.php?3,12381 works.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: armel (armv5tel)

Kernel: Linux 4.15.0-3-marvell
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- no debconf information

Markus

Processed: found 897590 in 4.16.5-1

[Debian Bug Tracking System]

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

> found 897590 4.16.5-1
Bug #897590 [src:linux] linux-image-4.9.0-6-armmp: Missing CONFIG_MFD_TPS65217 
may cause hardware damage
Marked as found in versions linux/4.16.5-1.
> thanks
Stopping processing here.

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

Bug#895248: pygtk: Intent to Adopt

[Jeremy Bicha]

On Sun, Apr 8, 2018 at 3:19 PM, Adrian Bunk  wrote:
> pygtk still has many (including popular) reverse dependencies.
> Python 2 will be removed in bullseye, and there is no clear
> reason why pygtk has to be removed one release earlier.

Thank you for your interest in pygtk. I apologize for the late response.

Based on the number of popular packages using pygtk, it doesn't seem
practical to completely remove pygtk before the Buster release. It
sounds like we are agreed that it should be removed for Bullseye
(probably early in fact). Therefore, I think the Debian GNOME team
will continue its (very) minimal maintenance for the package. You're
welcome to help work on the package if you think there is anything
that needs doing.

Thanks,
Jeremy Bicha

Bug#888412: marked as done (sphinx-gallery: FTBFS without network access)

[Debian Bug Tracking System]

Your message dated Fri, 04 May 2018 01:04:41 +
with message-id 
and subject line Bug#888412: fixed in sphinx-gallery 0.1.13-2
has caused the Debian Bug report #888412,
regarding sphinx-gallery: FTBFS without network access
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.)


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

Hi Maintainer

sphinx-gallery FTBFS without network access, as can be seen in the
following build log excerpt from reproducible builds [1]:


Unexpected failing examples:
/build/sphinx-gallery-0.1.13/tutorials/seaborn/plot_seaborn_notebook.py
failed leaving traceback:
Traceback (most recent call last):
  File 
"/build/sphinx-gallery-0.1.13/tutorials/seaborn/plot_seaborn_notebook.py",
line 31, in 
tips = sns.load_dataset("tips", cache=False)
  File "/usr/lib/python2.7/dist-packages/seaborn/utils.py", line 397,
in load_dataset
df = pd.read_csv(full_path, **kws)
  File "/usr/lib/python2.7/dist-packages/pandas/io/parsers.py", line
655, in parser_f
return _read(filepath_or_buffer, kwds)
  File "/usr/lib/python2.7/dist-packages/pandas/io/parsers.py", line
392, in _read
filepath_or_buffer, encoding, compression)
  File "/usr/lib/python2.7/dist-packages/pandas/io/common.py", line
186, in get_filepath_or_buffer
req = _urlopen(url)
  File "/usr/lib/python2.7/urllib2.py", line 154, in urlopen
return opener.open(url, data, timeout)
  File "/usr/lib/python2.7/urllib2.py", line 429, in open
response = self._open(req, data)
  File "/usr/lib/python2.7/urllib2.py", line 447, in _open
'_open', req)
  File "/usr/lib/python2.7/urllib2.py", line 407, in _call_chain
result = func(*args)
  File "/usr/lib/python2.7/urllib2.py", line 1241, in https_open
context=self._context)
  File "/usr/lib/python2.7/urllib2.py", line 1198, in do_open
raise URLError(err)
URLError: 


Regards
Graham


[1]
https://tests.reproducible-builds.org/debian/rb-pkg/sphinx-gallery.html
--- End Message ---
--- Begin Message ---
Source: sphinx-gallery
Source-Version: 0.1.13-2

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated sphinx-gallery 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, 03 May 2018 19:55:46 -0400
Source: sphinx-gallery
Binary: python-sphinx-gallery python3-sphinx-gallery python-sphinx-gallery-doc
Architecture: source all
Version: 0.1.13-2
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi 
Changed-By: Sandro Tosi 
Description:
 python-sphinx-gallery - extension that builds an HTML gallery of examples from 
Python scr
 python-sphinx-gallery-doc - extension that builds an HTML gallery of examples 
from Python scr
 python3-sphinx-gallery - extension that builds an HTML gallery of examples 
from Python scr
Closes: 888412 889284 897497
Changes:
 sphinx-gallery (0.1.13-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
 .
   [ Sandro Tosi ]
   * debian/control
 - bump Standards-Version to 4.1.4 (no changes needed)
 - add matplotlib, pil, sphinx, seaborn, mayavi2 to depends/suggests;
   Closes: #889284
   * debian/patches/0002-skip-seaborn-tests-require-network-access.patch
 - skip seaborn tests, require network access; patch taken from Ubuntu;
   Closes: #888412
   * 
debian/patches/0003-use-facecolor-instead-of-axisbg-when-calling-plt.axe.patch
 - fix example failing with recent matplotlib; Closes: #897497
   * 
debian/patches/0004-Fix-compatibility-of-SphinxDocLinkResolver-with-Sphi.patch
 - fix compatibility with Sphinx 1.7, taked from upstream repo
Checksums-Sha1:
 418789809cc91c7f192783263a43a1fce23c 2414 sphinx-gallery_0.1.13-2.dsc
 e917555094a91e55a054f528024b937a5c1c1eb6 4408 

Bug#897497: marked as done (sphinx-gallery: FTBFS: SyntaxError: invalid syntax)

[Debian Bug Tracking System]

Your message dated Fri, 04 May 2018 01:04:41 +
with message-id 
and subject line Bug#897497: fixed in sphinx-gallery 0.1.13-2
has caused the Debian Bug report #897497,
regarding sphinx-gallery: FTBFS: SyntaxError: invalid syntax
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.)


-- 
897497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897497
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sphinx-gallery
Version: 0.1.13-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20180502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>/doc'
> sphinx-build -b html -d _build/doctrees   . _build/html
> Running Sphinx v1.7.4
> making output directory...
> loading pickled environment... not yet created
> [autosummary] generating autosummary for: advanced_configuration.rst, 
> changes.rst, faq.rst, getting_started.rst, index.rst, reference.rst, 
> syntax.rst, utils.rst
> [autosummary] generating autosummary for: 
> /<>/doc/gen_modules/sphinx_gallery.backreferences.rst, 
> /<>/doc/gen_modules/sphinx_gallery.docs_resolv.rst, 
> /<>/doc/gen_modules/sphinx_gallery.downloads.rst, 
> /<>/doc/gen_modules/sphinx_gallery.gen_gallery.rst, 
> /<>/doc/gen_modules/sphinx_gallery.gen_rst.rst, 
> /<>/doc/gen_modules/sphinx_gallery.notebook.rst, 
> /<>/doc/gen_modules/sphinx_gallery.py_source_parser.rst, 
> /<>/doc/gen_modules/sphinx_gallery.sorting.rst
> loading intersphinx inventory from 
> http://www.sphinx-doc.org/en/stable/objects.inv...
> loading intersphinx inventory from https://docs.python.org/2/objects.inv...
> loading intersphinx inventory from 
> http://docs.enthought.com/mayavi/mayavi/objects.inv...
> loading intersphinx inventory from https://matplotlib.org/objects.inv...
> loading intersphinx inventory from 
> https://docs.scipy.org/doc/scipy/reference/objects.inv...
> loading intersphinx inventory from 
> https://docs.scipy.org/doc/numpy/objects.inv...
> loading intersphinx inventory from 
> http://scikit-learn.org/stable/objects.inv...
> generating gallery...
> generating gallery for auto_examples... [ 12%] plot_sys_argv.py
> generating gallery for auto_examples... [ 25%] plot_exp.py
> generating gallery for auto_examples... [ 37%] plot_colors.py
> generating gallery for auto_examples... [ 50%] plot_quantum.py
> generating gallery for auto_examples... [ 62%] plot_seaborn.py
> /usr/lib/python2.7/dist-packages/seaborn/timeseries.py:183: UserWarning: The 
> tsplot function is deprecated and will be removed or replaced (in a 
> substantially altered version) in a future release.
>   warnings.warn(msg, UserWarning)
> generating gallery for auto_examples... [ 75%] plot_choose_thumbnail.py
> generating gallery for auto_examples... [ 87%] plot_function_identifier.py
> generating gallery for auto_examples... [100%] plot_gallery_version.py
> 
> generating gallery for auto_examples/sin_func... [ 50%] plot_sin.py
> generating gallery for auto_examples/sin_func... [100%] 
> plot_sin_black_background.py
> WARNING: /<>/examples/sin_func/plot_sin_black_background.py 
> failed to execute correctly: Traceback (most recent call last):
>   File "/<>/examples/sin_func/plot_sin_black_background.py", 
> line 20, in 
> axes = plt.axes((0.1, 0.1, 0.8, 0.8), axisbg=bg_color)
>   File "/usr/lib/python2.7/dist-packages/matplotlib/pyplot.py", line 938, in 
> axes
> return gcf().add_axes(rect, **kwargs)
>   File "/usr/lib/python2.7/dist-packages/matplotlib/figure.py", line 1136, in 
> add_axes
> a = projection_class(self, rect, **kwargs)
>   File "/usr/lib/python2.7/dist-packages/matplotlib/axes/_base.py", line 539, 
> in __init__
> self.update(kwargs)
>   File "/usr/lib/python2.7/dist-packages/matplotlib/artist.py", line 888, in 
> update
> for k, v in props.items()]
>   File "/usr/lib/python2.7/dist-packages/matplotlib/artist.py", line 881, in 
> _update_property
> raise AttributeError('Unknown property %s' % k)
> AttributeError: Unknown property axisbg
> 
> 
> generating gallery for auto_examples/no_output... [ 25%] plot_strings.py
> generating gallery for auto_examples/no_output... [ 50%] just_code.py
> generating gallery for auto_examples/no_output... [ 75%] plot_raise.py
> WARNING: /<>/examples/no_output/plot_raise.py failed to execute 
> correctly: Traceback (most recent call last):
>   File "/<>/examples/no_output/plot_raise.py", line 24, in 
> 
> iae
> NameError: name 

Bug#897497: Bug #897497 in sphinx-gallery marked as pending

[morph]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/modules/sphinx-gallery/commit/f7d521ab3f09a6db9bc1424fb3ffb46138757d00


fix example failing with recent matplotlib; Closes: #897497



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/897497

Bug#888412: Bug #888412 in sphinx-gallery marked as pending

[morph]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/modules/sphinx-gallery/commit/4e400188855f7ea1d9b636b56befa2f0413cf03a


skip seaborn tests, require network access; patch taken from Ubuntu; Closes: 
#888412



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/888412

Processed: Bug #888412 in sphinx-gallery marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #888412 [src:sphinx-gallery] sphinx-gallery: FTBFS without network access
Added tag(s) pending.

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

Processed: Bug #897497 in sphinx-gallery marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #897497 [src:sphinx-gallery] sphinx-gallery: FTBFS: SyntaxError: invalid 
syntax
Added tag(s) pending.

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

Processed: bug 897497 is forwarded to https://github.com/sphinx-gallery/sphinx-gallery/issues/373

[Debian Bug Tracking System]

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

> forwarded 897497 https://github.com/sphinx-gallery/sphinx-gallery/issues/373
Bug #897497 [src:sphinx-gallery] sphinx-gallery: FTBFS: SyntaxError: invalid 
syntax
Set Bug forwarded-to-address to 
'https://github.com/sphinx-gallery/sphinx-gallery/issues/373'.
> thanks
Stopping processing here.

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

Processed: Re: access-modifier-checker: FTBFS: Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libcommons-lang3-java
Bug #897525 [src:access-modifier-checker] access-modifier-checker: FTBFS: 
Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar
Bug reassigned from package 'src:access-modifier-checker' to 
'libcommons-lang3-java'.
No longer marked as found in versions access-modifier-checker/1.12-1.
Ignoring request to alter fixed versions of bug #897525 to the same values 
previously set
> affects -1 access-modifier-checker
Bug #897525 [libcommons-lang3-java] access-modifier-checker: FTBFS: Failed to 
execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar
Added indication that 897525 affects access-modifier-checker

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

Bug#897525: access-modifier-checker: FTBFS: Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar

[Emmanuel Bourg]

Control: reassign -1 libcommons-lang3-java
Control: affects -1 access-modifier-checker

This is actually a Java 10 incompatibility in libcommons-lang3-java.
It's fixed in the version 3.7.

Bug#896740: marked as done (rows FTBFS with dh-python >= 3.20180313)

[Debian Bug Tracking System]

Your message dated Thu, 03 May 2018 23:34:58 +
with message-id 
and subject line Bug#896740: fixed in rows 0.3.1-3
has caused the Debian Bug report #896740,
regarding rows FTBFS with dh-python >= 3.20180313
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.)


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

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

...
   dh_auto_test -O--buildsystem=pybuild
I: pybuild pybuild:267: cp -r ./tests .pybuild/pythonX.Y_2.7/build
cp: cannot create directory '.pybuild/pythonX.Y_2.7/build': No such file or 
directory
E: pybuild pybuild:336: test: plugin distutils failed with: exit code=1: cp -r 
./tests .pybuild/pythonX.Y_2.7/build
dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 returned 
exit code 13
make: *** [debian/rules:12: build] Error 25
--- End Message ---
--- Begin Message ---
Source: rows
Source-Version: 0.3.1-3

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

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

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

Debian distribution maintenance software
pp.
Paulo Roberto Alves de Oliveira (aka kretcheu)  (supplier 
of updated rows 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, 03 May 2018 19:33:00 -0300
Source: rows
Binary: rows python-rows
Architecture: source all
Version: 0.3.1-3
Distribution: unstable
Urgency: medium
Maintainer: Paulo Roberto Alves de Oliveira (aka kretcheu) 
Changed-By: Paulo Roberto Alves de Oliveira (aka kretcheu) 
Description:
 python-rows - library to tabular data, no matter the format
 rows   - common, beautiful interface to tabular data, no matter the format
Closes: 896740
Changes:
 rows (0.3.1-3) unstable; urgency=medium
 .
   * debian/control:
   - Bumped Standards-Version to 4.1.4.
   - Bumped debhelper compatibility to 11.
   * debian/copyright
   - Updated upstream and packaging years.
   * debian/rules:
   - Changed PYBUILD variables to solve FTBFS error on new version
 of dh-python. (Closes:#896740).
   * debian/python-rows.examples:
   - Changed to include examples files.
   * debian/rows.examples:
   - Changed to include examples files.
Checksums-Sha1:
 f3bd9435fc71e419b3616248e1c148c64bf9fc44 2062 rows_0.3.1-3.dsc
 a2db8c16f7968f2cf00ad21ecb235e6061f005e8 8568 rows_0.3.1-3.debian.tar.xz
 465d47a739bbdfe896ddeaea4d41a3a0acfdb7a4 104420 python-rows_0.3.1-3_all.deb
 31948184ceae128b9babf6aba01ea35706801159 83652 rows_0.3.1-3_all.deb
 1768b1b148c676d7811576a1ac89f33b9589a34b 8693 rows_0.3.1-3_amd64.buildinfo
Checksums-Sha256:
 3e47e1d88718a5dc07c0374f0b6d8c4d4641106b6a5332b06e39cbcfc8ac8160 2062 
rows_0.3.1-3.dsc
 08aaf7375474f141a494d61677705734db89f39893543eb274015a30505485dc 8568 
rows_0.3.1-3.debian.tar.xz
 7d1807060c59047d116f819ee7713df57a3bfc5f99041774db2367a640612f97 104420 
python-rows_0.3.1-3_all.deb
 a6c42e39a032838f9104f121182832ff6f59498facc90fecec22602f15830d3f 83652 
rows_0.3.1-3_all.deb
 c90944f9267013b3bb5f4111680e96b6d5c371f2ef8442019ad76c8fbbcb1567 8693 
rows_0.3.1-3_amd64.buildinfo
Files:
 8d532bbf307c68ca411f49ea500367b6 2062 utils optional rows_0.3.1-3.dsc
 9e955f717ed5294331fd49cd07d1a547 8568 utils optional rows_0.3.1-3.debian.tar.xz
 6c0128025b4b2d8a1da3948a4dbcd524 104420 python optional 
python-rows_0.3.1-3_all.deb
 b6ae670e0f232a0bfcf087e71e8ca1ea 83652 utils optional rows_0.3.1-3_all.deb
 fe312047311fa57ec4a1bd77b0c1fccc 8693 utils optional 
rows_0.3.1-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEXjotitpi0kBiLshCOfF6X1rvvnMFAlrrlnMACgkQOfF6X1rv
vnMHFw/+PkOHjFzGwzE4xrcvveewT/hvt1yIPcImKpfOqFIqZpkV4DKX8JMS0bc3
QRwwD/9LEnRupAtQIu1sJ9KfZwtGLxFvV56HjZLH/twxvKyyJ5hygtXV7v5wYkdX
RUdnvU5wXFXFovDA0s4+eQSSZ1xFUYpBSllWWVOFs6vGNLgnZ87M9lX0ahXzaZiW
cCZWRpBWw5ohiG+g8aI+9wybw6qrRdHuSkh/6xgGuNH0FHAfpCBSPP3sRFUxOrjQ

Bug#897664: ruby-rjb: FTBFS: make[2]: javah: Command not found

[Chris Lamb]

Source: ruby-rjb
Version: 1.5.5-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

ruby-rjb fails to build from source in unstable/amd64:

  […]

   dpkg-buildpackage -rfakeroot -us -uc -ui -b
  dpkg-buildpackage: info: source package ruby-rjb
  dpkg-buildpackage: info: source version 1.5.5-2
  dpkg-buildpackage: info: source distribution unstable
  dpkg-buildpackage: info: source changed by Chris Lamb 
   dpkg-source --before-build ruby-rjb-1.5.5
  dpkg-buildpackage: info: host architecture amd64
   fakeroot debian/rules clean
  dh clean --buildsystem=ruby --with ruby
 dh_auto_clean -O--buildsystem=ruby
dh_ruby --clean
 dh_ruby --clean
 debian/rules override_dh_clean
  make[1]: Entering directory '«BUILDDIR»'
  dh_clean -O--buildsystem=ruby
  rm -rf test/jp test/jartest test/jartest2
  rm -f rjb-global.rake rjb.gemspec
  make[1]: Leaving directory '«BUILDDIR»'
   debian/rules build
  dh build --buildsystem=ruby --with ruby
 dh_update_autotools_config -O--buildsystem=ruby
 dh_autoreconf -O--buildsystem=ruby
 dh_auto_configure -O--buildsystem=ruby
dh_ruby --configure
 debian/rules override_dh_auto_build
  make[1]: Entering directory '«BUILDDIR»'
  mkdir -p $(dirname test/jp/co/infoseek/hp/arton/rjb/Test.class)
  LC_ALL=C.UTF-8 javac -classpath test -d test test/Test.java
  Note: test/Test.java uses or overrides a deprecated API.
  Note: Recompile with -Xlint:deprecation for details.
  mkdir -p $(dirname test/jp/co/infoseek/hp/arton/rjb/IBase.class)
  LC_ALL=C.UTF-8 javac -classpath test -d test test/IBase.java
  mkdir -p $(dirname test/jp/co/infoseek/hp/arton/rjb/Base.class)
  LC_ALL=C.UTF-8 javac -classpath test -d test test/Base.java
  mkdir -p $(dirname test/jp/co/infoseek/hp/arton/rjb/ExtBase.class)
  LC_ALL=C.UTF-8 javac -classpath test -d test test/ExtBase.java
  mkdir -p $(dirname test/jp/co/infoseek/hp/arton/rjb/Two.class)
  LC_ALL=C.UTF-8 javac -classpath test -d test test/Two.java
  mkdir -p $(dirname test/jp/co/infoseek/hp/arton/rjb/TwoCaller.class)
  LC_ALL=C.UTF-8 javac -classpath test -d test test/TwoCaller.java
  mkdir -p $(dirname test/jp/co/infoseek/hp/arton/rjb/CallbackTest.class)
  LC_ALL=C.UTF-8 javac -classpath test -d test test/CallbackTest.java
  mkdir -p test/jartest
  LC_ALL=C.UTF-8 javac -d test/jartest test/JarTest.java
  jar -cvf test/jartest.jar -C test/jartest 
jp/co/infoseek/hp/arton/rjb/JarTest.class
  added manifest
  adding: jp/co/infoseek/hp/arton/rjb/JarTest.class(in = 734) (out= 
414)(deflated 43%)
  mkdir -p test/jartest2
  LC_ALL=C.UTF-8 javac -classpath test/jartest -d test/jartest2 
test/JarTest2.java
  jar -cvf test/jartest2.jar -C test/jartest2 
jp/co/infoseek/hp/arton/rjb/JarTest2.class
  added manifest
  adding: jp/co/infoseek/hp/arton/rjb/JarTest2.class(in = 818) (out= 
439)(deflated 46%)
  dh_auto_build -O--buildsystem=ruby
dh_ruby --build
 dh_ruby --build
  make[1]: Leaving directory '«BUILDDIR»'
 dh_auto_test -O--buildsystem=ruby
dh_ruby --test
 create-stamp debian/debhelper-build-stamp
   fakeroot debian/rules binary
  dh binary --buildsystem=ruby --with ruby
 dh_testroot -O--buildsystem=ruby
 dh_prep -O--buildsystem=ruby
 debian/rules override_dh_auto_install
  make[1]: Entering directory '«BUILDDIR»'
  sed -e '$i $spec = spec' rjb.rake > rjb-global.rake
  ruby -e 'load "rjb-global.rake"; File.open("rjb.gemspec", "w") { |f| f.write 
$spec.to_ruby };'
  LC_ALL=C.UTF-8 dh_auto_install -O--buildsystem=ruby
dh_ruby --install «BUILDDIR»/debian/ruby-rjb
 dh_ruby --install
  
  
┌──┐
  │ Install files   
 │
  
└──┘
  
  install -d «BUILDDIR»/debian/ruby-rjb/usr/lib/ruby/vendor_ruby
  install -D -m644 «BUILDDIR»/lib/rjbextension.rb 
/home/lamby/temp/cdt.20180503160321.dQzXzHsOjv.db.ruby-rjb/ruby-rjb-1.5.5/debian/ruby-rjb/usr/lib/ruby/vendor_ruby/rjbextension.rb
  install -D -m644 «BUILDDIR»/lib/rjb.rb 
/home/lamby/temp/cdt.20180503160321.dQzXzHsOjv.db.ruby-rjb/ruby-rjb-1.5.5/debian/ruby-rjb/usr/lib/ruby/vendor_ruby/rjb.rb
  install -D -m644 «BUILDDIR»/lib/rjb/extension.rb 
/home/lamby/temp/cdt.20180503160321.dQzXzHsOjv.db.ruby-rjb/ruby-rjb-1.5.5/debian/ruby-rjb/usr/lib/ruby/vendor_ruby/rjb/extension.rb
  install -D -m644 «BUILDDIR»/lib/rjb/version.rb 
/home/lamby/temp/cdt.20180503160321.dQzXzHsOjv.db.ruby-rjb/ruby-rjb-1.5.5/debian/ruby-rjb/usr/lib/ruby/vendor_ruby/rjb/version.rb
  install -D -m644 «BUILDDIR»/lib/rjb/list.rb 
/home/lamby/temp/cdt.20180503160321.dQzXzHsOjv.db.ruby-rjb/ruby-rjb-1.5.5/debian/ruby-rjb/usr/lib/ruby/vendor_ruby/rjb/list.rb
  
  

Processed: vjvdkjsvdsf

[Debian Bug Tracking System]

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

> block 897551 by 897573
Bug #897551 [src:usbview] usbview: FTBFS: convert-im6.q16: unable to open file 
`/tmp/magick-20115vbmutCN0nGsV': No such file or directory @ 
error/constitute.c/ReadImage/544.
897551 was not blocked by any bugs.
897551 was not blocking any bugs.
Added blocking bug(s) of 897551: 897573
>
End of message, stopping processing here.

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

Bug#896779: marked as done (python-pyelftools: missing build dependency on python3-distutils)

[Debian Bug Tracking System]

Your message dated Thu, 03 May 2018 22:21:37 +
with message-id 
and subject line Bug#896779: fixed in python-pyelftools 0.24-4.1
has caused the Debian Bug report #896779,
regarding python-pyelftools: missing build dependency on python3-distutils
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.)


-- 
896779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896779
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pyelftools
Version: 0.24-4
Severity: serious

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

...
I: pybuild base:217: python3.6 setup.py clean 
Traceback (most recent call last):
  File "setup.py", line 10, in 
from distutils.core import setup
ModuleNotFoundError: No module named 'distutils.core'
E: pybuild pybuild:336: clean: plugin distutils failed with: exit code=1: 
python3.6 setup.py clean 
dh_auto_clean: pybuild --clean -i python{version} -p 3.6 returned exit code 13
make: *** [debian/rules:7: clean] Error 25


Due to

python3.6 (3.6.5~rc1-2) unstable; urgency=medium

  * python3.6: Drop dependency on python3-distutils.
...
 -- Matthias Klose   Tue, 20 Mar 2018 14:29:58 +0800
--- End Message ---
--- Begin Message ---
Source: python-pyelftools
Source-Version: 0.24-4.1

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

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

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated python-pyelftools 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, 03 May 2018 23:57:36 +0200
Source: python-pyelftools
Binary: python-pyelftools python3-pyelftools
Architecture: source
Version: 0.24-4.1
Distribution: unstable
Urgency: medium
Maintainer: Tomasz Buchert 
Changed-By: Matthias Klose 
Description:
 python-pyelftools - pure-python2 library for parsing ELF and DWARF
 python3-pyelftools - pure-python3 library for parsing ELF and DWARF
Closes: 896779
Changes:
 python-pyelftools (0.24-4.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Build-depend on python3-distutils. Closes: #896779.
   * Bump standards version; no changes required.
Checksums-Sha1:
 51de92aba254bf3fb634827f72e132f637a39e50 2061 python-pyelftools_0.24-4.1.dsc
 812b8b0fc28b08e0821c9f1070aefaa708d1c7a8 3632 
python-pyelftools_0.24-4.1.debian.tar.xz
 e20ba2e77403d1f0cb2c75918fcafbd7298ba220 6297 
python-pyelftools_0.24-4.1_source.buildinfo
Checksums-Sha256:
 c22bdfb879a0aa181e8a54271b51bc40893dd6bb6e355d743fd8aa590e40f05d 2061 
python-pyelftools_0.24-4.1.dsc
 aee8bd518cbe8d39cb2e29766ba6ac11c7c9d5f55190eb225ff68c89f1114cb1 3632 
python-pyelftools_0.24-4.1.debian.tar.xz
 fff8aa51aeea5e500e95356e80f0931505ad17e5b5f18db43a570045a303 6297 
python-pyelftools_0.24-4.1_source.buildinfo
Files:
 0b08506f689daf14a3d584f573e32d1c 2061 python optional 
python-pyelftools_0.24-4.1.dsc
 1b23fbc888ea3b3c7a9bc74e32915d91 3632 python optional 
python-pyelftools_0.24-4.1.debian.tar.xz
 057890193d1acc5e88d97f6e82bd9a08 6297 python optional 
python-pyelftools_0.24-4.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAlrrhoUQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9bueD/99RgnZE4wziNn7BxG/tQYePrc4GaRwT6LD
mAai8kat8sx44QNuiyG2MgRVtV91J+grFTIjRDtTgA+6QxEPweeHJXEh8z1u1Myq
XdQRXGEZ44DehkvlK38SBeO3o76D1jhwzgAzq+yu+j9CxgAj1J2Sb53OxjyEnlM+
6Tbk2t6enqBe3rwXGVF32ZwoPD319AIDXpI52Hd1z5woyRKIp4jbvCDHh8JmZraY
HmM8kRgwUMwW1vmxQXtxt0WpsLp05UKZ4CAp5Q91BEum75iMcErbuvIVNWaWRpIG
Dbkxns9Opf+1PbjtTd5CAw5+kcvkcR//OcL7jp+C84mF0wonaBGYQcv/rDH76qZm
Q51hPOBPymjR2967zqQOfuxd72zT1n/V7s2YfC7NOLVzjF+CdZW7bkpjFAXZWdi1
avgJATf8YYsCXV29fDv1WujkKYLHIeSoQVZ8hSobZw5ofX2Wn3KRvTBBQw2rF7AJ
JEzno5RObSCRvTaPPZFykMEbi02tZzQSN0MWQYANbo91bf8ojS1cyHTcWbhFT1Nm
254hpWuzdeG4W1HH8fg0s/XlwTDk71puu4hToY8QVSwJxSOTGuynH/muUTrHS4tQ
3HqOi1wushTwYkBG+5OcaGqdCrV5o41REfHpUGlrZ6fqO5j+Q0yP6k+X8hsP6YQD
u8nlEqFS9A==
=g1zo
-END PGP SIGNATURE End Message ---

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 896876 https://github.com/mesonbuild/meson/issues/3488
Bug #896876 [meson] libcloudproviders FTBFS with meson 0.46.0-1
Set Bug forwarded-to-address to 
'https://github.com/mesonbuild/meson/issues/3488'.
>
End of message, stopping processing here.

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

Bug#892267: 3dldf: FTBFS on mips64el, hurd-i386, ia64, powerpc, x32 - "src/3dldf tngnts_1.ldf" segfaults

[Hilmar Preuße]

On 07.03.2018 13:13, James Cowgill wrote:

> 3dldf FTBFS on the above architectures with the error:
>> ../src/3dldf tngnts_1.ldf
>> GNU 3DLDF Version 2.0.3
>> Copyright (C) 2013 The Free Software Foundation
>> Author:  Laurence D. Finston
>>
>> GNU 3DLDF comes with ABSOLUTELY NO WARRANTY;
>> for details see the file COPYING,
>> which you should have received in the distribution of GNU 3DLDF 2.0.3
>> This is Free Software, and you are welcome to redistribute it under certain 
>> conditions;
>> for details, again, see the file COPYING.
>>
>> Please send bug reports to laurence.fins...@gmx.de
>> Web site:  http://www.gnu.org/software/3dldf/LDF.html
>>
>> make[4]: *** [Makefile_sub:21: tngnts_1.mp] Segmentation fault
> FYI:

I'm able to reproduce this on i386:

../src/3dldf tngnts_1.ldf
GNU 3DLDF Version 2.0.3
Copyright (C) 2013 The Free Software Foundation
Author:  Laurence D. Finston

GNU 3DLDF comes with ABSOLUTELY NO WARRANTY;
for details see the file COPYING,
which you should have received in the distribution of GNU 3DLDF 2.0.3
This is Free Software, and you are welcome to redistribute it under
certain conditions;
for details, again, see the file COPYING.

Please send bug reports to laurence.fins...@gmx.de
Web site:  http://www.gnu.org/software/3dldf/LDF.html

Makefile_sub:21: recipe for target 'tngnts_1.mp' failed
make[4]: *** [tngnts_1.mp] Segmentation fault (core dumped)
make[4]: *** Deleting file 'tngnts_1.mp'



hille@sid:~/3dldf-2.0.3+dfsg $ gdb src/3dldf examples/core

Type "apropos word" to search for commands related to "word"...
Reading symbols from src/3dldf...done.
[New LWP 4101]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
Core was generated by `../src/3dldf tngnts_1.ldf'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  Id_Map_Entry_Type::operator*= (this=0x13003f0, t=...) at
./imetfncs.web:3864
3864  if (   scanner_node->run_state.multithread_input
(gdb) bt
#0  Id_Map_Entry_Type::operator*= (this=0x13003f0, t=...) at
./imetfncs.web:3864
#1  0x0043cf8a in yyparse (parameter=) at parser.y++:29090
#2  0x00432761 in main (argc=, argv=) at
./main.web:1478

Hilmar
-- 
#206401 http://counter.li.org



signature.asc
Description: OpenPGP digital signature

Bug#897555: subversion: FTBFS: /bin/bash: /usr/lib/jvm/default-java/bin/javah: No such file or directory

[Emmanuel Bourg]

On Wed, 2 May 2018 22:11:49 -0400 James McCoy  wrote:

> Ah, that's because the javah command was removed in Java 10, to be
> replaced by running "javac -h".
> 
> It would have been useful to get a notice about this ahead of time, for
> those not as involved with Java.  Especially since this has apparently
> been planned since Java 8.

Sorry for the lack of communication around the switch, there was a
deprecation warning about javah during the build since the switch to
OpenJDK 9 in March, but it might have been difficult to notice for
Subversion.

Looking at the build log it seems javah is invoked 5 times and the
headers are all generated into the subversion/bindings/javahl/include
directory. Did you try disabling the calls to javah and adding '-h
subversion/bindings/javahl/include/' to the javac parameters?

Emmanuel Bourg

Bug#897417: openmpi: v3.0.1.real-1 FTBFS on most architectures

[Graham Inggs]

Hi Alastair

It appears this is already fixed upstream [1] :

configury: use javac vs javah whenever possible

javah is no more available from Java 10, so try
javac -h first (available since Java 8) and fallback on javah

Regards
Graham


[1] 
https://github.com/open-mpi/ompi/commit/5370586d98b880d3e14659252620bebca92022af

Bug#897653: tar 1.30 breaks pristine-tar

[Antonio Terceiro]

Package: tar
Version: 1.30+dfsg-1
Severity: grave
Justification: causes non-serious data loss

Hi,

After tar 1.30 arrived in unstabled, pristine-tar can no longer
reproduce tarballs that it previously could. For example I just hit this
with bundler:

$ debcheckout -a bundler
declared git repository at g...@salsa.debian.org:ruby-team/bundler.git
git clone https://salsa.debian.org/ruby-team/bundler.git bundler ...
Cloning into 'bundler'...
remote: Counting objects: 3981, done.
remote: Compressing objects: 100% (1289/1289), done.
remote: Total 3981 (delta 2570), reused 3950 (delta 2551)
Receiving objects: 100% (3981/3981), 3.55 MiB | 24.00 KiB/s, done.
Resolving deltas: 100% (2570/2570), done.
git remote set-url --push origin g...@salsa.debian.org:ruby-team/bundler.git ...
$ cd bundler/
$ pristine-tar checkout /tmp/bundler_1.16.1.orig.tar.gz
xdelta3: target window checksum mismatch: XD3_INVALID_INPUT
xdelta3: normally this indicates that the source file is incorrect
xdelta3: please verify the source file with sha1sum or equivalent
xdelta3: target window checksum mismatch: XD3_INVALID_INPUT
xdelta3: normally this indicates that the source file is incorrect
xdelta3: please verify the source file with sha1sum or equivalent
xdelta3: target window checksum mismatch: XD3_INVALID_INPUT
xdelta3: normally this indicates that the source file is incorrect
xdelta3: please verify the source file with sha1sum or equivalent
xdelta3: target window checksum mismatch: XD3_INVALID_INPUT
xdelta3: normally this indicates that the source file is incorrect
xdelta3: please verify the source file with sha1sum or equivalent
pristine-tar: Failed to reproduce original tarball. Please file a bug report.
pristine-tar: failed to generate tarball

See also #897249 and #897421 for similar pristine-tar user reports.
Downgrading tar to 1.29b-2 makes it work again.

I realize that pristine-tar is not sustainable in the long run, but for
better or worse it became a relevant part of Debian development
infrastructure. I'm filing this bug to avoid this situation hitting
testing, while we figure some way out of this.

Bdale, do you have any initial thoughts on this?


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

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

Versions of packages tar depends on:
ii  libacl1  2.2.52-3+b1
ii  libc62.27-3
ii  libselinux1  2.7-2+b2

tar recommends no packages.

Versions of packages tar suggests:
ii  bzip21.0.6-8.1
ii  ncompress4.2.4.4-20
pn  tar-doc  
pn  tar-scripts  
ii  xz-utils 5.2.2-1.3

-- no debconf information


signature.asc
Description: PGP signature

Bug#897490: marked as done (libhtmlparser-java: FTBFS: [javac] /<>/src/resources/HtmlTaglet.java:27: error: package com.sun.tools.doclets does not exist)

[Debian Bug Tracking System]

Your message dated Thu, 03 May 2018 19:51:38 +
with message-id 
and subject line Bug#897490: fixed in libhtmlparser-java 1.6.20060610.dfsg0-9
has caused the Debian Bug report #897490,
regarding libhtmlparser-java: FTBFS: [javac] 
/<>/src/resources/HtmlTaglet.java:27: error: package 
com.sun.tools.doclets does not exist
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.)


-- 
897490: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897490
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libhtmlparser-java
Version: 1.6.20060610.dfsg0-8
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20180502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build -- -f src/build.xml -Dant.build.javac.target=1.7 jarparser 
> javadoc filterbuilder thumbelina
>   ant -propertyfile ./debian/ant.properties -Duser.name debian -f 
> src/build.xml -Dant.build.javac.target=1.7 jarparser javadoc filterbuilder 
> thumbelina
> Buildfile: /<>/src/build.xml
> 
> compilelexer:
> [javac] /<>/src/build.xml:271: warning: 'includeantruntime' 
> was not set, defaulting to build.sysclasspath=last; set to false for 
> repeatable builds
> [javac] Compiling 32 source files to /<>/src/src
> [javac] warning: [options] bootstrap class path not set in conjunction 
> with -source 7
> [javac] Note: /<>/src/src/org/htmlparser/lexer/Page.java 
> uses or overrides a deprecated API.
> [javac] Note: Recompile with -Xlint:deprecation for details.
> [javac] Note: Some input files use unchecked or unsafe operations.
> [javac] Note: Recompile with -Xlint:unchecked for details.
> [javac] 1 warning
> 
> compileparser:
> [javac] /<>/src/build.xml:297: warning: 'includeantruntime' 
> was not set, defaulting to build.sysclasspath=last; set to false for 
> repeatable builds
> [javac] Compiling 107 source files to /<>/src/src
> [javac] warning: [options] bootstrap class path not set in conjunction 
> with -source 7
> [javac] Note: Some input files use or override a deprecated API.
> [javac] Note: Recompile with -Xlint:deprecation for details.
> [javac] Note: Some input files use unchecked or unsafe operations.
> [javac] Note: Recompile with -Xlint:unchecked for details.
> [javac] 1 warning
> 
> jarparser:
> [mkdir] Created dir: /<>/src/lib
>   [jar] Building jar: /<>/src/lib/htmlparser.jar
> 
> JDK_OK:
> 
> JDK_Warning:
>  [echo] ***
>  [echo] *  WARNING: The detected JDK version is not 1.4!  *
>  [echo] ***
> 
> init:
>  [echo] today is Mar 30, 2018
>  [echo] versionTag=1_6_20180330
>  [echo] previous version number = 1.6
>  [echo] previous version type = Release Build
>  [echo] previous version date = Jun 10, 2006
> 
> javadoc:
> [javac] /<>/src/build.xml:450: warning: 'includeantruntime' 
> was not set, defaulting to build.sysclasspath=last; set to false for 
> repeatable builds
> [javac] Compiling 1 source file
> [javac] 
> [javac]   WARNING
> [javac] 
> [javac] The -source switch defaults to 9 in JDK 9.
> [javac] If you specify -target 1.7 you now must also specify -source 1.7.
> [javac] Ant will implicitly add -source 1.7 for you.  Please change your 
> build file.
> [javac] warning: [options] bootstrap class path not set in conjunction 
> with -source 7
> [javac] /<>/src/resources/HtmlTaglet.java:27: error: package 
> com.sun.tools.doclets does not exist
> [javac] import com.sun.tools.doclets.Taglet;
> [javac] ^
> [javac] /<>/src/resources/HtmlTaglet.java:62: error: cannot 
> find symbol
> [javac] public class HtmlTaglet implements Taglet
> [javac]^
> [javac]   symbol: class Taglet
> [javac] Note: /<>/src/resources/HtmlTaglet.java uses or 
> overrides a deprecated API.
> [javac] Note: Recompile with -Xlint:deprecation for details.
> [javac] Note: /<>/src/resources/HtmlTaglet.java uses 
> unchecked or unsafe operations.
> [javac] Note: Recompile with -Xlint:unchecked for details.
> [javac] 2 errors
> [javac] 1 warning
> 
> BUILD FAILED
> /<>/src/build.xml:450: Compile failed; see the compiler error 
> output for details.
> 
> Total time: 3 seconds
> 

Bug#897338: Tested on hardware

[Lisandro Damián Nicanor Pérez Meyer]

El jueves, 3 de mayo de 2018 06:17:14 -03 Maximiliano Curia escribió:
> ¡Hola Александр!
> 
> El 2018-05-03 a las 07:54 +0300, Александр Керножицкий escribió:
> > I tried Debian Testing on real hardware and SDDM seems to work there. So I
> > can reproduce the bug only on VirtualBox.
> It seems that the new sddm requires virtualbox-guest-dkms and
> virtualbox-guest-x11 to run inside a virtualbox, I'm not sure why.

OpenGL probably? Wild guess here...


-- 
11: En Word, como se hace para pasar al proximo renglon si se alcanzo
el extramo derecho de la hoja.
* Se reinicia la maquina, se abre el Guord, se va a archivo, Nuevo
renglon, Preferencias, Abajo del otro renglon, Poner el cursor al
proncipio del nuevo renglon, Elegir misma letra que el anterior,
respetar la pagina anterior, respetar el margen anterior, respetar
numeracion de pagina, comenzar a escribir, click en "Ok deseo comenzar
a escribir", click en "Esta seguro que desea comenzar a Escribir",
click en "Ultima advertencia", click en "Comience a escribir"
Damian Nadales
http://mx.grulic.org.ar/lurker/message/20080307.141449.a70fb2fc.es.html

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Bug#897540: marked as done (r-bioc-variantannotation: FTBFS: g++: error: /libtabix.a: No such file or directory)

[Debian Bug Tracking System]

Your message dated Thu, 03 May 2018 18:52:02 +
with message-id 
and subject line Bug#897540: fixed in r-bioc-variantannotation 1.26.0-1
has caused the Debian Bug report #897540,
regarding r-bioc-variantannotation: FTBFS: g++: error: /libtabix.a: No such 
file or directory
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.)


-- 
897540: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897540
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-bioc-variantannotation
Version: 1.24.5-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20180502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>/src'
> gcc -std=gnu99 -I/usr/share/R/include -DNDEBUG -D_USE_KNETFILE -DBGZF_CACHE 
> -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE 
> -I"/usr/lib/R/site-library/S4Vectors/include" 
> -I"/usr/lib/R/site-library/IRanges/include" 
> -I"/usr/lib/R/site-library/XVector/include" 
> -I"/usr/lib/R/site-library/Biostrings/include" 
> -I"/usr/lib/R/site-library/Rsamtools/include"-fpic  -g -O2 
> -fdebug-prefix-map=/build/r-base-3.4.4=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g  -c 
> Biostrings_stubs.c -o Biostrings_stubs.o
> gcc -std=gnu99 -I/usr/share/R/include -DNDEBUG -D_USE_KNETFILE -DBGZF_CACHE 
> -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE 
> -I"/usr/lib/R/site-library/S4Vectors/include" 
> -I"/usr/lib/R/site-library/IRanges/include" 
> -I"/usr/lib/R/site-library/XVector/include" 
> -I"/usr/lib/R/site-library/Biostrings/include" 
> -I"/usr/lib/R/site-library/Rsamtools/include"-fpic  -g -O2 
> -fdebug-prefix-map=/build/r-base-3.4.4=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g  -c 
> IRanges_stubs.c -o IRanges_stubs.o
> gcc -std=gnu99 -I/usr/share/R/include -DNDEBUG -D_USE_KNETFILE -DBGZF_CACHE 
> -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE 
> -I"/usr/lib/R/site-library/S4Vectors/include" 
> -I"/usr/lib/R/site-library/IRanges/include" 
> -I"/usr/lib/R/site-library/XVector/include" 
> -I"/usr/lib/R/site-library/Biostrings/include" 
> -I"/usr/lib/R/site-library/Rsamtools/include"-fpic  -g -O2 
> -fdebug-prefix-map=/build/r-base-3.4.4=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g  -c 
> R_init_VariantAnnotation.c -o R_init_VariantAnnotation.o
> gcc -std=gnu99 -I/usr/share/R/include -DNDEBUG -D_USE_KNETFILE -DBGZF_CACHE 
> -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE 
> -I"/usr/lib/R/site-library/S4Vectors/include" 
> -I"/usr/lib/R/site-library/IRanges/include" 
> -I"/usr/lib/R/site-library/XVector/include" 
> -I"/usr/lib/R/site-library/Biostrings/include" 
> -I"/usr/lib/R/site-library/Rsamtools/include"-fpic  -g -O2 
> -fdebug-prefix-map=/build/r-base-3.4.4=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g  -c 
> XVector_stubs.c -o XVector_stubs.o
> gcc -std=gnu99 -I/usr/share/R/include -DNDEBUG -D_USE_KNETFILE -DBGZF_CACHE 
> -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE 
> -I"/usr/lib/R/site-library/S4Vectors/include" 
> -I"/usr/lib/R/site-library/IRanges/include" 
> -I"/usr/lib/R/site-library/XVector/include" 
> -I"/usr/lib/R/site-library/Biostrings/include" 
> -I"/usr/lib/R/site-library/Rsamtools/include"-fpic  -g -O2 
> -fdebug-prefix-map=/build/r-base-3.4.4=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g  -c dna_hash.c -o 
> dna_hash.o
> gcc -std=gnu99 -I/usr/share/R/include -DNDEBUG -D_USE_KNETFILE -DBGZF_CACHE 
> -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE 
> -I"/usr/lib/R/site-library/S4Vectors/include" 
> -I"/usr/lib/R/site-library/IRanges/include" 
> -I"/usr/lib/R/site-library/XVector/include" 
> -I"/usr/lib/R/site-library/Biostrings/include" 
> -I"/usr/lib/R/site-library/Rsamtools/include"-fpic  -g -O2 
> -fdebug-prefix-map=/build/r-base-3.4.4=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g  -c rle.c -o rle.o
> gcc -std=gnu99 -I/usr/share/R/include -DNDEBUG -D_USE_KNETFILE -DBGZF_CACHE 
> -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE 
> -I"/usr/lib/R/site-library/S4Vectors/include" 
> -I"/usr/lib/R/site-library/IRanges/include" 
> -I"/usr/lib/R/site-library/XVector/include" 
> -I"/usr/lib/R/site-library/Biostrings/include" 
> 

Bug#897644: python-gwcs depends on cruft package python-asdf

[peter green]

Package: python-gwcs
Version: 0.8.0-1
Severity: serious

python-gwcs depends on the binary package python-asdf which is no longer built 
by the source package python-asdf

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 897531 
> https://bitbucket.org/heldercorreia/speedcrunch/issues/830/build-with-drebuild_manual-fails-on-debian
Bug #897531 [src:speedcrunch] speedcrunch: FTBFS: make[4]: *** No rule to make 
target 'doc/manual.qrc', needed by 'CMakeFiles/speedcrunch_arcc_manual'.  Stop.
Set Bug forwarded-to-address to 
'https://bitbucket.org/heldercorreia/speedcrunch/issues/830/build-with-drebuild_manual-fails-on-debian'.
>
End of message, stopping processing here.

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

Bug#894619: marked as done (sdcc FTBFS with lyx 2.3.0-2)

[Debian Bug Tracking System]

Your message dated Thu, 03 May 2018 17:50:20 +
with message-id 
and subject line Bug#894619: fixed in sdcc 3.5.0+dfsg-2.1
has caused the Debian Bug report #894619,
regarding sdcc FTBFS with lyx 2.3.0-2
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.)


-- 
894619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894619
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lyx
Version: 2.3.0-2
Severity: serious
Control: affects -1 src:sdcc

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

...
This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017/Debian) 
(preloaded format=latex)
 restricted \write18 enabled.
entering extended mode
(./sdccman.tex
LaTeX2e <2017-04-15>
Babel <3.18> and hyphenation patterns for 3 language(s) loaded.

support/Systemcall.cpp (294): Systemcall: 'latex "sdccman.tex"' finished with 
exit code 1
This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017/Debian) 
(preloaded format=latex)
 restricted \write18 enabled.
entering extended mode
(./sdccman.tex
LaTeX2e <2017-04-15>
Babel <3.18> and hyphenation patterns for 3 language(s) loaded.

support/Systemcall.cpp (294): Systemcall: 'latex "sdccman.tex"' finished with 
exit code 1
make: *** [debian/rules:71: build-indep-stamp] Error 1
--- End Message ---
--- Begin Message ---
Source: sdcc
Source-Version: 3.5.0+dfsg-2.1

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

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

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated sdcc 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: Wed, 18 Apr 2018 19:34:21 +0300
Source: sdcc
Binary: sdcc sdcc-libraries sdcc-ucsim sdcc-doc
Architecture: source
Version: 3.5.0+dfsg-2.1
Distribution: unstable
Urgency: medium
Maintainer: Gudjon I. Gudjonsson 
Changed-By: Adrian Bunk 
Description:
 sdcc   - Small Device C Compiler
 sdcc-doc   - Small Device C Compiler (documentation)
 sdcc-libraries - Small Device C Compiler (libraries)
 sdcc-ucsim - Micro-controller simulator for SDCC
Closes: 894619
Changes:
 sdcc (3.5.0+dfsg-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add patch from Dr. Tobias Quathamer to fix FTBFS with lyx 2.3.
 (Closes: #894619)
Checksums-Sha1:
 5eae1988ec54d4452146749c25b8fa798ecaaa46 2339 sdcc_3.5.0+dfsg-2.1.dsc
 0f15c7ca4c9d57a316e8a05414ee82c12e6366e5 27068 
sdcc_3.5.0+dfsg-2.1.debian.tar.xz
Checksums-Sha256:
 91d63f402440f58beecd06ae9a794c466443de14620bf5bf98f9df1df9239338 2339 
sdcc_3.5.0+dfsg-2.1.dsc
 698d18e8fbf5a5b3459088ed95a9b4743530572ca622030ef1b1c668255f0f14 27068 
sdcc_3.5.0+dfsg-2.1.debian.tar.xz
Files:
 df977fa3ef8c9ecc52b1a1e517dd1c53 2339 electronics optional 
sdcc_3.5.0+dfsg-2.1.dsc
 fdc2dc565f6f071cd85dba6178cc7859 27068 electronics optional 
sdcc_3.5.0+dfsg-2.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlrXdXgACgkQiNJCh6LY
mLFUtQ//WTlH6jsFc3KanjUji0crq+etW/hNVutl2xSnkvG7y0BlYI9fW0kY/nfE
4dOAztUZMXzac41nmHCd3MUbxWOfNFjXEKrFRzmu/ZmKkVS4yqwDCpn/OF0t/Emp
iAPA2Q6uUCOC85orbg8VvPCEHtczPkCMH0ZhMsgGlWwQLXIm+WWaCz8vTFXe570c
JYHmu5dKVlQ8c+dSCDJk+4tvgqpiB758IO3xUXl6Db1BnyutqyfBA+zIAhv9VQ3v
bLvoWtDjPzt4ZkXGfflFkA6xjwELmqLnDG+gXv/zqlHOsKDyJ5Ra+ScM262X8RST
fg8SbJyE+zzck/gYVVIOFa3x9ZsA2fNnc9htxuc8eAhHTVwiITr2QxgFbLDqQ5jy
+iILNiPdod7odvaCkmy4VQkDxJNJZmyPHwhCW1l7j2wTfnLpw4dR+eG/CuuEEm+J
lfytIk8H6xHjoZcTHt+N9qTUYpkeP8v3BOiQAWaLxhMD3gVcnsxF4dOj4osF/IqG
M5jzRgTZQb8uD1JacH80yiV6pDqNRuBqv+xvVdyItc0jjfJaY1UvyWf8td5QS4/O
NSGUeuL9pQ+I04t9LkOZrPKLahvYfQqIIFfD2kYw/G3+EMp/WG0VpzXiOhTPjjzJ
+4WmLao3nzJnpIfv1SZB6u7XOhN+Kb55rb5RG3msY9Rhk1TSQQE=
=Dyg5
-END PGP SIGNATURE End Message ---

Bug#897006: [petsc-maint] Bug#897006: petsc FTBFS on mips: f951: out of memory

[Drew Parsons]

On Wed, 2018-05-02 at 08:28 -0500, Satish Balay wrote:
> On Tue, 1 May 2018, Drew Parsons wrote:
> 
> > Looks like that does the trick. Running make in src/dm/f90-mod, it
> > successfully compiles and archives petscdmmod.o and
> > petscdmplexmod.o
> > inside build-arch/lib/libpetsc.a
> 
> Great! I've merged it to maint - so this change should be in petsc-
> 3.9.2

I'll add the patch to Debian, or update to 3.9.2, which happens first.

> BTW: the current build [with gmakefile] does not invoke make in
> individual source dirs. But I think this compile in source dir should
> be equivalent.

I've confirmed now that it also builds and links properly from the top-
level makefile.

Drew

Bug#897452: marked as done (openmpi: FTBFS: configure: error: cannot continue)

[Debian Bug Tracking System]

Your message dated Thu, 03 May 2018 17:36:37 +
with message-id 
and subject line Bug#897452: fixed in openmpi 3.0.1.real-3
has caused the Debian Bug report #897452,
regarding openmpi: FTBFS: configure: error: cannot continue
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.)


-- 
897452: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897452
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openmpi
Version: 3.0.1.real-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20180502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> checking Java support available... no
> 
> *** Java MPI bindings
> checking if want Java bindings... yes
> configure: WARNING: Java bindings requested but no Java support found
> configure: error: cannot continue
>   tail -v -n \+0 config.log

The full build log is available from:
   http://aws-logs.debian.net/2018/05/02/openmpi_3.0.1.real-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: openmpi
Source-Version: 3.0.1.real-3

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated openmpi 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, 03 May 2018 04:49:34 +0100
Source: openmpi
Binary: openmpi-bin libopenmpi-dev libopenmpi3 openmpi-common openmpi-doc
Architecture: source amd64 all
Version: 3.0.1.real-3
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Description:
 libopenmpi-dev - high performance message passing library -- header files
 libopenmpi3 - high performance message passing library -- shared library
 openmpi-bin - high performance message passing library -- binaries
 openmpi-common - high performance message passing library -- common files
 openmpi-doc - high performance message passing library -- man pages
Closes: 897452
Changes:
 openmpi (3.0.1.real-3) unstable; urgency=medium
 .
   * Add kfreebsd, sh4 to the non-Java list (no openjdk-9 support).
 Closes: #897452
Checksums-Sha1:
 97ee8f998dae48bae6b28cab6bafd6ea74d0f292 2736 openmpi_3.0.1.real-3.dsc
 595bf4f9df1f853a9713047bb2a4304fc2578920 61128 
openmpi_3.0.1.real-3.debian.tar.xz
 c8f954b02f7ea04875b79774f92800411c3ea7b1 9496 
libopenmpi-dev-dbgsym_3.0.1.real-3_amd64.deb
 a488c6d84b997d2623fd3bc3a1b86d989ec1d862 935768 
libopenmpi-dev_3.0.1.real-3_amd64.deb
 81f9e9241d8a50bbf8530d1794908ffcd34f7df2 27125916 
libopenmpi3-dbgsym_3.0.1.real-3_amd64.deb
 c94f0d6f14a08cfdfbcda58dc0994b6912146bad 2094960 
libopenmpi3_3.0.1.real-3_amd64.deb
 78ac7642c6839b2c6ab79a6ac129e586bdf56cdb 227188 
openmpi-bin-dbgsym_3.0.1.real-3_amd64.deb
 bdaf1b5df6d43aa64ba58465d10642f1b3c16d1f 202620 
openmpi-bin_3.0.1.real-3_amd64.deb
 6bd045547d3222713429d1d9f06d0e5b93d4acc3 158492 
openmpi-common_3.0.1.real-3_all.deb
 e4612c91a9ea642101eff9cec5d13d45bd911bae 755904 
openmpi-doc_3.0.1.real-3_all.deb
 7ee6fa936f189949c96f79269662454d12716c8a 13691 
openmpi_3.0.1.real-3_amd64.buildinfo
Checksums-Sha256:
 0b8a41f3625f76f4ec6ac2e89b147af5d4a0b9826d543bd6091cfd78c37240a8 2736 
openmpi_3.0.1.real-3.dsc
 443cf17638f4367d207732ef2741d82c1e57495e612630da66cbb04d312bede8 61128 
openmpi_3.0.1.real-3.debian.tar.xz
 1815bf9486f9614ef7602874f3300a5fd209b47f17a58daffe8e49a96ef5a32c 9496 
libopenmpi-dev-dbgsym_3.0.1.real-3_amd64.deb
 adf213f4a865bfe409802a4954f2193c1297ea4a0cca57cfe0cbad8826bf1837 935768 

Bug#897507: marked as done (flextra: FTBFS: Fatal Error: Can't open module file 'grib_api.mod' for reading at (1): No such file or directory)

[Debian Bug Tracking System]

Your message dated Thu, 03 May 2018 17:04:51 +
with message-id 
and subject line Bug#897507: fixed in flextra 5.0-9
has caused the Debian Bug report #897507,
regarding flextra: FTBFS: Fatal Error: Can't open module file 'grib_api.mod' 
for reading at (1): No such file or directory
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.)


-- 
897507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897507
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: flextra
Version: 5.0-8
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20180502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> f77 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -fPIC  -fconvert=little-endian -frecord-marker=4  -I/usr/include   -c -o 
> caldate.o caldate.f
> f77 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -fPIC  -fconvert=little-endian -frecord-marker=4  -I/usr/include   -c -o 
> openoutput.o openoutput.f
> f77 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -fPIC  -fconvert=little-endian -frecord-marker=4  -I/usr/include   -c -o 
> checklimits.o checklimits.f
> f77 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -fPIC  -fconvert=little-endian -frecord-marker=4  -I/usr/include   -c -o 
> coordtrafo.o coordtrafo.f
> f77 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -fPIC  -fconvert=little-endian -frecord-marker=4  -I/usr/include   -c -o 
> orolininterpol.o orolininterpol.f
> f77 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -fPIC  -fconvert=little-endian -frecord-marker=4  -I/usr/include   -c -o 
> etatrafo.o etatrafo.f
> f77 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -fPIC  -fconvert=little-endian -frecord-marker=4  -I/usr/include   -c -o 
> petters.o petters.f
> f77 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -fPIC  -fconvert=little-endian -frecord-marker=4  -I/usr/include   -c -o 
> eta.ecmwf.o eta.ecmwf.f
> f77 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -fPIC  -fconvert=little-endian -frecord-marker=4  -I/usr/include   -c -o 
> FLEXTRA.o FLEXTRA.f
> f77 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -fPIC  -fconvert=little-endian -frecord-marker=4  -I/usr/include   -c -o 
> pp.ecmwf.o pp.ecmwf.f
> f77 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -fPIC  -fconvert=little-endian -frecord-marker=4  -I/usr/include   -c -o 
> geteta.o geteta.f
> f77 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -fPIC  -fconvert=little-endian -frecord-marker=4  -I/usr/include   -c -o 
> getfields.o getfields.f
> f77 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -fPIC  -fconvert=little-endian -frecord-marker=4  -I/usr/include   -c -o 
> pvinterpol.o pvinterpol.f
> f77 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -fPIC  -fconvert=little-endian -frecord-marker=4  -I/usr/include   -c -o 
> getheight.o getheight.f
> f77 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -fPIC  -fconvert=little-endian -frecord-marker=4  -I/usr/include   -c -o 
> random.o random.f
> f77 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -fPIC  -fconvert=little-endian -frecord-marker=4  -I/usr/include   -c -o 
> readavailable.o readavailable.f
> f77 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -fPIC  -fconvert=little-endian -frecord-marker=4  -I/usr/include   -c -o 
> getwind.o getwind.f
> f77 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -fPIC  -fconvert=little-endian -frecord-marker=4  -I/usr/include   -c -o 
> readcommand.o readcommand.f
> f77 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -fPIC  -fconvert=little-endian -frecord-marker=4  -I/usr/include   -c -o 
> gridcheck.o gridcheck.f
> gridcheck.f:52:9:
> 
>use grib_api
>  1
> Fatal Error: Can't open module file 'grib_api.mod' for reading at (1): No 
> such file or directory
> compilation terminated.
> make[2]: *** [: gridcheck.o] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2018/05/02/flextra_5.0-8_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date 

Bug#897518: marked as done (flexpart: FTBFS: Fatal Error: Can't open module file 'grib_api.mod' for reading at (1): No such file or directory)

[Debian Bug Tracking System]

Your message dated Thu, 03 May 2018 17:04:43 +
with message-id 
and subject line Bug#897518: fixed in flexpart 9.02-19
has caused the Debian Bug report #897518,
regarding flexpart: FTBFS: Fatal Error: Can't open module file 'grib_api.mod' 
for reading at (1): No such file or directory
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.)


-- 
897518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897518
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: flexpart
Version: 9.02-17
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20180502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> gfortran -c -O2 -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian 
> -frecord-marker=4 -I/usr/include par_mod.f90
> gfortran -c -O2 -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian 
> -frecord-marker=4 -I/usr/include com_mod.f90
> gfortran -c -O2 -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian 
> -frecord-marker=4 -I/usr/include conv_mod.f90
> gfortran -c -O2 -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian 
> -frecord-marker=4 -I/usr/include hanna_mod.f90
> gfortran -c -O2 -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian 
> -frecord-marker=4 -I/usr/include interpol_mod.f90
> gfortran -c -O2 -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian 
> -frecord-marker=4 -I/usr/include cmapf_mod.f90
> gfortran -c -O2 -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian 
> -frecord-marker=4 -I/usr/include unc_mod.f90
> gfortran -c -O2 -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian 
> -frecord-marker=4 -I/usr/include oh_mod.f90
> gfortran -c -O2 -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian 
> -frecord-marker=4 -I/usr/include xmass_mod.f90
> gfortran -c -O2 -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian 
> -frecord-marker=4 -I/usr/include flux_mod.f90
> gfortran -c -O2 -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian 
> -frecord-marker=4 -I/usr/include point_mod.f90
> gfortran -c -O2 -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian 
> -frecord-marker=4 -I/usr/include outg_mod.f90
> gfortran -c -O2 -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian 
> -frecord-marker=4 -I/usr/include writeheader.f90
> gfortran -c -O2 -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian 
> -frecord-marker=4 -I/usr/include assignland.f90
> gfortran -c -O2 -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian 
> -frecord-marker=4 -I/usr/include calcpar_gfs.f90
> gfortran -c -O2 -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian 
> -frecord-marker=4 -I/usr/include part0.f90
> gfortran -c -O2 -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian 
> -frecord-marker=4 -I/usr/include caldate.f90
> gfortran -c -O2 -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian 
> -frecord-marker=4 -I/usr/include partdep.f90
> gfortran -c -O2 -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian 
> -frecord-marker=4 -I/usr/include coordtrafo.f90
> gfortran -c -O2 -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian 
> -frecord-marker=4 -I/usr/include psih.f90
> gfortran -c -O2 -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian 
> -frecord-marker=4 -I/usr/include raerod.f90
> gfortran -c -O2 -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian 
> -frecord-marker=4 -I/usr/include drydepokernel.f90
> gfortran -c -O2 -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian 
> -frecord-marker=4 -I/usr/include random.f90
> gfortran -c -O2 -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian 
> -frecord-marker=4 -I/usr/include erf.f90
> gfortran -c -O2 -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian 
> -frecord-marker=4 -I/usr/include readavailable.f90
> gfortran -c -O2 -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian 
> -frecord-marker=4 -I/usr/include ew.f90
> gfortran -c -O2 -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian 
> -frecord-marker=4 -I/usr/include readcommand.f90
> gfortran -c -O2 -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian 
> -frecord-marker=4 -I/usr/include advance.f90
> gfortran -c -O2 -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian 
> -frecord-marker=4 -I/usr/include readdepo.f90
> gfortran -c -O2 -mcmodel=medium -O2 

Bug#864719: marked as done (slapd: fails to configure when olcSuffix contains a backslash-escaped umlaut)

[Debian Bug Tracking System]

Your message dated Thu, 03 May 2018 15:39:46 +
with message-id 
and subject line Bug#864719: fixed in openldap 2.4.46+dfsg-1
has caused the Debian Bug report #864719,
regarding slapd: fails to configure when olcSuffix contains a backslash-escaped 
umlaut
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.)


-- 
864719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864719
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: slapd
Version: 2.4.31-2+deb7u3
Severity: serious
Justification: fails to configure

With recent security updates being available in Debian oldstable
(soon to be oldoldstable, but hey!), the package fails to upgrade
because it fails to configure if the olcSuffix contains a nōn-ASCII
character (and a space, but I don’t think that is it).

I will be filtering the name of our client as follows, believing
that the problem will still appear.

olcSuffix: o=Kundenname M\c3\bcumlaut,c=de

No, I did not invent this…

With “set -x” in slapd.postinst (and reverting the default /bin/sh
to bash to be sure it’s not an mksh problem) I get:

root@prodname-dollarcustomer:~ # dpkg -a --configure
Setting up slapd (2.4.31-2+deb7u3) ...
+ . /usr/share/debconf/confmodule
++ '[' '!' '' ']'
++ PERL_DL_NONLAZY=1
++ export PERL_DL_NONLAZY
++ '[' '' ']'
++ exec /usr/share/debconf/frontend /var/lib/dpkg/info/slapd.postinst configure 
2.4.31-2+deb7u3
+ . /usr/share/debconf/confmodule
++ '[' '!' 1 ']'
++ '[' -z '' ']'
++ exec
++ '[' '' ']'
++ exec
++ DEBCONF_REDIR=1
++ export DEBCONF_REDIR
+ MODE=configure
+ OLD_VERSION=2.4.31-2+deb7u3
+ '[' -f /etc/default/slapd ']'
+ . /etc/default/slapd
++ SLAPD_CONF=
++ SLAPD_USER=openldap
++ SLAPD_GROUP=openldap
++ SLAPD_PIDFILE=
++ SLAPD_SERVICES='ldap:/// ldapi:///'
++ SLAPD_SENTINEL_FILE=/etc/ldap/noslapd
++ SLAPD_OPTIONS=
+ '[' -z '' ']'
+ '[' -f /etc/ldap/slapd.conf ']'
+ SLAPD_CONF=/etc/ldap/slapd.d
+ '[' configure = configure ']'
+ '[' openldap = openldap ']'
+ create_new_user
++ getent group openldap
+ '[' -z openldap:x:112: ']'
++ getent passwd openldap
+ '[' -z 'openldap:x:106:112:OpenLDAP Server 
Account,,,:/var/lib/ldap:/bin/false' ']'
+ is_initial_configuration configure 2.4.31-2+deb7u3
+ '[' configure = configure ']'
+ '[' -z 2.4.31-2+deb7u3 ']'
+ '[' configure = reconfigure ']'
+ '[' '' ']'
+ '[' configure = configure ']'
+ '[' '!' -e /etc/ldap/slapd.d ']'
+ return 1
+ postinst_upgrade_configuration
++ database_dumping_destdir
++ local dir
++ db_get slapd/dump_database_destdir
++ _db_cmd 'GET slapd/dump_database_destdir'
++ _db_internal_IFS='
'
++ IFS=' '
++ printf '%s\n' 'GET slapd/dump_database_destdir'
++ IFS='
'
++ IFS='
'
++ read -r _db_internal_line
++ RET=/var/backups/slapd-VERSION
++ case ${_db_internal_line%%[  ]*} in
++ return 0
+++ sed -e s/VERSION/2.4.31-2+deb7u3/
+++ echo /var/backups/slapd-VERSION
++ dir=/var/backups/slapd-2.4.31-2+deb7u3
++ mkdir -p -m 700 /var/backups/slapd-2.4.31-2+deb7u3
++ echo /var/backups/slapd-2.4.31-2+deb7u3
+ echo -n '  Backing up /etc/ldap/slapd.d in 
/var/backups/slapd-2.4.31-2+deb7u3... '
  Backing up /etc/ldap/slapd.d in /var/backups/slapd-2.4.31-2+deb7u3... + 
backup_config_once
+ local backupdir
+ '[' -z '' ']'
++ database_dumping_destdir
++ local dir
++ db_get slapd/dump_database_destdir
++ _db_cmd 'GET slapd/dump_database_destdir'
++ _db_internal_IFS='
'
++ IFS=' '
++ printf '%s\n' 'GET slapd/dump_database_destdir'
++ IFS='
'
++ IFS='
'
++ read -r _db_internal_line
++ RET=/var/backups/slapd-VERSION
++ case ${_db_internal_line%%[  ]*} in
++ return 0
+++ sed -e s/VERSION/2.4.31-2+deb7u3/
+++ echo /var/backups/slapd-VERSION
++ dir=/var/backups/slapd-2.4.31-2+deb7u3
++ mkdir -p -m 700 /var/backups/slapd-2.4.31-2+deb7u3
++ echo /var/backups/slapd-2.4.31-2+deb7u3
+ backupdir=/var/backups/slapd-2.4.31-2+deb7u3
+ '[' -e /etc/ldap/slapd.d ']'
+ cp -a /etc/ldap/slapd.d /var/backups/slapd-2.4.31-2+deb7u3
+ FLAG_CONFIG_BACKED_UP=yes
+ echo done.
done.
+ database_format_changed
+ dpkg --compare-versions 2.4.31-2+deb7u3 lt-nl 2.4.25-2
+ return 1
+ migrate_to_slapd_d_style
+ previous_version_older 2.4.23-3
+ dpkg --compare-versions 2.4.31-2+deb7u3 lt-nl 2.4.23-3
+ return 1
+ previous_version_older 2.4.23-5
+ dpkg --compare-versions 2.4.31-2+deb7u3 lt-nl 2.4.23-5
+ return 1
+ configure_v2_protocol_support
+ local new_conf
+ db_get slapd/allow_ldap_v2
+ _db_cmd 'GET slapd/allow_ldap_v2'
+ _db_internal_IFS='
'
+ IFS=' '
+ printf '%s\n' 'GET slapd/allow_ldap_v2'
+ IFS='
'
+ IFS='
'
+ read -r _db_internal_line
+ RET=false
+ case ${_db_internal_line%%[   ]*} in
+ return 0
+ '[' 

Bug#897592: ebtables: randomly FTBFS - makefile is not parallel safe

[Alberto Molina Coballes]

Thanks James, these kinds of errors are often difficult to deal with.

Do you think that it should be enough disabling parallel build in dh?
Tested on amd64 seems to work properly.

Alberto

Bug#897483: ust: FTBFS: LTTngUst.c:20:10: fatal error: org_lttng_ust_LTTngUst.h: No such file or directory

[Michael Jeanson]

On 2018-05-02 04:07 PM, Lucas Nussbaum wrote:
> Source: ust
> Version: 2.10.1-2
> Severity: serious
> Tags: buster sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20180502 qa-ftbfs
> Justification: FTBFS on amd64
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
> 
> Relevant part (hopefully):
>> /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. 
>> -I../include/lttng  -I../include -I../include 
>> -I/usr/lib/jvm/default-java/include 
>> -I/usr/lib/jvm/default-java/include/linux -Wdate-time -D_FORTIFY_SOURCE=2 
>> -Wall -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
>> -Wformat -Werror=format-security -c -o LTTngUst.lo LTTngUst.c
>> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I../include/lttng 
>> -I../include -I../include -I/usr/lib/jvm/default-java/include 
>> -I/usr/lib/jvm/default-java/include/linux -Wdate-time -D_FORTIFY_SOURCE=2 
>> -Wall -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
>> -Wformat -Werror=format-security -c LTTngUst.c  -fPIC -DPIC -o 
>> .libs/LTTngUst.o
>> LTTngUst.c:20:10: fatal error: org_lttng_ust_LTTngUst.h: No such file or 
>> directory
>>  #include "org_lttng_ust_LTTngUst.h"
>>   ^~
>> compilation terminated.
>> make[4]: *** [Makefile:501: LTTngUst.lo] Error 1
> 
> The full build log is available from:
>http://aws-logs.debian.net/2018/05/02/ust_2.10.1-2_unstable.log
> 
> A list of current common problems and possible solutions is available at
> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
> 
> About the archive rebuild: The rebuild was done on EC2 VM instances from
> Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
> failed build was retried once to eliminate random failures.
> 

Hi,

That's surprising, I did a source upload a week or so ago that built
fine on the buildds. Looking at both build logs the difference seems to
be that the default jdk changed from 9 to 10.

I'll try to reproduce the failure on my system and fix it.

Thanks for the heads up,

Michael

Bug#897597: marked as done (udev rules installed into wrong path)

[Debian Bug Tracking System]

Your message dated Thu, 03 May 2018 15:06:57 +
with message-id 
and subject line Bug#897597: fixed in casync 2+20180321-2
has caused the Debian Bug report #897597,
regarding udev rules installed into wrong path
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.)


-- 
897597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897597
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: casync
Version: 2+20180321-1
Severity: serious

It seems we install the udev rules file into the wrong path as

 usr/rules.d/75-casync.rules

This happens because meson.build contains
 udevdir = dependency('udev', required : 
false).get_pkgconfig_variable('udevdir')
 udevrulesdir = join_paths(udevdir, 'rules.d')
but in the build chroot there is no udev.pc (it's provided by the udev
package).
The simplest fix is to add a Build-Depends on udev.



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

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

Versions of packages casync depends on:
ii  libacl1  2.2.52-3+b1
ii  libc62.27-3
ii  libcurl3-gnutls  7.58.0-2
ii  libfuse2 2.9.7-1
ii  liblzma5 5.2.2-1.3
ii  libselinux1  2.7-2+b2
ii  libssl1.11.1.0h-2
ii  libudev1 238-4
ii  libzstd1 1.3.4+dfsg-2
ii  zlib1g   1:1.2.11.dfsg-1

casync recommends no packages.

casync suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: casync
Source-Version: 2+20180321-2

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

Debian distribution maintenance software
pp.
Felipe Sateler  (supplier of updated casync 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, 03 May 2018 10:12:33 -0300
Source: casync
Binary: casync
Architecture: source
Version: 2+20180321-2
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 

Changed-By: Felipe Sateler 
Description:
 casync - content addressable data synchronizer
Closes: 897597
Changes:
 casync (2+20180321-2) unstable; urgency=medium
 .
   * Add udev Build-Depends to be able to query udev.pc (Closes: #897597)
Checksums-Sha1:
 4ee668ea13eaed62c8dfae022e369ee77f5fd1a8 2283 casync_2+20180321-2.dsc
 1dae824e5eb6e258894efc3604b04a47ad0b397b 2840 casync_2+20180321-2.debian.tar.xz
 3e8244643d09aa1d2cb7b2f0e12aa7d9fba35665 8000 
casync_2+20180321-2_source.buildinfo
Checksums-Sha256:
 e788b2487b82044ec56d4fe39200e1e9dc2bec03a16180cd6356fe49f6127767 2283 
casync_2+20180321-2.dsc
 a7f647c277bd10774dfdefe0e900eaf1e1f78fa931308a491582ef10e2e6e113 2840 
casync_2+20180321-2.debian.tar.xz
 8971c7178573b321f89407d1519f3a242c211588272ef925ea4d705c92fffa02 8000 
casync_2+20180321-2_source.buildinfo
Files:
 f57cbb5818bda9e9fdbef752c9c067a7 2283 utils optional casync_2+20180321-2.dsc
 c79e9b2d7d4425d6028b1f8bc1bee8d2 2840 utils optional 
casync_2+20180321-2.debian.tar.xz
 905024c01520ef21d8fbc8eb124e822c 8000 utils optional 
casync_2+20180321-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEIY7gNiAzyHtsE1+ko7q64kCN1s8FAlrrC08UHGZzYXRlbGVy
QGRlYmlhbi5vcmcACgkQo7q64kCN1s/B3g/9H9HonyO3XvC8cRM80NV3VbsWWdKx
45unpcfMQW8vvs9fzQh1Lg6XlW1MPsgQRHoRyh8AIfXokYVujKKnYxVMR7Rwpv1k
vR/ZPBgiJvidB7MNdCo6SSk/OpWlxjEsJrnSzO79r4sJhRIiHZw0qnSO9j4h60f3
A+tNvOsWKhX9uMHw8nuLin/2WA867O+/vklAI0M5qmvsoErufAN/PixANpySuEP0
cnE39NNTU4TJblUxTLqAtv5bxb6XmjsAKrQzDPEnRJzaHQ5MN6cShfBy1i+dSK0i
6YAg/NHqUOl8/fHQqZq1nbGXNEGj/l2scJBPX0lQGggYXDTp1v1fE2XBvO/spVGu
q9ngWZYXF1XaEck1yCwXwa4eYR7WU/HZ2I8J4FSsCixqTycXCuPRcP5btD1OkDnw

Bug#895782: please remove or update to 5.2.X both sources, dkms and gui/cli

[PICCORO McKAY Lenz]

i REVISED THAT THE REQUIRED PATCH ARE ALREADY IN
*virtualbox_5.1.8-dfsg-7.dsc*

WHY NOT JUST RE-BACKPORT THAT VERSION TO JESSIE? that currently has this
problem!

Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com

2018-05-03 9:48 GMT-04:00 PICCORO McKAY Lenz :

> hi, any oklder than 5.2 will faild to build the kernel module again linux
> 4.7+ and in jessie/*stretch* there are kernels 4.7+ (4.9+ for backports
> and 4.15+)
>
> please remove it the virtualbox backport until a good package are
> available..
>
> also i can see that strecht not have a virtualbox normal package..
>
> *i think a debian release cannot be do if many important package are not
> available due broke upgrades!*
>
> an upgrade from jessie to strecht broke the setup of a virtualbox user!
>
> Lenz McKAY Gerardo (PICCORO)
> http://qgqlochekone.blogspot.com
>

Processed: your mail

[Debian Bug Tracking System]

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

> severity 897071 grave
Bug #897071 [texmaker] texmaker does notr start "symbol lookup error" and 
"undefined symbol: synctex_next_result"
Severity set to 'grave' from 'important'
> severity 896656 grave
Bug #896656 [texmaker] texmaker: Texmaker fails to start due to new libsynctex1
Severity set to 'grave' from 'important'
> merge 897071 896656
Bug #897071 [texmaker] texmaker does notr start "symbol lookup error" and 
"undefined symbol: synctex_next_result"
Bug #896656 [texmaker] texmaker: Texmaker fails to start due to new libsynctex1
Merged 896656 897071
> thanks
Stopping processing here.

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

Bug#897597: Bug #897597 in casync marked as pending

[fsateler]

Control: tag -1 pending

Hello,

Bug #897597 in casync 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/systemd-team/casync/commit/41080a73a8c2785318ab1c718f19e87b1f017bce


Add udev Build-Depends to be able to query udev.pc

Closes: #897597



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/897597

Processed: Bug #897597 in casync marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #897597 [casync] udev rules installed into wrong path
Added tag(s) pending.

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

Bug#895782: please remove or update to 5.2.X both sources, dkms and gui/cli

[PICCORO McKAY Lenz]

hi, any oklder than 5.2 will faild to build the kernel module again linux
4.7+ and in jessie/*stretch* there are kernels 4.7+ (4.9+ for backports and
4.15+)

please remove it the virtualbox backport until a good package are
available..

also i can see that strecht not have a virtualbox normal package..

*i think a debian release cannot be do if many important package are not
available due broke upgrades!*

an upgrade from jessie to strecht broke the setup of a virtualbox user!

Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com

Bug#896414: marked as done (python3-fswrap: fswrap fails to import)

[Debian Bug Tracking System]

Your message dated Thu, 03 May 2018 13:35:27 +
with message-id 
and subject line Bug#896414: fixed in python-fswrap 1.0.1-0.2
has caused the Debian Bug report #896414,
regarding python3-fswrap: fswrap fails to import
to be marked as done.

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

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


-- 
896414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896414
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-fswrap
Version: 1.0.1-0.1
Severity: serious
User: helm...@debian.org
Usertags: python-import

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

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/fswrap.py", line 14, in 
from distutils import dir_util
ImportError: cannot import name 'dir_util'

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

Helmut
--- End Message ---
--- Begin Message ---
Source: python-fswrap
Source-Version: 1.0.1-0.2

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

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

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

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated python-fswrap 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, 03 May 2018 15:06:12 +0200
Source: python-fswrap
Binary: python-fswrap python3-fswrap
Architecture: source
Version: 1.0.1-0.2
Distribution: unstable
Urgency: medium
Maintainer: Julien Danjou 
Changed-By: Andrej Shadura 
Description:
 python-fswrap - unified object oriented interface to file system objects
 python3-fswrap - unified object oriented interface to file system objects 
(Python
Closes: 896414
Changes:
 python-fswrap (1.0.1-0.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Enable autopkgtest.
   * Add missing python3-distutils dependency (Closes: #896414).
   * Update Vcs-* to point to Salsa.
Checksums-Sha1:
 075bb9984330bf46c7a3449404e295ade160d21b 1867 python-fswrap_1.0.1-0.2.dsc
 ec97c34c120461b8bd0f60ebccc16bca29e1bc88 2224 
python-fswrap_1.0.1-0.2.debian.tar.xz
Checksums-Sha256:
 afcce94fa453ead86cb1b3b625b26b47db65eb18f5022c3fe33362b5278abdcf 1867 
python-fswrap_1.0.1-0.2.dsc
 d6cea103b5513da9fe493afa2a8c7118f42bee83122a5bf253a616348456af3c 2224 
python-fswrap_1.0.1-0.2.debian.tar.xz
Files:
 563edb89d41e7898be21b49c6b0a0e33 1867 python extra python-fswrap_1.0.1-0.2.dsc
 2330d7a42183e0d349d614059231ea8e 2224 python extra 
python-fswrap_1.0.1-0.2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAlrrC3cACgkQXkCM2RzY
OdL+NggAm/WQ2sNMwUKVtZNtY0e2vjTeLEIM7XPMGWrMuwQDM8sG//FOcaPWXw0J
sdn28pr0d7aeKu4rZ4oonfC7xa3HP7xDxhguH1shZA8rzOc4u46o6LB0kGlyvkz9
5NVrSSrptKG3I+PL8T4dxNsJPBsWkAga6URQFANa19mor5Yns7pb64f3ZeAQBeed
6RvLQiYkmRpUjHJsHfajPMLbCMc2SUgt70WNo9UaXiGiiGVVvbB6PbyJxwO3GY2v
xMyEQPIJC1400MTA5I3uUa5OLZdFIjAtNNXl/I99Zjcd/1sJzPqHMsoWRrx6+ixg
n/sHobP6rotQsi0BWByjPQtNu7F9cQ==
=kNCp
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#896485: FTBFS with sphinx 1.7.2: exception: cannot import name 'Directive'

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +patch
Bug #896485 {Done: Ondrej Novy } [src:alembic] FTBFS with 
sphinx 1.7.2: exception: cannot import name 'Directive'
Added tag(s) patch.

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

Bug#896485: FTBFS with sphinx 1.7.2: exception: cannot import name 'Directive'

[Stuart Prescott]

Control: tags -1 +patch

Attached is a patch that fixes this FTBFS; the offending import is no longer 
needed and so just deleting the line is enough to solve the bug. (This is 
fixed in a similar fashion upstream along with a few other changes to 
numpydoc.)

cheers
Stuart

-- 
Stuart Prescotthttp://www.nanonanonano.net/   stu...@nanonanonano.net
Debian Developer   http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7From 4f08d02c13dc4aa98e31f2e9ba58bc065712da45 Mon Sep 17 00:00:00 2001
From: Stuart Prescott 
Date: Thu, 3 May 2018 23:09:56 +1000
Subject: [PATCH 2/2] Remove unneeded import from numpydoc to fix FTBFS

(Closes: #896633)
---
 debian/changelog|  1 +
 debian/patches/numpydoc-directive.patch | 10 ++
 debian/patches/series   |  1 +
 3 files changed, 12 insertions(+)
 create mode 100644 debian/patches/numpydoc-directive.patch

diff --git a/debian/changelog b/debian/changelog
index 891b035..9a08cba 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -8,6 +8,7 @@ python-numpy (1:1.13.3-3) UNRELEASED; urgency=medium
 
   [ Stuart Prescott ]
   * add debhelper sequence to support --with numpy,numpy3
+  * Remove unneeded import in numpydoc, fixing FTBFS (Closes: #896633)
 
  -- Ondřej Nový   Tue, 13 Feb 2018 10:05:23 +0100
 
diff --git a/debian/patches/numpydoc-directive.patch b/debian/patches/numpydoc-directive.patch
new file mode 100644
index 000..72eb865
--- /dev/null
+++ b/debian/patches/numpydoc-directive.patch
@@ -0,0 +1,10 @@
+--- a/doc/sphinxext/numpydoc/numpydoc.py
 b/doc/sphinxext/numpydoc/numpydoc.py
+@@ -29,7 +29,6 @@
+ raise RuntimeError("Sphinx 1.0.1 or newer is required")
+ 
+ from .docscrape_sphinx import get_doc_object, SphinxDocString
+-from sphinx.util.compat import Directive
+ 
+ if sys.version_info[0] >= 3:
+ sixu = lambda s: s
diff --git a/debian/patches/series b/debian/patches/series
index 3e2b507..fa55b09 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,3 +1,4 @@
+numpydoc-directive.patch
 03_force_f2py_version.patch
 10_use_local_python.org_object.inv_sphinx.diff
 python3-soabi.patch
-- 
2.11.0

Bug#897466: bart-view: FTBFS: multind.h:17:10: fatal error: misc/nested.h: No such file or directory

[Uecker, Martin]

Hi Andreas,

we will need to re-upload the bart package 
to export the missing files. I will prepare a new
upload.

Best,
Martin

Am Donnerstag, den 03.05.2018, 12:07 +0200 schrieb Andreas Tille:
> Hi Martin,
> 
> can you please have a look?
> 
> Kind regards
> 
>  Andreas.
> 
> On Wed, May 02, 2018 at 09:55:11PM +0200, Lucas Nussbaum wrote:
> > Source: bart-view
> > Version: 0.1.00-1
> > Severity: serious
> > Tags: buster sid
> > User: debian...@lists.debian.org
> > Usertags: qa-ftbfs-20180502 qa-ftbfs
> > Justification: FTBFS on amd64
> > 
> > Hi,
> > 
> > During a rebuild of all packages in sid, your package failed to
> > build on
> > amd64.
> > 
> > Relevant part (hopefully):
> > > cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-
> > > protector-strong -Wformat -Werror=format-security -std=c11
> > > -fopenmp -export-dynamic -o view -I/usr/include/bart/ `pkg-config 
> > > --cflags gtk+-3.0` src/main.c src/view.c src/draw.c `pkg-config
> > > --libs gtk+-3.0` /usr/lib/bart//libmisc.a /usr/lib/bart//libnum.a
> > > -lm -lpng
> > > In file included from src/view.c:24:0:
> > > /usr/include/bart/num/multind.h:17:10: fatal error:
> > > misc/nested.h: No such file or directory
> > >  #include "misc/nested.h"
> > >   ^~~
> > > compilation terminated.
> > > make[1]: *** [Makefile:52: view] Error 1
> > 
> > The full build log is available from:
> >    http://aws-logs.debian.net/2018/05/02/bart-view_0.1.00-1_unstabl
> > e.log
> > 
> > A list of current common problems and possible solutions is
> > available at
> > http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to
> > contribute!
> > 
> > About the archive rebuild: The rebuild was done on EC2 VM instances
> > from
> > Amazon Web Services, using a clean, minimal and up-to-date chroot.
> > Every
> > failed build was retried once to eliminate random failures.
> > 
> > ___
> > Debian-med-packaging mailing list
> > debian-med-packag...@alioth-lists.debian.net
> > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med
> > -packaging
> 
> 

Bug#887951: marked as done (Build-Depends on deprecated libnm-glib/libnm-gtk libraries)

[Debian Bug Tracking System]

Your message dated Thu, 03 May 2018 13:04:54 +
with message-id 
and subject line Bug#887951: fixed in network-manager-strongswan 1.4.3-2
has caused the Debian Bug report #887951,
regarding Build-Depends on deprecated libnm-glib/libnm-gtk libraries
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.)


-- 
887951: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887951
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: network-manager-strongswan
Version: 1.4.2-1
Severity: important
User: pkg-utopia-maintain...@lists.alioth.debian.org
Usertags: libnm

Hi,

your package declares a Build-Depends on the deprecated
libnm-glib/libnm-gtk libraries via

PKG_CHECK_MODULES(LIBNM_GLIB, NetworkManager >= 1.1.0 libnm-util libnm-glib 
libnm-glib-vpn)
PKG_CHECK_MODULES(LIBNM_GTK, libnm-gtk >= 1.1.0)

libnm-glib support was needed to support older versions of
gnome-shell. This is no longer the case with the
upload of gnome-shell 3.26.2-4.

Please consider disabling libnm-glib support in
network-manager-strongswan and dropping the Build-Depends on
 network-manager-dev
 libnm-util-dev
 libnm-glib-dev
 libnm-glib-vpn-dev
 libnm-gtk-dev

Disabling libnm-glib also means no longer installing
/etc/NetworkManager/VPN/nm-strongswan-service.name.
Please make sure to remove that conffile on upgrades.

I've made similar changes to the pkg-utopia maintainer VPN plugins like
in 
https://anonscm.debian.org/git/pkg-utopia/network-manager-openvpn.git/commit/?id=76c6d69f657cb815ab5ed8a7f9babb714d83b62c
https://anonscm.debian.org/git/pkg-utopia/network-manager-openvpn.git/commit/?id=063fea54cad1abd303bb4ec0f295d82db0aba95a

I notice that network-manager-strongswan does not provide a
--without-libnm-glib switch. You should ask upstream to provide such a
switch, the alternative is to patch configure.ac/Makefile.am yourself.

Regards,
Michael



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

Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), 
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: network-manager-strongswan
Source-Version: 1.4.3-2

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

Debian distribution maintenance software
pp.
Harald Dunkel  (supplier of updated network-manager-strongswan 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 30 Apr 2018 16:44:16 +0200
Source: network-manager-strongswan
Binary: network-manager-strongswan
Architecture: source
Version: 1.4.3-2
Distribution: unstable
Urgency: medium
Maintainer: Harald Dunkel 
Changed-By: Harald Dunkel 
Description:
 network-manager-strongswan - network management framework (strongSwan plugin)
Closes: 887951
Changes:
 network-manager-strongswan (1.4.3-2) unstable; urgency=medium
 .
   * new upstream version 1.4.3
   * drop deprecated libnm-glib/libnm-gtk libraries (Closes: #887951)
   * Don't rely on NetworkManager.pc for paths when building without
 libnm-glib
   * skip revision 1.4.3-1, due to problems discovered during review.
Checksums-Sha1:
 ef4f6a14493045a06cb148eef50bb0423d753d11 1863 
network-manager-strongswan_1.4.3-2.dsc
 f53b045a7de11570ff257c9afc09a967cf572078 305195 
network-manager-strongswan_1.4.3.orig.tar.bz2
 9e46c699b8034add7c7ccdac518ca98be4a2107b 3988 
network-manager-strongswan_1.4.3-2.debian.tar.xz
Checksums-Sha256:
 806255b3e56d73143b2c949b3a31733f3c42a89e7b48b0ebdfe79f982a6b4708 1863 
network-manager-strongswan_1.4.3-2.dsc
 542811171fd3c97bc5cda6af12e154461f1f699f86141d966c020b58b928f44b 305195 
network-manager-strongswan_1.4.3.orig.tar.bz2
 8817d46e0ef3e2b7c2618b0afcfd6d7de4fbb059b150d7d9e38a3f2183e3495b 3988 

Bug#897592: ebtables: randomly FTBFS - makefile is not parallel safe

[Arturo Borrero Gonzalez]

On 3 May 2018 at 12:07, James Cowgill  wrote:
> When parallel builds are enabled, the "scripts" and "exec" targets will
> be run in parallel which fails because:
> - exec does not create $(DESTDIR)$(BINDIR) so will fail if scripts has
> not created it yet.
> - exec copies ebtables-save_ which will also fail if scripts has not
> created it yet.
>

Thanks James :-)

your report saved us valuable time investigating the issue by ourselves.

May I ask you to send a patch? That would be awesome, we always
welcome help in the pkg-netfilter team.

Bug#897479: marked as done (appindicator3-sharp: FTBFS: generated.c:4:10: fatal error: libappindicator/app-indicator.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Thu, 03 May 2018 12:49:39 +
with message-id 
and subject line Bug#897479: fixed in appindicator3-sharp 12.10.0+git20151221-5
has caused the Debian Bug report #897479,
regarding appindicator3-sharp: FTBFS: generated.c:4:10: fatal error: 
libappindicator/app-indicator.h: No such file or directory
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.)


-- 
897479: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897479
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: appindicator3-sharp
Version: 12.10.0+git20151221-4
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20180502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> /bin/bash ../../libtool  --tag=CC   --mode=compile gcc 
> -DPACKAGE_NAME=\"appindicator3-sharp\" 
> -DPACKAGE_TARNAME=\"appindicator3-sharp\" -DPACKAGE_VERSION=\"12.10.0\" 
> -DPACKAGE_STRING=\"appindicator3-sharp\ 12.10.0\" -DPACKAGE_BUGREPORT=\"\" 
> -DPACKAGE_URL=\"\" -DPACKAGE=\"appindicator3-sharp\" -DVERSION=\"12.10.0\" 
> -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 
> -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 
> -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" 
> -I.  -pthread -I/usr/include/libayatana-appindicator3-0.1 
> -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/gtk-3.0 
> -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
> -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
> -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo 
> -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
> -I/usr/include/fribidi -I/usr/include/atk-1.0 -I/usr/include/cairo 
> -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 
> -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I../.. 
> -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
> -fdebug-prefix-map=/<>/appindicator3-sharp-12.10.0+git20151221=. 
> -fstack-protector-strong -Wformat -Werror=format-security -c -o generated.lo 
> generated.c
> libtool: compile:  gcc -DPACKAGE_NAME=\"appindicator3-sharp\" 
> -DPACKAGE_TARNAME=\"appindicator3-sharp\" -DPACKAGE_VERSION=\"12.10.0\" 
> "-DPACKAGE_STRING=\"appindicator3-sharp 12.10.0\"" -DPACKAGE_BUGREPORT=\"\" 
> -DPACKAGE_URL=\"\" -DPACKAGE=\"appindicator3-sharp\" -DVERSION=\"12.10.0\" 
> -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 
> -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 
> -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" 
> -I. -pthread -I/usr/include/libayatana-appindicator3-0.1 
> -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/gtk-3.0 
> -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
> -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
> -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo 
> -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
> -I/usr/include/fribidi -I/usr/include/atk-1.0 -I/usr/include/cairo 
> -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 
> -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I../.. 
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -fdebug-prefix-map=/<>/appindicator3-sharp-12.10.0+git20151221=. 
> -fstack-protector-strong -Wformat -Werror=format-security -c generated.c  
> -fPIC -DPIC -o .libs/generated.o
> generated.c:4:10: fatal error: libappindicator/app-indicator.h: No such file 
> or directory
>  #include 
>   ^
> compilation terminated.
> make[2]: *** [Makefile:474: generated.lo] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/2018/05/02/appindicator3-sharp_12.10.0+git20151221-4_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: appindicator3-sharp

Bug#897597: udev rules installed into wrong path

[Michael Biebl]

Package: casync
Version: 2+20180321-1
Severity: serious

It seems we install the udev rules file into the wrong path as

 usr/rules.d/75-casync.rules

This happens because meson.build contains
 udevdir = dependency('udev', required : 
false).get_pkgconfig_variable('udevdir')
 udevrulesdir = join_paths(udevdir, 'rules.d')
but in the build chroot there is no udev.pc (it's provided by the udev
package).
The simplest fix is to add a Build-Depends on udev.



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

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

Versions of packages casync depends on:
ii  libacl1  2.2.52-3+b1
ii  libc62.27-3
ii  libcurl3-gnutls  7.58.0-2
ii  libfuse2 2.9.7-1
ii  liblzma5 5.2.2-1.3
ii  libselinux1  2.7-2+b2
ii  libssl1.11.1.0h-2
ii  libudev1 238-4
ii  libzstd1 1.3.4+dfsg-2
ii  zlib1g   1:1.2.11.dfsg-1

casync recommends no packages.

casync suggests no packages.

-- no debconf information

Bug#897468: marked as done (osm-gps-map: FTBFS: osm-gps-map-track.h:93: Error: OsmGpsMap: identifier not found on the first line:)

[Debian Bug Tracking System]

Your message dated Thu, 03 May 2018 12:05:28 +
with message-id 
and subject line Bug#897468: fixed in osm-gps-map 1.1.0-3
has caused the Debian Bug report #897468,
regarding osm-gps-map: FTBFS: osm-gps-map-track.h:93: Error: OsmGpsMap: 
identifier not found on the first line:
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.)


-- 
897468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897468
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: osm-gps-map
Version: 1.1.0-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20180502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> g-ir-scanner: link: /bin/bash ../libtool --mode=link --tag=CC gcc -o 
> /<>/src/tmp-introspectz4uenqyy/OsmGpsMap-1.0 -export-dynamic 
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security 
> -UGDK_DISABLE_DEPRECATED 
> /<>/src/tmp-introspectz4uenqyy/OsmGpsMap-1.0.o -L. 
> libosmgpsmap-1.0.la -lgio-2.0 -lgobject-2.0 -Wl,--export-dynamic 
> -lgmodule-2.0 -pthread -lglib-2.0 -Wl,-z,relro -Wl,-z,now
> libtool: link: gcc -o 
> /<>/src/tmp-introspectz4uenqyy/.libs/OsmGpsMap-1.0 -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security 
> -UGDK_DISABLE_DEPRECATED 
> /<>/src/tmp-introspectz4uenqyy/OsmGpsMap-1.0.o 
> -Wl,--export-dynamic -pthread -Wl,-z -Wl,relro -Wl,-z -Wl,now 
> -Wl,--export-dynamic  -L. ./.libs/libosmgpsmap-1.0.so -lgio-2.0 -lgobject-2.0 
> -lgmodule-2.0 -lglib-2.0 -pthread
> osm-gps-map-track.h:93: Error: OsmGpsMap: identifier not found on the first 
> line:
>  *
>   ^
> osm-gps-map-track.c:231: Warning: OsmGpsMap: incorrect number of parameters 
> in comment block, parameter annotations will be ignored.
> osm-gps-map-polygon.h:56: Warning: OsmGpsMap: osm_gps_map_polygon_get_track: 
> return value: Missing (transfer) annotation
> make[3]: Leaving directory '/<>/src'
> make[3]: Entering directory '/<>/src'
> /usr/bin/g-ir-compiler --includedir=. --includedir=. --includedir=. 
> OsmGpsMap-1.0.gir -o OsmGpsMap-1.0.typelib
> make[3]: Leaving directory '/<>/src'
> Making all in examples
> make[3]: Entering directory '/<>/examples'
> gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -I../src -Wall 
> -Wstrict-prototypes -Wnested-externs -Werror=missing-prototypes 
> -Werror=implicit-function-declaration -Werror=pointer-arith -Werror=init-self 
> -Werror=format-security -Werror=format=2 -Werror=missing-include-dirs 
> -Werror=return-type   -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/gtk-3.0 
> -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
> -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
> -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo 
> -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
> -I/usr/include/fribidi -I/usr/include/atk-1.0 -I/usr/include/cairo 
> -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 
> -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -I/usr/include/cairo -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 
> -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -pthread 
> -I/usr/include/libsoup-2.4 -I/usr/include/libxml2 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -UGDK_DISABLE_DEPRECATED -c -o 
> editable_track-editable_track.o `test -f 'editable_track.c' || echo 
> './'`editable_track.c
> make[3]: Leaving directory '/<>/examples'
> make[3]: Entering directory '/<>/examples'
> gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -I../src -Wall 
> -Wstrict-prototypes -Wnested-externs -Werror=missing-prototypes 
> -Werror=implicit-function-declaration -Werror=pointer-arith -Werror=init-self 
> -Werror=format-security -Werror=format=2 -Werror=missing-include-dirs 
> -Werror=return-type   -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/gtk-3.0 
> -I/usr/include/at-spi2-atk/2.0 

Processed: Re: Bug#892267: 3dldf: FTBFS on mips64el, hurd-i386, ia64, powerpc, x32 - "src/3dldf tngnts_1.ldf" segfaults

[Debian Bug Tracking System]

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

> forwarded 892267 https://savannah.gnu.org/bugs/?53821
Bug #892267 [src:3dldf] 3dldf: FTBFS on mips64el, hurd-i386, ia64, powerpc, x32 
- "src/3dldf tngnts_1.ldf" segfaults
Set Bug forwarded-to-address to 'https://savannah.gnu.org/bugs/?53821'.
> stop
Stopping processing here.

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

Bug#892267: 3dldf: FTBFS on mips64el, hurd-i386, ia64, powerpc, x32 - "src/3dldf tngnts_1.ldf" segfaults

[Hilmar Preuße]

forwarded 892267 https://savannah.gnu.org/bugs/?53821
stop

Am 07.03.2018 um 13:13 teilte James Cowgill mit:

Hi,


3dldf FTBFS on the above architectures with the error:

../src/3dldf tngnts_1.ldf
GNU 3DLDF Version 2.0.3
Copyright (C) 2013 The Free Software Foundation
Author:  Laurence D. Finston


Just for the records: I've forwarded the bug to upstream.

Hilmar
--
#206401 http://counter.li.org

Bug#897254: CVE-2018-9060

[Dirk Eddelbuettel]

On 3 May 2018 at 13:41, Moritz Muehlenhoff wrote:
| On Thu, May 03, 2018 at 06:33:50AM -0500, Dirk Eddelbuettel wrote:
| > They aren't quite sure how to get back CVE/Mitre now. Do you have any tips /
| > suggestions / HOWTOs ?
| 
| Best to use the https://cveform.mitre.org/ form:
| "Select a request type" -> "Request and update to an existing CVE entry" and
| for "Type of update requested" select "Update description". Those are usually
| processed within a working day.

Excellent, thank you -- I passed that on.

Dirk

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#897493: marked as done (paleomix: FTBFS: dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Thu, 03 May 2018 11:50:40 +
with message-id 
and subject line Bug#897493: fixed in paleomix 1.2.13.2-1
has caused the Debian Bug report #897493,
regarding paleomix: FTBFS: dh_auto_test: pybuild --test --test-nose -i 
python{version} -p 2.7 returned exit code 13
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.)


-- 
897493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897493
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: paleomix
Version: 1.2.12-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20180502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # apply fix that seems to be needed due to improperly set
> # time zone in pbuilder
> sed -i~ 's/"MTime": "2005-07-07 08:50:00"/"MTime": "2005-07-07 06:50:00"/' 
> tests/common_tests/makefile_test.py
> PATH=/<>/bin/:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
>  dh_auto_test
> I: pybuild base:217: cd /<>/.pybuild/cpython2_2.7/build; 
> python2.7 -m nose 
> --exclude='(test_requirementobj__version__command_not_executable)'
> F.F..F.
> ==
> FAIL: atomiccmd_test.builder_test.test_java_builder__default__no_config
> --
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
> self.test(*self.arg)
>   File 
> "/<>/.pybuild/cpython2_2.7/build/tests/atomiccmd_test/builder_test.py",
>  line 534, in test_java_builder__default__no_config
> "-jar", "%(AUX_JAR)s"])
> AssertionError: Lists differ: ['java', '-server', '-Djava.io... != ['java', 
> '-server', '-Djava.io...
> 
> First differing element 5:
> '-jar'
> '-Xmx4g'
> 
> Second list contains 1 additional elements.
> First extra element 7:
> '%(AUX_JAR)s'
> 
>   ['java',
>'-server',
>'-Djava.io.tmpdir=%(TEMP_DIR)s',
>'-Djava.awt.headless=true',
>'-XX:+UseSerialGC',
> +  '-Xmx4g',
>'-jar',
>'%(AUX_JAR)s']
> 
> ==
> FAIL: atomiccmd_test.builder_test.test_java_builder__defaults__call
> --
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
> self.test(*self.arg)
>   File 
> "/<>/.pybuild/cpython2_2.7/build/tests/atomiccmd_test/builder_test.py",
>  line 545, in test_java_builder__defaults__call
> "-jar", "%(AUX_JAR)s"])
> AssertionError: Lists differ: ['java', '-server', '-Djava.io... != ['java', 
> '-server', '-Djava.io...
> 
> First differing element 5:
> '-jar'
> '-Xmx4g'
> 
> Second list contains 1 

Bug#876120: marked as done (FTBFS: gtkdoc-mktmpl: command not found)

[Debian Bug Tracking System]

Your message dated Thu, 03 May 2018 11:50:27 +
with message-id 
and subject line Bug#876120: fixed in oath-toolkit 2.6.1-1.1
has caused the Debian Bug report #876120,
regarding FTBFS: gtkdoc-mktmpl: command not found
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.)


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


>From my buildlog (trying to build oath-toolkit with xmlsec 1.2.25
using ratt):

[...]
Selecting previously unselected package gtk-doc-tools.
Preparing to unpack .../49-gtk-doc-tools_1.26-1_all.deb ...
Unpacking gtk-doc-tools (1.26-1) ...
[...]
checking for gtkdoc-check... /usr/bin/gtkdoc-check
checking for gtkdoc-rebase... /usr/bin/gtkdoc-rebase
checking for gtkdoc-mkpdf... /usr/bin/gtkdoc-mkpdf
checking whether to build gtk-doc documentation... yes
[...]
aking all in gtk-doc
make[5]: Entering directory '/<>/liboath/gtk-doc'
  DOC   Scanning header files
  DOC   Rebuilding template files
/bin/bash: gtkdoc-mktmpl: command not found
Makefile:1412: recipe for target 'tmpl-build.stamp' failed
make[5]: *** [tmpl-build.stamp] Error 127
make[5]: Leaving directory '/<>/liboath/gtk-doc'
Makefile:1392: recipe for target 'all-recursive' failed
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory '/<>/liboath'
Makefile:1204: recipe for target 'all' failed
make[3]: *** [all] Error 2
make[3]: Leaving directory '/<>/liboath'
Makefile:401: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/<>'
Makefile:357: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/<>'
/usr/share/cdbs/1/class/makefile.mk:77: recipe for target 
'debian/stamp-makefile-build' failed
make: *** [debian/stamp-makefile-build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

Build finished at 2017-09-18T16:15:32Z

Did it move to an other package?

Regards,

Rene

-- System Information:
Debian Release: 8.9
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: armhf (armv7l)

Kernel: Linux 3.18.0-trunk-rpi2 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: oath-toolkit
Source-Version: 2.6.1-1.1

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

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

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated oath-toolkit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 15 Apr 2018 21:19:41 +0300
Source: oath-toolkit
Binary: liboath-dev liboath0 oathtool oath-dbg libpam-oath
Architecture: source
Version: 2.6.1-1.1
Distribution: unstable
Urgency: medium
Maintainer: OATH Toolkit Team 
Changed-By: Adrian Bunk 
Description:
 liboath-dev - Development files for the OATH Toolkit Liboath library
 liboath0   - OATH Toolkit Liboath library
 libpam-oath - OATH Toolkit libpam_oath PAM module
 oath-dbg   - OATH Toolkit debugging symbols
 oathtool   - OATH Toolkit oathtool command line tool
Closes: 876120
Changes:
 oath-toolkit (2.6.1-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Update gtk-doc files, fixing FTBFS with gtk-doc-tools >= 1.26.
 (Closes: #876120)
Checksums-Sha1:
 1d629d1350ae0e52602dbbfd52ea02e6499690e6 2256 oath-toolkit_2.6.1-1.1.dsc
 726e6dfd26324e608c8082c50b3431708975ef02 19872 
oath-toolkit_2.6.1-1.1.debian.tar.xz
Checksums-Sha256:
 bd122f2eced67fffa06bd1359c19f08c930e1cbcc92efa3b28a149e9cf8e2072 2256 
oath-toolkit_2.6.1-1.1.dsc
 aeeace61d03441d175eab26a779fdeba5072cf99f64f0deb4699164c567cb6e4 19872 
oath-toolkit_2.6.1-1.1.debian.tar.xz
Files:
 

Bug#876594: marked as done (dee FTBFS with gtk-doc-tools 1.26: gtkdoc-mktmpl is no longer available)

[Debian Bug Tracking System]

Your message dated Thu, 03 May 2018 11:49:39 +
with message-id 
and subject line Bug#876594: fixed in dee 1.0.10-3.2
has caused the Debian Bug report #876594,
regarding dee FTBFS with gtk-doc-tools 1.26: gtkdoc-mktmpl is no longer 
available
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.)


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

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

...
Making all in dee-1.0
make[5]: Entering directory '/build/1st/dee-1.0.10/doc/reference/dee-1.0'
  DOC   Scanning header files
  DOC   Introspecting gobjects
  DOC   Rebuilding template files
/bin/bash: gtkdoc-mktmpl: command not found
Makefile:677: recipe for target 'tmpl-build.stamp' failed
make[5]: *** [tmpl-build.stamp] Error 127
--- End Message ---
--- Begin Message ---
Source: dee
Source-Version: 1.0.10-3.2

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 15 Apr 2018 21:46:01 +0300
Source: dee
Binary: libdee-1.0-4 libdee-dev libdee-1.0-4-dbg libdee-doc gir1.2-dee-1.0 
dee-tools
Architecture: source
Version: 1.0.10-3.2
Distribution: unstable
Urgency: medium
Maintainer: Kartik Mistry 
Changed-By: Adrian Bunk 
Description:
 dee-tools  - model to synchronize mutiple instances over DBus - tooling
 gir1.2-dee-1.0 - GObject introspection data for the Dee library
 libdee-1.0-4 - model to synchronize mutiple instances over DBus - shared lib
 libdee-1.0-4-dbg - model to synchronize mutiple instances over DBus
 libdee-dev - model to synchronize mutiple instances over DBus - dev files
 libdee-doc - model to synchronize mutiple instances over DBus - documentation
Closes: 876594
Changes:
 dee (1.0.10-3.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Update gtk-doc files, fixing FTBFS with gtk-doc-tools >= 1.26.
 (Closes: #876594)
Checksums-Sha1:
 0c593aa970079dc60e5c158b8b4d30271a9e02fe 2323 dee_1.0.10-3.2.dsc
 bca9e76b6126fe4ae8482ac3bc67610da095cc75 13744 dee_1.0.10-3.2.debian.tar.xz
Checksums-Sha256:
 6878459e1d6992b1338e95a9c2c4703969863e4ed334adc34dbb99b5f5c456c7 2323 
dee_1.0.10-3.2.dsc
 24c8c22e612e2adcaf2bc9fb1e96c6afeb6f21fa8a054559f2dd1622e5812c4d 13744 
dee_1.0.10-3.2.debian.tar.xz
Files:
 7652756df30a09e05a64ddcfbade3479 2323 libs optional dee_1.0.10-3.2.dsc
 49f101c7e1a0780cbfbeeabd5f1463c6 13744 libs optional 
dee_1.0.10-3.2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlrTnrwACgkQiNJCh6LY
mLEGQxAAxwxknpPAefDEdfihm7OO2QcIghLBGxoUpI1yU0cg7exab7/ptZO2F1Ab
c+7ktsi8evt6CQmbOoEXGaJC8lRIaKRIVJIcCVVIyHzdT7BuUsk4Jasr/XSHegW5
RPPFmFS4UxAP0YYDC9AEcxNIZLs3GmXC337jDZs6k/988iuCGAUDiMhtvZ1lO68H
JXmhqo6eZgeenyXXT4eyqSVQib0qy019U2YjGA/ZQhYGHaj+nn75LCN4+pAyQaXv
/TNRDhiD95bQOp7xRja5RWaMvd9R8JNyHpdOH8zrnMDircRgliKAj/HKJ00h1qiX
LoogD2eMz8cV9pbROKa3rBKzK3Q4ZBEckDCEuirFV4G2iI3LFSts9bY4dGcTY5fk
CHlN2lMtGHLxSEliu7Vu0739EFPWIoejJQehNUvytRJTdg4yWGW8pqpfjubyRtoV
bRKSHalTh6uUbzyJWUY+hL4OiTbdGMBEbaL0cQwIeW1ORF718jJhqgs/f843481S
CZbBZhGT6MpcwRrdR0VbzUcuWkbtdEP2sAQqGUj1GunHSOqzreTsoKOrsl2O3f2+
/OpxL48SZS8qeefULTuBMOv9lSB3AOLA1JHCkrmXWWBsI+WpE5RoZg5w2dDpbs1p
mDo/IYeQZEmfhmHI8qPZVSFm1llHhVPjLE1u5v2Vjko0UxO/gNk=
=5iW7
-END PGP SIGNATURE End Message ---

Bug#893861: thawab: Intent to remove from Debian

[Jeremy Bicha]

Final warning.

If we don't hear back immediately, I will be converting this bug into
a Debian removal bug for thawab very soon.

Thanks,
Jeremy Bicha

Bug#869990: marked as done (madness FTBFS with cmake 3.9.0)

[Debian Bug Tracking System]

Your message dated Thu, 03 May 2018 11:50:06 +
with message-id 
and subject line Bug#869990: fixed in madness 0.10.1~gite4aa500e-10.1
has caused the Debian Bug report #869990,
regarding madness FTBFS with cmake 3.9.0
to be marked as done.

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

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


-- 
869990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869990
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: madness
Version: 0.10.1~gite4aa500e-10
Severity: serious
Tags: buster sid

https://buildd.debian.org/status/fetch.php?pkg=madness=armel=0.10.1~gite4aa500e-10=1501199307=0
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/madness.html

...
-- Found PythonInterp: /usr/bin/python (found version "2.7.13") 
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE  
-- Found MPI_C: /usr/lib/arm-linux-gnueabi/libmpich.so  
-- Found MPI_CXX: 
/usr/lib/arm-linux-gnueabi/libmpichcxx.so;/usr/lib/arm-linux-gnueabi/libmpich.so
  
CMake Error at cmake/modules/FindMKL.cmake:43 (else):
  A duplicate ELSE command was found inside an IF block.
Call Stack (most recent call first):
  external/lapack.cmake:8 (find_package)
  CMakeLists.txt:495 (include)


-- Configuring incomplete, errors occurred!
--- End Message ---
--- Begin Message ---
Source: madness
Source-Version: 0.10.1~gite4aa500e-10.1

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 20 Apr 2018 22:29:45 +0300
Source: madness
Binary: libmadness-dev
Architecture: source
Version: 0.10.1~gite4aa500e-10.1
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Adrian Bunk 
Description:
 libmadness-dev - Numerical Environment for Scientific Simulation (development 
file
Closes: 869990
Changes:
 madness (0.10.1~gite4aa500e-10.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix FTBFS with >= 3.9.0. (Closes: #869990)
Checksums-Sha1:
 18bd8035d8a4a51f3ec389a919073d66de01712f 2154 
madness_0.10.1~gite4aa500e-10.1.dsc
 500957315fcf5388d09630f66da1217d7879fa3f 8384 
madness_0.10.1~gite4aa500e-10.1.debian.tar.xz
Checksums-Sha256:
 13fb9930cef2f8ac4c1054f9b5afb40b3110d64702872d4ebfa449bd2d3d9c7e 2154 
madness_0.10.1~gite4aa500e-10.1.dsc
 51eb70e0a5553c70b2af4527d850d2a8c62fa6fe4ac98f3509bd9b4fd3adbb05 8384 
madness_0.10.1~gite4aa500e-10.1.debian.tar.xz
Files:
 d3c3d2ecf4f65fe852ac9b652aef346b 2154 libdevel optional 
madness_0.10.1~gite4aa500e-10.1.dsc
 7657aa309684dd84dcef265dc39caa76 8384 libdevel optional 
madness_0.10.1~gite4aa500e-10.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlraSIgACgkQiNJCh6LY
mLHG2A/+PWVvyVVUXMKU8WEo5UO81c7hSR0afpxfICwLuk0zaqMq3FuUfuqdXWWC
CMhOFUqEdexI2nMqVfJlNbxS85PMa8x343WNXOkwf4uakIY3dirIhoYiKc0TXYUE
r/KxHjrzihR/WQPN1w7R95EJOT6kwkMA8yoXbmLGlE7no0hNN1D+o0KKt298T0Za
lg/vypalheA9xVl6vPgoQH+0Vh/oMmqu1cuo4YvYJx8tNAbuXPv7I5vtLjRPyCd4
wvd3tDeHg2CsJs+oM/IXbmAccYLZzXP0ZXSE9OCn5xel53jhBPO81ASyMxoplIOg
4yIlMq6NkrCv0NSvXDiuYulyo1Duvy4hzrFp5OZ8BTEa0R4L5LKuwWG0Ro+dGGUA
2acYiDdxcl/I74IODlujsdpqzWeFAQYEiPpREu7Ik8kYJ/ThyzOUTQwIA4zLZ/Yq
YjqOPhaf19naIenDmiNwUzfk8rWP8Q9LIBpAHU2Yo1sToVuuP21So0cGTjeP+7Kl
OYPJXDM/Xk3cw/nii3SqPkLlOK5wLyPd8tkOjLzHR79q70PsJJnPZvS0UaGjncza
wpTpdWTfyWq8nzWXjyEqoIozYv9EEQL3SEZOKhv1Y9ifi8bZetgbBgKpziSF6nXx
gfhTcpEhvI5G2h1IaDI9J0se+a6g2AHX6pEjzlkbka9O7VD1ASY=
=LfbC
-END PGP SIGNATURE End Message ---

Processed: convert synaesthesia bug to removal bug

[Debian Bug Tracking System]

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

> severity 891701 normal
Bug #891701 [synaesthesia] Intent to file removal bug for synaesthesia
Severity set to 'normal' from 'serious'
> reassign 891701 ftp.debian.org
Bug #891701 [synaesthesia] Intent to file removal bug for synaesthesia
Bug reassigned from package 'synaesthesia' to 'ftp.debian.org'.
No longer marked as found in versions synaesthesia/2.4-5.1.
Ignoring request to alter fixed versions of bug #891701 to the same values 
previously set
> retitle 891701 RM: synaesthesia -- RoQA; unmaintained, depends on esound
Bug #891701 [ftp.debian.org] Intent to file removal bug for synaesthesia
Changed Bug title to 'RM: synaesthesia -- RoQA; unmaintained, depends on 
esound' from 'Intent to file removal bug for synaesthesia'.
> thanks
Stopping processing here.

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

Bug#897254: CVE-2018-9060

[Moritz Muehlenhoff]

On Thu, May 03, 2018 at 06:33:50AM -0500, Dirk Eddelbuettel wrote:
> 
> Hi Moritz,
> 
> On 30 April 2018 at 23:54, Moritz Mühlenhoff wrote:
> | Hi Dirk,
> | 
> | On Mon, Apr 30, 2018 at 04:33:48PM -0500, Dirk Eddelbuettel wrote:
> | > There is no GUI in R on
> | > Linux (there used to be a Gnome1/Gtk one a lng time ago).
> | 
> | Ah, ok. I wasn't aware of that.
> | 
> | Even if we'd build some kind of GUI, tricking a user into manually pasting
> | an overly long string into a specific input box is quite a stretch for
> | labelling a bug a security issue
> 
> Upstream had the same sentiment ... but fixed it:
> 
>   
> https://github.com/wch/r-source/commit/c7263b067451b9cd553c4f42dd2b54b82689fbb4
> 
>   (that is the easier-to-use git mirror of their svn)

Thanks for confirming.
 
> They aren't quite sure how to get back CVE/Mitre now. Do you have any tips /
> suggestions / HOWTOs ?

Best to use the https://cveform.mitre.org/ form:
"Select a request type" -> "Request and update to an existing CVE entry" and
for "Type of update requested" select "Update description". Those are usually
processed within a working day.

Cheers,
Moritz

Bug#897590: linux-image-4.9.0-6-armmp: Missing CONFIG_MFD_TPS65217 may cause hardware damage

[Romain Perier]

Hello,

I have proposed a merge request for this at
https://salsa.debian.org/kernel-team/linux/merge_requests/12

Thanks,
Regards,
Romain

On Thu, May 03, 2018 at 10:03:14AM +, PA Nilsson wrote:
> Package: src:linux
> Version: 4.9.82-1+deb9u3
> Severity: grave 
> 
> Dear Maintainer,
> 
> When shutting down BeagleBoneBlack, running Debian 9.3, it was
> discovered that the system still draws excessive power and puts the
> system out of spec with possible hardware damage as a result.
> 
> This is due to the PMIC not shutting down correctly, as described by the
> referenced posts:
> http://bugs.elinux.org/issues/143
> https://groups.google.com/forum/#%21msg/beagleboard/7sxPePT7wkM/V1Ft-xxh0agJ
> 
> This in turn is due to the driver for the PMIC is not avaialble since
> CONFIG_MFD_TPS65217 is missing.
> 
> Setting CONFIG_MFD_TPS65217 will enable the correct shutdown procedure.
> 
> 
> 
> -- Package-specific info:
> ** Version:
> Linux version 4.9.0-6-armmp (debian-ker...@lists.debian.org) (gcc version 
> 6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02)
> 
> ** Command line:
> console=ttyO0,115200n8 root=/dev/mmcblk1p2 rw rootfstype=ext4 rootwait
> 
> ** Not tainted
> 
> ** Kernel log:
> Unable to read kernel log; any relevant messages should be attached
> 
> ** Model information
> Hardware  : Generic AM33XX (Flattened Device Tree)
> Revision  : 
> Device Tree model: TI AM335x BeagleBone Black
> 
> ** Loaded modules:
> dm_crypt
> dm_mod
> xts
> gf128mul
> algif_skcipher
> af_alg
> sd_mod
> sg
> uas
> usb_storage
> scsi_mod
> fuse
> snd_soc_simple_card
> snd_soc_simple_card_utils
> omap_aes
> omap_sham
> crypto_engine
> omap_rng
> rng_core
> tilcdc
> snd_soc_davinci_mcasp
> snd_soc_omap
> ledtrig_heartbeat
> omap_hwspinlock
> ledtrig_timer
> tda998x
> hwspinlock_core
> snd_soc_core
> snd_pcm_dmaengine
> snd_pcm
> drm_kms_helper
> snd_timer
> snd
> soundcore
> at24
> cppi41
> omap_wdt
> drm
> leds_gpio
> cpufreq_dt
> nvmem_core
> nf_conntrack_ipv4
> nf_defrag_ipv4
> xt_tcpudp
> xt_conntrack
> nf_conntrack
> iptable_filter
> ip_tables
> x_tables
> autofs4
> ext4
> crc16
> jbd2
> crc32c_generic
> fscrypto
> ecb
> mbcache
> smsc
> musb_dsps
> musb_hdrc
> udc_core
> davinci_mdio
> usbcore
> phy_am335x
> phy_generic
> usb_common
> phy_am335x_control
> ti_cpsw
> cpsw_ale
> cpsw_common
> davinci_cpdma
> omap_hsmmc
> musb_am335x
> 
> ** PCI devices:
> not available
> 
> ** USB devices:
> not available
> 
> 
> -- System Information:
> Debian Release: 9.4
>   APT prefers stable
>   APT policy: (500, 'stable')
> Architecture: armhf (armv7l)
> 
> Kernel: Linux 4.9.0-6-armmp (SMP w/1 CPU core)
> Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=C 
> (charmap=ANSI_X3.4-1968)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages linux-image-4.9.0-6-armmp depends on:
> ii  initramfs-tools [linux-initramfs-tool]  0.130
> ii  kmod23-2
> ii  linux-base  4.5
> 
> Versions of packages linux-image-4.9.0-6-armmp recommends:
> pn  firmware-linux-free  
> pn  irqbalance   
> 
> Versions of packages linux-image-4.9.0-6-armmp suggests:
> pn  debian-kernel-handbook  
> pn  linux-doc-4.9   
> 
> Versions of packages linux-image-4.9.0-6-armmp is related to:
> pn  firmware-amd-graphics 
> pn  firmware-atheros  
> pn  firmware-bnx2 
> pn  firmware-bnx2x
> pn  firmware-brcm80211
> pn  firmware-cavium   
> pn  firmware-intel-sound  
> pn  firmware-intelwimax   
> pn  firmware-ipw2x00  
> pn  firmware-ivtv 
> pn  firmware-iwlwifi  
> pn  firmware-libertas 
> pn  firmware-linux-nonfree
> pn  firmware-misc-nonfree 
> pn  firmware-myricom  
> pn  firmware-netxen   
> pn  firmware-qlogic   
> pn  firmware-realtek  
> pn  firmware-samsung  
> pn  firmware-siano
> pn  firmware-ti-connectivity  
> pn  xen-hypervisor
> 
> -- no debconf information

Processed: owner 897590

[Debian Bug Tracking System]

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

> owner 897590 !
Bug #897590 [src:linux] linux-image-4.9.0-6-armmp: Missing CONFIG_MFD_TPS65217 
may cause hardware damage
Owner recorded as romain.per...@gmail.com.
> thanks
Stopping processing here.

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

Bug#895742: marked as done (python-acidobasic should be named python3-acidobasic)

[Debian Bug Tracking System]

Your message dated Thu, 03 May 2018 11:00:13 +
with message-id 
and subject line Bug#895742: fixed in pyacidobasic 2.8-1
has caused the Debian Bug report #895742,
regarding python-acidobasic should be named python3-acidobasic
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.)


-- 
895742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895742
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-acidobasic
Version: 2.7-4
Severity: serious
Justification: violates python policy 3.3

The package python-acidobasic is wrongly named. It contains a Python 3.x
module. Python 2.x packages should carry a python- prefix while Python
3.x packages should carry a python3- prefix. Please rename the package
to python3-acidobasic.

Helmut
--- End Message ---
--- Begin Message ---
Source: pyacidobasic
Source-Version: 2.8-1

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

Debian distribution maintenance software
pp.
Georges Khaznadar  (supplier of updated pyacidobasic 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 23 Apr 2018 11:13:09 +0200
Source: pyacidobasic
Binary: pyacidobasic
Architecture: source all
Version: 2.8-1
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar 
Changed-By: Georges Khaznadar 
Description:
 pyacidobasic - simulation tool for acido-basic titrations
Closes: 895742
Changes:
 pyacidobasic (2.8-1) unstable; urgency=medium
 .
   * new upstream release.
   * renamed the binary package to pyacidobasic. It Closes: #895742,
 and it is not necessary to make a python3-acidobasic package since
 all python scripts are now under /usr/share/pyacidobasic. The new
 packages conflicts with, and replaces python-acidobasic.
   * upgraded Standards-Version to 4.1.4
Checksums-Sha1:
 fc79022aa5180c8bc160308c6545f1e9319a5f85 2007 pyacidobasic_2.8-1.dsc
 1dface32c2eab2ed3148512c1c4dfc36f183cb98 486840 pyacidobasic_2.8.orig.tar.xz
 a242aa8a20e9952f77add79e51c23a17c43ef071 4268 pyacidobasic_2.8-1.debian.tar.xz
 b8d06e7b58614e91fac413bd8623e7ccfe483d4c 56692 pyacidobasic_2.8-1_all.deb
 a49223fcfb688eb379f55c935a6f4c2694cd6108 11284 
pyacidobasic_2.8-1_amd64.buildinfo
Checksums-Sha256:
 33afd23a9d78a225e2d92314a414efd6a3329fcfbfab1d2843b1b1d0d0a3115d 2007 
pyacidobasic_2.8-1.dsc
 39a06294869c9f3ac71b4767cec223d0964c7fa7715dc3169ad1cdc7c2c52ad6 486840 
pyacidobasic_2.8.orig.tar.xz
 6bd32724b1c1bb858f12f286abc67a88056076bce24624675c909515809a57d9 4268 
pyacidobasic_2.8-1.debian.tar.xz
 e597391113e5e59c1ad9e95f3715dfd5f1f94830f09db950b163aafab7fc7781 56692 
pyacidobasic_2.8-1_all.deb
 24fc074db502a4eaa4bc5a7781b8e2efd1093e3a9e2923440c782bacdb957233 11284 
pyacidobasic_2.8-1_amd64.buildinfo
Files:
 6fb4f6208f8bb0c56a8609dfb5163cc2 2007 python extra pyacidobasic_2.8-1.dsc
 aa6dac1a1b563e89c9d34a8f711cfd51 486840 python extra 
pyacidobasic_2.8.orig.tar.xz
 d31aeec8e54aa40809a280dfc8b50bac 4268 python extra 
pyacidobasic_2.8-1.debian.tar.xz
 6ea7bc5c1f29281a558d70d62be3ffe9 56692 python extra pyacidobasic_2.8-1_all.deb
 9c717e4732435f765c6b6f0eebcd 11284 python extra 
pyacidobasic_2.8-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEM0CzZP9nFT+3zK6FHCgWkHE2rjkFAlrdu1cACgkQHCgWkHE2
rjnFqA//UAS41bzDCFVB31id0QnCRmE05vkXwPS/PwxJecaRUK5ZyPEv3xbSW9e0
yqCwsE4pxpCTm1XgrjArqSWrL19PGV9C9HfBloV+LjdQUrflz0nv/0MehdoiIt+4
2oOIzkma+UQbKmRqtAj8JLraAKnxBDaKh/phmPEJU+zoU+4YTamL8nu4JC6e0KYg
3lKmTgZqxphMkpqgEtnABma+3mswDBaX8JSQp/SUddwsghBlmZfW3xLDsxXyQZtD
xmrwP+FGH2DBb40URSCRDMTUnDFKmLWeJ7oXATJfJNSXbT2s23LEbybfDSEM6hMC
W3Spw/TfrUUJMjgE16B5pAxBSgJ8atmnjfuXv9te+uJMqTxLyWPOQITO7AjOmaWP
6zLNtfdSFV6P9OFPUqdKGe2Uu/1dq8inTXdfqA/ezZ1Hyl5jurd8/ZAiACFXypsX
Bp6IBamy4WHItuF/ADbitHpu3AgXDPJ7swNq2XfyzRea30go07DHv1wfM8YcYDqN
Q4Mg3ctwqW7f2/6f4YrqGm9XIX5tDCXff+DA8wxdHgjLsWLKbvMXLR4pYaAKm5Ln
6slIeK85zfdAaQEIk5wfXV2C+PAKX7HRkPBwdLXriQ1EXWfEJ7IAjQE0tQtzY7+u

Bug#897592: ebtables: randomly FTBFS - makefile is not parallel safe

[James Cowgill]

Source: ebtables
Version: 2.0.10.4-4
Severity: serious
Tags: sid buster

Hi,

ebtables randomly FTBFS during the install stage. Example on ppc64el:
>   make -j8 -Oline install DESTDIR=/<>/debian/ebtables 
> AM_UPDATE_INFO_DIR=no "INSTALL=install --strip-program=true"
> make[1]: Entering directory '/<>'
> mkdir -p /<>/debian/ebtables/etc
> make[1]: Leaving directory '/<>'
> make[1]: Entering directory '/<>'
> sed -e 's/$(VERSION)/2.0.10-4/' -e 's/$(DATE)/December\ 2011/' -e 
> 's/$(LOCKFILE)/\/run\/ebtables.lock/' ebtables.8 > ebtables.8_
> make[1]: Leaving directory '/<>'
> make[1]: Entering directory '/<>'
> install -m 0644 -o root -g root ethertypes 
> /<>/debian/ebtables/etc/ethertypes
> make[1]: Leaving directory '/<>'
> make[1]: Entering directory '/<>'
> mkdir -p /<>/debian/ebtables/lib/ebtables 
> /<>/debian/ebtables/etc/init.d 
> /<>/debian/ebtables/etc/default 
> /<>/debian/ebtables/usr/share/man/man8
> make[1]: Leaving directory '/<>'
> make[1]: Entering directory '/<>'
> cat ebtables-save | sed 's/__EXEC_PATH__/\/sbin/g' > ebtables-save_
> make[1]: Leaving directory '/<>'
> make[1]: Entering directory '/<>'
> mkdir -p /<>/debian/ebtables/sbin
> make[1]: Leaving directory '/<>'
> make[1]: Entering directory '/<>'
> install -m 0755 -o root -g root ebtables /<>/debian/ebtables/sbin
> install: cannot overwrite directory '/<>/debian/ebtables/sbin' 
> with non-directory
> make[1]: *** [Makefile:176: exec] Error 1
> make[1]: Leaving directory '/<>'
> make[1]: *** Waiting for unfinished jobs
> make[1]: Entering directory '/<>'
> cat ebtables.sysv | sed 's/__EXEC_PATH__/\/sbin/g' | sed 
> 's/__SYSCONFIG__/\/etc\/default/g' > ebtables.sysv_
> make[1]: Leaving directory '/<>'
> make[1]: Entering directory '/<>'
> if [ "/<>/debian/ebtables" != "" ]; then mkdir -p 
> /<>/debian/ebtables/etc/init.d; fi
> make[1]: Leaving directory '/<>'
> make[1]: Entering directory '/<>'
> cat ebtables-config | sed 's/__SYSCONFIG__/\/etc\/default/g' > 
> ebtables-config_
> make[1]: Leaving directory '/<>'
> make[1]: Entering directory '/<>'
> if [ "/<>/debian/ebtables" != "" ]; then mkdir -p 
> /<>/debian/ebtables/etc/default; fi
> make[1]: Leaving directory '/<>'
> dh_auto_install: make -j8 -Oline install 
> DESTDIR=/<>/debian/ebtables AM_UPDATE_INFO_DIR=no 
> "INSTALL=install --strip-program=true" returned exit code 2
> make: *** [debian/rules:4: binary-arch] Error 25

This happens because 2.0.10.4-4 enabled parallel builds (by virtue of
using dh compat 11), but the install part of the makefile is not safe to
run in parallel.

For example, in this case we have something like this (trimmed slightly):
> .PHONY: scripts
> scripts: ebtables-save ebtables.sysv ebtables-config
>   cat ebtables-save | sed 's/__EXEC_PATH__/$(tmp1)/g' > ebtables-save_
>   mkdir -p $(DESTDIR)$(BINDIR)
[...]
> .PHONY: exec
> exec: ebtables ebtables-restore
>   mkdir -p $(DESTDIR)$(LIBDIR) $(DESTDIR)$(INITDIR) 
> $(DESTDIR)$(SYSCONFIGDIR) $(DESTDIR)$(MANDIR)/man8
>   install -m 0755 -o root -g root $(PROGNAME) $(DESTDIR)$(BINDIR)
>   install -m 0755 -o root -g root ebtables-restore 
> $(DESTDIR)$(BINDIR)/ebtables-restore
>   install -m 0755 -o root -g root ebtables-save_ 
> $(DESTDIR)$(BINDIR)/ebtables-save
[...]
> .PHONY: install
> install: $(MANDIR)/man8/ebtables.8 $(DESTDIR)$(ETHERTYPESFILE) scripts exec

When parallel builds are enabled, the "scripts" and "exec" targets will
be run in parallel which fails because:
- exec does not create $(DESTDIR)$(BINDIR) so will fail if scripts has
not created it yet.
- exec copies ebtables-save_ which will also fail if scripts has not
created it yet.

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#896274: marked as done (python3-segyio: segyio fails to import)

[Debian Bug Tracking System]

Your message dated Thu, 03 May 2018 10:21:12 +
with message-id 
and subject line Bug#896274: fixed in segyio 1.5.3-1
has caused the Debian Bug report #896274,
regarding python3-segyio: segyio fails to import
to be marked as done.

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

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


-- 
896274: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896274
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-segyio
Version: 1.5.2-1
Severity: serious
User: helm...@debian.org
Usertags: python-import

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

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/segyio/__init__.py", line 87, in 
from .open import open
  File "/usr/lib/python3/dist-packages/segyio/open.py", line 1, in 
import numpy
ModuleNotFoundError: No module named 'numpy'

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

Helmut
--- End Message ---
--- Begin Message ---
Source: segyio
Source-Version: 1.5.3-1

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

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

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

Debian distribution maintenance software
pp.
Jørgen Kvalsvik  (supplier of updated segyio 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, 03 May 2018 09:27:33 +0200
Source: segyio
Binary: libsegyio1 libsegyio-dev segyio-bin python3-segyio
Architecture: source
Version: 1.5.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jørgen Kvalsvik 
Description:
 libsegyio-dev - SEG-Y read/write library for seismic processing (development)
 libsegyio1 - SEG-Y read/write library for seismic processing (runtime)
 python3-segyio - SEG-Y read/write library for seismic processing (python3 
bindings
 segyio-bin - SEG-Y read/write library for seismic processing (shell utilities)
Closes: 896274
Changes:
 segyio (1.5.3-1) unstable; urgency=medium
 .
   * New upstream release
   * Upgrade to Standards-Version 4.1.4
   * Compute python dependencies with dh_python3 (Closes: #896274)
   * Move d/tests/control to d/tests/control.autodep8
   * Enable autopkg tests for python module import
   * Only depend on libsegyio-dev for linkage test
Checksums-Sha1:
 f217bc34144f9aff2c2dfa38026d139ca247a9e1 2267 segyio_1.5.3-1.dsc
 842582b42d5b0c3d85048975adea5dbc95c85362 225173 segyio_1.5.3.orig.tar.gz
 3cc75f61b83fb34f80b4a29e516f0742d076b5b1 3148 segyio_1.5.3-1.debian.tar.xz
 f3be26f2dcad0f102fbd90599079322ba02f68d8 9068 segyio_1.5.3-1_amd64.buildinfo
Checksums-Sha256:
 244abb6a0d8ce26c2c06086584296740494e3363f2d8c28f94f60357a2da3985 2267 
segyio_1.5.3-1.dsc
 34459ad8f336c6f7767f7f7f6d321eee4ac8ffc4567f89cea786a17f903bdd47 225173 
segyio_1.5.3.orig.tar.gz
 19da7b55ff6d15de784b5e60c95793ce8a8b2e1dbe7b438914e2c202d4e9c674 3148 
segyio_1.5.3-1.debian.tar.xz
 87b77b9809fa7d4a8d8e834a6e35bbff6efc72607518f37a023aa4cebf277b59 9068 
segyio_1.5.3-1_amd64.buildinfo
Files:
 eb846cf9b018bcd60dc53533560e3a81 2267 science optional segyio_1.5.3-1.dsc
 d58d77871031fd378e03e3f1162df36e 225173 science optional 
segyio_1.5.3.orig.tar.gz
 2535e493599f4d75f9465f96153a746d 3148 science optional 
segyio_1.5.3-1.debian.tar.xz
 9720cb7a1e131f70752107e7c1aa79df 9068 science optional 
segyio_1.5.3-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAlrq31wACgkQLOzpNQ7O
vkp28Q/+IXpvh0aHx/buZ5sH1volF6F0ShUnZkiW7JpXwHwkDmByQrAPnTa06emt
9TrPFr4y9K49S+HKyHJcZa2g82dDYYHeggx32u3CK3EDgfmVJLUHEEuo3wQ2GOnz

Bug#897591: tar: FTBFS on "slow" buildds - test 118 fails

[James Cowgill]

Source: tar
Version: 1.30+dfsg-1
Severity: serious
Tags: sid buster fixed-upstream

Hi,

tar seems to FTBFS on the "slow" buildds with test 118 failing:
> ## -- ##
> ## Detailed failed tests. ##
> ## -- ##
> 
> # -*- compilation -*-
> 118. dirrem02.at:31: testing explicitly named directory removed before 
> reading ...
> ./dirrem02.at:34:
> mkdir gnu
> (cd gnu
> TEST_TAR_FORMAT=gnu
> export TEST_TAR_FORMAT
> TAR_OPTIONS="-H gnu"
> export TAR_OPTIONS
> rm -rf *
> 
> mkdir dir
> mkdir dir/sub
> genfile --file dir/file1
> genfile --file dir/sub/file2
> 
> case "$TEST_TAR_FORMAT" in
> posix) CPT=5;;
> gnu)   CPT=3;;
> *) exit 77
> esac
> 
> genfile --run --checkpoint=$CPT --unlink dir/sub/file2 --unlink dir/sub -- \
>tar --blocking-factor=1 --checkpoint=1 --checkpoint-action='sleep=1' \
>--checkpoint-action='echo' -c -f archive.tar \
>--listed-incremental db -v dir dir/sub >/dev/null
> )
> --- - 2018-04-29 23:47:31.495714503 +
> +++ /<>/tar-1.30+dfsg/tests/testsuite.dir/at-groups/118/stderr  
> 2018-04-29 23:47:31.482584629 +
> @@ -1,5 +1,6 @@
>  tar: dir: Directory is new
>  tar: dir/sub: Directory is new
> +tar: dir/sub: file changed as we read it
>  tar: dir/sub: Cannot open: No such file or directory
>  tar: Exiting with failure status due to previous errors
>  
> stdout:
> 118. dirrem02.at:31: 118. explicitly named directory removed before reading 
> (dirrem02.at:31): FAILED (dirrem02.at:34)

I think this is fixed by this upstream commit (untested):
https://git.savannah.gnu.org/cgit/tar.git/commit/?id=64b43fdf70d82c39eb2ca900cd4f8e49b86c2020

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#897484: marked as done (r-bioc-iranges: FTBFS: NCList.c:1499:9: error: too few arguments to function 'new_Hits')

[Debian Bug Tracking System]

Your message dated Thu, 3 May 2018 12:06:36 +0200
with message-id <20180503100636.z5ef757xcwjox...@an3as.eu>
and subject line Re: Bug#897484: r-bioc-iranges: FTBFS: NCList.c:1499:9: error: 
too few arguments to function 'new_Hits'
has caused the Debian Bug report #897484,
regarding r-bioc-iranges: FTBFS: NCList.c:1499:9: error: too few arguments to 
function 'new_Hits'
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.)


-- 
897484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897484
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-bioc-iranges
Version: 2.12.0-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20180502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> gcc -std=gnu99 -I/usr/share/R/include -DNDEBUG  
> -I"/usr/lib/R/site-library/S4Vectors/include"-fpic  -g -O2 
> -fdebug-prefix-map=/build/r-base-3.4.4=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g  -c NCList.c -o 
> NCList.o
> NCList.c: In function 'NCList_find_overlaps':
> NCList.c:1499:18: warning: passing argument 1 of 'new_Hits' from incompatible 
> pointer type [-Wincompatible-pointer-types]
>   return new_Hits(qh_buf->elts, sh_buf->elts, IntAE_get_nelt(qh_buf),
>   ^~
> In file included from NCList.c:6:0:
> /usr/lib/R/site-library/S4Vectors/include/S4Vectors_interface.h:531:6: note: 
> expected 'const char *' but argument is of type 'int *'
>  SEXP new_Hits(
>   ^~~~
> NCList.c:1499:46: warning: passing argument 3 of 'new_Hits' makes pointer 
> from integer without a cast [-Wint-conversion]
>   return new_Hits(qh_buf->elts, sh_buf->elts, IntAE_get_nelt(qh_buf),
>   ^~
> In file included from NCList.c:6:0:
> /usr/lib/R/site-library/S4Vectors/include/S4Vectors_interface.h:531:6: note: 
> expected 'const int *' but argument is of type 'size_t {aka long unsigned 
> int}'
>  SEXP new_Hits(
>   ^~~~
> NCList.c:1499:9: error: too few arguments to function 'new_Hits'
>   return new_Hits(qh_buf->elts, sh_buf->elts, IntAE_get_nelt(qh_buf),
>  ^~~~
> In file included from NCList.c:6:0:
> /usr/lib/R/site-library/S4Vectors/include/S4Vectors_interface.h:531:6: note: 
> declared here
>  SEXP new_Hits(
>   ^~~~
> NCList.c: In function 'NCList_find_overlaps_in_groups':
> NCList.c:1609:18: warning: passing argument 1 of 'new_Hits' from incompatible 
> pointer type [-Wincompatible-pointer-types]
>   return new_Hits(qh_buf->elts, sh_buf->elts, IntAE_get_nelt(qh_buf),
>   ^~
> In file included from NCList.c:6:0:
> /usr/lib/R/site-library/S4Vectors/include/S4Vectors_interface.h:531:6: note: 
> expected 'const char *' but argument is of type 'int *'
>  SEXP new_Hits(
>   ^~~~
> NCList.c:1609:46: warning: passing argument 3 of 'new_Hits' makes pointer 
> from integer without a cast [-Wint-conversion]
>   return new_Hits(qh_buf->elts, sh_buf->elts, IntAE_get_nelt(qh_buf),
>   ^~
> In file included from NCList.c:6:0:
> /usr/lib/R/site-library/S4Vectors/include/S4Vectors_interface.h:531:6: note: 
> expected 'const int *' but argument is of type 'size_t {aka long unsigned 
> int}'
>  SEXP new_Hits(
>   ^~~~
> NCList.c:1609:9: error: too few arguments to function 'new_Hits'
>   return new_Hits(qh_buf->elts, sh_buf->elts, IntAE_get_nelt(qh_buf),
>  ^~~~
> In file included from NCList.c:6:0:
> /usr/lib/R/site-library/S4Vectors/include/S4Vectors_interface.h:531:6: note: 
> declared here
>  SEXP new_Hits(
>   ^~~~
> make[1]: *** [/usr/lib/R/etc/Makeconf:159: NCList.o] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2018/05/02/r-bioc-iranges_2.12.0-2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
On Wed, May 02, 2018 at 10:05:12PM +0200, Lucas Nussbaum wrote:
> Source: r-bioc-iranges
> Version: 2.12.0-2

Closed with new upstream version upload.

This error happened due to a transition of BioConductor packaged.  We
are aware that we are not 

Bug#897466: bart-view: FTBFS: multind.h:17:10: fatal error: misc/nested.h: No such file or directory

[Andreas Tille]

Hi Martin,

can you please have a look?

Kind regards

 Andreas.

On Wed, May 02, 2018 at 09:55:11PM +0200, Lucas Nussbaum wrote:
> Source: bart-view
> Version: 0.1.00-1
> Severity: serious
> Tags: buster sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20180502 qa-ftbfs
> Justification: FTBFS on amd64
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
> 
> Relevant part (hopefully):
> > cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> > -Wformat -Werror=format-security -std=c11 -fopenmp -export-dynamic -o view 
> > -I/usr/include/bart/ `pkg-config --cflags gtk+-3.0` src/main.c src/view.c 
> > src/draw.c `pkg-config --libs gtk+-3.0` /usr/lib/bart//libmisc.a 
> > /usr/lib/bart//libnum.a -lm -lpng
> > In file included from src/view.c:24:0:
> > /usr/include/bart/num/multind.h:17:10: fatal error: misc/nested.h: No such 
> > file or directory
> >  #include "misc/nested.h"
> >   ^~~
> > compilation terminated.
> > make[1]: *** [Makefile:52: view] Error 1
> 
> The full build log is available from:
>http://aws-logs.debian.net/2018/05/02/bart-view_0.1.00-1_unstable.log
> 
> A list of current common problems and possible solutions is available at
> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
> 
> About the archive rebuild: The rebuild was done on EC2 VM instances from
> Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
> failed build was retried once to eliminate random failures.
> 
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging

-- 
http://fam-tille.de

Bug#897590: linux-image-4.9.0-6-armmp: Missing CONFIG_MFD_TPS65217 may cause hardware damage

[PA Nilsson]

Package: src:linux
Version: 4.9.82-1+deb9u3
Severity: grave 

Dear Maintainer,

When shutting down BeagleBoneBlack, running Debian 9.3, it was
discovered that the system still draws excessive power and puts the
system out of spec with possible hardware damage as a result.

This is due to the PMIC not shutting down correctly, as described by the
referenced posts:
http://bugs.elinux.org/issues/143
https://groups.google.com/forum/#%21msg/beagleboard/7sxPePT7wkM/V1Ft-xxh0agJ

This in turn is due to the driver for the PMIC is not avaialble since
CONFIG_MFD_TPS65217 is missing.

Setting CONFIG_MFD_TPS65217 will enable the correct shutdown procedure.



-- Package-specific info:
** Version:
Linux version 4.9.0-6-armmp (debian-ker...@lists.debian.org) (gcc version 6.3.0 
20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02)

** Command line:
console=ttyO0,115200n8 root=/dev/mmcblk1p2 rw rootfstype=ext4 rootwait

** Not tainted

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
Hardware: Generic AM33XX (Flattened Device Tree)
Revision: 
Device Tree model: TI AM335x BeagleBone Black

** Loaded modules:
dm_crypt
dm_mod
xts
gf128mul
algif_skcipher
af_alg
sd_mod
sg
uas
usb_storage
scsi_mod
fuse
snd_soc_simple_card
snd_soc_simple_card_utils
omap_aes
omap_sham
crypto_engine
omap_rng
rng_core
tilcdc
snd_soc_davinci_mcasp
snd_soc_omap
ledtrig_heartbeat
omap_hwspinlock
ledtrig_timer
tda998x
hwspinlock_core
snd_soc_core
snd_pcm_dmaengine
snd_pcm
drm_kms_helper
snd_timer
snd
soundcore
at24
cppi41
omap_wdt
drm
leds_gpio
cpufreq_dt
nvmem_core
nf_conntrack_ipv4
nf_defrag_ipv4
xt_tcpudp
xt_conntrack
nf_conntrack
iptable_filter
ip_tables
x_tables
autofs4
ext4
crc16
jbd2
crc32c_generic
fscrypto
ecb
mbcache
smsc
musb_dsps
musb_hdrc
udc_core
davinci_mdio
usbcore
phy_am335x
phy_generic
usb_common
phy_am335x_control
ti_cpsw
cpsw_ale
cpsw_common
davinci_cpdma
omap_hsmmc
musb_am335x

** PCI devices:
not available

** USB devices:
not available


-- System Information:
Debian Release: 9.4
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: armhf (armv7l)

Kernel: Linux 4.9.0-6-armmp (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=C 
(charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-image-4.9.0-6-armmp depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.130
ii  kmod23-2
ii  linux-base  4.5

Versions of packages linux-image-4.9.0-6-armmp recommends:
pn  firmware-linux-free  
pn  irqbalance   

Versions of packages linux-image-4.9.0-6-armmp suggests:
pn  debian-kernel-handbook  
pn  linux-doc-4.9   

Versions of packages linux-image-4.9.0-6-armmp is related to:
pn  firmware-amd-graphics 
pn  firmware-atheros  
pn  firmware-bnx2 
pn  firmware-bnx2x
pn  firmware-brcm80211
pn  firmware-cavium   
pn  firmware-intel-sound  
pn  firmware-intelwimax   
pn  firmware-ipw2x00  
pn  firmware-ivtv 
pn  firmware-iwlwifi  
pn  firmware-libertas 
pn  firmware-linux-nonfree
pn  firmware-misc-nonfree 
pn  firmware-myricom  
pn  firmware-netxen   
pn  firmware-qlogic   
pn  firmware-realtek  
pn  firmware-samsung  
pn  firmware-siano
pn  firmware-ti-connectivity  
pn  xen-hypervisor

-- no debconf information

Processed: Re: Bug#897465: sagan: FTBFS: ./conftest.c:120: undefined reference to `strlcat'

[Debian Bug Tracking System]

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

> tags 897465 - moreinfo unreproducible
Bug #897465 [src:sagan] sagan: FTBFS: ./conftest.c:120: undefined reference to 
`strlcat'
Ignoring request to alter tags of bug #897465 to the same tags previously set
> severity 897465 normal
Bug #897465 [src:sagan] sagan: FTBFS: ./conftest.c:120: undefined reference to 
`strlcat'
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#897465: sagan: FTBFS: ./conftest.c:120: undefined reference to `strlcat'

[Pierre Chifflier]

tags 897465 - moreinfo unreproducible
severity 897465 normal
thanks

Hi Lucas,

I cannot reproduce this FTBFS here (in pbuilder), nor in a porter box.
However, I just uploaded sagan-1.1.8-2, where a build-dep was missing.

These issues may be related (though I don't see how). Can you test again
and confirm if it is fixed ?

Thanks,
Pierre


On Wed, May 02, 2018 at 10:05:20PM +0200, Lucas Nussbaum wrote:
> Source: sagan
> Version: 1.1.8-1
> Severity: serious
> Tags: buster sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20180502 qa-ftbfs
> Justification: FTBFS on amd64
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
> 
> Relevant part (hopefully):
> > gcc: fatal error: no input files
> > compilation terminated.
> > configure:5639: $? = 1
> > configure:5643: checking whether we are using the GNU C compiler
> > configure:5671: result: yes
> > configure:5680: checking whether gcc accepts -g
> > configure:5741: result: yes
> > configure:5758: checking for gcc option to accept ISO C89
> > configure:5834: result: none needed
> > configure:5859: checking whether gcc understands -c and -o together
> > configure:5896: result: yes
> > configure:5920: checking whether make sets $(MAKE)
> > configure:5942: result: yes
> > configure:6008: checking for pkg-config
> > configure:6026: found /usr/bin/pkg-config
> > configure:6038: result: /usr/bin/pkg-config
> > configure:6063: checking pkg-config is at least version 0.9.0
> > configure:6066: result: yes
> > configure:6076: checking for ANSI C header files
> > configure:6180: result: yes
> > configure:6188: checking for sys/wait.h that is POSIX.1 compatible
> > configure:6214: gcc -c -g -O2 -fdebug-prefix-map=/<>=. 
> > -fstack-protector-strong -Wformat -Werror=format-security -D__Linux__ 
> > -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c >&5
> > configure:6214: $? = 0
> > configure:6221: result: yes
> > configure:6233: checking stdio.h usability
> > configure:6233: gcc -c -g -O2 -fdebug-prefix-map=/<>=. 
> > -fstack-protector-strong -Wformat -Werror=format-security -D__Linux__ 
> > -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c >&5
> > configure:6233: $? = 0
> > configure:6233: result: yes
> > configure:6233: checking stdio.h presence
> > configure:6233: gcc -E -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c
> > configure:6233: $? = 0
> > configure:6233: result: yes
> > configure:6233: checking for stdio.h
> > configure:6233: result: yes
> > configure:6233: checking for stdlib.h
> > configure:6233: result: yes
> > configure:6233: checking for sys/types.h
> > configure:6233: result: yes
> > configure:6233: checking for unistd.h
> > configure:6233: result: yes
> > configure:6233: checking for stdint.h
> > configure:6233: result: yes
> > configure:6233: checking for inttypes.h
> > configure:6233: result: yes
> > configure:6233: checking ctype.h usability
> > configure:6233: gcc -c -g -O2 -fdebug-prefix-map=/<>=. 
> > -fstack-protector-strong -Wformat -Werror=format-security -D__Linux__ 
> > -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c >&5
> > configure:6233: $? = 0
> > configure:6233: result: yes
> > configure:6233: checking ctype.h presence
> > configure:6233: gcc -E -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c
> > configure:6233: $? = 0
> > configure:6233: result: yes
> > configure:6233: checking for ctype.h
> > configure:6233: result: yes
> > configure:6233: checking errno.h usability
> > configure:6233: gcc -c -g -O2 -fdebug-prefix-map=/<>=. 
> > -fstack-protector-strong -Wformat -Werror=format-security -D__Linux__ 
> > -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c >&5
> > configure:6233: $? = 0
> > configure:6233: result: yes
> > configure:6233: checking errno.h presence
> > configure:6233: gcc -E -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c
> > configure:6233: $? = 0
> > configure:6233: result: yes
> > configure:6233: checking for errno.h
> > configure:6233: result: yes
> > configure:6233: checking fcntl.h usability
> > configure:6233: gcc -c -g -O2 -fdebug-prefix-map=/<>=. 
> > -fstack-protector-strong -Wformat -Werror=format-security -D__Linux__ 
> > -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c >&5
> > configure:6233: $? = 0
> > configure:6233: result: yes
> > configure:6233: checking fcntl.h presence
> > configure:6233: gcc -E -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c
> > configure:6233: $? = 0
> > configure:6233: result: yes
> > configure:6233: checking for fcntl.h
> > configure:6233: result: yes
> > configure:6233: checking for sys/stat.h
> > configure:6233: result: yes
> > configure:6233: checking for string.h
> > configure:6233: result: yes
> > configure:6233: checking getopt.h usability
> > configure:6233: gcc -c -g -O2 -fdebug-prefix-map=/<>=. 
> > -fstack-protector-strong -Wformat -Werror=format-security -D__Linux__ 
> > -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c >&5
> > configure:6233: $? = 0
> > configure:6233: result: yes
> > configure:6233: checking getopt.h presence
> > configure:6233: gcc -E -Wdate-time 

Bug#897338: Tested on hardware

[Maximiliano Curia]

¡Hola Александр!

El 2018-05-03 a las 07:54 +0300, Александр Керножицкий escribió:

I tried Debian Testing on real hardware and SDDM seems to work there. So I can 
reproduce the bug only on VirtualBox.


It seems that the new sddm requires virtualbox-guest-dkms and 
virtualbox-guest-x11 to run inside a virtualbox, I'm not sure why.


Happy hacking,
--
"We must be very careful when we give advice to younger people: sometimes they 
follow it!"

-- Edsger W. Dijkstra
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#897417: Any chance of fixing its compatibility with openjdk-10?

[Alastair McKinstry]

On 03/05/2018 09:52, Boyuan Yang wrote:
> On Wed, 02 May 2018 16:27:22 + Alastair McKinstry  
> wrote:
>> Source: openmpi
>> Source-Version: 3.0.1.real-2
>> Changes:
>>  openmpi (3.0.1.real-2) unstable; urgency=medium
>>  .
>>* Builds against openjdk-9 as openjdk-19 (now default) doesn't ship
>>  javah, which we need for java bindings. Closes: 
> Hi Alastair,
>
> Thank you for the quick fix; however, I'm wondering if you could forward this 
> issue to upstream to deal with the disapperance of javah.
>
> According to https://openjdk.java.net/jeps/313 , javah was deprecated in 
> OpenJDK 9 and removed in OpenJDK 10. I'm wondering if you could forward this 
> information to upstream to have the problem solved so that we don't have to 
> depend on the non-default Java version.
>
> --
> Best Regards,
> Boyuan Yang
Hi Boyuan

Yes, thats my plan. Its just that I needed to get some fixes into
openmpi quickly to complete the openmpi3 transition.

regards
Alastair

-- 
Alastair McKinstry, , , 
https://diaspora.sceal.ie/u/amckinstry
Misentropy: doubting that the Universe is becoming more disordered. 




signature.asc
Description: OpenPGP digital signature

Bug#895506: marked as done (apertium-swe-nor FTBFS: test failure)

[Debian Bug Tracking System]

Your message dated Thu, 03 May 2018 09:07:37 +
with message-id 
and subject line Bug#895506: fixed in apertium-swe-nor 0.2.0~r69544-2
has caused the Debian Bug report #895506,
regarding apertium-swe-nor FTBFS: test failure
to be marked as done.

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

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


-- 
895506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895506
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apertium-swe-nor
Version: 0.2.0~r69544-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apertium-swe-nor.html

...
   dh_auto_test -O--fail-missing
make -j1 test VERBOSE=1
make[1]: Entering directory '/build/1st/apertium-swe-nor-0.2.0~r69544'
echo "Såg hon inte orden?" | apertium -d . swe-nno | tee .test-mt
Såg kummen ikkje orda?
1c1
< Såg ho ikkje orda?
---
> Såg kummen ikkje orda?
make[1]: *** [Makefile:878: test] Error 1
--- End Message ---
--- Begin Message ---
Source: apertium-swe-nor
Source-Version: 0.2.0~r69544-2

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

Debian distribution maintenance software
pp.
Kartik Mistry  (supplier of updated apertium-swe-nor 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, 03 May 2018 11:33:48 +0530
Source: apertium-swe-nor
Binary: apertium-swe-nor
Architecture: source all
Version: 0.2.0~r69544-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Kartik Mistry 
Description:
 apertium-swe-nor - Apertium translation data for the Swedish-Norwegian pair
Closes: 895506
Changes:
 apertium-swe-nor (0.2.0~r69544-2) unstable; urgency=medium
 .
   * debian/rules:
 + Disable failing tests to fix FTBFS (Closes: #895506)
   * debian/control:
 + Updated Standards-Version to 4.1.4
 + Updated Vcs-* URLs.
   * Update debian/watch file.
Checksums-Sha1:
 069aa091649c1fe41e1a796a74856674466582df 2287 
apertium-swe-nor_0.2.0~r69544-2.dsc
 90049fd77197918168e284f5be5485a1684b69ed 2024 
apertium-swe-nor_0.2.0~r69544-2.debian.tar.xz
 1c74d4ff707f9831ef92de36cac449ab1ef6a75d 4402644 
apertium-swe-nor_0.2.0~r69544-2_all.deb
 ce0af9c553ff6339cc319c3849e205a4f654798d 6577 
apertium-swe-nor_0.2.0~r69544-2_amd64.buildinfo
Checksums-Sha256:
 c7b3dc58b4ca52b859720c3d48c3a5099f557eff1affcc9523d095d3d2aec79b 2287 
apertium-swe-nor_0.2.0~r69544-2.dsc
 9a7d1968975592c26665483d6ff56fe9df22eedbbc33993cd09034cf98a5f314 2024 
apertium-swe-nor_0.2.0~r69544-2.debian.tar.xz
 387d2b36571d6fed3d9ddf97a07a0d269498bd01e3b28338cd8d8c8a23a1d815 4402644 
apertium-swe-nor_0.2.0~r69544-2_all.deb
 a8576a0d8a801914ccd33b402f62874b4192f89b18ffce3bb8c5ed325e723af1 6577 
apertium-swe-nor_0.2.0~r69544-2_amd64.buildinfo
Files:
 3da03d8383bebd6b6014bf971dd99091 2287 science optional 
apertium-swe-nor_0.2.0~r69544-2.dsc
 79cc4fcf5484edbc91d9efd2838d64eb 2024 science optional 
apertium-swe-nor_0.2.0~r69544-2.debian.tar.xz
 821463148dd0b6e07bfa44ade1d361f7 4402644 science optional 
apertium-swe-nor_0.2.0~r69544-2_all.deb
 ffce6f917ac0ff3ddbb42499f7ad16e3 6577 science optional 
apertium-swe-nor_0.2.0~r69544-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEa2MbXvVUr2sRlmKSAsHT8ng6pN4FAlrqwNsACgkQAsHT8ng6
pN6ffxAApGstElsbAsx/43oaaAi++ExYSflTbyH/MVezZvYpt90hBgMEOqXyIgXx
831XSvvDrXztC1qKzjSPa0NqwCRhFrddKzkbZgnW9xVTFQquBxJz2LRwmoghswjg
wcGsxzzekXoDi7WfY8b3o+gPkkoKzXvh5h4eVNQpmCjWyxBly+DgbCaED2nTT/+6
GYi+yRo24CVPu+PnZOkG7tyR8CLKu/usu+O9//wO8locvYtE1NTc43RrVIpPEWBQ
TezmQ5JW1UcRidZmtFcv8/lKhRDtAAdIrNDFuAWNTmsYBXguJhRa+wkazzEI7trI
IXekDbbjsM9IuH2CCYJd3cNUqoE1ITtxsgqj+Cs3lHLipPzyaW6snejJHi/x5Zn4
xsgNmJCJy9Sj22GRqG13QoJnrl0dpw1XiFc0SDtDu5XW2SBaJgUIOin91G8p3oSw
bN2s6Y/FeI8/jmxZhXCj0ejeUoriG5Z3GxJm0Hm+MwL/4RaoPa5bHOZE0yHGWII+
iUcDHUiwpQIvOeiNhAujdvuEcXSwNYq8RGv2jzDpf55LWhvv/AseGPiPPUU8Qszf
lxtVzMwZHvSFU9sNVlNWKu2C8QwrCW/Ps4AKwQa6ZhCmAnUtUzYJkyDO8AIzD/od
DPLQjKctj7DqkZ2Ksn+673Nnt3jV2iPlLFvYvrdgHMuGvWgR4iA=

Bug#897403: marked as done (readline: depends on old ncurses packages)

[Debian Bug Tracking System]

Your message dated Thu, 03 May 2018 07:58:43 +
with message-id 
and subject line Bug#897403: fixed in readline 7.0-4
has caused the Debian Bug report #897403,
regarding readline: depends on old ncurses packages
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.)


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

Hi,

Your package depends on old multilib readline packages, which have been
renamed:

lib32ncursesw5-dev -> lib32ncurses-dev
lib64ncurses5-dev  -> lib64ncurses-dev
lib32tinfo-dev -> lib32ncurses-dev

Please update to those in your Depends and Build-Depends.

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.15.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), 
LANGUAGE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: readline
Source-Version: 7.0-4

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated readline package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 02 May 2018 13:36:22 +0200
Source: readline
Binary: libreadline7 lib64readline7 readline-common libreadline-dev 
lib64readline-dev rlfe lib32readline7 lib32readline-dev readline-doc
Architecture: source
Version: 7.0-4
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose 
Changed-By: Matthias Klose 
Description:
 lib32readline-dev - GNU readline and history libraries, development files 
(32-bit)
 lib32readline7 - GNU readline and history libraries, run-time libraries 
(32-bit)
 lib64readline-dev - GNU readline and history libraries, development files 
(64-bit)
 lib64readline7 - GNU readline and history libraries, run-time libraries 
(64-bit)
 libreadline-dev - GNU readline and history libraries, development files
 libreadline7 - GNU readline and history libraries, run-time libraries
 readline-common - GNU readline and history libraries, common files
 readline-doc - GNU readline and history libraries, documentation and examples
 rlfe   - Front-end using readline to "cook" input lines for other programs
Closes: 897403
Changes:
 readline (7.0-4) unstable; urgency=medium
 .
   * Update ncurses build dependencies. Closes: #897403.
   * Stop building the libreadline7-dbg package.
Checksums-Sha1:
 c1e01c2d53454c38c395b5f9957de867f06935c4 2444 readline_7.0-4.dsc
 34ee08f670e608d98c01fed1fd40b7baa3ca97ee 29964 readline_7.0-4.debian.tar.xz
 698ca30c8df5a876bf4d0a69dbafe85c82cab23a 6995 readline_7.0-4_source.buildinfo
Checksums-Sha256:
 6cf8b5489b4bfe2c30d9fc595cbd663fb40d56723b78440889e8eac339183783 2444 
readline_7.0-4.dsc
 e29a0a07356ee0389a981214e26a4841d06e98d5f4e5caa50b9ae4a0995613ef 29964 
readline_7.0-4.debian.tar.xz
 288d26a891f8e1dc600af83f12c653964c988eced63b4fa7184dce0eeb162edf 6995 
readline_7.0-4_source.buildinfo
Files:
 d08bfda3f96364cec6e4eba9425addda 2444 libs important readline_7.0-4.dsc
 0cf03f368a8c8a2d2a9defcd1a415d15 29964 libs important 
readline_7.0-4.debian.tar.xz
 ab97812e03d8f5c95159e1bbb4faf764 6995 libs important 
readline_7.0-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAlrqtcQQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9f0iEACX6tZ4oFVESjjQmlNndZsr+R2jJpOSevSY
JsOr9ymlL8ptGPKaCBNt4+vutJVuX6BWFd/zufJiz4FfZWox/9cEvBOJD5N5cwEO
yY96+BdsaQh2/wtc1p/1C0Wk3mlB20F0CM7gSnLafQvNd+gr5WJ4MOhfDYfnCqfQ
yJ1vRApZzQgqcxkx5AlEszgogX1syy22ESVc0svrmiwVW/sUSQzEzMZ8ejYAZyJd

Bug#846677: marked as done (tomcatjss: FTBFS: [javac] /<>/src/org/apache/tomcat/util/net/jss/IJSSFactory.java:26: error: cannot find symbol)

[Debian Bug Tracking System]

Your message dated Thu, 03 May 2018 07:59:59 +
with message-id 
and subject line Bug#846677: fixed in tomcatjss 7.3.0-1
has caused the Debian Bug report #846677,
regarding tomcatjss: FTBFS: [javac] 
/<>/src/org/apache/tomcat/util/net/jss/IJSSFactory.java:26: error: 
cannot find symbol
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.)


-- 
846677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846677
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tomcatjss
Version: 7.1.4-4
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161202 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> ant -Dant.build.javac.source=1.5 \
>   -Dant.build.javac.target=1.5
> Buildfile: /<>/build.xml
> 
> compile:
> [mkdir] Created dir: /<>/build/classes
> [javac] /<>/build.xml:209: warning: 'includeantruntime' was 
> not set, defaulting to build.sysclasspath=last; set to false for repeatable 
> builds
> [javac] Compiling 7 source files to /<>/build/classes
> [javac] warning: [options] bootstrap class path not set in conjunction 
> with -source 1.5
> [javac] warning: [options] source value 1.5 is obsolete and will be 
> removed in a future release
> [javac] warning: [options] target value 1.5 is obsolete and will be 
> removed in a future release
> [javac] warning: [options] To suppress warnings about obsolete options, 
> use -Xlint:-options.
> [javac] 
> /<>/src/org/apache/tomcat/util/net/jss/IJSSFactory.java:26: 
> error: cannot find symbol
> [javac] import org.apache.tomcat.util.net.ServerSocketFactory;
> [javac]  ^
> [javac]   symbol:   class ServerSocketFactory
> [javac]   location: package org.apache.tomcat.util.net
> [javac] 
> /<>/src/org/apache/tomcat/util/net/jss/IJSSFactory.java:29: 
> error: cannot find symbol
> [javac] public ServerSocketFactory getSocketFactory(AbstractEndpoint 
> endpoint);
> [javac]^
> [javac]   symbol:   class ServerSocketFactory
> [javac]   location: interface IJSSFactory
> [javac] 
> /<>/src/org/apache/tomcat/util/net/jss/JSSFactory.java:26: 
> error: cannot find symbol
> [javac] import org.apache.tomcat.util.net.ServerSocketFactory;
> [javac]  ^
> [javac]   symbol:   class ServerSocketFactory
> [javac]   location: package org.apache.tomcat.util.net
> [javac] 
> /<>/src/org/apache/tomcat/util/net/jss/JSSFactory.java:33: 
> error: cannot find symbol
> [javac] public ServerSocketFactory getSocketFactory(AbstractEndpoint 
> endpoint) {
> [javac]^
> [javac]   symbol:   class ServerSocketFactory
> [javac]   location: class JSSFactory
> [javac] 
> /<>/src/org/apache/tomcat/util/net/jss/JSSImplementation.java:28:
>  error: cannot find symbol
> [javac] import org.apache.tomcat.util.net.ServerSocketFactory;
> [javac]  ^
> [javac]   symbol:   class ServerSocketFactory
> [javac]   location: package org.apache.tomcat.util.net
> [javac] 
> /<>/src/org/apache/tomcat/util/net/jss/JSSImplementation.java:55:
>  error: cannot find symbol
> [javac] public ServerSocketFactory 
> getServerSocketFactory(AbstractEndpoint endpoint) {
> [javac]^
> [javac]   symbol:   class ServerSocketFactory
> [javac]   location: class JSSImplementation
> [javac] 
> /<>/src/org/apache/tomcat/util/net/jss/JSSSocketFactory.java:60: 
> error: cannot find symbol
> [javac] org.apache.tomcat.util.net.ServerSocketFactory,
> [javac]   ^
> [javac]   symbol:   class ServerSocketFactory
> [javac]   location: package org.apache.tomcat.util.net
> [javac] 
> /<>/src/org/apache/tomcat/util/net/jss/JSSImplementation.java:30:
>  error: JSSImplementation is not abstract and does not override abstract 
> method getSSLUtil(SSLHostConfigCertificate) in SSLImplementation
> [javac] public class JSSImplementation extends SSLImplementation {
> [javac]^
> [javac] 
> /<>/src/org/apache/tomcat/util/net/jss/JSSImplementation.java:56:
>  error: cannot find symbol
> [javac] ServerSocketFactory ssf = 
> factory.getSocketFactory(endpoint);
> [javac] ^
> [javac]   symbol:   class ServerSocketFactory
> [javac]   location: 

Bug#897534: marked as done (mandelbulber2: FTBFS: Last OS error: No such file or directory)

[Debian Bug Tracking System]

Your message dated Thu, 03 May 2018 07:56:33 +
with message-id 
and subject line Bug#897534: fixed in mandelbulber2 2.13.2-3
has caused the Debian Bug report #897534,
regarding mandelbulber2: FTBFS: Last OS error: No such file or directory
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.)


-- 
897534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897534
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mandelbulber2
Version: 2.13.2-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20180502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> xsltproc -''-nonet -''-param man.charmap.use.subset "0" 
> /usr/share/xml/docbook/stylesheet/docbook-xsl/manpages/docbook.xsl 
> debian/mandelbulber2.man.xml
> I/O error : Attempt to load network entity 
> http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd
> debian/mandelbulber2.man.xml:55: warning: failed to load external entity 
> "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd;
> ]>
>   ^
> Note: Writing mandelbulber2.1
> cd docs ; ./build.sh
> This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018/Debian) 
> (preloaded format=pdflatex)
>  restricted \write18 enabled.
> entering extended mode
> (./handbook.tex
> LaTeX2e <2018-04-01> patch level 2
> Babel <3.18> and hyphenation patterns for 3 language(s) loaded.
> (./mandelbulber2/preamble.tex
> (/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
> Document Class: article 2014/09/29 v1.4h Standard LaTeX document class
> (/usr/share/texlive/texmf-dist/tex/latex/base/size12.clo))
> (/usr/share/texlive/texmf-dist/tex/latex/geometry/geometry.sty
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifpdf.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifvtex.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty
> (/usr/share/texlive/texmf-dist/tex/latex/ucs/utf8x.def))
> (/usr/share/texlive/texmf-dist/tex/latex/ucs/ucs.sty
> (/usr/share/texlive/texmf-dist/tex/latex/ucs/data/uni-global.def))
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsmath.sty
> For additional information on amsmath, use the `?' option.
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amstext.sty
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsgen.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsbsy.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsopn.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amsfonts.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amssymb.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/graphics.cfg)
> (/usr/share/texlive/texmf-dist/tex/latex/graphics-def/pdftex.def)))
> (/usr/share/texlive/texmf-dist/tex/latex/tools/longtable.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/booktabs/booktabs.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/hyperref.sty
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/hobsub-hyperref.sty
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/hobsub-generic.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/oberdiek/auxhook.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/oberdiek/kvoptions.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/pd1enc.def)
> (/usr/share/texlive/texmf-dist/tex/latex/latexconfig/hyperref.cfg)
> (/usr/share/texlive/texmf-dist/tex/latex/url/url.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/hpdftex.def
> (/usr/share/texlive/texmf-dist/tex/latex/oberdiek/rerunfilecheck.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/listings/listings.sty
> (/usr/share/texlive/texmf-dist/tex/latex/listings/lstmisc.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/listings/listings.cfg))
> (/usr/share/texlive/texmf-dist/tex/latex/float/float.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/pgf/frontendlayer/tikz.sty
> (/usr/share/texlive/texmf-dist/tex/latex/pgf/basiclayer/pgf.sty
> (/usr/share/texlive/texmf-dist/tex/latex/pgf/utilities/pgfrcs.sty
> (/usr/share/texlive/texmf-dist/tex/generic/pgf/utilities/pgfutil-common.tex
> 

Bug#897417: Any chance of fixing its compatibility with openjdk-10?

[Boyuan Yang]

On Wed, 02 May 2018 16:27:22 + Alastair McKinstry  
wrote:
> Source: openmpi
> Source-Version: 3.0.1.real-2
> Changes:
>  openmpi (3.0.1.real-2) unstable; urgency=medium
>  .
>* Builds against openjdk-9 as openjdk-19 (now default) doesn't ship
>  javah, which we need for java bindings. Closes: 

Hi Alastair,

Thank you for the quick fix; however, I'm wondering if you could forward this 
issue to upstream to deal with the disapperance of javah.

According to https://openjdk.java.net/jeps/313 , javah was deprecated in 
OpenJDK 9 and removed in OpenJDK 10. I'm wondering if you could forward this 
information to upstream to have the problem solved so that we don't have to 
depend on the non-default Java version.

--
Best Regards,
Boyuan Yang

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

Processed: notfound 897455 in geos/3.6.2-1, severity of 897455 is normal

[Debian Bug Tracking System]

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

> notfound 897455 geos/3.6.2-1
Bug #897455 {Done: Lucas Nussbaum } [src:geos] geos: FTBFS: 
configure: error: Could not find ruby interpreter.
No longer marked as found in versions geos/3.6.2-1.
> severity 897455 normal
Bug #897455 {Done: Lucas Nussbaum } [src:geos] geos: FTBFS: 
configure: error: Could not find ruby interpreter.
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Processed: severity of 669214 is serious

[Debian Bug Tracking System]

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

> severity 669214 serious
Bug #669214 [libjpedal-jbig2-java] libjpedal-jbig2-java: obsolete depends 
default-jdk-builddep
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#897455: marked as done (geos: FTBFS: configure: error: Could not find ruby interpreter.)

[Debian Bug Tracking System]

Your message dated Thu, 3 May 2018 08:05:50 +0200
with message-id <20180503060550.dnteo37co3wvi...@xanadu.blop.info>
and subject line Re: Bug#897455: geos: FTBFS: configure: error: Could not find 
ruby interpreter.
has caused the Debian Bug report #897455,
regarding geos: FTBFS: configure: error: Could not find ruby interpreter.
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.)


-- 
897455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897455
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: geos
Version: 3.6.2-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20180502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> checking for swig... /usr/bin/swig
> checking for SWIG version... 3.0.12
> configure: SWIG executable is '/usr/bin/swig'
> configure: SWIG library directory is '/usr/share/swig3.0'
> checking for ruby... no
> configure: error: Could not find ruby interpreter.
>   tail -v -n \+0 config.log

The full build log is available from:
   http://aws-logs.debian.net/2018/05/02/geos_3.6.2-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
On 03/05/18 at 07:28 +0200, Sebastiaan Couwenberg wrote:
> Control: tags -1 unreproducible moreinfo
> 
> Hi Lucas,
> 
> Thanks for reporting this issue.
> 
> Unfortunately I cannot reproduce it in an up-to-date unstable chroot.
> 
> Can you still reproduce this issue?

Strange, maybe one of the dependencies changed to depend on 'ruby'
(which wasn't installed in my build). I'm closing the bug.

Lucas--- End Message ---

Bug#897583: haskell-graphviz: FTBFS: unsatisfiable build-dependency: libghc-fgl-dev (< 5.6) but 5.6.0.0-2 is to be installed

[Lucas Nussbaum]

Source: haskell-graphviz
Version: 2999.19.0.0-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20180502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: cdbs, debhelper (>= 9), ghc (>= 8), ghc-prof, 
> haskell-devscripts (>= 0.13), libghc-colour-dev (<< 2.4), libghc-colour-dev 
> (>= 2.3), libghc-colour-prof, libghc-dlist-dev (<< 0.9), libghc-dlist-dev (>= 
> 0.5), libghc-dlist-prof, libghc-fgl-dev (<< 5.6), libghc-fgl-dev (>= 5.4), 
> libghc-fgl-prof, libghc-polyparse-dev (<< 1.13), libghc-polyparse-dev (>= 
> 1.9), libghc-polyparse-prof, libghc-temporary-dev (<< 1.3), 
> libghc-temporary-dev (>= 1.1), libghc-temporary-prof, libghc-text-dev, 
> libghc-text-prof, libghc-wl-pprint-text-dev (<< 1.2.0.0), 
> libghc-wl-pprint-text-dev (>= 1.1.0.0), libghc-wl-pprint-text-prof, ghc-doc, 
> libghc-colour-doc, libghc-dlist-doc, libghc-fgl-doc, libghc-polyparse-doc, 
> libghc-temporary-doc, libghc-text-doc, libghc-wl-pprint-text-doc
> Filtered Build-Depends: cdbs, debhelper (>= 9), ghc (>= 8), ghc-prof, 
> haskell-devscripts (>= 0.13), libghc-colour-dev (<< 2.4), libghc-colour-dev 
> (>= 2.3), libghc-colour-prof, libghc-dlist-dev (<< 0.9), libghc-dlist-dev (>= 
> 0.5), libghc-dlist-prof, libghc-fgl-dev (<< 5.6), libghc-fgl-dev (>= 5.4), 
> libghc-fgl-prof, libghc-polyparse-dev (<< 1.13), libghc-polyparse-dev (>= 
> 1.9), libghc-polyparse-prof, libghc-temporary-dev (<< 1.3), 
> libghc-temporary-dev (>= 1.1), libghc-temporary-prof, libghc-text-dev, 
> libghc-text-prof, libghc-wl-pprint-text-dev (<< 1.2.0.0), 
> libghc-wl-pprint-text-dev (>= 1.1.0.0), libghc-wl-pprint-text-prof, ghc-doc, 
> libghc-colour-doc, libghc-dlist-doc, libghc-fgl-doc, libghc-polyparse-doc, 
> libghc-temporary-doc, libghc-text-doc, libghc-wl-pprint-text-doc
> dpkg-deb: building package 'sbuild-build-depends-haskell-graphviz-dummy' in 
> '/<>/resolver-leDeuw/apt_archive/sbuild-build-depends-haskell-graphviz-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-haskell-graphviz-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-leDeuw/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-leDeuw/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-leDeuw/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-leDeuw/apt_archive ./ Sources [714 B]
> Get:5 copy:/<>/resolver-leDeuw/apt_archive ./ Packages [780 B]
> Fetched 2457 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install haskell-graphviz build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-haskell-graphviz-dummy : Depends: libghc-fgl-dev (< 
> 5.6) but 5.6.0.0-2 is to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   
http://aws-logs.debian.net/2018/05/02/haskell-graphviz_2999.19.0.0-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Bug#897540: r-bioc-variantannotation: FTBFS: g++: error: /libtabix.a: No such file or directory

[Andreas Tille]

Hi Lucas,

thanks for your QA effort.

On Wed, May 02, 2018 at 10:53:42PM +0200, Lucas Nussbaum wrote:
> > gcc -std=gnu99 -I/usr/share/R/include -DNDEBUG -D_USE_KNETFILE -DBGZF_CACHE 
> > -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE 
> > -I"/usr/lib/R/site-library/S4Vectors/include" 
> > -I"/usr/lib/R/site-library/IRanges/include" 
> > -I"/usr/lib/R/site-library/XVector/include" 
> > -I"/usr/lib/R/site-library/Biostrings/include" 
> > -I"/usr/lib/R/site-library/Rsamtools/include"-fpic  -g -O2 
> > -fdebug-prefix-map=/build/r-base-3.4.4=. -fstack-protector-strong -Wformat 
> > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g  -c writevcf.c 
> > -o writevcf.o
> > Error: Functions found when exporting methods from the namespace 'IRanges' 
> > which are not S4 generic: 'endoapply', 'mendoapply'
> > Execution halted
> > Error: Functions found when exporting methods from the namespace 'IRanges' 
> > which are not S4 generic: 'endoapply', 'mendoapply'
> > Execution halted
> > Error: Functions found when exporting methods from the namespace 'IRanges' 
> > which are not S4 generic: 'endoapply', 'mendoapply'
> > Execution halted
> > g++ -shared -L/usr/lib/R/lib -Wl,-z,relro -o VariantAnnotation.so 
> > Biostrings_stubs.o IRanges_stubs.o R_init_VariantAnnotation.o 
> > XVector_stubs.o dna_hash.o rle.o strhash.o utilities.o vcffile.o vcftype.o 
> > writevcf.o /libbam.a /libbcf.a /libtabix.a -lz -pthread -L/usr/lib/R/lib -lR
> > Error: Functions found when exporting methods from the namespace 'IRanges' 
> > which are not S4 generic: 'endoapply', 'mendoapply'
> > Execution halted
> > Error: Functions found when exporting methods from the namespace 'IRanges' 
> > which are not S4 generic: 'endoapply', 'mendoapply'
> > Execution halted
> > Error: Functions found when exporting methods from the namespace 'IRanges' 
> > which are not S4 generic: 'endoapply', 'mendoapply'
> > Execution halted
> > g++: error: /libbam.a: No such file or directory
> > g++: error: /libbcf.a: No such file or directory
> > g++: error: /libtabix.a: No such file or directory
> > make[1]: *** [/usr/share/R/share/make/shlib.mk:6: VariantAnnotation.so] 
> > Error 1

while this issue seems totally unrelated to the new upstream version of
BioConductor packages I will upload all preconditions for the new
version first and check the issue in the new version.

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#896791: marked as done (gringo: missing build dependency on python3-distutils)

[Debian Bug Tracking System]

Your message dated Thu, 03 May 2018 06:49:45 +
with message-id 
and subject line Bug#896791: fixed in gringo 5.2.2-6
has caused the Debian Bug report #896791,
regarding gringo: missing build dependency on python3-distutils
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.)


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

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

...
Traceback (most recent call last):
  File "/build/1st/gringo-5.2.2/cmake/python-site.py", line 1, in 
from distutils.sysconfig import get_python_lib, get_config_vars
ModuleNotFoundError: No module named 'distutils.sysconfig'


Due to

python3.6 (3.6.5~rc1-2) unstable; urgency=medium

  * python3.6: Drop dependency on python3-distutils.
...
 -- Matthias Klose   Tue, 20 Mar 2018 14:29:58 +0800
--- End Message ---
--- Begin Message ---
Source: gringo
Source-Version: 5.2.2-6

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

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

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

Debian distribution maintenance software
pp.
Ralf Treinen  (supplier of updated gringo 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, 03 May 2018 08:30:23 +0200
Source: gringo
Binary: gringo
Architecture: source
Version: 5.2.2-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Ralf Treinen 
Description:
 gringo - grounding tools for (disjunctive) logic programs
Closes: 896791
Changes:
 gringo (5.2.2-6) unstable; urgency=medium
 .
   * Team upload
   * Added build-dependency python3-distutils in order to fix FTBFS. Thanks
 to Adrian Bunk for the patch (closes: #896791)
   * Added debian/gbp.conf with pristine-tar=True
Checksums-Sha1:
 cc738f88332b5a67cb08612759b76bade096637f 2087 gringo_5.2.2-6.dsc
 fa970402ff2a74e0e2f43dc199830a86a44beb8f 13992 gringo_5.2.2-6.debian.tar.xz
 ab620833756b069e20ca41cbe1182bb2c6ea0b36 7282 gringo_5.2.2-6_source.buildinfo
Checksums-Sha256:
 2c0b27e0191a6dce7bfdcc462faaf55c7e146273d7f58d1126dae317889103f7 2087 
gringo_5.2.2-6.dsc
 a669078df87c7eace3c64457171e60c79cf1223737a5e387fd50c008e5efc1fb 13992 
gringo_5.2.2-6.debian.tar.xz
 45425f06fc708838508dfa15f3454db297430b659dca3c42054529c39b7956df 7282 
gringo_5.2.2-6_source.buildinfo
Files:
 840129cda925a31946e17da61a5e4694 2087 interpreters optional gringo_5.2.2-6.dsc
 e74e72062660f024cdafa5af0e189b3a 13992 interpreters optional 
gringo_5.2.2-6.debian.tar.xz
 65da917acfa6c7180572b77b3217d129 7282 interpreters optional 
gringo_5.2.2-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEAgVIKeEtDyqOZI5idFxHZtTKzf8FAlrqrMIACgkQdFxHZtTK
zf9rcBAAsapungHQgqo+GMk8UtZhQlYu1dcLMhxZB027Pk19Prlx+WSWGtY/UkI+
ITbjZXJIqv5wq+BWFFDUQFNVWLgCDCR1hwKzTqs95jJ/0RZuKSLU4N/wnbgKboxB
+rFbrjObx1VptPDRnpXV3pKAnqieDEBirrSWcNZ3TsJKCSLRIkTQvgUt5nZfofcJ
kDxr0TDha4KWM1STar5CdjvqIdwAgwxBtCNuUr5Ip1axgJZTgFQ2/WC/fLIffmXJ
yRF09Ft2SgShTInL7UEwhCuyuZ++Dvh0YMJX9jNiclxQ5xJME1tMJnbQC3c6BbQ2
HKcr8XBy7DUDMTYqI+uwYQU8PYvU0ftJcao7N2N7fsOykZTfcWXTu9JzhLgnC8J1
7pmB8g47A9BW77qXDR6ANQdQBOahY0KOMkmlne1EwPlxyv7u4QXjM11/9MG6T4hQ
FKxQaTB4/YSGqPIC1+OMc30VEFD1XZpxAm/PZTy9A0IuqqANtt1Vs2vqLfO9FuO0
bppcGRRQAfufoYEMzM/Rwyli5y38mSfjSCGUg5YtlIaV++VC1sKwzlfOvb9KS+ZU
RwbERERnm4DthFE21SCMx/fsa+GZ7wMXnk1OtgwXzw78d1CIyUKmVGFzju3aalJ1
hzScENWmuK5qUseAkDd5F0OphyKimpU35B/kFJ6dvIMlm4qteS4=
=62y9
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#897487: sfcgal: FTBFS: value_semantic.hpp:167: undefined reference to `boost::program_options::validate(boost::any&, std::vector<std::__cxx11::basic_string<char, std::char_traits

[Debian Bug Tracking System]

Processing control commands:

> tags -1 upstream
Bug #897487 [src:sfcgal] sfcgal: FTBFS: value_semantic.hpp:167: undefined 
reference to `boost::program_options::validate(boost::any&, 
std::vector, std::allocator > > const&, 
std::__cxx11::basic_string*, int)'
Added tag(s) upstream.
> forwarded -1 https://github.com/Oslandia/SFCGAL/issues/166
Bug #897487 [src:sfcgal] sfcgal: FTBFS: value_semantic.hpp:167: undefined 
reference to `boost::program_options::validate(boost::any&, 
std::vector, std::allocator > > const&, 
std::__cxx11::basic_string*, int)'
Set Bug forwarded-to-address to 'https://github.com/Oslandia/SFCGAL/issues/166'.

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

Bug#897487: sfcgal: FTBFS: value_semantic.hpp:167: undefined reference to `boost::program_options::validate(boost::any&, std::vector<std::__cxx11::basic_string<char, std::char_traits, std::alloc

[Sebastiaan Couwenberg]

Control: tags -1 upstream
Control: forwarded -1 https://github.com/Oslandia/SFCGAL/issues/166

Hi Lucas,

Thanks for reporting this issue.

I've confirmed the build failure, which I suspect was triggered by the
recent update of CGAL to 4.12, and forwarded it upstream.

Kind Regards,

Bas