-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Legacy ROS releases have been moved to the snapshots repo. #64
Conversation
This legacy template has only ever been applied to distros older than Indigo. I'm guessing ROS1 Jade will be migrated to snapshot as well? Or is the plan to eventually house/move all EOL distros out of package.ros.org and into snapshots.ros.org as they age out, e.g including Indigo and Lunar? |
Yes. Jade isn't being rebuilt and so when the next sync happens it will be removed from packages.ros.org.
Yes that's the plan so far. Lunar and Indigo (on Trusty) are being rebuilt this round so they'll remain on packages.ros.org for now but part of the wind-down process for ROS distributions as they reach end-of-support will be to move them to the snapshots repo with a |
@ruffsl I have no idea how to actually invoke the template generator and build new Dockerfiles. |
Some older docs are here, but simply once this template PR is merged, then all one has to do is temporarily uncomment the EOL comments in the manifest.yaml and update the older Dockerfiles with create_dockerfolders: git clone https://github.com/osrf/docker_images.git
cd docker_images/docker
docker build --no-cache --tag=osrf:docker .
./run bash
cd ros
./create_dockerfolders.py dir -d ./ -a
exit
git add ...
git commit ... Then you'd want to revert the manifest.yaml to how is was and update the library manifest file ( cd docker_images/docker
./run bash
cd ros
./create_dockerlibrary.py -m manifest.yaml -o ros
exit
git add ...
git commit ... I can try this tomorrow; I'm a little tied up currently. |
I found those docs and worked backwards. I didn't end up using the manifest.yaml but instead individually triggered the scripts on each affected dockerfile. The results of that attempt are in osrf/docker_images#273
❤️ Take care of what you need to. This will keep. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, with one inline question
docker_templates/templates/docker_images_legacy/create_ros_core_image.Dockerfile.em
Show resolved
Hide resolved
Merging, keeping in mind that this template currently applies only to distro older than hydro. Ideas of how to apply templates to all EOL distros explored at osrf/docker_images#281 |
The changes described in https://discourse.ros.org/t/security-issue-on-ros-build-farm/9342/8 will remove unsupported ROS releases from the live ROS repositories. The packages for these releases are being migrated to the ROS Snapshots repositories.
This switches legacy releases to adding the snapshots key and using the snapshots http format for final snapshots.