[ci] use flag '--allow-releaseinfo-change' in some 'apt-get update' calls

[jameslamb]

On PRs I opened within the last hour (#4522, #4523), the r-package (ubuntu-latest, R-devel, GCC ASAN/UBSAN) (pull_request) job is failing.

E: Repository 'http://deb.debian.org/debian testing InRelease' changed its 'Codename' value from 'bullseye' to 'bookworm'
Error: Process completed with exit code 100.

https://github.com/microsoft/LightGBM/pull/4523/checks?check_run_id=3332073359

After some research, I think this could be fixed by preferring apt update to apt-get update. A similar error was reported a few hours ago in https://www.mail-archive.com/[email protected]/msg772749.html, and responses in that thread suggest that running apt update in place of apt-get update can fix it (e.g. https://www.mail-archive.com/[email protected]/msg772763.html).

As far as I can tell from that thread, this is happening because of this combination of factors:

1. there was a new Debian release today: https://wiki.debian.org/DebianReleases#Production_Releases
2. some package(s) shipped in that release with bad metadata related to that new release
3. apt-get update does not install new dependencies of upgradeable software (https://linuxhint.com/diff_apt_vs_aptget/)

Opening this PR to replace calls to apt-get update with apt update in R jobs using rhub/ container images.

Notes for Reviewers

It's possible similar changes will need to be made for other jobs in the future, and maybe even that we should completely prefer apt to apt-get, but that requires more research and I think it's outside of the scope of this PR.

[jameslamb]

Doesn't seem like this worked 😬

I'm going to try just rebuilding #4522, maybe it was fixed upstrean.

[jameslamb]

I'm going to try just rebuilding #4522, maybe it was fixed upstrean.

That did not work, sadly. https://github.com/microsoft/LightGBM/pull/4522/checks?check_run_id=3334336822

Investigating some other options locally right now.

[jameslamb]

Following another suggestion from https://www.mail-archive.com/[email protected]/msg772749.html worked for me locally (in a container using the rhub/rocker-gcc-san:latest image).

For the 'apt-get' front-end, the necessary solution is to run the
command 'apt-get update --allow-releaseinfo-change'.

Just pushed 890feea, which I hope will resolve this issue.

[StrikerRUS]

Thank you for fast fix!

I think we can add this flag to other apt-get update calls.

[jameslamb]

I think we can add this flag to other apt-get update calls.

Sure! I didn't do that here because I think it needs a bit of investigation. I'm not sure what version of apt-get that flag was added in and this project's CI jobs cover a wide range of Ubuntu versions.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity since it was closed. To start a new related discussion, open a new issue at https://github.com/microsoft/LightGBM/issues including a reference to this.