Please fix bug 183862 FINALY!

Message

doro1211 · Post by **doro1211** » Sat Jul 19, 2008 8:37 pm

That's a far cry from a compiler (gcc) bug...

Let_Me_Be · Post by **Let_Me_Be** » Sun Jul 20, 2008 1:35 am

The ebuild ignores USE flag settings. Therefore the documentation is always built. This bug is still present.

I had another problem, that turned this bug into a blocker. The documentation build always failed with access violation, and therefore, hal could not be installed. This seems to be a GCC compiler bug. But I'm so pissed off by the bug itself, that I'm not going to test it any further.

doro1211 · Post by **doro1211** » Sun Jul 20, 2008 1:38 am

No, this isn't a GCC bug. It's a gentoo/portage/ebuild type of bug. A GCC bug usually manifests with the compiler segfaulting or coredumping.

Agreed though that it's a bug and should be fixed. It's very odd for one version of HAL to be ok (the dependency tree fixed) and then later versions broken. That just doesn't make sense.

pilla · Post by **pilla** » Sun Jul 20, 2008 2:04 am

Developers are usually more receptive to bugs with patches included. In this case, I don't think it would be so dificult to come out with a tested patch for one of the ebuilds.

doro1211 · Post by **doro1211** » Sun Jul 20, 2008 2:05 am

Yes, it should be trivial to modify the dependencies in the ebuild. (Like one line of change...)

You could also easily put it in an overlay to fix your own issues.

Let_Me_Be · Post by **Let_Me_Be** » Sun Jul 20, 2008 2:20 am

doro1211 wrote:No, this isn't a GCC bug. It's a gentoo/portage/ebuild type of bug. A GCC bug usually manifests with the compiler segfaulting or coredumping.

Software segfaults when compiled with one version of GCC and works when compiled with other version. Yeah this is definitely an ebuild bug

pilla wrote:Developers are usually more receptive to bugs with patches included. In this case, I don't think it would be so dificult to come out with a tested patch for one of the ebuilds.

Please stop this nonsense. There IS a patch.

yabbadabbadont · Post by **yabbadabbadont** » Sun Jul 20, 2008 2:59 am

Let_Me_Be wrote:
pilla wrote:Developers are usually more receptive to bugs with patches included. In this case, I don't think it would be so dificult to come out with a tested patch for one of the ebuilds.
Please stop this nonsense. There IS a patch.

Wow. Telling pilla, who is a forums admin, to "stop this nonsense."

You better hope he has a good sense of humor.

Let_Me_Be · Post by **Let_Me_Be** » Sun Jul 20, 2008 3:12 am

yabbadabbadont wrote:
Let_Me_Be wrote:
pilla wrote:Developers are usually more receptive to bugs with patches included. In this case, I don't think it would be so dificult to come out with a tested patch for one of the ebuilds.
Please stop this nonsense. There IS a patch.
Wow. Telling pilla, who is a forums admin, to "stop this nonsense."

You better hope he has a good sense of humor.

Guess what? I don't care if he is the admin of the universe. For me he is just someone, who has no idea what is this topic (or the bug) about, an just jumped in to tell everybody how stupid they were.

For the last time (and if anyone else jumps in with other great ideas, i won't reply). There is bug, that is one year old. The bug has a user posted patch attached. After the bug was opened there were at least 6 new versions of the ebuild published. This is not even the only one bug, that describes this problem, there is another bug 222315 (version bump request), that was closed as FIXED (how the hell can you close a bug as FIXED when it was not fixed at all???). Because there was another related bug (probably GCC bug) this ignorance resulted into a blocker (it was not possible to build hal at all). This blocker is now fixed, because gtk-doc does not fail any more when compiled with GCC 4.3.1. The bug remains (I'm really looking forward to see another blocker, related to this bug).

VoidMage · Post by **VoidMage** » Sun Jul 20, 2008 11:20 am

Please, Let_Me_Be, calm down.
Yes, it's annoying, but trowing a hissy fit wont change a thing (not like I didn't threw one on bugzilla).
And that was not a gcc bug, more likely it was a problem with one of your libraries (or other packages)
not being updated (maybe a missed deep dependency or a failed revdep-rebuild).

AllenJB · Post by **AllenJB** » Sun Jul 20, 2008 12:20 pm

Developers prefer 1 bug per issue, so a version bump is FIXED once that version is in the main package repository. Any issues with the new ebuild should be filed as a separate issue (as noted in the comments of the version bump bug).

As already mentioned in this thread, the patch attached to the bug isn't complete - while it adds the configure option, it doesn't handle the additional dependency. It would also be useful if people submitting patches tested whether doxygen is still required, and if not, patch it out if it's not.

Once a patch is posted, it's also useful for people to test the patched package in a local overlay and submit a comment on any issues they run into (if people have already posted that the patch works, then it's curtesy not to keep posting additional comments that the patch works - just post if there are problems).

If testers have time, they could also test with different combinations of USE flags.

You may also want to consider voting on the bug to help the developers see which bugs users consider important.

VoidMage · Post by **VoidMage** » Sun Jul 20, 2008 12:27 pm

It would also be useful if people submitting patches tested whether doxygen is still required, and if not, patch it out if it's not.

It would also be useful if somebody read NEWS from hal tarball, where it's explicitly said, that they stopped using doxygen.

pilla · Post by **pilla** » Sun Jul 20, 2008 7:20 pm

Let_Me_Be wrote: Guess what? I don't care if he is the admin of the universe. For me he is just someone, who has no idea what is this topic (or the bug) about, an just jumped in to tell everybody how stupid they were.

Guess what? I'm the same moderator that told you before to keep a professional tone, and that wasn't for no reason. Enjoy your ban until you learn how to deal with people without throwing crap around.

doro1211 · Post by **doro1211** » Sun Jul 20, 2008 9:47 pm

Call me old fashioned, but considering the Gentoo devs aren't even paid, and the amazing quality of work and innovation they produce, I'm not going to go around demanding anything. Offering suggestions, pointing out bugs, etc... that's all good, and most are receptive to those things, but one shouldn't have a sense of entitlement when one is doing nothing to earn it.