Repository navigation
GCC version on debian7-arm hosts #770
Description
I've been looking at Ansible scripts in this repo and I don't quite understand how debian7 boxes are configured.
Here it adds wheezy-backports. Here it installs gcc-4.8. However, there is no gcc-4.8 package in wheezy-backports.
Am I missing something? I asked in IRC and @joaocgreis suggested creating an issue and pinging @jbergstroem, so here I am.
Activity
joaocgreis commentedon Jun 28, 2017
@seishun I'm not very familiar with the Linux hosts on CI, but I can do some guesswork from what I see. Let's hope I can help more than harm.
From your description, I'd say that you're right and either the Ansible script is broken because it was never even run, or it worked some time in the past (does wheezy-backports remove packages?).
@jbergstroem made a big effort to refactor and move the scripts from
setup/toansible/, but there are still platforms that were never tested, and it looks like you found one of them. This is probably because all the Raspberry Pis were deployed before, or the scripts have not been refactored yet.Looking at the old
setup/folder, I see 3 candidates:armv7-wheezy: this is for some armv7 machines we had that were not Raspberry Pis. I believe @rvagg recently moved them to Scaleway, so the ssh config section is outdated.debian-wheezy-gcc: looking at the files inside, this is only Docker.raspberry-pi: now this folder has manydebian7-armso this is probably the one that works (or worked at some point).The README inside
raspberry-pimentions that thedebian7machines useraspbian-2015-05-07. I found this about a slightly older version on SO: https://raspberrypi.stackexchange.com/a/27968 . So, gcc-4.8 is already there and does not need the backports repo.So, that makes sense for how the current
debian7machines were deployed. I don't know why theansible/folder has that backports repo, but I'd guess it was copied from somewhere else and never tested or meant just as a placeholder for something better later. I also don't know why we support the Raspberry Pi 1 if there is no maintained OS for it.@seishun if you want to work on #762, it looks like there is some urgency to it, just changing the old scripts in
setup/should do, and we can run those. This would not be an option if you were adding a completely new platform or theansible/scripts already worked well for it. If you want to get more involved, refactoringsetup/raspberry-pi/toansible/would be great and very welcome (but no small job).seishun commentedon Jul 1, 2017
Thanks, that makes sense.
It seems Ubuntu 14.04 is another platform where the
ansible/scripts haven't been tested, since it tries to usesystemdinstead ofupstart(and fails). Do you know how Ubuntu 14.04 machines are being deployed now?setup/ubuntu14.04?It would be great to have a list of platforms along with their currently used method of deployment.
I think this requires detailed knowledge about how it should work, which I don't have (yet). I'd rather entrust this to someone with more experience.
joaocgreis commentedon Jul 4, 2017
I have already fixed Ubuntu 14.04: #735 . The only thing left needed for that PR to land is one final test with the changes that were made during review. @seishun if you run it and it works well, let me know and I'll land it.
To answer your question: I used that PR to deploy the machine that is building node-chakracore nightlies. So, since it was not used before, all machines currently in CI have been deployed with
setup/ubuntu14.04.seishun commentedon Jul 5, 2017
@joaocgreis I see. I assume once that PR lands, all further deployments to Ubuntu 14.04 will be done using the scripts under
ansible, so changes relevant to #762 should be done there rather than insetup/ubuntu14.04, correct?joaocgreis commentedon Jul 6, 2017
@seishun that is correct.
seishun commentedon Jul 16, 2017
@joaocgreis I got it working on Ubuntu 14.04 (see #797), now I'm looking into Centos 6. It looks like the
ansible/scripts haven't been tested on Centos 6 because I get the following error:If I install libselinux-python manually, then the following happens:
Judging by the comments in the file, it seems
ansible/roles/baselayout/tasks/partials/repo/centos6.ymlis unfinished.How would you suggest to proceed with the Centos 6 changes? I don't feel qualified to finish the refactoring.
jbergstroem commentedon Jul 17, 2017
@seishun i think the centos 6 fail is a result of a recent change in ansible. Lets create another issue for that.
seishun commentedon Jul 18, 2017
@jbergstroem Alright, created an issue: #801.
rvagg commentedon Apr 2, 2018
I think this is solved now via #1199 and #1204