On Fri, 2007-02-02 at 14:04 +0200, Petteri Räty wrote:
> Tom Fredrik Blenning Klaussen wrote:
> Please tell us what kinds of bugs we are talking about so we can tell
> you if they are bugs in your program or ebuilds.
>
> >
> > I have also not mapped the bugs to particular packages yet, as I plan to
> > do, but at any rate it seems likely there will be a large number to
> > report. How do I go ahead with this?
> >
>
> I would have the problems writting in a nice format to a txt file and
> put the text file online and post a link to this mailing list for us to
> take a look. If there is a genuine problem, we can use bugzilla after
> that to fix it.
OK, the bugreport is now ready. I have investigated a few of them, and
there are three classes of bugs.
ignored.empty: Quite obvious the file is empty
ignored.shouldNotBeExecutable: These are files that belongs to a class
of files that definitely shouldn't be executable.
Unknown: This class contains all the files that wasn't positively
identified with any cause for being executable. There may be a few false
detections here, but most should be true problems. Of the types I've
identified within this class there are two kinds.
-Scripts without the hash-bang(#!) identifier.
-Files that should not have an executable bit.
For the full list see:
http://www.blenning.no/gentoo-stuff/bugreport1.txt
With difference in indentation the format is:
package
class
file
output from "file" command
--
Tom Fredrik Blenning Klaussen <[EMAIL PROTECTED]>
--
gentoo-dev@gentoo.org mailing list
