Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 280693 - gnome-extra/gnome-lirc-properties-0.2.8 fails to build
Summary: gnome-extra/gnome-lirc-properties-0.2.8 fails to build
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Doug Goldstein (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-07 19:29 UTC by Kyle Evans
Modified: 2010-10-06 19:15 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
incomplete ebuild (gnome-lirc-properties-0.2.8.ebuild,921 bytes, text/plain)
2009-08-14 18:22 UTC, Kyle Evans
Details
proposed ebuild (gnome-lirc-properties-0.3.1.ebuild,1.21 KB, text/plain)
2009-08-15 16:19 UTC, Kyle Evans
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Kyle Evans 2009-08-07 19:29:07 UTC
Build error due to configuration script not found.

Reproducible: Always

Steps to Reproduce:
1. ACCEPT_KEYWORDS=~amd64 emerge gnome-lirc-properties
2.
3.

Actual Results:  
 * Messages for package gnome-extra/gnome-lirc-properties-0.2.8:

 * 
 * ERROR: gnome-extra/gnome-lirc-properties-0.2.8 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line  165:  Called econf '--with-lirc-confdir=/etc' '--enable-policy-kit'
 *               ebuild.sh, line  539:  Called die
 * The specific snippet of code:
 *   		die "no configure script found"
 *  The die message:
 *   no configure script found
 * 
 * If you need support, post the topmost build error, and the call stack if relevant.
 * A complete build log is located at '/var/tmp/portage/gnome-extra/gnome-lirc-properties-0.2.8/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/gnome-extra/gnome-lirc-properties-0.2.8/temp/environment'.
 * 


Expected Results:  
Build w/o errors

Version 0.2.7 has the same issue.

I am using app-misc/lirc-0.8.5
Comment 1 James Earl Spahlinger 2009-08-09 21:56:01 UTC
Please paste the output of 'emerge --info' into a bugzilla comment to assist the maintainers in resolving this issue

Comment 2 Kyle Evans 2009-08-14 18:22:36 UTC
Created attachment 201254 [details]
incomplete ebuild

mmm, how about the ebuild itself. After posting this bug I tried going into the tmp folder to build manually and couldn't find any source. That is when I looked at the ebuild only to find half of it. How this made it into portage is beyond me. There is no source link, no unpack, no install... I'm no expert, but I think we need that stuff. 

I was going to try to hack together an ebuild but being I don't know what I'm doing it hasn't happened yet. I do have the location of the new source, which is now at 3.1. 

http://ftp.gnome.org/pub/gnome/sources/gnome-lirc-properties/0.3/
Comment 3 Kyle Evans 2009-08-15 16:19:27 UTC
Created attachment 201342 [details]
proposed ebuild

Here is my hack. There are some bugs to work out but I wanted to get this up ASAP. A few notes: 

-I did not touch any of the dependancies from the 0.2.8 ebuild

-After the first successful compile, the program would not start due to /etc/hardware.conf file not found. After creating, it would start. I ultimately moved the location to /etc/lirc as having a hardware.conf file in /etc did not seem intuitive. I'm not sure if this could have any implications when interfacing the the master lirc program(I only mention this because after some very brief testing I get a could not initialize hardware error during the custom configuration learn function). 

-I have LIRC_DEVICES=all and it takes eons for the program to start, all the while spitting out messages of the following nature"
...
WARNING:root:/usr/share/gnome-lirc-properties/remotes.tar.gz: Remote NOVA-T500 listed twice in incoming/893f9fd8ccfd69c70703b447fd3939e26747e4aa.conf and incoming/99df5e54fac7f296e638cbc08a8ce016220257fa.conf.
WARNING:root:/usr/share/gnome-lirc-properties/remotes.tar.gz: Remote iMON-PAD listed twice in incoming/a6b8fdd6c1576ba64d2d5af3aa60c327e89d91a6.conf and incoming/e4584b9bb35f6581ccf58f5cc55bccba0f7e6444.conf.
WARNING:root:/usr/share/gnome-lirc-properties/remotes.tar.gz: Remote linux-input-layer listed twice in incoming/2d185b2ff99fa227dec980ddb68e14f46746d5d5.conf and incoming/453f25348fc340949d7476ab97c4dac9025d387b.conf.

-Although the icons are installed, there is not one tied to the gnome-control-center item.
Comment 4 Kyle Evans 2009-08-22 00:30:51 UTC
So it turns out that I don't need lirc for my computer as reciever outputs normal keycodes and all I need to do is edit the definitions. This means I can't test the ebuild. 

In reference to my previous post, it looks like there would be implications with isolating the configuration files to /etc/lirc as lirc uses /etc/lircd.conf. So, we'll either have to put up with having lircd.conf, lircd.conf.gnome, & harware.conf in /etc, or something will need patched to make everything coherent and mesh together. I'll leave this up to the maintainers. In its current state I don't believe the proposed ebuild will work correctly with lirc. 

The icon not showing up in the control center is only a reboot issue. It is, however, placed in the gnome menu inconsistant with the other control center icons. It's by itself in the "Administration" menu while everything else is in "Preferences" menu. This may just be a gnome versioning issue. I am using 2.26.3. 

So that's all, I hope I've contributed something.
Comment 5 Jeremy Olexa (darkside) (RETIRED) archtester gentoo-dev Security 2009-08-22 18:46:33 UTC
assigning to maintainer.
Comment 6 Samuli Suominen (RETIRED) gentoo-dev 2010-10-06 19:15:58 UTC
+*gnome-lirc-properties-0.5.1 (06 Oct 2010)
+
+  06 Oct 2010; Samuli Suominen <ssuominen@gentoo.org>
+  +gnome-lirc-properties-0.5.1.ebuild:
+  Version bump (to replace policykit with polkit). Fix building wrt #280693
+  by Kyle Evans. Fix python usage wrt #313463 by Arfrever Frehtes Taifersar
+  Arahesis.