Bug#713126: gcj-4.6: FTBFS: unsatisfiable build-dependency: automake (< 1:1.12) but 1:1.13.3-1 is to be installed
Source: gcj-4.6
Version: 4.6.4-2
Severity: serious
Tags: jessie sid
User: debian-qa@lists.debian.org
Usertags: qa-ftbfs-20130620 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
> ┌──────────────────────────────────────────────────────────────────────────────┐
> │ Install gcj-4.6 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-gcj-4.6-dummy : Depends: automake (< 1:1.12) but 1:1.13.3-1 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/ftbfs-logs/2013/06/20/gcj-4.6_4.6.4-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.
Reply to: