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? -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
