amoeba opened a new issue, #47705: URL: https://github.com/apache/arrow/issues/47705
### Describe the enhancement requested In https://github.com/apache/arrow/pull/47622 we see an issue with the rhub `rhub/debian-gcc-release` image which surfaced once testing jumped from trixie to forky when debian trixie was released. When you run the image, you get this error: ``` root@789ada25a54b:/# apt update Get:1 http://deb.debian.org/debian testing InRelease [147 kB] Get:2 http://deb.debian.org/debian testing-updates InRelease [45.1 kB] Get:3 http://deb.debian.org/debian-security testing-security InRelease [43.4 kB] E: Repository 'http://deb.debian.org/debian testing InRelease' changed its 'Codename' value from 'trixie' to 'forky' N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details. Do you want to accept these changes and continue updating from this repository? [y/N] ``` We could work around it by tweaking our scripts but we should instead just migrate to a newer equivalent image from rhub v2. As I understand things, `debian-gcc-release` was part of the v1 rhub infrastructure which as [deprecated in mid-2024](https://blog.r-hub.io/2024/04/11/rhub2/) and we can see that the related images haven't been updated in ~2 years on https://hub.docker.com/r/rhub/debian-gcc-release so this makes sense. I'm not sure yet of the [available images](https://r-hub.github.io/containers/) is the equivalent. ### Component(s) Continuous Integration, R -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
