[Vmware-package-maintainers] unsupported packages

[Moritz Muehlenhoff]

On Mon, Apr 20, 2009 at 10:11:36PM +0200, Nico Golde wrote:
> Hi,
> I just added vmware-package to the package-tags file to 
> reflect that we can't provide security support for this 
> package (Cced maintainers to inform them of this).
> 
> The vmware-package comes with a script that uses an upstream 
> tarball to create .deb files. The versions and md5sums of 
> the tarballs are hardcoded in the script and the user needs 
> to download the tarball himself. As far as I see this is 
> outdated and won't even work currently.
> 
> But we somehow need to reflect that we can't support this 
> package in the tracker data. So far issues regarding vmware 
> got a fix status or an NFU but in my opinion none of this is 
> really appropriate.
> 
> For stable there is no support anyway but for unstable we 
> traditionally supported packages in case we have some spare 
> time and the issue is easy fixable.
> 
> So I think we need to make a decision at this point to 
> either don't support contrib/non-free completely and mark 
> these issues as NFU or we need to introduce a tag for 
> unsupported packages (Florian what do you think?).

We should make it clear that non-free and contrib are not
supported. These installer packages for proprietary packages
don't belong into the archive anyway IMO.

Cheers,
        Moritz