Hi,
Thanks for the suggestions. We have placed all environment variables that exist when rpm runs into both %post, and have exported them before running yum. We are still getting the same error.
Also, %post has been stripped down to just /usr/bin/echo blah > /tmp/file - it doesn't look like it even gets executed - the truss(1) output seems to show that the file is unlink() 'ed by a PPID before it is executed.
-j
--- On Thu, 11/12/09, Seth Vidal <skvidal@xxxxxxxxxxxxxxxxx> wrote:
From: Seth Vidal <skvidal@xxxxxxxxxxxxxxxxx>
Subject: Re: YUM install [package.rpm] fails on Solaris, reports success
To: "Yellowdog Updater, Modified" <yum@xxxxxxxxxxxxxxxxx>
Date: Thursday, November
12, 2009, 9:55 PM
On Thu, 12 Nov 2009, Joshua Burns wrote:
>
> For what it's worth, I, too, was chagrined at having to report a surprise issue this late in the game. Having gotten this
> far, I had assumed that if RPM could install a given package, YUM would also succeed.
>
> Any help you are able to give would of course be greatly appreciated. This is a particularly key moment (a fork in the
> road, if you will) in the history of the company's infrastructure, and the successful use of this technology could have
> major impact on the adoption of open-source technology over open-wallet technology.
>
okay - so normally when something works when you run it with rpm and doesn't with yum it is environment variables or improper assumptions in the scriptlets about paths, etc.
So maybe a good place to start is to dump the env you're
running in when you run rpm and then dump the environment inside python in yum .
anything odd going on with login shells vs /bin/sh for example?
-sv
-----Inline Attachment Follows-----
|
_______________________________________________
Yum mailing list
Yum@xxxxxxxxxxxxxxxxx
http://lists.baseurl.org/mailman/listinfo/yum
