Some Linux distributions now provide s3cmd package in their base or add-ons package repositories. Unfortunately these repositories are very often “frozen” in the sense that package versions are never upgraded. From some points of view this is an understandable policy, however it also means that you will never automatically get any cool new features of future s3cmd releases.
For example – Fedora 8 (FC8) has been released with s3cmd 0.9.8.1 and even if security issues may get fixed in their updates repository it is unlikely that the users of FC8 will ever get any new features from s3cmd 0.9.8.4, for instance.
Therefore we decided to provide package repositories / RPM repositories / DEB repositories for some of the most popular distributions with the always most recent s3cmd package ready for installation.
Here is a list of currently supported distributions:
|RHEL 5 & CentOS 5||s3tools.repo|
|RHEL 6 & CentOS 6||s3tools.repo||Use also for Amazon Linux AMI|
|SLES 10||s3tools.repo||See note|
|Debian & Ubuntu||s3tools.list||NEW|
We can’t provide packages for discontinued RPM based distributions like openSUSE 10.3 or Fedora 10 and older. However you can grab the .src.rpm file from one of the repositories above and rebuild it for your system, that should work just fine.
How to add s3tools repository to RedHat, CentOS and Fedora
There are probably some graphical package managers in RedHat based systems, but I only use yum ;-)
- As a superuser (root) go to
- Download s3tools.repo file for your distribution. Links to these .repo files are in the table above. For instance if you’re on CentOS 5
- Run if you don’t have s3cmd rpm package installed yet, or if you already have s3cmd rpm installed and long for a newer version.
- You will be asked to accept a new GPG key – answer yes (perhaps twice).
- That’s it. Next time you run you’ll automatically get the very latest s3cmd for your system.
How to add s3tools repository to OpenSUSE 11 and SLES 11
There are two ways to do it. The one described below uses command line package management tool called zypper, the other way is using YaST.
- Become a superuser (root)
- Find the s3tools.repo URL in the table above and run for instance: if you’re on OpenSUSE 11.0
- Install s3cmd with:
- You will be asked whether you want to trust a new GPG key. Answer yes two times.
- That’s it. The s3cmd package will now be kept up to date together with all your other installed packages.
Standard installation media for SuSE Linux Enterprise Server 10 and Enterprise Desktop 10 don’t contain package that s3cmd depends on. Therefore there is an extra step required before installing s3cmd:
- In YaST open Software -> Installation sources
- Click on Add and select Specify URL option
- First URL to add is http://download.opensuse.org/repositories/devel:/languages:/python/SLE_10 — that’s required for python-elementtree package.
- Repeat the above steps (Add and Specify URL) and add the s3cmd repository with URL http://s3tools.org/repo/SLE_10
- Exit the module with Finish
- Now from YaST module list select Software -> Software Management and search for s3cmd. A number of dependencies will be selected, namely: , , and
- You may be required to import one or two GPG signing keys while adding the repositories above or during package installation.
Our DEB repository has been carefully created in the most compatible way – it should work for Debian 5 (Lenny), Debian 6 (Squeeze), Ubuntu 10.04 LTS (Lucid Lynx) and for all newer and possibly for some older Ubuntu releases. Follow these steps from the command line:
- Import S3tools signing key:
wget -O- -q http://s3tools.org/repo/deb-all/stable/s3tools.key | sudo apt-key add -
- Add the repo to sources.list:
sudo wget -O/etc/apt/sources.list.d/s3tools.list http://s3tools.org/repo/deb-all/stable/s3tools.list
- Refresh package cache and install the newest s3cmd:
sudo apt-get update && sudo apt-get install s3cmd
All other distributions
We’re keen to host repositories for other distributions and operating systems maintained by the other people. Unfortunately at the moment we’re unable to build packages for other distributions then those in the table above…