GitHub user karuturi opened a pull request:
https://github.com/apache/cloudstack/pull/833
changed the systemvm base iso file from debian-7.8.0 to debian-7.9.0
7.8.0 url is not available(404 Error)
This fixes the jenkins
http://jenkins.buildacloud.org/job/build-systemvm-master/624/console which is
failing with the below error
```
Checking if isofile iso-cd/debian-7.8.0-i386-netinst.iso already exists.
Full path:
/home/jenkins/acs/workspace/build-systemvm-master/tools/appliance/iso/iso-cd/debian-7.8.0-i386-netinst.iso
There was an error downloading
http://cdimage.debian.org/cdimage/archive/7.8.0/i386/iso-cd/debian-7.8.0-i386-netinst.iso:
404 Not Found
```
This is tested and build is successful at
http://jenkins.buildacloud.org/view/parameterized/job/parameterized-sytemvm/1/
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/cloudstack systemvm-build
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/833.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #833
----
commit eb98e71a34ed2e4b8d7798c7a93708312ed0a793
Author: Rajani Karuturi <[email protected]>
Date: 2015-09-15T16:16:18Z
changed the systemvm base iso file from debian-7.8.0 to debian-7.9.0
7.8.0 url is not available(404 Error)
This fixes the jenkins
http://jenkins.buildacloud.org/job/build-systemvm-master/624/console which is
failing with the below error
```
Checking if isofile iso-cd/debian-7.8.0-i386-netinst.iso already exists.
Full path:
/home/jenkins/acs/workspace/build-systemvm-master/tools/appliance/iso/iso-cd/debian-7.8.0-i386-netinst.iso
There was an error downloading
http://cdimage.debian.org/cdimage/archive/7.8.0/i386/iso-cd/debian-7.8.0-i386-netinst.iso:
404 Not Found
```
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
