Hi Joachim, On Fri, Jan 19, 2007 at 11:35:19PM +0000, Joachim Breitner wrote: > Am Samstag, den 20.01.2007, 00:07 +0100 schrieb Aurélien GÉRÔME: > > The powerpc package is unusable, so this bug is RC. To lower the > > severity to important, you can ask for the removal of the powerpc deb > > from the archive and restrict the build of xaralx to some architectures > > where the package is known to work on. > > > > Please do not take this is as an offense, this is not meant to be. :) > > I don’t have a powerpc box around to test this. I could do as you said > and have only i386 included, but I actually feel like just having xaralx > removed from testing anyways: It was not completely free’ed as promised > and xaralx is not important enough to increase the non-free section of > etch IMHO. > > Hopefully xaralx development will pick up again and the core will become > free as well. Until then, we maybe should keep it out of testing > alltogether, for example with this RC bug :-)
Sure. :) > Do I need to take action or will xaralx be removed automatically from > etch now that is has an RC bug? The package is currently in testing, so you will have to mail debian-release to ask for its removal, or the Release Managers will see this bug and remove the package by themselves. :) Well, you have 2 choices: 1/ You can keep the powerpc deb in unstable with this RC bug. 2/ You can release a package with only i386 and amd64 in the Architecture field and downgrade the severity of this bug. With this, only the known working architectures will enter testing (in non-freeze state). Cheers, -- .''`. Aurélien GÉRÔME : :' : `. `'` Free Software Developer `- Unix Sys & Net Admin
signature.asc
Description: Digital signature
