Following the install guide on the wiki, looks like there's an issue with 
the RPM repo:

curl -s 
https://packagecloud.io/install/repositories/scalr/scalr-server-oss/script.rpm.sh
 | 
sudo bash
Detected operating system as centos/7.
Checking for curl...
Detected curl...
Downloading repository file: 
https://packagecloud.io/install/repositories/scalr/scalr-server-oss/config_file.repo?os=centos&dist=7&source=script
done.
Installing pygpgme to verify GPG signatures...
Loaded plugins: fastestmirror
https://packagecloud.io/scalr/scalr-server-oss/el/7/SRPMS/repodata/repomd.xml: 
[Errno 14] HTTPS Error 302 - Found
Trying other mirror.


 One of the configured repositories failed (scalr_scalr-server-oss-source),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the 
problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a 
working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Disable the repository, so yum won't use it by default. Yum will 
then
        just ignore the repository until you permanently enable it again or 
use
        --enablerepo for temporary usage:

            yum-config-manager --disable scalr_scalr-server-oss-source

     4. Configure the failing repository to be skipped, if it is 
unavailable.
        Note that yum will try to contact the repo. when it runs most 
commands,
        so will have to try and fail each time (and thus. yum will be be 
much
        slower). If it is a very temporary problem though, this is often a 
nice
        compromise:

            yum-config-manager --save 
--setopt=scalr_scalr-server-oss-source.skip_if_unavailable=true

failure: repodata/repomd.xml from scalr_scalr-server-oss-source: [Errno 
256] No more mirrors to try.
https://packagecloud.io/scalr/scalr-server-oss/el/7/SRPMS/repodata/repomd.xml: 
[Errno 14] HTTPS Error 302 - Found
Installing yum-utils...
Loaded plugins: fastestmirror
base                                                     | 3.6 kB     00:00   
  
extras                                                   | 3.4 kB     00:00   
  
https://packagecloud.io/scalr/scalr-server-oss/el/7/SRPMS/repodata/repomd.xml: 
[Errno 14] HTTPS Error 302 - Found
Trying other mirror.


 One of the configured repositories failed (scalr_scalr-server-oss-source),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the 
problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a 
working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Disable the repository, so yum won't use it by default. Yum will 
then
        just ignore the repository until you permanently enable it again or 
use
        --enablerepo for temporary usage:

            yum-config-manager --disable scalr_scalr-server-oss-source

     4. Configure the failing repository to be skipped, if it is 
unavailable.
        Note that yum will try to contact the repo. when it runs most 
commands,
        so will have to try and fail each time (and thus. yum will be be 
much
        slower). If it is a very temporary problem though, this is often a 
nice
        compromise:

            yum-config-manager --save 
--setopt=scalr_scalr-server-oss-source.skip_if_unavailable=true

failure: repodata/repomd.xml from scalr_scalr-server-oss-source: [Errno 
256] No more mirrors to try.
https://packagecloud.io/scalr/scalr-server-oss/el/7/SRPMS/repodata/repomd.xml: 
[Errno 14] HTTPS Error 302 - Found
Generating yum cache for scalr_scalr-server-oss...
https://packagecloud.io/scalr/scalr-server-oss/el/7/x86_64/repodata/repomd.xml: 
[Errno 14] HTTPS Error 302 - Found
Trying other mirror.


 One of the configured repositories failed (scalr_scalr-server-oss),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the 
problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a 
working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Disable the repository, so yum won't use it by default. Yum will 
then
        just ignore the repository until you permanently enable it again or 
use
        --enablerepo for temporary usage:

            yum-config-manager --disable scalr_scalr-server-oss

     4. Configure the failing repository to be skipped, if it is 
unavailable.
        Note that yum will try to contact the repo. when it runs most 
commands,
        so will have to try and fail each time (and thus. yum will be be 
much
        slower). If it is a very temporary problem though, this is often a 
nice
        compromise:

            yum-config-manager --save 
--setopt=scalr_scalr-server-oss.skip_if_unavailable=true

failure: repodata/repomd.xml from scalr_scalr-server-oss: [Errno 256] No 
more mirrors to try.
https://packagecloud.io/scalr/scalr-server-oss/el/7/x86_64/repodata/repomd.xml: 
[Errno 14] HTTPS Error 302 - Found

The repository is setup! You can now install packages.


Error 302 is a redirect, so I follow the redirect:

<repomd xmlns="http://linux.duke.edu/metadata/repo";>
<data type="other">
<location 
href="repodata/69a5c1ee346d2df3f5c11e6374e87ceaea7267c2-other.xml.gz"/>
<checksum type="sha">69a5c1ee346d2df3f5c11e6374e87ceaea7267c2</checksum>
<timestamp>1467164091</timestamp>
<open-checksum 
type="sha">8bfc1933bb195d3aad9baf17813b2bd76cd8e4ae</open-checksum>
</data>
<data type="filelists">
<location 
href="repodata/9865cd3515a90e813f50ca2b538bb99687b21140-filelists.xml.gz"/>
<checksum type="sha">9865cd3515a90e813f50ca2b538bb99687b21140</checksum>
<timestamp>1467164091</timestamp>
<open-checksum 
type="sha">3e01e5f12431462527bcd0e51880522b3f03114e</open-checksum>
</data>
<data type="primary">
<location 
href="repodata/576d29ab183dbcd0516e114ca782830da64a76f2-primary.xml.gz"/>
<checksum type="sha">576d29ab183dbcd0516e114ca782830da64a76f2</checksum>
<timestamp>1467164091</timestamp>
<open-checksum 
type="sha">53999881933a47ef11b3908a8b6634b9c249f74e</open-checksum>
</data>
</repomd>


Try to access linux.duke.edu, it redirects to sites.duke.edu/linux - and 
there aren't any scalr packages to be found.

-- 
You received this message because you are subscribed to the Google Groups 
"scalr-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to