how to tst the "erase " functionality of an rpm
pinto.elia at gmail.com
Fri Feb 20 16:51:45 UTC 2009
On Fri, Feb 20, 2009 at 2:00 PM, Panu Matilainen
<pmatilai at laiskiainen.org>wrote:
> On Thu, 19 Feb 2009, devzero2000 wrote:
>> On Thu, Feb 19, 2009 at 12:03 AM, Jennis Pruett <jennyp at lanl.gov> wrote:
>> > I am not allowed "root" on any system, but we build rpms to
>> > give to our sysadmins.
>> > My problem: Using my .spec file, I create rpms.
>> > But I can't find any way to test what will happen when the rpm
>> > is obsolete and the systems folks have to do the rpm -e rpm_that_I
>> > built_at_one_time_in_antoher_life.rpm
>> > I can cpio the rpm, and use the rpm -qip to check it. But there is no
>> > that I know
>> > of, to verify that the erasure will actually remove everything.
> Well, generally rpm removes what it knows about. If you're creating files
> from %post and such, try to move that to the package contents. Or if not
> possible, make %ghost files of anything that you expect to get created
> either in scriptlets or software runtime.
> > Anyone have an idea?
>> > Thanks,
>> > J
>> Use a chroot. Most also build in a chroot
> Yup, except chroot needs root privilege which is not available here:
I ask my sysadm to create a chroot for a user (o for myself ) - i hope that
it is possible to ask something to the sysadmin - telling it to use
pam_chroot for this username. So no root priv are necessary for that user.
For accessing the machine from ssh it is necessary disable ssh privilege
separation but IMHO it is not a problem for a development env. This is what
i have done in the past . In the future probably i try pam_namespace and
the linux shared subtree.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Rpm-list