Ok, I'll give that a shot on Monday. But if it's not included in the
devel image the I would have already installed it via yum.
Now onto the other 70 packages that also fail :(
On 22 Aug 2009, at 19:21, Rusty Lynch <[email protected]> wrote:
On Sat, 2009-08-22 at 00:07 -0700, Glen Gray wrote:
So does that basically mean the I shouldn't use the development image
to do dev work.
From the sounds of it I'd be better taking the netbook image and yum
installing the dev packages.
It also sounds like the libudev-devel package is broken. The file
should be in the correct location and owned by the package.
That is a very strange package, but packaging udev requires going
outside the boundaries of what we would normally consider acceptable
practices.
I'm doing a few things at once right now and not verifying my guess
that
this is an issue caused by not running the post install section in
image
creation. If i'm correct then this should be logged as a bug.
BTW, the build system wouldn't see this because libudev-devel is not
one
of the pre-installed packages. If an RPM declares a build-time dep on
libudev-devel then it is installed in the chroot using a normal yum
install (so the post install is executed.)
Should be pretty easy to fix and there should be VERY few packages
that
would attempt bizarre acrobatics, so instead of moving to a non-devel
image, i would just:
$ rpm -e --nodeps libudev-devel
$ yum install libudev-devel
--rusty
_______________________________________________
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
