First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 118683
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: AMD64 Project <amd64@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Giovani <giovanifaccin@yahoo.com.br>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 118683 depends on: Show dependency tree
Show dependency graph
Bug 118683 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)







View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2006-01-11 10:05 0000 
Hello there!

I would just like to report that I've installed the media-gfx/opendx-4.3.2-r1
(with ~amd64) keyword and also the media-gfx/opendx-samples-4.3.2 (with ~*)
keyword on my gentoo amd64 PC. Both are working perfectly out of the box.

I'm not sure about what is needed for an ebuild to be considered as tested/
stable; anyway I'd just like to inform that I've tried them and they are
working here. Since the opendx-samples is masked by missing keyword in amd64
(but worked out of the box!), maybe could it be switched to testing (~amd64)
keyword?

Giovani

PS: If I've reported this feedback in the wrong place, sorry for the mistake!
Should this be the case, where should I report masked / testing packages that
are working? Thanks!

------- Comment #1 From Karol Wojtaszek (RETIRED) 2006-01-26 13:40:23 0000 ------- 
media-gfx/opendx stable on amd64
media-gfx/opendx-samples are ~amd64 and must wait for 30 days period time to
get it stable.
First Last Prev Next    No search results available      Search page      Enter new bug