> * Removed spellcast
I uploaded yesterday spellcast{,-doc} packages built in my woody
environment to stable. Should I go ahead and submit binary packages for the
remaining architectures? (i.e. all save i386) Can you consider moving
spellcast to 'further'? Sorry for not doing this in the scheduled
time...
> tiger stable 2.2.4-22 alpha arm hppa i386 ia64 m68k mips mipsel powerpc s390 sparc source
> tiger updates 2.2.4-23 alpha arm hppa i386 ia64 m68k mips mipsel powerpc s390 sparc source
I would like this to go in. What's pending? Also, could I upload a new
version updating deb_advisories?
> spellcast stable 1.0-12 alpha arm hppa i386 ia64 m68k mips mipsel powerpc s390 sparc source
> spellcast-doc stable 1.0 alpha arm hppa i386 ia64 m68k mips mipsel powerpc s390 sparc source
>
> This package is non-free, and not going to become free again,
> so there's no desire to compile it for all architectures and
> move it into non-free. See Bug#241002.
Well, compiling spellcast for all architectures is probably a few hours
work on my side. This package is not really very "high profile" and I
wouldn't really mind if it was removed from stable.... your call.
Regards
Javier
Attachment:
signature.asc
Description: Digital signature