[Debian-med-packaging] Bug#986524: freecontact: FTBFS: devlibs error: There is no package matching [libgfortran-8-dev] and noone provides it, please report bug to d-shlibs maintainer

Lucas Nussbaum lucas at debian.org
Wed Apr 7 07:44:39 BST 2021


Source: freecontact
Version: 1.0.21-8
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210406 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> dh_install
> d-shlibmove --commit \
>             --multiarch \
>             --exclude-la \
>             --devunversioned \
>             --override s/libblas3-dev/libblas-dev/ \
>             --v5 \
>                     --override s/libgfortran[345]-dev/libgfortran-8-dev/ \
>                     --override s/libquadmath0-dev/libgcc-8-dev/ \
>             --override s/liblapack3-dev/liblapack-dev/ \
>             --movedev debian/tmp/usr/include/* usr/include \
>             debian/tmp/usr/lib/*/*.so
> Library package automatic movement utility
>  --> libblas-dev package exists.
> devlibs error: There is no package matching [libgfortran-8-dev] and noone provides it, please report bug to d-shlibs maintainer
>  --> liblapack-dev package exists.
> make[1]: *** [debian/rules:29: override_dh_install] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2021/04/06/freecontact_1.0.21-8_testing.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!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

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.



More information about the Debian-med-packaging mailing list