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