Please remove me from the mailing list - there isn't an option to remove on the web as stated below.
rpm-list-request@redhat.com wrote:
Send Rpm-list mailing list submissions to
rpm-list@redhat.com
To subscribe or unsubscribe via the World Wide Web, visit
https://www.redhat.com/mailman/listinfo/rpm-list
or, via email, send a message with subject or body 'help' to
rpm-list-request@redhat.com
You can reach the person managing the list at
rpm-list-admin@redhat.com
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Rpm-list digest..."
Today's Topics:
1. rpm --root (Allen Wayne Best)
2. Re: rpm --root (Jeff Johnson)
3. Re: rpm --root (Allen Wayne Best)
4. Re: rpm --root (Jeff Johnson)
5. Re: rpm --root (Allen Wayne Best)
6. %preun and %postun does not run (Valery Reznic)
7. Help with rpmlib (Steve Hill)
> ATTACHMENT part 3.1 message/rfc822
From: Allen Wayne Best
To: rpm-list@redhat.com
Subject: rpm --root
Date: Sun, 21 Sep 2003 12:28:40 -0700
hi all:
can anyone affirm that 'rpm --root /mnt/sysimage' will do what i think the man
page is saying it will do: install the rpms in the system directories
starting at /mnt/sysimage and not in the current /.
a rh9 installation went south, way south, after appling all the current rh9
updates. now is get a segmentation fault when i do a chroot /mnt/sysimage,
and get same when i try to boot the system. as by one on information, the
same was happening during ( and not before) the rpm -Fuh of the the updates.
any input is greatly appreciated. i really don't want to hose the system
worse! :)
--
regards,
allen wayne best, esq
"your friendly neighborhood rambler owner"
"my rambler will go from 0 to 105"
Current date: 34:25:9::263:2003
The problem with any unwritten law is that you do!
n't know
where to go
to erase it.
-- Glaser and Way
> ATTACHMENT part 3.2 message/rfc822
Date: Sun, 21 Sep 2003 17:10:02 -0400
From: Jeff Johnson
To: rpm-list@redhat.com
Subject: Re: rpm --root
Allen Wayne Best wrote:
>hi all:
>
>can anyone affirm that 'rpm --root /mnt/sysimage' will do what i think the man
>page is saying it will do: install the rpms in the system directories
>starting at /mnt/sysimage and not in the current /.
>
>
Yes, that's --root behavior.
>a rh9 installation went south, way south, after appling all the current rh9
>updates. now is get a segmentation fault when i do a chroot /mnt/sysimage,
>and get same when i try to boot the system. as by one on information, the
>same was happening during ( and not before) the rpm -Fuh of the the updates.
>
>any input is greatly appreciated. i really don't wan!
t to hose
the system
>worse! :)
>
>
Anaconda might be easiest. Rename /var/lib/rpm, and do minimal install,
but don't remake a file system
on your existing partitions. Once you're booted, replace /var/lib/rpm,
and use -Va to figger what's
changed.
73 de Jeff
> ATTACHMENT part 3.3 message/rfc822
From: Allen Wayne Best
To: rpm-list@redhat.com
Subject: Re: rpm --root
Date: Sun, 21 Sep 2003 14:23:58 -0700
On Sunday 21 September 2003 14:10, Jeff Johnson pronounced:
> Allen Wayne Best wrote:
> >hi all:
> >
> >can anyone affirm that 'rpm --root /mnt/sysimage' will do what i think the
> > man page is saying it will do: install the rpms in the system directories
> > starting at /mnt/sysimage and not in the current /.
>
> Yes, that's --root behavior.
>
> >a rh9 installation went south, way south, a!
fter
appling all the current
> > rh9 updates. now is get a segmentation fault when i do a chroot
> > /mnt/sysimage, and get same when i try to boot the system. as by one on
> > information, the same was happening during ( and not before) the rpm -Fuh
> > of the the updates.
> >
> >any input is greatly appreciated. i really don't want to hose the system
> >worse! :)
>
> Anaconda might be easiest. Rename /var/lib/rpm, and do minimal install,
> but don't remake a file system
> on your existing partitions. Once you're booted, replace /var/lib/rpm,
> and use -Va to figger what's
> changed.
>
> 73 de Jeff
if i understand you correctly,
mv /var/lib/rpm /var/lib/old.rpm (the entire directory!)
install as if fresh install
install the least necessary
don't install a file system
(this part i am not following you on... could you explain a bit more??)
--
regards,
allen wayne best, esq
"your friendly neighborhood rambler owner"
"my rambler will go from 0 to 105"
Current date: 16:20:14::263:2003
Why are programmers non-productive?
Because their time is wasted in meetings.
Why are programmers rebellious?
Because the management interferes too much.
Why are the programmers resigning one by one?
Because they are burnt out.
Having worked for poor management, they no longer value their jobs.
-- Geoffrey James, "The Tao of Programming"
> ATTACHMENT part 3.4 message/rfc822
Date: Sun, 21 Sep 2003 17:35:28 -0400
From: Jeff Johnson
To: rpm-list@redhat.com
Subject: Re: rpm --root
Allen Wayne Best wrote:
>On Sunday 21 September 2003 14:10, Jeff Johnson pronounced:
>
>
>>Allen Wayne Best wrote:
>>
>>
>>>hi all:
>>>
>>>can anyone affirm that!
'rpm
--root /mnt/sysimage' will do what i think the
>>>man page is saying it will do: install the rpms in the system directories
>>>starting at /mnt/sysimage and not in the current /.
>>>
>>>
>>Yes, that's --root behavior.
>>
>>
>>
>>>a rh9 installation went south, way south, after appling all the current
>>>rh9 updates. now is get a segmentation fault when i do a chroot
>>>/mnt/sysimage, and get same when i try to boot the system. as by one on
>>>information, the same was happening during ( and not before) the rpm -Fuh
>>>of the the updates.
>>>
>>>any input is greatly appreciated. i really don't want to hose the system
>>>worse! :)
>>>
>>>
>>Anaconda might be easiest. Rename /var/lib/rpm, and do minimal install,
>>but don't remake a file system
>>!
on your
existing partitions. Once you're booted, replace /var/lib/rpm,
>>and use -Va to figger what's
>>changed.
>>
>>73 de Jeff
>>
>>
>
>if i understand you correctly,
>
>mv /var/lib/rpm /var/lib/old.rpm (the entire directory!)
>install as if fresh install
>install the least necessary
>don't install a file system
>(this part i am not following you on... could you explain a bit more??)
>
>
If you run mkfs on a partition, everything will be lost.
Not running mkfs will replace files from the minimal set of pkgs,
leaving everything
else intact.
If you don't understand this, you're probably better off installing
manually using --root.
That will work too, with fewer side effects and surprises.
73 de Jeff
> ATTACHMENT part 3.5 message/rfc822
From: Allen Wayne Best
To:
rpm-list@redhat.com, Jeff Johnson
Subject: Re: rpm --root
Date: Sun, 21 Sep 2003 19:50:03 -0700
Jeff:
thanks so much for your assistance. I, or rather, the computer, is back up and
running. i did an update and told anaconda tht i wanted to review/select the
programs to install. this may have not worked had i not had
kernel-2.4.20-6Boot installed. i am now chasing down the other problems i had
before the install of the security updates. needless to say, i am again a
happy geek with bugs in my smile, thanks to your kind suggestions.
On Sunday 21 September 2003 14:35, Jeff Johnson pronounced:
> Allen Wayne Best wrote:
> >On Sunday 21 September 2003 14:10, Jeff Johnson pronounced:
> >>Allen Wayne Best wrote:
> >>>hi all:
> >>>
> >>>can anyone affirm that 'rpm --root /mnt/sysimage' will do what i think
> >>> the man page is sayin!
g it will
do: install the rpms in the system
> >>> directories starting at /mnt/sysimage and not in the current /.
> >>
> >>Yes, that's --root behavior.
> >>
> >>>a rh9 installation went south, way south, after appling all the current
> >>>rh9 updates. now is get a segmentation fault when i do a chroot
> >>>/mnt/sysimage, and get same when i try to boot the system. as by one on
> >>>information, the same was happening during ( and not before) the rpm
> >>> -Fuh of the the updates.
> >>>
> >>>any input is greatly appreciated. i really don't want to hose the system
> >>>worse! :)
> >>
> >>Anaconda might be easiest. Rename /var/lib/rpm, and do minimal install,
> >>but don't remake a file system
> >>on your existing partitions. Once you're booted, replace /var/lib/rpm,
!
>
>>and use -Va to figger what's
> >>changed.
> >>
> >>73 de Jeff
> >
> >if i understand you correctly,
> >
> >mv /var/lib/rpm /var/lib/old.rpm (the entire directory!)
> >install as if fresh install
> >install the least necessary
> >don't install a file system
> >(this part i am not following you on... could you explain a bit more??)
>
> If you run mkfs on a partition, everything will be lost.
>
> Not running mkfs will replace files from the minimal set of pkgs,
> leaving everything
> else intact.
>
> If you don't understand this, you're probably better off installing
> manually using --root.
>
> That will work too, with fewer side effects and surprises.
>
> 73 de Jeff
>
>
> _______________________________________________
> Rpm-list mailing list
>
Rpm-list@redhat.com
> https://www.redhat.com/mailman/listinfo/rpm-list
--
regards,
allen wayne best, esq
"your friendly neighborhood rambler owner"
"my rambler will go from 0 to 105"
Current date: 58:46:19::263:2003
The only thing that experience teaches us is that experience teaches us
nothing.
-- Andre Maurois (Emile Herzog)
> ATTACHMENT part 3.6 message/rfc822
Date: Mon, 22 Sep 2003 02:59:58 -0700 (PDT)
From: Valery Reznic
Subject: %preun and %postun does not run
To: rpm-list@redhat.com
Good day.
I wrote a following simple specfile:
Name: Test
Version: 1.0.0
Revision: 1
License: Dummy
Group: Dummy
Summary: Test
%description
test
%files
%pre
echo pre
%post
echo post
%preun
echo preun
%postun
echo postun
and another one - exactly same, but with revision 2
Now I do
following:
1) rpm -U test-1.0.0-1.i386.rpm
Output:
pre
post
(Expected)
2) rpm -e test
Output:
preun
postun
(Expected)
3) rpm -U test-1.0.0-1.i386.rpm
Output:
pre
post
(Expected)
4) rpm -U --force test-1.0.0-1.i386.rpm
Output:
pre
post
pre/post uninstall scripts are not running !
5) rpm -U --force test-1.0.0-2.i386.rpm
Output:
pre
post
preun
postun
(Expected)
6) rpm -U --force test-1.0.0-1.i386.rpm
Output:
pre
post
preun
postun
(Expected)
I.e, when i try upgrade package to the package with
same version and release pre/post uninstall scripts
are not run (and pre/post install are run).
I don't this behavour documentated.
Is it a normal or it's a bug ?
Is it a way to force rpm to run pre/post uninstall
scripts in these case too ?
It was tested on rpm-4.0.3 (RedHat 7.2) and
rpm-4.2 (RedHat
9)
Valery
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
> ATTACHMENT part 3.7 message/rfc822
Date: Mon, 22 Sep 2003 16:29:10 +0100 (BST)
From: Steve Hill
To: rpm-list@redhat.com
Subject: Help with rpmlib
I am trying to write a program (in C) to sort out the dependencies of
SRPMs so I can build an entire distribution from SRPMs (in a chroot(),
starting with only the basics such as compiler and a few basic libs).
The problem I'm having is that rpmlib seems to be very undocumented - I
need to get the requires and provides list from each RPM, but I can't see
how to do this. Looking at the RPM source it seems to use functions such
as rpmdsNew, rpmdsInit and rpmdsNext - none of which seem to be documented
at all (I'm using the online API docs at rpm.org, the Maximum!
RPM book
and
the Redhat RPM Guide book).
How would I go about doing this? (or is there a better way?)
--
- Steve Hill
Senior Software Developer Email: steve@navaho.co.uk
Navaho Technologies Ltd. Tel: +44-870-7034015
... Alcohol and calculus don't mix - Don't drink and derive! ...
_______________________________________________
Rpm-list mailing list
Rpm-list@redhat.com
https://www.redhat.com/mailman/listinfo/rpm-list