I'd like to say thanks for reporting back, Alex We just fixed the repo 2~3 days ago.
So that's not a false alarm. Sorry to take it so long. Feel free to post any issue you encountered in mailing list. 2015-09-09 1:05 GMT+08:00 RJ Nowling <[email protected]>: > It was broken but we fixed it recently :) > > On Tue, Sep 8, 2015 at 12:01 PM, Alex Bordei <[email protected] > > wrote: > >> Hi RJ, >> >> Dump me. It never occurred to me it might be more than 1000 entries. >> >> I was trying to install bigtop’s RPMs on centos 7 about a week ago, got a >> few file not found errors and I thought the files might be missing from the >> repo, but everything seems to be ok now because as you said you can’t >> browse S3 except at the root. >> >> So, never mind, false alarm. >> >> Alex >> >> *---* >> *ALEX BORDEI *| Product Manager | Bigstep | T: +44 (0) 2075 109 054 >> | bigstep.com <http://www.bigstep.com/> >> >> PLEASE NOTE: This email and any file transmitted are confidential and/or >> legally privileged and intended only for the person(s) directly addressed. >> If you are not the intended recipient, any use, copying, transmission, >> distribution, or other forms of dissemination is strictly prohibited. If >> you have received this email in error, please notify the sender immediately >> and permanently delete the email and files, if any. >> >> >> >> >> On 8 Sep 2015, at 19:46, RJ Nowling <[email protected]> wrote: >> >> Hi Alex, >> >> S3 only gives you the first 1000 entries. You have to using page to view >> the rest. Additionally, since S3 is a key-value store, you can't do things >> like directory listings. >> >> Can you give us more details on your workflow? Adding the repo file at >> the link you gave and then do a yum install should be enough. >> >> Thanks, >> RJ >> >> On Tue, Sep 8, 2015 at 11:41 AM, Alex Bordei < >> [email protected]> wrote: >> >>> Hi everyone, >>> >>> Unless I’m doing something stupid, the repo, referred to from any OS’s >>> repo file (eg:http:// >>> www.apache.org/dist/bigtop/bigtop-1.0.0/repos/centos7/bigtop.repo) >>> >>> … which refers to: >>> >>> http://bigtop.s3.amazonaws.com/releases/1.0.0/centos/7/x86_64 >>> >>> … seems to yield: >>> >>> <Error> >>> <Code>NoSuchKey</Code> >>> <Message>The specified key does not exist.</Message> >>> <Key>releases/1.0.0/centos/7/x86_64</Key> >>> <RequestId>62FE23EAFBEF46EE</RequestId> >>> <HostId> >>> 5dhy0HiMJAp/R9QwQWU77H6zm+syH/MnGhcABY+jfWmFc1cOy7w/anIDNoIkQ79G >>> </HostId> >>> </Error> >>> >>> which means that you can’t install packages generated by bigtop on any >>> of the centos6 or centos7 and possibly others. >>> >>> Also at the http://bigtop.s3.amazonaws.com I can see releases up to >>> 0.5.0. I can see the artefacts properly created by the CI system >>> http://ci.bigtop.apache.org:8080/job/Bigtop-1.0.0-rpm/BUILD_ENVIRONMENTS=centos-7,label=docker-slave-06/lastSuccessfulBuild/artifact/output/hadoop/x86_64/, >>> but >>> they do not seem to get pushed to AWS. >>> >>> If you want, we could mirror that repo (in the UK for now) or get the >>> artefacts somehow from the CI system automatically. >>> >>> thanks, >>> Alex >>> >>> *---* >>> *ALEX BORDEI *| Product Manager | Bigstep | T: +44 (0) 2075 109 >>> 054 | bigstep.com <http://www.bigstep.com/> >>> >>> PLEASE NOTE: This email and any file transmitted are confidential >>> and/or legally privileged and intended only for the person(s) directly >>> addressed. If you are not the intended recipient, any use, copying, >>> transmission, distribution, or other forms of dissemination is strictly >>> prohibited. If you have received this email in error, please notify the >>> sender immediately and permanently delete the email and files, if any. >>> >>> >>> >>> >>> >> >> >
