Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 186371 - No explanation why many bison ebuilds are now gone
Summary: No explanation why many bison ebuilds are now gone
Status: RESOLVED WONTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: High normal
Assignee: Gentoo's Team for Core System packages
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-07-23 20:05 UTC by Harald van Dijk (RETIRED)
Modified: 2010-03-29 17:10 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Harald van Dijk (RETIRED) gentoo-dev 2007-07-23 20:05:19 UTC
There is no accompanying ChangeLog entry for

http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-devel/bison/Manifest?r1=1.100&r2=1.101

It's a pain to have to resort to sources.gentoo.org to find why ebuilds have been removed, and yes, I actually did care for bison. Policy says a ChangeLog entry is required as well, and some tools rely on the ChangeLog being used properly (including portage itself). Could you please add an entry?
Comment 1 Robin Johnson archtester Gentoo Infrastructure gentoo-dev Security 2007-10-09 23:47:41 UTC
vapier: ping
Comment 2 Harald van Dijk (RETIRED) gentoo-dev 2009-01-11 10:42:55 UTC
vapier: you sat on this for over a year, then closed this without any explanation or any action. If changelog entries are no longer mandatory, reassign this to the docs team, otherwise again: please add one. It's not like I reported this months after you nuked the ebuilds; I reported this the very same day.
Comment 3 Harald van Dijk (RETIRED) gentoo-dev 2010-03-29 17:08:32 UTC
Useless. *Again* you waited a year to do absolutely nothing about this, then closed it without any comment. Reopening to close this properly...
Comment 4 Harald van Dijk (RETIRED) gentoo-dev 2010-03-29 17:10:27 UTC
...as WONTFIX, because I see no way how you could argue that this is not a valid bug.