Skip to content
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

Install apt transport https #551

Merged
merged 9 commits into from
Jun 7, 2018
Merged

Conversation

mikaelarguedas
Copy link
Contributor

WIP do not merge opening for visibility and testing.
Alternative to #549

@dirk-thomas
Copy link
Member

I updated the comment but isn't there a good chance that the installation will already fail when we hit a https mirror?

@mikaelarguedas
Copy link
Contributor Author

I updated the comment but isn't there a good chance that the installation will already fail when we hit a https mirror?

Yeah it should be done before the sed IMO.
We faced mirror issues (requiring the use of cloudfront) mostly for the additional components (nonfree contrib etc). So I would hope that the install before changing the mirror will work (but I dont have any number to back it ^^)

@clalancette
Copy link
Contributor

I've deployed the updated version of this PR to 20 of the failing packages on the buildfarm using this command:

TZ=PST+08 generate_release_jobs.py https://raw.githubusercontent.com/ros-infrastructure/ros_buildfarm_config/production/index.yaml melodic ds --package-names xacro actionlib_tutorials audio_play diagnostic_analysis ecl_linear_algebra executive_smach filters hardware_interface message_filters qb_chain qb_device_utils robot_activity rosdiagnostic rosmon roswtf rqt_bag rqt_graph rqt_logger_level rqt_py_common rqt_robot_steering

All 20 of those that I reconfigured are now passing. As an additional piece of data, many of the downstream packages (which were not reconfigured) are still failing. So this definitely seems to be helping so far.

@clalancette
Copy link
Contributor

All right, most of Melodic on Debian Stretch has rebuilt with this change, and seems much happier (Moveit is still building, but it will take a while). Travis keeps failing; I haven't investigated it yet, though it seems unrelated. Reviews are certainly welcome, then we can decide whether to merge with the failing CI or investigate it.

@dirk-thomas
Copy link
Member

dirk-thomas commented Jun 7, 2018

To be considered for merging the change to the version needs to be reverted.

With that commit CI will get retriggered anyway. If it still fails please look into it since it will only get merged with a green CI. For spurious error you can always retrigger the Travis builds if necessary.

Signed-off-by: Chris Lalancette <[email protected]>
@mikaelarguedas
Copy link
Contributor Author

Travis has been having connexion issues today. I experienced it on several repositories.

The last 5 travis run all failed at different times but all because of connection issue. Let's 🤞 for the new round build but if we don't get travis to pass I'd recommend merging before the nightlies anyway to get this deployed on all jobs.

Change looks good to me with the version reverted 👍

@dirk-thomas dirk-thomas merged commit ab006e7 into master Jun 7, 2018
@dirk-thomas dirk-thomas deleted the install-apt-transport-https branch June 7, 2018 22:37
@dirk-thomas dirk-thomas restored the install-apt-transport-https branch June 7, 2018 22:37
@dirk-thomas dirk-thomas deleted the install-apt-transport-https branch June 7, 2018 23:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants