On Fri, Dec 02, 2005 at 12:37:11PM +0200, Damyan Ivanov wrote: > I am puzzled about how to proceed. > firebird2 packages are uploaded on i386, built with new allocator and don't > export any suspicious symbols. > At the time of the upload, however, amd64 buildd were still with g++ with c2 > allocator and therefore the amd64 packages are still using the old allocator > use the wrong symbols. > I was too quick with the upload, I know. I've had to wait for the official > announcement that all buildds are updated. Sorry about that. > The questions now is how to proceed. > If amd64 was an official arch, then I should request a binNMU here, AFAIU. But > what about the unofficial amd64? You'll need to contact the amd64 buildd maintainers to request a binNMU. Please see <http://www.debian.org/ports/amd64/> for various contact links. Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. vorlon@debian.org http://www.debian.org/
Attachment:
signature.asc
Description: Digital signature