778860 – sys-apps/portage: use [INFO], [WARN] and [ERROR] prefixes to ensure that severity of emerge messages is clearly distinguishable

Bug 778860 - sys-apps/portage: use [INFO], [WARN] and [ERROR] prefixes to ensure that severity of emerge messages is clearly distinguishable

Summary: sys-apps/portage: use [INFO], [WARN] and [ERROR] prefixes to ensure that seve...

Status:	IN_PROGRESS

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Core - Interface (emerge) (show other bugs)
Hardware:	All All

Importance:	Normal normal (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2021-03-28 07:11 UTC by Zac Medico
Modified:	2022-07-20 15:40 UTC (History)
CC List:	5 users (show)

See Also:	472104 https://github.com/gentoo/portage/pull/759 859535 https://github.com/gentoo/portage/pull/862
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Zac Medico gentoo-dev

2021-03-28 07:11:30 UTC

Since emerge outputs many different kinds of warning messages, it is important to clearly indicate when those messages are non-fatal, in order to ensure that they are distinguishable from fatal errors. Maybe a prefix like [WARN] would be helpful for this.

Comment 1 Zac Medico gentoo-dev

2021-03-28 07:28:13 UTC

The message from bug 472104 is one that might be displayed with an [INFO] prefix.

Comment 2 Michał Górny archtester

2021-09-29 09:36:06 UTC

My elog PR should be good enough for this.  It's a bit of compromise between verbosity and short output as it uses two-letter codes but this should be good enough to distinguish them.