[arch-dev-public] GCC 9 removed from [testing]
Hi all, I just deleted GCC 9 and related packages from [testing] due to the filesystem corruption bug when bcache is used[1]. You will have to -Syuu your systems. People hungry for breakage can install it from [gcc9] repo I uploaded to pkgbuild.com: [gcc9] Server = https://pkgbuild.com/~bpiotrowski/gcc9/ Bartłomiej
On 26/05/2019 18.51, Bartłomiej Piotrowski via arch-dev-public wrote:
Hi all,
I just deleted GCC 9 and related packages from [testing] due to the filesystem corruption bug when bcache is used[1]. You will have to -Syuu your systems.
People hungry for breakage can install it from [gcc9] repo I uploaded to pkgbuild.com:
[gcc9] Server = https://pkgbuild.com/~bpiotrowski/gcc9/
Bartłomiej
[1] should be pointing to https://bugs.archlinux.org/task/62730
On Sun, 26 May 2019 at 19:51, Bartłomiej Piotrowski via arch-dev-public <arch-dev-public@archlinux.org> wrote:
You will have to -Syuu your systems.
Also remember to recreate your testing and staging chroots!
On 5/26/19 12:51 PM, Bartłomiej Piotrowski via arch-dev-public wrote:
Hi all,
I just deleted GCC 9 and related packages from [testing] due to the filesystem corruption bug when bcache is used[1]. You will have to -Syuu your systems.
People hungry for breakage can install it from [gcc9] repo I uploaded to pkgbuild.com:
[gcc9] Server = https://pkgbuild.com/~bpiotrowski/gcc9/
Question: are you going to set up an archbuild alias on soyuz/dragon for this, the way you did for gcc8? (Which reminds me, those archbuild aliases still exist and could be deleted). Also please bump the pkgrel for these packages as they were currently just cp'ed from testing. dbscripts knows how to auto-reject uploaded packages built with your repo, as long as the gcc/binutils/etc. pkgver-pkgrel are new and thus do not appear in the archives. (This will not help for someone who is building against an outdated [testing] chroot, so yeah, those need to be refreshed.) -- Eli Schwartz Bug Wrangler and Trusted User
On 26/05/2019 22.39, Eli Schwartz via arch-dev-public wrote:
Question: are you going to set up an archbuild alias on soyuz/dragon for this, the way you did for gcc8? (Which reminds me, those archbuild aliases still exist and could be deleted).
I can create it, sure.
Also please bump the pkgrel for these packages as they were currently just cp'ed from testing. dbscripts knows how to auto-reject uploaded packages built with your repo, as long as the gcc/binutils/etc. pkgver-pkgrel are new and thus do not appear in the archives.
I think packages built againt GCC9 with bumped pkgrel would be rejected anyway ("package does not appear in repositories" or something along this) but yeah, I don't plan to touch it for the time being. BP
On 02/06/2019 09.37, Bartłomiej Piotrowski via arch-dev-public wrote:
On 26/05/2019 22.39, Eli Schwartz via arch-dev-public wrote:
Question: are you going to set up an archbuild alias on soyuz/dragon for this, the way you did for gcc8? (Which reminds me, those archbuild aliases still exist and could be deleted).
I can create it, sure.
Also please bump the pkgrel for these packages as they were currently just cp'ed from testing. dbscripts knows how to auto-reject uploaded packages built with your repo, as long as the gcc/binutils/etc. pkgver-pkgrel are new and thus do not appear in the archives.
I think packages built againt GCC9 with bumped pkgrel would be rejected anyway ("package does not appear in repositories" or something along this) but yeah, I don't plan to touch it for the time being.
Ah, right, I forgot it also does some archive magic now. I guess I will have to change it then… Likely today in the evening.
participants (3)
-
Bartłomiej Piotrowski
-
Eli Schwartz
-
Evangelos Foutras