Stuart R. Anderson wrote: > > There are 2 Serious bugs against the LSB dev package that need to be > resolved. One of them will need a freeze exception to allow a new > version of the package into testing. > > First the easy one: > > #478180 [lsb-build-cc2] lsb-build-cc2 depends on gcc-3.3, g++-3.3 which > isn't built anymore > > I have filed a bug (though I can't find the bug number right now), > asking for > all of the LSB v2 package to be completely removed from everything post > Etch. > V2 of the spec has come and been gone long enough that these package are no > longer needed. The list of package which should be removed is lsb-appchk2, > lsb-build-base2, and lsb-buildcc2.
Ok, removal bugs filed to be sure they do get removed. > Now for the one that requires an exception: > > #478174 [lsb-build-cc3] lsb-build-cc3 depends on g++-3.4 which > is not built anymore > > The fix for this is part of the new version from upstream of the LSB tools. > This package is in unstable now, but this package was removed from testing > a while back during a sweep of packages that had invalid dependencies. > It's removal from testing may mean that it is not showing up on some > lists of bugs that need resolving for Lenny. It needs an exception to be > allowed back into testing now. unblocked. > Due to a poor choice made almost 10 years ago, the LSB development packages > are distributed as seperate source bundles, instead of a single source > bundle. This means that the rest of the packages that should be updated > at the > same time as lsb-build-cc3 are in fact seperate packages instead of being > multiple binary package from a single source package. Ok, should probably be fixed for squeeze. > The complete list of related packages, which need an exception to go > into testing/lenny is lsb-appchk3, lsb-build-base3, lsb-build-cc3, and > lsb-pkgchk3. unblocked and removal bugs filed for the not anymore supported architectures. Please request updates in Packages-arch-specific for lsb-appchk3 and lsb-pkgchk3. Cheers Luk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
