It is marked beta1 only because that was the last prerelease tag set, and we never bothered committing a change to that line. Glad to hear it is working now for you. I hope we can get an actual 1.5.0 released soon. On Apr 6, 2014 10:28 AM, "Will McCown" <w...@ross-mccown.com> wrote:
> On 4/5/2014 9:53 PM, matt_dom...@dell.com wrote: > > when I did this on a Fedora 20 fresh install, sudo python setup.py > install wound up with the package installed into /usr/bin/s3cmd, and its > modules in > > /usr/lib/python2.7/site-packages/S3/ > > > > Could they be in both from previous attempts, causing confusion? > > Thank you, yes that was exactly the problem. The rpm had installed > libraries in /usr/lib/python2.6/site-packages the "sudo python setup.py > install" put them in /usr/local/lib (odd that it was > the reverse of your installation, but maybe that's yet another > difference between Redhat/Fedora and Suse.) > > After carefully removing all traces of the old package the git > master branch installs and seems to run fine (with very limited > testing). > > So now the only question is: Why does the development branch > identify itself as a beta release? > > -- > Will McCown, Rolling Hills Estates, CA > w...@ross-mccown.com > > > ------------------------------------------------------------------------------ > _______________________________________________ > S3tools-general mailing list > S3tools-general@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/s3tools-general > >
------------------------------------------------------------------------------
_______________________________________________ S3tools-general mailing list S3tools-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/s3tools-general
