openssh: no pre-release sanity check? [Re: ssh-to-rawhide hangs
opensource at till.name
Sun Sep 11 20:31:55 UTC 2011
On Sun, Sep 11, 2011 at 10:44:35AM -0400, Clyde E. Kunkel wrote:
> On 09/11/2011 04:33 AM, Jim Meyering wrote:
> > darrell pfeifer wrote:
> >> Fails for me too, with the same error.
> > Thanks for confirming that.
> > I don't mean to be rude or inflammatory, but do have to wonder how such
> > a fundamentally-broken package was released -- even to rawhide. In the
> > fedora openssh release process, isn't there some sort of sanity check
> > that would catch this before inflicting it on all rawhide users?
> Maybe there needs to be a classification for rawhide similar to the
> karma system for updates-testing, but limited to just a set of packages
> that should just always work (maybe openssh would be one). For such
> packages, there should be a test validation set that the maintainer runs
> to automatically allow the package into rawhide.
AutoQA will eventually allow to run functional tests for packages afaik.
This is imho the right place to put more effort into.
More information about the devel