Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 157921 - please mark media-video/okle-0.4 stable on amd64
Summary: please mark media-video/okle-0.4 stable on amd64
Status: RESOLVED DUPLICATE of bug 138936
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High enhancement
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords: STABLEREQ
Depends on:
Blocks:
 
Reported: 2006-12-12 08:11 UTC by Paweł Hajdan, Jr. (RETIRED)
Modified: 2013-03-24 20:41 UTC (History)
1 user (show)

See Also:
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 Paweł Hajdan, Jr. (RETIRED) gentoo-dev 2006-12-12 08:11:12 UTC 
There is bug 138936 about okle stabilisation, but it has been closed and my comment about amd64 has been ignored.

okle-0.4 compiles and works fine on my stable amd64, so please mark it, as it is already stabilised for other arches.
Comment 1 Paweł Hajdan, Jr. (RETIRED) gentoo-dev 2006-12-12 08:12:33 UTC 
To clarify: the bug itself is not closed, but it seems that nobody really cares about it.
Comment 2 Jakub Moc (RETIRED) gentoo-dev 2006-12-12 08:13:46 UTC 

*** This bug has been marked as a duplicate of 138936 ***
Comment 3 Jakub Moc (RETIRED) gentoo-dev 2006-12-12 08:14:55 UTC 
(In reply to comment #1)
> To clarify: the bug itself is not closed, but it seems that nobody really cares
> about it.
> 

You've missed Bug 138936 Comment #4 perhaps?
Comment 4 Marijn Schouten (RETIRED) gentoo-dev 2006-12-12 08:15:33 UTC 
If you'd taken the time to actually read the bug you mention you'd have seen:

Recommending not to mark stable on amd64. During testing, when there is no cd
in the drive, okle will begin to loop indefinitely, eating processor:
%CPU %MEM
89   3.7  0:35.87 okle_gui

Please re-add amd64 when the issues with this program are resolved. An error
message or some kind of notification would be nice, but simply looping up is
not an acceptable error response to consider this for the stable branch.