You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Roman Shaposhnik (Assigned) (JIRA)" <ji...@apache.org> on 2012/04/04 06:15:21 UTC

[jira] [Assigned] (BIGTOP-509) make all is failing because flume-1.0.0-incubating.tar.gz does not exist in APACHE_MIRROR

     [ https://issues.apache.org/jira/browse/BIGTOP-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Roman Shaposhnik reassigned BIGTOP-509:
---------------------------------------

    Assignee: Ron Bogdanoff

Ron, assigning to you -- feel free to take a stab at it!
                
> make all is failing because flume-1.0.0-incubating.tar.gz does not exist in APACHE_MIRROR
> -----------------------------------------------------------------------------------------
>
>                 Key: BIGTOP-509
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-509
>             Project: Bigtop
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 0.3.0
>         Environment: all
>            Reporter: Ron Bogdanoff
>            Assignee: Ron Bogdanoff
>             Fix For: 0.3.0
>
>
> bigtop.mk is attempting to download http://apache.osuosl.org/flume/flume-1.0.0-incubating//flume-1.0.0-incubating.tar.gz
> However, it looks like flume-1.0.0 has been removed from the mirror site.  Instead there is http://apache.osuosl.org/flume/flume-1.1.0-incubating//flume-1.1.0-incubating.tar.gz
> I have not submitted a patch as flume-1.1.0 has not been certified/tested on bigtop-0.3.0.   

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Re: [jira] [Assigned] (BIGTOP-509) make all is failing because flume-1.0.0-incubating.tar.gz does not exist in APACHE_MIRROR

Posted by Doug Chang <do...@stanfordalumni.org>.
Hi everybody: there is a quick workaround to this without doing a patch.
Download the version of flume from here;
http://apache.mirrors.hoobly.com/incubator/flume/flume-1.1.0-incubating/ to
/bigtop/dl

you will see 2 files in here, one called

 173020 2012-03-26 01:27 apache-flume-1.1.0-incubating.tar.gz

and one called:
334 2012-04-04 06:02 flume-1.0.0-incubating.tar.gz

copy the apache-flume file over the flume file like:

sudo mv apache-flume-1.1.0-incubating.tar.gz flume-1.0.0-incubating.tar.gz

go back to \bigtop and do a make all.....

dont get stuck!!!  :)

dc



On Tue, Apr 3, 2012 at 9:15 PM, Roman Shaposhnik (Assigned) (JIRA) <
jira@apache.org> wrote:

>
>     [
> https://issues.apache.org/jira/browse/BIGTOP-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>
> Roman Shaposhnik reassigned BIGTOP-509:
> ---------------------------------------
>
>    Assignee: Ron Bogdanoff
>
> Ron, assigning to you -- feel free to take a stab at it!
>
> > make all is failing because flume-1.0.0-incubating.tar.gz does not exist
> in APACHE_MIRROR
> >
> -----------------------------------------------------------------------------------------
> >
> >                 Key: BIGTOP-509
> >                 URL: https://issues.apache.org/jira/browse/BIGTOP-509
> >             Project: Bigtop
> >          Issue Type: Bug
> >          Components: General
> >    Affects Versions: 0.3.0
> >         Environment: all
> >            Reporter: Ron Bogdanoff
> >            Assignee: Ron Bogdanoff
> >             Fix For: 0.3.0
> >
> >
> > bigtop.mk is attempting to download
> http://apache.osuosl.org/flume/flume-1.0.0-incubating//flume-1.0.0-incubating.tar.gz
> > However, it looks like flume-1.0.0 has been removed from the mirror
> site.  Instead there is
> http://apache.osuosl.org/flume/flume-1.1.0-incubating//flume-1.1.0-incubating.tar.gz
> > I have not submitted a patch as flume-1.1.0 has not been
> certified/tested on bigtop-0.3.0.
>
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA
> administrators:
> https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
>