A fresh installation of the FOSS-Cloud version 1.1.0 has a missing profile.
vmsrv02 ~ # emerge -G git
!!! /etc/portage/make.profile is not a symlink and will probably prevent most merges.
!!! It should point into a profile within /usr/local/portage/profiles/
!!! (You can safely ignore this message when syncing. It's harmless.)
!!! Your current profile is invalid. If you have just changed your profile
!!! configuration, you should revert back to the previous configuration.
!!! Allowed actions are limited to --help, --info, --search, --sync, and
!!! --version.
vmsrv02 ~ #
vmsrv02 ~ # ls -al /etc/portage/make.profile
lrwxrwxrwx 1 root root 47 28. Nov 22:47 /etc/portage/make.profile -> ../../usr/local/portage/profiles/foss-cloud/1.2
vmsrv02 ~ #
vmsrv02 ~ # ls -al /usr/local/portage/
total 0
drwxr-xr-x 2 root root 6 5. Nov 18:40 .
drwxr-xr-x 6 root root 63 7. Nov 22:37 ..
vmsrv02 ~ #
ahem, you should update the Guide: if you are still pulling the 1.0 branch for the portage-overlay you obviously don't get the profile for 1.2.
Instead you should pull the master directly (during 1.1 development) or the 1.2 branch (once 1.2 gets released).
The same goes for the portage tree itself.
Updated the documentation in our internal wiki under Binary_package_installation to reflect latest changes.
The paths in the docu are invalid at the moment!
For release candidates:
packages.foss-cloud.org/foss-cloud/releases/1.1/packages
For final releases:
packages.foss-cloud.org/foss-cloud/releases/1.1/packages
None of these paths is valid!
On the other hand, "releases/1.0" exists or then "pre-releases/1,0" resp. "pre-releases/1,0"
Works for me:
Installing a binary package works as well:
Die you follow the following instructions?
If you have a productive (releases) FOSS-Cloud Installation, execute the following command:
If you have a test (pre-releases) FOSS-Cloud Installation instead, execute the following command: