On 29/04/2010, at 10:50 PM, sebb wrote: > On 29/04/2010, Brett Porter <br...@apache.org> wrote: >> The correct one for reporting problems (vs new uploads) is: >> http://jira.codehaus.org/browse/MEV >> >> In general, you want to make sure it is fixed at the source first if it's an >> imported forge like Apache's. > > So, is the correct procedure as follows: > > 1) Update the hash files on the imported repository, in this case the > Apache release repo. > 2) Raise an MEV JIRA issue to get the hashes updated on the central repo. > > Or have I misunderstood something?
That would work. Though we expect that to be a really rare occurrence, and starting to use repository managers for the forges means they should never make it to central with bad hashes in the first place... - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
