On 06/04/11 15:15, Piotr Pokora wrote: >>>> Note that this is the last bit for the gir1.2 transition. If you don't >>>> drop the >>>> gir1.0-midgard2 package from unstable, midgard2-core may be removed from >>>> testing. >>> >>> I doubt there's anything I can do. >> >> There is: you can build midgard2-core with --disable-introspection and remove >> the gir1.0-midgard2 binary package. You can of course keep gir1.2-midgard2 in >> experimental. > > It doesn't make sense to provide library without gir.
Why not? It makes a lot of sense to me. This is not different than a library that builds a shared library and some, say, python bindings, and nobody uses the python bindings. You can stop building them, and the library users will still use that. This is the same with s/python/gir/. > As I wrote > earlier, let's keep it in exp, and remove from testing and sid if required. > >>> I think it has to be this way until libgda4 FTB issues are resolved. >>> >>> BTW, any hint how to debug libgda4 build segfaults? >> >> gdb? :-) > > On debian build servers? Not there. Though it's most likely reproducible from porter boxes or a VM. Cheers, Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
