Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 429332 - net-misc/asterisk-1.8.13.1 build log not verbose
Summary: net-misc/asterisk-1.8.13.1 build log not verbose
Status: RESOLVED OBSOLETE
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Tony Vroon (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: verbose_build
  Show dependency tree
 
Reported: 2012-08-01 10:56 UTC by Julian Ospald
Modified: 2012-08-04 22:24 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
asterisk-1.8.13.1:20120801-104238.log (asterisk-1.8.13.1:20120801-104238.log,161.25 KB, text/plain)
2012-08-01 10:56 UTC, Julian Ospald
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Julian Ospald 2012-08-01 10:56:50 UTC
Created attachment 319970 [details]
asterisk-1.8.13.1:20120801-104238.log

Build log should always be verbose, please force it until some EAPI includes a fix for this.

Other versions might be affected as well.
Comment 1 Tony Vroon (RETIRED) gentoo-dev 2012-08-01 10:57:50 UTC
All versions will be affected. Please provide rationale.
Comment 2 Julian Ospald 2012-08-01 10:58:41 UTC
That is explained in the tracker. Do you need a patch for this?
Comment 3 Tony Vroon (RETIRED) gentoo-dev 2012-08-01 11:02:49 UTC
All I see is a tracker bug with your personal opinion. The use of "should" in the RFC document way makes me ask for a -dev consensus, dev handbook excerpt or council decision before I invest time changing all my ebuilds.
A non-invasive patch that applies to all ebuilds without a revision bump is okay to commit though.
Comment 4 Tony Vroon (RETIRED) gentoo-dev 2012-08-01 11:04:02 UTC
In fact, this will take a patch tarball update. Please provide 1 patch that I will integrate on the next bump for each branch.
Comment 5 Julian Ospald 2012-08-01 11:07:52 UTC
(In reply to comment #3)
> All I see is a tracker bug with your personal opinion. The use of "should"
> in the RFC document way makes me ask for a -dev consensus, dev handbook
> excerpt or council decision before I invest time changing all my ebuilds.

That is not entirely correct, see

http://archives.gentoo.org/gentoo-dev/msg_ce7d33748936663e84a5463fbf7f4d39.xml

and bug 384193
and bug 379497