Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 115131 - showeq-5.2.4.0-r1.ebuild (Update)
Summary: showeq-5.2.4.0-r1.ebuild (Update)
Status: VERIFIED LATER
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High enhancement (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-10 14:08 UTC by Jesse Waldack
Modified: 2005-12-10 16:26 UTC (History)
0 users

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


Attachments
showeq-5.2.4.0-r1.ebuild (showeq-5.2.4.0-r1.ebuild,794 bytes, text/plain)
2005-12-10 14:09 UTC, Jesse Waldack
Details
showeq-5.2.4.0-r1.tar.bz2 (update) (showeq-5.2.4.0-r1.tar.bz2,785.28 KB, text/plain)
2005-12-10 14:11 UTC, Jesse Waldack
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Waldack 2005-12-10 14:08:04 UTC
Greetings.

I submitted the 5.4.2.0 ebuild last night, and wanted to have it state that 
amd64 and x86 were stable, but they ended up marked as testing along with ppc. 

Since I don't even know if any of our users try it with ppc, I'm sending an -
r1.ebuild that removes ppc all together.  Hope then the result will be that 
both amd64 and x86 are stable.

Thanks :)

-Jesse
Comment 1 Jesse Waldack 2005-12-10 14:09:51 UTC
Created attachment 74456 [details]
showeq-5.2.4.0-r1.ebuild

Am I supposed to give to you the .tar.bz2 files as well?  I didn't last time. 
I'll attach it this time.  Thanks.
Comment 2 Jesse Waldack 2005-12-10 14:11:33 UTC
Created attachment 74457 [details]
showeq-5.2.4.0-r1.tar.bz2 (update)

This isn't changed at all from the showeq-5.2.4.0.tar.bz2 , I only changed the
.ebuild file . bit didn't submit the .tar.bz2 last time.  Thanks.
Comment 3 Jakub Moc (RETIRED) gentoo-dev 2005-12-10 14:28:43 UTC
We cannot mark something stable after one day in portage... 

http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=3&chap=1#doc_chap4
Comment 4 Jesse Waldack 2005-12-10 16:26:59 UTC
ok - then we'll just leave it as "testing".  The nature of the program 
requires updates every 2-6 weeks anyway, so sounds like it's likely to stay 
in "testing" as long as it's maintained in your database.

I'll mark the bug as closed and this can be ignored.

thanks for that link . I'm new at this, and didn't know.

-Jesse