RPM limitations at kickstart time?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: RPM limitations at kickstart time?
- From: Hal Wine <hal@xxxxxxxxxxxxxx>
- Date: Thu, 13 Jan 2005 12:52:19 -0800
- Cc:
- User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040913
with rpm 4.2.3-10 (RHEL 3 ES update 3), I'm seeing rpm database
corruption when having an RPM install another RPM in a %post scriptlet.
Supposedly, this is permitted since 4.1-1, and it works fine outside of
kickstart (anaconda).
rpm at kickstart time claims to support the feature (as advertised via
examination of 'rpm --showrc' output.
Any pointers to solutions? Or documentation of the limitations at
kickstart time?
Thanks,
--Hal
P.S. Yes, I have my reasons for doing this, and jbj claims it's possible
:) See http://www.redhat.com/archives/rpm-list/2004-November/msg00020.html
[Index of Archives]
[Kickstart]
[Fedora Users]
[Fedora Legacy List]
[Fedora Maintainers]
[Fedora Desktop]
[Fedora SELinux]
[Big List of Linux Books]
[Yosemite News]
[Yosemite Photos]
[KDE Users]
[Fedora Tools]