There is a known bug at http://bugzilla.moblin.org/show_bug.cgi?id=5496, which may influence the autopackage installation script. Please correct the /dev/stdin and /dev/stdout file manually and try rpmbuild again.
>The udev init script /etc/udev/makedev.d/00-base.files wronly creates the >/dev/stdin and /dev/stdout symbolic links. stdin and stdout are wronly swaped. >Applications that depend/use these files get broken. For instance, autopackage >installations scripts use /dev/stdin[out] files and they silently halt, which >waiting for stdout when expecting stdin and vice versa. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Glen Gray Sent: 2009年8月26日 17:38 To: Glen Gray Cc: [email protected] Subject: Re: [Moblin Dev] moblin .src.rpm files that don't build Ok, managed to spare some time on checking up on this again this morning. After the fresh install of the image and the yum install of the devel packages etc we're in a marginally better position than before, but still a long way from acceptable. There are 57 failed .src.rpm files now. 38 of which are due to "Installed (but unpackaged) file(s) found". And a lot of those are down to /usr/share/info/dir being created, which was something I pointed out back at the beginning of June with my patch to acct. You can see the full list of failed rpms (with links to the rpmbuild output for each one here, http://slaine.org/moblin On 24 Aug 2009, at 17:40, Glen Gray wrote: > I've left a fresh run going on a new jailed env based off the stock > 18/08 image. Earlier I removed all the -devel packages and > reinstalled. The failed count dropped to 60 on that run. Let's see > how it goes tonight. > > On 21 Aug 2009, at 16:27, Glen Gray <[email protected]> wrote: > >> Thanks for responding Arjan. >> >> On 21 Aug 2009, at 16:19, Arjan van de Ven wrote: >> >>> Glen Gray wrote: >>>> Here's the list of all the src.rpm files that didn't build. I've >>>> not spent a lot of time trying to debug this as I would have >>>> expected the src.rpm files for a distro to be buildable on that >>>> distro. It's also possible that I've something up with my moblin >>>> env. >>> >>> something must be wrong, since we actually create moblin by >>> building on moblin.. >> >> That was my understanding and why I went to the trouble to setup a >> moblin chroot to do my dev work under. >> >>> can we take ONE out of your list, and can you show us how it fails >>> please? >> >> >> You should see one for devicekit shortly. That was the first one on >> the list. >> >> Cheers, >> -- >> Glen Gray <[email protected]> Digital Depot, Thomas Street >> Software Engineering Manager Dublin 8, Ireland >> Lincor Solutions Ltd. Ph: +353 (0) 1 4893682 >> >> _______________________________________________ >> Moblin dev Mailing List >> [email protected] >> >> To manage or unsubscribe from this mailing list visit: >> http://lists.moblin.org/listinfo/dev or your user account on >> http://moblin.org >> once logged in. >> >> For more information on the Moblin Developer Mailing lists visit: >> http://moblin.org/community/mailing-lists -- Glen Gray <[email protected]> Digital Depot, Thomas Street Software Engineering Manager Dublin 8, Ireland Lincor Solutions Ltd. Ph: +353 (0) 1 4893682 _______________________________________________ Moblin dev Mailing List [email protected] To manage or unsubscribe from this mailing list visit: http://lists.moblin.org/listinfo/dev or your user account on http://moblin.org once logged in. For more information on the Moblin Developer Mailing lists visit: http://moblin.org/community/mailing-lists _______________________________________________ Moblin dev Mailing List [email protected] To manage or unsubscribe from this mailing list visit: http://lists.moblin.org/listinfo/dev or your user account on http://moblin.org once logged in. For more information on the Moblin Developer Mailing lists visit: http://moblin.org/community/mailing-lists
