| 1 |
Hans de Hartog wrote: |
| 2 |
> Philip Webb wrote: |
| 3 |
> |
| 4 |
>> It would help if you listed the packages in question. |
| 5 |
>> |
| 6 |
> |
| 7 |
> Also thanks to Ryan and Steve to illustrate the situation |
| 8 |
> in the "not_so_common_packages" scene. (BTW, how do I check |
| 9 |
> for an "overlay somewhere"?) |
| 10 |
> |
| 11 |
> - freewheeling (dies in glibc with double free or corruption) |
| 12 |
> In the tree is only 0.5_pre4 (masked ~x86). There's bug |
| 13 |
> 149784 asking for a version bump to 0.5.2a and the newest |
| 14 |
> version from the freewheeling people is 0.5.3 |
| 15 |
> |
| 16 |
> - sooperlooper (won't build at all) |
| 17 |
> In the tree is only 1.0.3 (masked ~x86). No bugs reported. |
| 18 |
> Latest version is 1.0.8c (and even 1.0.8u for the Mac). |
| 19 |
> I guess I've to file a bug asking for a version bump? |
| 20 |
|
| 21 |
If you're going to file a stabilization bug, then make sure you do this: |
| 22 |
|
| 23 |
First, make sure the ebuild works and the program compiles cleanly |
| 24 |
without any problems. Make sure that all possible deps are stable for |
| 25 |
it (if they aren't file stable request bugs for those first). You can |
| 26 |
check the stable status by going to http://packages.gentoo.org/ and |
| 27 |
searching for the package in question. |
| 28 |
|
| 29 |
Then, when you file the bug, make sure you add the arches to the CC list |
| 30 |
so they get a copy. |
| 31 |
|
| 32 |
Oh yes, and don't file any stable request bugs unless the ebuild has |
| 33 |
been released for at least 30 days, and there are no bugs in bugzilla. |
| 34 |
|
| 35 |
That's a pretty hacked summary, again, but there ya go. :) Pretty much |
| 36 |
just make sure everything is "good to go" before filing a stable |
| 37 |
request. Doing the legwork really doesn't take much time, and it makes |
| 38 |
things much simpler for arch testers and developers. |
| 39 |
|
| 40 |
Steve |
| 41 |
-- |
| 42 |
gentoo-user@g.o mailing list |
Archives