Hi Daniel, I'm looking at fixing this issue, and I'd like your feedback on the proposed way to fix it: https://s.apache.org/nQsk
However, there are a couple questions I have before proceeding: * Do you think it is safe to do so? * The ASF must keep a record from all code contributions so we should never deliberately delete a commit. The offending one, though is "previous" to jclodus joining the ASF and is not reachable from any ASF release or any existing branch/tag. I guess it shouldn't be an issue then? * Since we will be pushing -mirror to the SF remote, will that trigger an email notification for each commit object pushed? (That would be potentially a huge email flood. Thanks! I. On Fri, 10 Aug 2018 at 01:56, Daniel Gruno <humbed...@apache.org> wrote: > > > On 2018/08/09 20:35:48, Olaf Flebbe <o...@oflebbe.de> wrote: > > Hi Ignasi, > > > > thanks for the explanation. > > > > Ticket is INFRA-16889. > > > > Infra found following error message: > > > > "File > > documentation/releasenotes/1.3.0-output/eucalyptus-partnercloud-s3.txt is > > 276.34 MB; this exceeds GitHub's file size limit of 100.00 MB" > > > > Daniel writes: > > > > "As stated above, you cannot sync the repo to github any longer. You'll > > have to pull out that file from the repo and wipe it from history." > > > > However I don't see immediatly the directory "documentation" within the > > jclouds repository. Do you have any clue about that directory and this file? > > It may not exist now, but it was there at some point, and that's what > breaking the sync. GitHub doesn't allow any files *in the history of the > project* to be more than 100MB. > > You're going to have to be nasty and weed out the file from the commit > history somehow, then rebase everything and force push a revised history. > > My guess is it's in the revision right after the sync broke. > > > > > Cheers, > > Olaf > >
