Your message dated Tue, 24 Jul 2012 13:12:55 +0200
with message-id <500e8337.6090...@arcticnet.no>
and subject line Re: [pkg-fgfs-crew] Bug#682644: flightgear: FTBFS:
build-dependency not installable: simgear-dev (>= 2.6.0-1)
has caused the Debian Bug report #682644,
regarding flightgear: FTBFS: build-dependency not installable: simgear-dev (>=
2.6.0-1)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
682644: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682644
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: flightgear
Version: 2.6.0-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120724 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 flightgear 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-flightgear-dummy : Depends: simgear-dev (>= 2.6.0-1)
> but it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.
The full build log is available from:
http://people.debian.org/~lucas/logs/2012/07/24/flightgear_2.6.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.
--- End Message ---
--- Begin Message ---
On 24. juli 2012 11:38, Lucas Nussbaum wrote:
> Source: flightgear
> Version: 2.6.0-1
> Severity: serious
> Tags: wheezy sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20120724 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 flightgear build dependencies (apt-based resolver)
>> │
>> └──────────────────────────────────────────────────────────────────────────────┘
Out of curiosity, are these bugs automatically or manually filed? In
either case, it doesn't seem useful to file a bug report because of a
build dependency that's sitting in ftp-master's NEW queue, since there's
not much the package maintainer can or should do about it (short of just
not uploading the dependent package at the same time as its
dependencies, I suppose, but delaying is not always convenient for a
volunteer maintainer, and might *also* cause temporary brokenness since
flightgear 2.4 should not be built with simgear 2.6 - and besides, once
everything's uploaded, it's too late to do anything about).
If this is automatic, is there any way to also automatically check the
NEW queue?
--- End Message ---
