Bug 654528

Summary:	arm stages critically outdated
Product:	Gentoo Release Media	Reporter:	Andreas K. Hüttel <dilfridge>
Component:	Stages	Assignee:	Gentoo Release Team <releng>
Status:	RESOLVED FIXED
Severity:	normal	CC:	alexander, arm, gentoo, gentoo, i, pacho
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Bug Depends on:
Bug Blocks:	646004

Description Andreas K. Hüttel archtester

2018-05-01 12:55:57 UTC

The last published arm stages (even autobuilds) are from 2016, and still contain gcc-4. 

This gcc does not build recent glibc releases (>=2.26) anymore.

Comment 1 Michael 'veremitz' Everitt 2018-05-02 03:44:26 UTC

Releases available at https://files.emjay-embedded.co.uk/unofficial-gentoo/arm-stages/ contain gcc-6.4.0-r1 currently.

RESO:FIXED

Comment 2 Daniel Cordero 2018-05-02 12:34:22 UTC

The armv7a_hardfp stage3 (dated 2016-11-29) contains a populated ./tmp/stage1root.

This:
1) wastes disk space (when uncompressed);
2) prevents using the stage3 tarball as a catalyst seed stage to build a newer stage1, due to conflicts with the old version of sandbox and stable versions in a current portage tree.

Comment 3 Michael 'veremitz' Everitt 2018-05-02 12:51:12 UTC

(In reply to Daniel Cordero from comment #2)
> The armv7a_hardfp stage3 (dated 2016-11-29) contains a populated
> ./tmp/stage1root.
> 
> This:
> 1) wastes disk space (when uncompressed);
> 2) prevents using the stage3 tarball as a catalyst seed stage to build a
> newer stage1, due to conflicts with the old version of sandbox and stable
> versions in a current portage tree.

99% sure this has been fixed on one of the many updates to catalyst, and /tmp is completely cleaned out. It shouldn't even reach the stage 2 let alone the 3!!

Comment 4 Harri Nieminen (Moiman) 2018-05-05 19:18:23 UTC

*** Bug 654994 has been marked as a duplicate of this bug. ***

Comment 5 Mikle Kolyada (RETIRED) archtester

2018-11-26 19:02:41 UTC

we have newer at distfiles.g.o as I see this