Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=639369 --- Comment #11 from Fabio Massimo Di Nitto <fdinitto@xxxxxxxxxx> 2010-10-26 11:45:53 EDT --- Or you can simply use the fedorahosted release area. The URL is already known for you and even if you haven't actually uploaded a tarball there, you can still update the spec file to point to it. To release there, you simply need to scp the tarball. See how we do it for cluster STABLE3 in make/releases.mk publish target. Your releases would be in https://fedorahosted.org/releases/g/f/gfs2-utils/.... I remember at somepoint, but I might be mistaken, that some of the fedora automatic tool checks, does a URL sanity check to verify that the tarball referenced by the spec file is actually the same as the one in the fedora build cache. I'd recommend to allow that check to run smoothly (aka add the URL as it costs nothing) as a mismatch is source of questions and BZs. Fabio -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review