severity 387783 serious
thanks
#include <hallo.h>
* Andreas Barth [Thu, Oct 19 2006, 11:27:36AM]:
> * Markus Laire ([EMAIL PROTECTED]) [061019 10:49]:
> > ps. Since the decision to downgrade[2] this bug was done by Andreas
> > Barth, I don't think I have the authority to restore the severity to
> > serious, and so I wanted to contact the Release Team to know what they
> > think about this matter.
>
> Just as a first note - if the maintainers consider this bug as serious,
> it is serious, and they should feel free to upgrade the bug again. I'll
> write something on the remainder soon.
Well, I consider it serious and I upgrading the severity again.
<Ganneff> Zomb: feel free.
>From my POV (and IANAL) there are not many workarounds:
- replace cdrecord.c with the version from the last millenium. Problem:
there are many new features missing and there are some subtle
changes. They can be reimplemented in few days..weeks, but there is
some risk that would be not mature enough for a stable release and
some things are so obvious that JS may come back and cry about
stollen IP because the code looks similar. Remember SCO.
- we could package a cdrtools-mixture package, containing:
GPLed build-system from cdrtools-2.01.01a01 or so
only files owned/created directly by Schilling
the resulting cdrecord binary would be available under the
Schily-GPLWAR (Schilling's GPL-like With Additional Restrictions),
that is just a provisoric name because Schilling does give concrete
answers. Assuming that this would need to go into non-free, all
dependent packages would need to be moved to contrib.
But... OTOH, if we go this way, we could also create a "cdrtools-src"
package which our users can use to build custom cdrecord/mkisofs/...
packages.
- ignore possible consequences, remove the offending code or disable
its function by technical measures. That is what some people already
do.
Eduard.
--
Der wahre Heldenmut besteht darin, über das Elend des Lebens erhaben
zu sein.
-- Napoleon I. Bonaparte
