Xavier Grave wrote:
At least, rev 79d029250b63dd2118188370321ab18cd61eb041 of org.debian.polyorb produces usable (from a DSA point of view) code.
Glad to hear that. Congratulations.
How do I close #701338 ? One line explaining that polyorb build depends on gcc-4.9 is enough ?
Unless I misunderstand, the fix for this bug is to patch PolyORB's configure and support/idlcpp.m4 files; this does not depend on a particular compiler. Pavel said his patch was accepted upstream; I interpret this as "PolyORB upstream" but, again, I may be entirely wrong.
Do we upload to experimental 2.11~20140128-1 in order people can play with it as soon as possible ?
It is always preferable to close a bug from the changelog of PolyORB, as part of an upload. And of course, free software works best when developers "release early, release often" :) The changelog should say something like: * new upstream version (details...). Closes: #701338. or * debian/patches/701338.diff: new. Closes: #701338. (with details in the patch file itself). -- Ludovic Brenta. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/[email protected]
