Jussi Lehtola wrote:
> Why not? The purpose of testing is to find out if the package breaks
> something. In the case of a new package there is no functionality of it
> to break; the only possibility of getting into trouble is if the package
> itself hasn't been made correctly (clashing file names or so on), which
> should be in any case picked up in the review.
But you still risk pushing out a completely broken new package, which
doesn't reflect well on you. ;-)
One of the ways this can happen is if you inadvertently built your new
package against a buildroot override which is not in stable yet. Or of
course the package itself could be broken.
Kevin Kofler
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
