Your message dated Fri, 06 Jan 2017 03:07:48 +0000
with message-id <e1cpkse-0002jk...@fasolo.debian.org>
and subject line Bug#850336: fixed in rmpi 0.6-6-2
has caused the Debian Bug report #850336,
regarding rmpi: FTBFS (Cannot find mpi.h header file)
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.)


-- 
850336: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850336
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:rmpi
Version: 0.6-6-1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -B"
but it failed:

--------------------------------------------------------------------------------
[...]
 debian/rules build-arch
CDBS WARNING:    simple-patchsys.mk is deprecated since 0.4.85 - please use 
source format 3.0 (quilt) instead
test -x debian/rules
mkdir -p "."
/usr/bin/make -f debian/rules reverse-config
make[1]: Entering directory '/<<PKGBUILDDIR>>'
CDBS WARNING:    simple-patchsys.mk is deprecated since 0.4.85 - please use 
source format 3.0 (quilt) instead
make[1]: 'reverse-config' is up to date.
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
if [ "debian/stamp-patched" = "reverse-patches" ]; then rm -f 
debian/stamp-patched; fi
patches: 
if [ "debian/stamp-patched" != "reverse-patches" ]; then touch 
debian/stamp-patched; fi
if [ "debian/stamp-patched" != "reverse-patches" ] ; then \

[... snipped ...]

if test -f /usr/bin/xvfb-run; then                      \
                 xvfb-run -a                    \
                        R CMD INSTALL -l 
/<<PKGBUILDDIR>>/debian/r-cran-rmpi/usr/lib/R/site-library --clean     \
                                "--no-test-load" .      \
                                "--built-timestamp=\"Sat, 25 Jun 2016 07:43:11 
-0500\""                 \
                                ;                               \
        else                                                    \
                 R CMD INSTALL -l 
/<<PKGBUILDDIR>>/debian/r-cran-rmpi/usr/lib/R/site-library    \
                                --clean "--no-test-load" .  \
                                "--built-timestamp=\"Sat, 25 Jun 2016 07:43:11 
-0500\""                 \
                                ;                               \
        fi
* installing *source* package 'Rmpi' ...
** package 'Rmpi' successfully unpacked and MD5 sums checked
checking for gcc... gcc -std=gnu99
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc -std=gnu99 accepts -g... yes
checking for gcc -std=gnu99 option to accept ISO C89... none needed
checking how to run the C preprocessor... gcc -std=gnu99 -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking mpi.h usability... no
checking mpi.h presence... no
checking for mpi.h... no
configure: error: "Cannot find mpi.h header file"
ERROR: configuration failed for package 'Rmpi'
* removing '/<<PKGBUILDDIR>>/debian/r-cran-rmpi/usr/lib/R/site-library/Rmpi'
/usr/share/R/debian/r-cran.mk:98: recipe for target 'R_any_arch' failed
make: *** [R_any_arch] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary-arch gave error exit 
status 2
--------------------------------------------------------------------------------

This is just how the build ends, not necessarily the relevant part.

I've put several build logs here:

https://people.debian.org/~sanvila/build-logs/rmpi/

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

The bug should be reproducible with sbuild on a single CPU virtual machine.

Thanks.

--- End Message ---
--- Begin Message ---
Source: rmpi
Source-Version: 0.6-6-2

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

Debian distribution maintenance software
pp.
Dirk Eddelbuettel <e...@debian.org> (supplier of updated rmpi 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: SHA1

Format: 1.8
Date: Thu, 05 Jan 2017 19:59:00 -0600
Source: rmpi
Binary: r-cran-rmpi
Architecture: source amd64
Version: 0.6-6-2
Distribution: unstable
Urgency: medium
Maintainer: Dirk Eddelbuettel <e...@debian.org>
Changed-By: Dirk Eddelbuettel <e...@debian.org>
Description:
 r-cran-rmpi - GNU R package interfacing MPI libraries for distributed computing
Closes: 850336
Changes:
 rmpi (0.6-6-2) unstable; urgency=medium
 .
   * configure.ac: Add a new location for mpi.h to account for updated
     layout in Open MPI 2.0; will send upstream too     (Closes: #850336)
   * configure: Updated accordingly
Checksums-Sha1:
 8fadd0c6c22b245796d2f18c9e39feccbd5f2d95 1658 rmpi_0.6-6-2.dsc
 802c9403f6ad0ad601423bf5b40f74c316b5e504 4445 rmpi_0.6-6-2.diff.gz
 ab7400d07bf1daf545918f75653ef42e16fca7e8 33896 
r-cran-rmpi-dbgsym_0.6-6-2_amd64.deb
 1a19840238510d900f58ecef3668aec9ae89ba79 194546 r-cran-rmpi_0.6-6-2_amd64.deb
 4f565706315dc888814af0b53d8fe808bece17e1 8326 rmpi_0.6-6-2_amd64.buildinfo
Checksums-Sha256:
 75cfe1d33b55513ab9b3d0b63404a792c2f96d117bd6c51665d2235d644f88cf 1658 
rmpi_0.6-6-2.dsc
 422352a326e7ff62fb5c31f7fdb473fe5cecd2f4a7231678034613273bc69edc 4445 
rmpi_0.6-6-2.diff.gz
 74f13c13794aeee6951fe256c98dd4da989244cd2d287ebda25a07bbf20cab72 33896 
r-cran-rmpi-dbgsym_0.6-6-2_amd64.deb
 4c5a41632d567811ec3988c8729704c6ebcaf67f1cd2f9620b77266fb159708b 194546 
r-cran-rmpi_0.6-6-2_amd64.deb
 1626488ba3a87541acb2ac86ab61721f82ca3808d59f775d7190649929724f57 8326 
rmpi_0.6-6-2_amd64.buildinfo
Files:
 5685fbb88be19e60920e81afa66e6b8a 1658 gnu-r optional rmpi_0.6-6-2.dsc
 f1dfe16f5bb594aba1cdcd04be472bc4 4445 gnu-r optional rmpi_0.6-6-2.diff.gz
 3ac0528b198b74c37b3e4ffa02a58bd7 33896 debug extra 
r-cran-rmpi-dbgsym_0.6-6-2_amd64.deb
 808b40d7139c6afaadb2e6312197ca18 194546 gnu-r optional 
r-cran-rmpi_0.6-6-2_amd64.deb
 4cd8aeea151aac49bb3a1d730f68b151 8326 gnu-r optional 
rmpi_0.6-6-2_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIVAwUBWG76JKFIn+KrmaIaAQIFMxAAi1aB1erEG/eKQbvWyq5hQY/EO2P40Vfr
+W3BiWk6CYxAXHTV3FX/HxRGclR7pXcsSHKhgUsSBSpN2hZS0RrFDQwb0h+bLMhh
Sexwn4WJht6p+ARD7sG7efMXsZzRWg2nvfgPY4lRAaKl7MVWKPw4G5Bpy0psWq+q
Po+nhnZOpPJOXAAKYYIELlXZqYUOBX/uw+6IHM9rGLCEAAJWs+c2rVzE7kjGFc0d
3B5GUMBZu4mnDTX4++D1xIdU9GKy8jdMn1TRQutE9Z1xzBkwMc0FzesCKCncPpSk
fd4y3NpLKrIBwVMphWIjYV7XgDqOWBADvfsOrvfNHFldlYtNVaeGkxcTgd2T5IFE
TYnm7nB/nhA3A+JzmDn7JwOs1Ft4Oz7khWkLhnSk5/1d/1nsJ2Sm3Bt/0XcSVzv5
psjNnS9VJlYt3To7UdwDpmjSvi7O3TVtaNXhr1UxUk8Zsm05QPUKp1Cwp8tv5owI
z0K3/JFxzNTtKxb+cMfPdrSoczkwfpsMeIwsJKJlR1dreFs5njYNPQgUXl6e2cdt
ZjMczgZ0A5LLfdcEGbIDkOA9HTryJYeWBBuEA30m3qI4+rjvfoxB9Yo7zpjyahiU
nLIVce0wHo0ZPBvo85CjFhL0KP4opBHO911ujWHDkDFgDrmCEWa9GbJJuqHpH7+L
L6WjjDDSOAE=
=/E2a
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to