Please fix bug 183862 FINALY!

Message

Let_Me_Be · Post by **Let_Me_Be** » Thu Jul 17, 2008 9:54 pm

I already tried to draw atention by opening a duplicate, now i will also try here.

Please fix this bug! It has changed into a blocker! There is no version of hal that actually compiles! No possible workaround! PLEASE!!!

cyrillic · Post by **cyrillic** » Thu Jul 17, 2008 10:53 pm

I am not an expert on HAL, but all the versions that I have used in the past have compiled and run without major problems.

This is what I am currently running on all my machines (~amd64 ~ppc ~x86)

Code: Select all

# equery list hal
[ Searching for package 'hal' in all categories among: ]
 * installed packages
[I--] [ ~] app-misc/hal-info-20080508 (0)
[I--] [ ~] sys-apps/hal-0.5.11-r1 (0)

VoidMage · Post by **VoidMage** » Thu Jul 17, 2008 11:14 pm

Please read [bug=229145]this[/bug] for an explanation what the real problem is.

Let_Me_Be · Post by **Let_Me_Be** » Thu Jul 17, 2008 11:18 pm

cyrillic wrote:I am not an expert on HAL, but all the versions that I have used in the past have compiled and run without major problems.

This is what I am currently running on all my machines (~amd64 ~ppc ~x86)
Code: Select all
# equery list hal
[ Searching for package 'hal' in all categories among: ]
 * installed packages
[I--] [ ~] app-misc/hal-info-20080508 (0)
[I--] [ ~] sys-apps/hal-0.5.11-r1 (0) 

How did you get the documentation generation to work?

This is my problem: http://bugs.gentoo.org/show_bug.cgi?id=232105

cyrillic · Post by **cyrillic** » Thu Jul 17, 2008 11:43 pm

Let_Me_Be wrote:How did you get the documentation generation to work?

None of my machines have USE="doc", so I guess any documentation bugs went unnoticed.

timeBandit · Post by **timeBandit** » Fri Jul 18, 2008 3:36 am

Moved from Kernel & Hardware to Portage & Programming.

Several points to note:

A minority of developers are active on the forums, complaints here to devs fall on few interested ears.
The bug you duplicated included a patch that might fix your problem, if you applied it to a copy of the ebuild in an overlay.
Given 1 & 2, your own interests might be better served--i.e., the repair committed sooner--if you tested the fix, provided feedback and otherwise offered to help.

On the whole, the community reacts better to those who offer even limited assistance than those who demand others take action.

Let_Me_Be · Post by **Let_Me_Be** » Fri Jul 18, 2008 6:37 am

cyrillic wrote:
Let_Me_Be wrote:How did you get the documentation generation to work?
None of my machines have USE="doc", so I guess any documentation bugs went unnoticed.

Well i have the doc turned off as well, the problem is that hal ignores this flag and builds documentation anyway. Could you please post the versions of dev-util/gtk-doc, and dev-libs/libxslt you have installed?

VoidMage · Post by **VoidMage** » Fri Jul 18, 2008 10:08 am

@cyrilic: I'm almost sure, that you're wrong,
the real reason this bug could go unnoticed by you,
was probably the fact that everything is probably OK,
if you have gtk-doc installed.

cwr · Post by **cwr** » Fri Jul 18, 2008 10:19 am

The workaround I use is to have "doc" set in make.conf, and "-doc" set in
package.use for hal, dbus, and a dbus documentation package whose name
I can't recall. That seems to work ok.

Another approach might be to take the doc flag out of make.conf, build dbus
and hal, and put the flag back.

Will

Let_Me_Be · Post by **Let_Me_Be** » Fri Jul 18, 2008 10:42 am

cwr wrote:The workaround I use is to have "doc" set in make.conf, and "-doc" set in
package.use for hal, dbus, and a dbus documentation package whose name
I can't recall. That seems to work ok.

Another approach might be to take the doc flag out of make.conf, build dbus
and hal, and put the flag back.

Will

FOR THE LAST TIME THAT F&*!(NG EBUILD IS IGNORING USE FLAGS SETTINGS!!!!! IF YOU SET -DOC WHEREVER YOU WANT IT WILL BE IGNORED!!!!! THE DOCUMENTATION WILL BE BUILT ANYWAY!!!!

Well it won't actually because it fails at that stage.

VoidMage · Post by **VoidMage** » Fri Jul 18, 2008 1:59 pm

As I said in bug 229145, the whole problem of doc useflag
comes from the fact, that hal maintainers failed to notice
that hal switched from doxygen to gtk-doc.
@Let_Me_Be: one simple question - does it work when you have gtk-doc installed
or are upstream files corrupted and it doesn't work even then ?

cyrillic · Post by **cyrillic** » Fri Jul 18, 2008 3:52 pm

Let_Me_Be wrote:Could you please post the versions of dev-util/gtk-doc, and dev-libs/libxslt you have installed?

Code: Select all

# equery list gtk-doc
[ Searching for package 'gtk-doc' in all categories among: ]
 * installed packages
[I--] [  ] dev-util/gtk-doc-am-1.10-r1 (0)

Code: Select all

# equery list libxslt
[ Searching for package 'libxslt' in all categories among: ]
 * installed packages
[I--] [  ] dev-libs/libxslt-1.1.24 (0)

ps. I don't have dev-util/gtk-doc installed at all, because all the packages that could use it look for USE="doc" which I have disabled globally in /etc/make.conf

Code: Select all

# equery depends gtk-doc
[ Searching for packages depending on gtk-doc... ]
app-admin/pessulus-2.16.4 (doc? >=dev-util/gtk-doc-1)
app-text/evince-2.22.2-r1 (doc? dev-util/gtk-doc)
app-text/gtkspell-2.0.11-r1 (doc? >=dev-util/gtk-doc-1)
dev-libs/atk-1.22.0 (doc? >=dev-util/gtk-doc-1)
dev-libs/glib-2.16.4 (doc? >=dev-util/gtk-doc-1.8)
dev-libs/gmime-2.2.17 (doc? >=dev-util/gtk-doc-1.0)
dev-libs/totem-pl-parser-2.22.3 (doc? dev-util/gtk-doc)
gnome-base/gail-1.22.3 (doc? >=dev-util/gtk-doc-1)
gnome-base/gconf-2.22.0 (doc? >=dev-util/gtk-doc-1)
gnome-base/gnome-desktop-2.22.3 (doc? >=dev-util/gtk-doc-1.4)
gnome-base/gnome-keyring-2.22.3 (doc? dev-util/gtk-doc)
gnome-base/gnome-panel-2.22.2 (doc? >=dev-util/gtk-doc-1)
gnome-base/gnome-vfs-2.22.0 (doc? >=dev-util/gtk-doc-1)
gnome-base/gvfs-0.2.5 (doc? >=dev-util/gtk-doc-1)
gnome-base/libbonobo-2.22.0 (doc? >=dev-util/gtk-doc-1)
gnome-base/libbonoboui-2.22.0 (doc? >=dev-util/gtk-doc-1)
gnome-base/libglade-2.6.2 (doc? >=dev-util/gtk-doc-1)
gnome-base/libgnome-2.22.0 (doc? >=dev-util/gtk-doc-1)
gnome-base/libgnomecanvas-2.20.1.1 (doc? >=dev-util/gtk-doc-1)
gnome-base/libgnomeprint-2.18.4 (doc? >=dev-util/gtk-doc-0.9)
gnome-base/libgnomeprintui-2.18.2 (doc? >=dev-util/gtk-doc-1)
gnome-base/libgnomeui-2.22.1 (doc? >=dev-util/gtk-doc-1)
gnome-base/librsvg-2.22.2 (doc? >=dev-util/gtk-doc-1)
gnome-base/orbit-2.14.13 (doc? >=dev-util/gtk-doc-1)
gnome-extra/evolution-data-server-2.22.3 (doc? >=dev-util/gtk-doc-1.9)
gnome-extra/libgsf-1.14.7 (doc? >=dev-util/gtk-doc-1)
media-gfx/gimp-2.4.6 (doc? >=dev-util/gtk-doc-1)
media-libs/swfdec-0.6.6-r1 (doc? >=dev-util/gtk-doc-1.6)
net-libs/gnutls-2.4.1 (doc? dev-util/gtk-doc)
net-libs/libsoup-2.4.1 (doc? >=dev-util/gtk-doc-1)
www-client/epiphany-2.22.3-r10 (doc? >=dev-util/gtk-doc-1)
x11-libs/cairo-1.6.4 (doc? >=dev-util/gtk-doc-1.6)
x11-libs/gksu-2.0.0-r1 (doc? dev-util/gtk-doc)
x11-libs/gtk+-2.12.11 (doc? >=dev-util/gtk-doc-1.8)
x11-libs/gtkglext-1.2.0 (doc? >=dev-util/gtk-doc-0.10)
x11-libs/gtksourceview-1.8.5-r1 (doc? >=dev-util/gtk-doc-1)
x11-libs/gtksourceview-2.2.2 (doc? >=dev-util/gtk-doc-1)
x11-libs/libgksu-2.0.5 (doc? >=dev-util/gtk-doc-1.2-r1)
x11-libs/libnotify-0.4.4 (doc? >=dev-util/gtk-doc-1.4)
x11-libs/libsexy-0.1.11 (doc? >=dev-util/gtk-doc-1.4)
x11-libs/libwnck-2.22.3 (doc? >=dev-util/gtk-doc-1.9)
x11-libs/pango-1.20.5 (doc? >=dev-util/gtk-doc-1)
x11-libs/vte-0.16.14 (doc? >=dev-util/gtk-doc-1.0)

pilla · Post by **pilla** » Fri Jul 18, 2008 4:27 pm

Let_Me_Be wrote: FOR THE LAST TIME THAT F&*!(NG EBUILD IS IGNORING USE FLAGS SETTINGS!!!!! IF YOU SET -DOC WHEREVER YOU WANT IT WILL BE IGNORED!!!!! THE DOCUMENTATION WILL BE BUILT ANYWAY!!!!

Chill down and keep a professional tone.

cwr · Post by **cwr** » Fri Jul 18, 2008 6:14 pm

Well, all I can say is that the settings:
dev-libs/dbus-glib -doc
sys-apps/dbus -doc
sys-apps/hal -doc
in package.use work for me, in both 2007.0 and 2008.0. YMMV.

Will

VoidMage · Post by **VoidMage** » Fri Jul 18, 2008 8:28 pm

@cwr: a very simple question - do you have gtk-doc installed ?
Cause that may be the key difference between those hit by the bug
and those unaffected by it.

cwr · Post by **cwr** » Sat Jul 19, 2008 10:24 am

Yes, gtk-doc is emerged; but it was emerged _after_ hal and dbus, so it
wouldn't have affected them. emerge -pv hal / dbus doesn't show anything
strange even now, but I haven't tried re-emerging them.

Will

Update: looking at the hal emerge log, the "-doc" flag turns on --docbook
and --doxygen in the configure script, and doxygen at least isn't emerged.
I can't check docbook, because it was emerged earlier.

VoidMage · Post by **VoidMage** » Sat Jul 19, 2008 12:26 pm

Do I need to spell it out ?!
IIRC, as of 0.5.8 hal moved from doxygen to gtk doc,
so whatever option regarding doxygen, that is in the ebuild, has completely NO EFFECT !!!

cwr · Post by **cwr** » Sat Jul 19, 2008 1:11 pm

Yes, well, I'm using hal-0.5.9-r3 which is fairly recent, and the ebuild
contains:

DEPEND="${RDEPEND}
dev-util/pkgconfig
>=dev-util/intltool-0.35
doc? ( app-doc/doxygen
app-text/docbook-sgml-utils
app-text/xmlto )"

which I thought gave a doxygen dependency. My apologies, but where
do I find the gtk-doc requirement?

Will

~

pilla · Post by **pilla** » Sat Jul 19, 2008 1:26 pm

I think that VoidMage means that the ebuild is wrong. It states that hal depends on oxygen while it depends on gtk-doc now. Is that it?

VoidMage · Post by **VoidMage** » Sat Jul 19, 2008 1:41 pm

@pilla: yes, that's EXACTLY what I mean.
Every single ebuild, except for 0.5.7 is incorrect.

StifflerStealth · Post by **StifflerStealth** » Sat Jul 19, 2008 4:39 pm

The HAL dev needs to be poked until he/she changes the ebuilds correctly. Leaving an incorrect depend this long when the bug is in b.g.o is inexcusable especially since there have been version bumps. I am normally on the devs' side, but not this time.

Cheers.

Let_Me_Be · Post by **Let_Me_Be** » Sat Jul 19, 2008 6:08 pm

VoidMage wrote:@Let_Me_Be: one simple question - does it work when you have gtk-doc installed
or are upstream files corrupted and it doesn't work even then ?

No it doesn't. There is some odd problem in the documentation build process (common for all packages using gtk-doc). See the bug i have posted.

Let_Me_Be · Post by **Let_Me_Be** » Sat Jul 19, 2008 6:56 pm

Great, so the bug that caused the documentation build to fail was a compiler bug. I have emerged the latest GCC, recompiled libxslt, gtk-doc and gtk-doc-am and the hal finally merged succesfully.

doro1211 · Post by **doro1211** » Sat Jul 19, 2008 7:02 pm

Not according to what's written above, it's a problem with the hal ebuilds not correctly specifying dependencies.

Unless I misread something...

Why are you saying it's a compiler error?

VoidMage · Post by **VoidMage** » Sat Jul 19, 2008 8:08 pm

Well, hal + doxygen/gtk-doc ignoring doc useflag is
an ebuild bug.