On 2014-01-25 14:31, Joachim Breitner wrote: > Dear Megaf, > Hi,
Adding the maintainer to CC. > Am Samstag, den 25.01.2014, 10:59 -0200 schrieb Megaf: >> Hi all. I was wondering why there's no Flightgear for Wheezy, then I >> found out this. >> https://lists.debian.org/debian-release/2012/11/msg01284.html >> >> >> The thing is, all those bugs are all fixed now. >> >> >> Bellow a short chat I had at Flightgear official channel at >> irc.flightgear.org >> >> * Now talking on #flightgear >> >> [....] > [...] > The current status of the package with regard to entering wheezy can be > seen on > http://packages.qa.debian.org/f/flightgear.html > where it says: > out of date on kfreebsd-amd64: flightgear (from 2.4.0-1.2) > out of date on kfreebsd-i386: flightgear (from 2.4.0-1.2) > flightgear (source, i386, amd64, armel, armhf, kfreebsd-amd64, > kfreebsd-i386, mips, mipsel, powerpc, s390x, sparc, ia64) has new bugs! > Updating flightgear introduces new bugs: #724686. > > That but says it is blocked by #720816, which was only closed recently. > So there is progress! > While it may have (also) been blocked by #720816, which was fixed recently, it is *still* blocked by #724686, which remains unfixed. There is a patch for that bug, but it hasn't been uploaded yet despite being available since 26th of Sep. I have been told that it has been applied to the repository, so hopefully it just need someone to do an upload (and accordingly, the CC of the flightgear maintainers). > The page also says that flightgear is part of two transitions, which can > further slow things down. > Once #724686 is fixed, we need to finish two "local" transitions around flightgear. One being openscenegraph and the other being simgear (the latter also maintained by the FlightGear maintainers). simgear needs flightgear fixed (#724686) and fgrun (#719402). Alternatively, the maintainers of fgrun willing (that would be the FlightGear maintainers again), we can ask the FTP masters to decruft simgear despite breaking fgrun. This would make fgrun uninstallable in sid, but it is already RC buggy and not in testing, so from the RT PoV, we don't mind that as a resolution. This leaves the openscenegraph transition. This is currently waiting for choreonoid [mipsel], fgrun (but see above), flightgear [kfreebsd-* mips], libcitygml, openwalnut and simgear. Note, the listed packages are source packages; the actual problem is one (or more) of the binary packages built from said sources. Some of these will probably just need a binNMU to finish. > So I guess eventually things will work out, just be patient for a little > while. > > Greetings, > Joachim > > > This situation will not resolve itself on its own. It needs a "Do'er" to get the mess cleaned up - I suspect that mostly that someone just needs to prod people into doing their part and then filing a binNMU request for the subset of the packages above that can be binNMU'ed (which excludes packages that are "horribly" broken, e.g. FTBFS). These transitions are currently not handled by the release team. Openscenegraph was considered but the request was closed (see #729289). I suppose we ought to reopen it, since the transition is certainly not done. If you (maintainer or otherwise) are interested in getting the situation resolved, but unsure how to approach it, I don't mind spending an hour or two showing you the ropes. "But I will only show you the door"[1]. As a member of the Release Team, I want to know there is someone taking responsibility for making flightgear remain RC bug free, so it is not removed from testing again due to inactivity. ~Niels [1] To (almost) quote a certain movie. -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52e95b67.4050...@thykier.net
