[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#715228: marked as done (nmu: fgrun_1.6.0-1)



Your message dated Sun, 07 Jul 2013 15:22:05 +0100
with message-id <1373206925.12336.27.camel@jacala.jungle.funky-badger.org>
and subject line Re: Bug#715228: nmu: fgrun_1.6.0-1
has caused the Debian Bug report #715228,
regarding nmu: fgrun_1.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 owner@bugs.debian.org
immediately.)


-- 
715228: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=715228
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: binnmu

nmu fgrun_1.6.0-1 . amd64 i386 . -m "Rebuild against simgear 2.6"

fgrun is currently uninstallable in sid:

  fgrun/i386 unsatisfiable Depends: simgear2.4.0 (>= 2.4.0)
  fgrun/amd64 unsatisfiable Depends: simgear2.4.0 (>= 2.4.0)

it builds successfully against simgear 2.6, (but simgear 2.6 ftbfs on
!linux-x86).


Andreas

--- End Message ---
--- Begin Message ---
On Sun, 2013-07-07 at 08:52 +0200, Andreas Beckmann wrote:
> nmu fgrun_1.6.0-1 . amd64 i386 . -m "Rebuild against simgear 2.6"
> 
> fgrun is currently uninstallable in sid:
> 
>   fgrun/i386 unsatisfiable Depends: simgear2.4.0 (>= 2.4.0)
>   fgrun/amd64 unsatisfiable Depends: simgear2.4.0 (>= 2.4.0)
> 
> it builds successfully against simgear 2.6, (but simgear 2.6 ftbfs on
> !linux-x86).

The latter is likely why nothing's been done about fgrun before.
Scheduled, with a dep-wait on simgear2.6.0 on the assumption that
someone will bother to fix it eventually...

Regards,

Adam

--- End Message ---

Reply to: