Skip to content
This repository was archived by the owner on Mar 3, 2023. It is now read-only.

Conversation

mfonville
Copy link
Contributor

Instead of upgrading completely to bionic as in #22416
because of possible glibc issues with older releases, limit the upgrade to bionic for just rpm

software-properties-common is added as earlier dependency in the script, because it contains the apt-add-repository command, so we need to be sure it is in place before adding the bionic repository.

@mfonville mfonville mentioned this pull request May 15, 2021
Copy link
Contributor

@DeeDeeG DeeDeeG left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, that works! 👍

In case it isn't clear, this is to support #22076, which (as written now) requires newer rpm than is available in Xenial.

(What the code comment this PR adds in the yml says, basically.)

Comment on lines 5 to 7
sudo apt-get update
sudo apt-get install -y wget software-properties-common
sudo apt-get install -y build-essential ca-certificates xvfb fakeroot git libsecret-1-dev rpm libx11-dev libxkbfile-dev xz-utils xorriso zsync libxss1 libgtk-3-0 libasound2 libicu-dev
sudo apt-get install -y build-essential ca-certificates xvfb fakeroot git libsecret-1-dev libx11-dev libxkbfile-dev xz-utils xorriso zsync libxss1 libgtk-3-0 libasound2 libicu-dev software-properties-common
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I notice that software-properties-common is on the higher apt-get install line already, frpm before the present PR.

(Not strictly related to this PR, but these two apt-get install lines could be combined for slightly faster execution, I think. And --no-upgrade would skip upgrading already-installed packages. Lastly, I wonder if the package cache is already populated, and if the first apt-get update can be skipped? That one takes a while to run. I can do these in a follow-up PR if you aren't interested in going admittedly a bit off-topic with these suggestions.)

Copy link
Contributor Author

@mfonville mfonville May 15, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will add the improvement of not having two separate apt-get statements, thanks

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's keep the first apt-get update in place though, to keep it fail-safe.
I don't think we should use --no-upgrade, because you actually might want to pull in a newer version of a package, like a security update, if it is available.

@sadick254 sadick254 merged commit 3fda4a9 into atom:master May 17, 2021
@mfonville
Copy link
Contributor Author

Thanks @sadick254

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants