[gentoo-dev] Use full package atoms for bug reports

[gentoo-dev] Use full package atoms for bug reports

[Christian Faulhammer]

[-- Attachment #1: Type: text/plain, Size: 313 bytes --]

Hi,

Please be so kind and use full package atoms in the bug description
line (especially when bug wrangling), searching is made easier that way.

V-Li

-- 
Christian Faulhammer, Gentoo Lisp project
<URL:http://www.gentoo.org/proj/en/lisp/>, #gentoo-lisp on FreeNode

<URL:http://www.faulhammer.org/>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: [gentoo-dev] Use full package atoms for bug reports

[Jeroen Roovers]

On Sun, 4 Jan 2009 14:52:11 +0100
Christian Faulhammer <fauli@gentoo.org> wrote:

> Hi,
> 
> Please be so kind and use full package atoms in the bug description
> line (especially when bug wrangling), searching is made easier that
> way.

  "Bug reports that refer to a single or a few (similar) packages
  should detail the package atom(s) as completely as possible in the
  Summary, including a version only when other versions do not exhibit
  the bug."[1]


Kind regards,
     jer


[1] http://www.gentoo.org/proj/en/qa/bug-wranglers/

[gentoo-dev] Re: Use full package atoms for bug reports

[Duncan]

Jeroen Roovers <jer@gentoo.org> posted
20090104174353.22981e4e@epia.jer-c2.orkz.net, excerpted below, on  Sun, 04
Jan 2009 17:43:53 +0100:

> On Sun, 4 Jan 2009 14:52:11 +0100
> Christian Faulhammer <fauli@gentoo.org> wrote:
> 
>> Please be so kind and use full package atoms in the bug description
>> line (especially when bug wrangling), searching is made easier that
>> way.
> 
>   "Bug reports that refer to a single or a few (similar) packages should
>   detail the package atom(s) as completely as possible in the Summary,
>   including a version only when other versions do not exhibit the
>   bug."[1]

> [1] http://www.gentoo.org/proj/en/qa/bug-wranglers/

I think the problem is more as in this bug.  Note the "Amarok2", the 
reason I ended up filing a dup, because I searched for "amarok-2" and 
didn't catch this bug.  Someone with the authority to do so might wish to 
change the summary accordingly...  altho it does seem most CCs were able 
to find the bug without the dup I ended up with, and the bug is still 
getting frequent CC additions.

Amarok2 - dev-db/mysql-community - ld: /usr/lib64/mysql/libmysqld.a
(client.o): relocation R_X86_64_32S against `client_errors' can not be 
used when making a shared object; recompile with -fPIC

http://bugs.gentoo.org/show_bug.cgi?id=238487

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

Re: [gentoo-dev] Re: Use full package atoms for bug reports

[Mike Auty]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Duncan wrote:
> Amarok2 - dev-db/mysql-community - ld: /usr/lib64/mysql/libmysqld.a
> (client.o): relocation R_X86_64_32S against `client_errors' can not be 
> used when making a shared object; recompile with -fPIC

Well, I fixed this individual instance.  As Jer pointed out, it's in the
bug-wrangling guide.  Unfortunately the bug wranglers are only human,
and sometimes some will slip through.  If you find any more, it might be
worth contacting a bug wrangler directly...

Mike  5:)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEARECAAYFAklhS6wACgkQu7rWomwgFXo5cwCePAVcKM2cJwY8SeXiDEHldzfl
NycAn3JA5dtadT7Ip/4RDyoXODd8NEtY
=PST+
-----END PGP SIGNATURE-----

[gentoo-dev] Re: Use full package atoms for bug reports

[Duncan]

Mike Auty <ikelos@gentoo.org> posted 49614BAD.6040403@gentoo.org,
excerpted below, on  Sun, 04 Jan 2009 23:52:13 +0000:

> Duncan wrote:
>> Amarok2 - dev-db/mysql-community - ld: /usr/lib64/mysql/libmysqld.a
>> (client.o): relocation R_X86_64_32S against `client_errors' can not be
>> used when making a shared object; recompile with -fPIC
> 
> Well, I fixed this individual instance.  As Jer pointed out, it's in the
> bug-wrangling guide.  Unfortunately the bug wranglers are only human,
> and sometimes some will slip through.  If you find any more, it might be
> worth contacting a bug wrangler directly...

Thanks.

FWIW, after I posted I got thinking.  I believe that may have happened 
because the bug was originally filed on amarok2 _pre builds, which had 
amarok-1.9x or some such versions, IIRC, but could have still been 
referred to as amarok2, thus the original name.  But in any case it could/
should have been updated after amarok-2 was released... and now it has 
been. =:^)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

[gentoo-dev] Re: Use full package atoms for bug reports

[Christian Faulhammer]

[-- Attachment #1: Type: text/plain, Size: 849 bytes --]

Hi,

Jeroen Roovers <jer@gentoo.org>:
> On Sun, 4 Jan 2009 14:52:11 +0100
> Christian Faulhammer <fauli@gentoo.org> wrote:
> > Please be so kind and use full package atoms in the bug description
> > line (especially when bug wrangling), searching is made easier that
> > way.
> 
>   "Bug reports that refer to a single or a few (similar) packages
>   should detail the package atom(s) as completely as possible in the
>   Summary, including a version only when other versions do not exhibit
>   the bug."[1]

 I know that piece, I wrote the initial version of that paragraph. :)
But some people who are allowed to assign directly (mostly developers)
tend to forget it.

V-Li

-- 
Christian Faulhammer, Gentoo Lisp project
<URL:http://www.gentoo.org/proj/en/lisp/>, #gentoo-lisp on FreeNode

<URL:http://www.faulhammer.org/>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]