I think I will shortly upload a the new upstream, but restrict the number of supported arch
Christian Lucas Nussbaum wrote: > On 02/10/07 at 21:45 +0200, Christian Bayle wrote: > >>> Lucas Nussbaum wrote: >>> >>>>> Automatic build of crystalspace_1.0-20070508-1 on >>>>> debian-31.osdl.marist.edu by sbuild/s390 98 >>>>> >>>>> >>>> [...] >>>> >>>> >>>>> g++ -c -o ./out/linux390/optimize/plugins/video/cursor/cursor.o -I. >>>>> -I./include -I./include -pipe -Wall -Wno-unknown-pragmas >>>>> -fvisibility=hidden -I/usr/local/include -fno-exceptions >>>>> -fvisibility-inlines-hidden -O3 -fomit-frame-pointer -ffast-math -g2 >>>>> -fPIC plugins/video/cursor/cursor.cpp >>>>> >>>>> ...skipped cscursor.so for lack of libcrystalspace.a... >>>>> make[1]: *** [all] Error 1 >>>>> make[1]: Leaving directory `/build/buildd/crystalspace-1.0-20070508/CS' >>>>> make: *** [build-arch-stamp] Error 2 >>>>> ****************************************************************************** >>>>> Build finished at 20070508-1809 >>>>> FAILED [dpkg-buildpackage died] >>>>> >>>>> >>> Hi Christian, >>> >>> Crystalspace 1.2rc2 is available from upstream. Maybe it's worth trying >>> to package it, to see if that bug is fixed? >>> >>> >> I don't believe a lot in this, the main problem with CS is that there is >> a system of dynamic modules that link with static libs when the dynamic >> version is not available. The is no obligation in the policy to provide >> a dynamic module. >> I think the best I should do is to restrict support to some arch, so the >> package can go in testing. >> > > Hi Christian, > > Any progress on this? > > I'm asking because crystalspace shows up very high on my list of > packages that should maybe be removed from Debian (RC buggy for a long > time, not in testing for a long time, low popcon). > > Thank you, > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
