Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Fix spec build #10500

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Aug 16, 2023
Merged

Fix spec build #10500

merged 1 commit into from
Aug 16, 2023

Conversation

SethTisue
Copy link
Member

@SethTisue SethTisue commented Aug 16, 2023 •
edited
Loading

at e.g. https://app.travis-ci.com/github/scala/scala/jobs/607977062 we're seeing

$ sudo apt-get update
Hit:1 http://archive.ubuntu.com/ubuntu bionic InRelease
Hit:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease
Hit:4 http://security.ubuntu.com/ubuntu bionic-security InRelease
Hit:5 http://apt.postgresql.org/pub/repos/apt bionic-pgdg InRelease
Hit:6 https://public.dhe.ibm.com/software/server/POWER/Linux/toolchain/at/ubuntu bionic InRelease
Hit:7 http://archive.ubuntu.com/ubuntu bionic-backports InRelease
Get:2 http://package.perforce.com/apt/ubuntu bionic InRelease [3,655 B]
Err:2 http://package.perforce.com/apt/ubuntu bionic InRelease
  The following signatures were invalid: EXPKEYSIG 7123CB760FF18869 Perforce Software (Package Signing) <[email protected]>
Reading package lists...
W: GPG error: http://package.perforce.com/apt/ubuntu bionic InRelease: The following signatures were invalid: EXPKEYSIG 7123CB760FF18869 Perforce Software (Package Signing) <[email protected]>
E: The repository 'http://package.perforce.com/apt/ubuntu bionic InRelease' is not signed.

one way to fix it might be to add Acquire::Check-Valid-Until false; to /etc/apt/apt.conf, as per https://askubuntu.com/questions/74345/how-do-i-bypass-ignore-the-gpg-signature-checks-of-apt

but maybe we could try first to get on a newer Ubuntu, since Travis-CI presumably won't support bionic indefinitely

the 2.12 and 2.13 spec builds are a bit different, so I might need to do experiments on both branches

we have been frozen on bionic because of a libssl version issue with wkhtmltopdf, so this might get painful

another possibility might be to move the spec build off Travis-CI and onto GitHub Actions.

previously: #10310, #10312

also scala/scala-dev#832 which has a brief remark about how the 2.12/2.13 divergence came about

@scala-jenkins scala-jenkins added this to the 2.12.19 milestone Aug 16, 2023
@SethTisue
Copy link
Member Author

it's going to take forever to even test these 😿

@SethTisue SethTisue marked this pull request as ready for review August 16, 2023 03:42
@SethTisue
Copy link
Member Author

ha, green on first try. I'm not sure if this will also fix non-PR runs, but in any case, let's take the upgrade

@SethTisue SethTisue added the internal not resulting in user-visible changes (build changes, tests, internal cleanups) label Aug 16, 2023
@SethTisue SethTisue merged commit 3c06c51 into scala:2.12.x Aug 16, 2023
@SethTisue SethTisue deleted the fix-spec-build branch August 16, 2023 03:43
@SethTisue SethTisue mentioned this pull request Aug 16, 2023
Merged
@SethTisue
Copy link
Member Author

gah. I didn't notice that the commit here lacked a proper commit message. oh well

@som-snytt
Copy link
Contributor

i think wip for "what i pushed" is a fine commit message.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
internal not resulting in user-visible changes (build changes, tests, internal cleanups)
Projects
None yet
Milestone
2.12.19
Development

Successfully merging this pull request may close these issues.
3 participants
@SethTisue @som-snytt @scala-jenkins