| Summary: | app-admin/petrovich-1.0.0 needs ~amd64 keyword | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | jieryn <jieryn> |
| Component: | Current packages | Assignee: | AMD64 Project <amd64> |
| Status: | RESOLVED INVALID | ||
| Severity: | enhancement | ||
| Priority: | Normal | ||
| Version: | 2005.1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | emerge info | ||
|
Description
jieryn
2006-02-05 17:46:28 UTC
Created attachment 78993 [details]
emerge info
As far as I can see, it compiles and runs. However, it just initializes an empty database and doesn't actually 'check' anything, providing no documentation. Can you verify that it actually does anything? i wasn't aware that was a requirement to get ~arch keyworded. if so, why is x86 team ~arching it? anyhow, someone thought this package was worth throwing into the tree, i've verified it meets ~arch criteria as i understood it to be (for non-mission critical apps): it 1) compiles, and 2) runs without doing anything drastic, e.g. segfault. if this is not sufficient, please direct me to a gentoo page which clearly outlines the requirements. thanks! (In reply to comment #3) > anyhow, someone thought this package was worth throwing into the tree, i've > verified it meets ~arch criteria as i understood it to be (for non-mission > critical apps): it 1) compiles, and 2) runs without doing anything drastic, > e.g. segfault. That's not exactly the requirement. The actual requirement is that it *works*, not just that it runs doing something else but crashing :P please direct me to that requirement. also, how did it get ~x86 keyworded then? I thought it was common sense that a package has to work before we declare it as working, but well, here you are: From http://www.gentoo.org/proj/en/base/amd64/tests/index.xml?part=1&chap=2: You need to install the package and then test thoroughly: 1. Package should install without errors and be ready to run 'out of the box' with minimal effort on the part of user. 2. Major functionality (which isn't hard to test) should all work with no significant errors. Minor errors like a typo are probably acceptable, and we understand you can't go through every operation possible, but it should work in an acceptable manner for day-to-day usage by a user. thank you. again though, __how did this get ~x86 keyworded given these requirements__? I don't know. How should I? I assume somebody make a mistake, it's pretty common for human beings. Closing bug. Please stop being difficult. Perhaps it is an amd64-specific problem; maybe the x86 arch team made a mistake, who knows. If you had a legitimate reason to want this keyworded, you would have made sure it worked first. Unfortunately, it doesn't. |
