Bug 557698

Summary:	[jkolo] Ebuild failures occuring in global scope
Product:	Gentoo Infrastructure	Reporter:	Michał Górny <mgorny>
Component:	Gentoo Overlays	Assignee:	Jerzy Kołosowski <jerzy>
Status:	RESOLVED FIXED
Severity:	normal
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
URL:	https://qa-reports.gentoo.org/output/repos/jkolo.html
See Also:	https://git.kolosowscy.pl/jurek/gentoo-overlay/issues/1
Whiteboard:
Package list:		Runtime testing required:	---
Bug Depends on:
Bug Blocks:	552950, 553024

Description Michał Górny archtester

2015-08-15 08:05:00 UTC

== == == == == == == == == == == == == == == == == == == == == == == ==
The repository owner is not registered on Bugzilla
Owner: ['jerzy@kolosowscy.pl']
== == == == == == == == == == == == == == == == == == == == == == == ==

Our automated repository checks [1] have detected that the 'jkolo'
repository contains ebuilds that trigger fatal errors during the cache
regeneration. This usually means that the ebuilds call 'die' in global
scope indicating serious issues.

Global-scope failures prevent the ebuild not only from being installed
but also from being properly processed by the Package Manager. Since
metadata can not be obtained for those ebuilds, no cache entries are
created for them and the Package Manager needs to retry running them
every time it stumbles upon them. This involves both a serious slowdown
and repeating error output while performing dependency resolution.

The most common cause of global-scope failures is use of removed or
banned APIs in old ebuilds. In particular, this includes eclasses being
removed or removing support for old EAPIs. Nonetheless there are also
other issues such as performing illegal operations in global scope
(external program calls), malformed bash in ebuilds or malformed
metadata.xml.

The error log for the repository can be found at:

  http://gentoo.github.io/repo-qa-check-results/jkolo.html

In particular, please look for highlighted '!!! ERROR' and '!!! caught
exception' lines. The former usually mean failures coming from eclasses
and the ebuild itself, while exceptions usually mean malformed ebuilds
or metadata.xml.

While at it, please consider fixing global-scope 'use' call warnings (if
any). They are not fatal but are considered a serious QA violation.
'use' functions must not ever be called outside of phase functions.

Please fix the issue ASAP, possibly via removing unmaintained, old
ebuilds. We reserve the right to remove the repository from our list if
we do not receive any reply within 4 weeks.

[1]:https://wiki.gentoo.org/wiki/Project:Repository_mirror_and_CI

Comment 1 Michał Górny archtester

2015-08-15 08:36:28 UTC

Hello, Jerzy. Could you confirm whether the e-mail address 'jerzy@kolosowscy.pl' belongs(-ed) to you or not? I've sent a mail there on July 4th but didn't get any reply.

Comment 2 Jerzy Kołosowski 2016-06-18 23:12:04 UTC

(In reply to Michał Górny from comment #1)
> Hello, Jerzy. Could you confirm whether the e-mail address
> 'jerzy@kolosowscy.pl' belongs(-ed) to you or not? I've sent a mail there on
> July 4th but didn't get any reply.

I updated the email in bugzilla, and removed ebuild causing trouble.

Comment 3 Michał Górny archtester

2016-06-19 05:35:13 UTC

Thanks a lot. It looks green now.