Bug 911456

Summary:	app-vim/airline-9999 fails to compile (9999-SYSTEM): rm: cannot remove t: No such file or directory
Product:	Gentoo Linux	Reporter:	Agostino Sarubbo <ago>
Component:	Current packages	Assignee:	Vim Maintainers <vim>
Status:	RESOLVED INVALID
Severity:	normal	CC:	rrogalski
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	build.log Red's build.log Red's emerge.info

Description Agostino Sarubbo gentoo-dev

2023-07-29 19:37:22 UTC

https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/

Issue: app-vim/airline-9999 fails to compile (9999-SYSTEM).
Discovered on: amd64 (internal ref: 9999_tinderbox)

NOTE:
(9999-SYSTEM) in the summary means that the bug was found on a STANDARD machine that tries the 9999 version of the ebuild. While bugs about 9999 version make sense until certain point, you should see it as a way to know in advance what will have in the future release.

Comment 1 Agostino Sarubbo gentoo-dev

2023-07-29 19:37:25 UTC

Created attachment 866611 [details]
build.log

build log and emerge --info

Comment 2 Sam James archtester

2023-09-18 12:52:02 UTC

Please don't file bugs en-masse for live ebuilds as part of automated testing.

Comment 3 Red 2024-04-29 04:52:57 UTC

I noticed today that I had the live version of airline masked from when I first set up this install over a year ago. When I undid my mask, I hit this error. This live ebuild has been nonfunctional for a very long time. While I agree with sam that tinderbox bugs for live ebuilds could just add a _ton_ of pointless workload, this bug could have been detected 9 months ago now. Maybe a solution to store live-ebuild build failures, and queue up another run in 2 weeks time and diff the errors? Perhaps a good middleground of not creating tons of bugs for 'fragile' upstreams while also helping keep our live ebuilds actually adjusted and tested with latest upstream changes.

Repro'd on both amd64 and ppc64le. And apologies for not reporting this a year ago when I first encountered it.

Comment 4 Red 2024-04-29 04:53:53 UTC

Created attachment 891930 [details]
Red's build.log

Comment 5 Red 2024-04-29 04:56:35 UTC

Created attachment 891931 [details]
Red's emerge.info