Re: What to do about old package left over from move to non-US?

[Daniel Stone <daniel@kabuki.openfridge.net>]

On Tue, May 22, 2001 at 07:48:44PM -0400, Jimmy Kaplowitz wrote:
> Hi all. I have moved my package althea to non-US because it now supports SSL.
> The old package, version 0.4.4a, is still in main. Once the new version is
> installed into non-US, should I file a bug (what severity?) against
> ftp.debian.org requesting the old version's removal? Or, should I keep it
> around until security problems are found in it so that those people who don't
> use non-US will see my package? I should mention, the package soon to be in
> non-US can easily be compiled without SSL with a simple and short Makefile
> change which I have documented in README.Debian and referred to in the package
> description, so it is of use to people who can't use non-US.

Hi Jimmy,
If you want it in non-US, then file a bug against ftp.debian.org requesting
its removal, however I would recommend splitting the package into althea (no
crpyto, in ftp.debian.org), and althea-ssl (crypto, in non-US), or althea
(with crypto, non-US), and althea-nossl (no crypto, in ftp.debian.org), with
that simple Makefile change you suggested.

:) d

-- 
Daniel Stone		<daniel@kabuki.openfridge.net> <daniel@kabuki.sfarc.net>