Subject: | |
From: | |
Reply To: | |
Date: | Fri, 22 Jun 2007 06:29:34 +0800 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Troy Dawson wrote:
> John Summerfield wrote:
>> Troy Dawson wrote:
>>> John Summerfield wrote:
>>>> John Summerfield wrote:
>>>>> Paul A. Rombouts wrote:
>>>>>> John Summerfield wrote:
>>>>>> [snip]
>>>>>>> My immediate problem is my preferred browser is Mozilla - er -
>>>>>>> Seamonkey. I couldn't find it with yum, nor with Google, nor can
>>>>>>> I see that anyone's asked about it for SL5.
>>>>>>>
>>>>>>> Does anyone have it? or should I just build it myself? Might have
>>>>>>> a src.rpm around here someplace....
>>>>>>>
>>>>>>
>>>>>> I had the same problem and I actually asked about seamonkey for
>>>>>> SL5 on
>>>>>> this list before you did, John.
>>>>>>
>>>>>> I recommend building this src rpm from releases.mozilla.org:
>>>>>> http://releases.mozilla.org/pub/mozilla.org/seamonkey/releases/1.1.2/contrib/FC_RPMS/source/seamonkey-1.1.2-1.src.rpm
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Hmm. A mere 34 mbytes. Okay, I pull bigger things through my modem.
>>>>> Thanks Paul.
>>>>
>>>> Er:
>>>> 15:05 [summer@numbat ~]$ sudo rpm -Fvh
>>>> /usr/src/redhat/RPMS/i386/seamonkey-1.1.2-1.i386.rpm /usr/src/re
>>>>
>>>> dhat/RPMS/i386/seamonkey-mail-1.1.2-1.i386.rpm
>>>> /usr/src/redhat/RPMS/i386/seamonkey-chat-1.1.2-1.i386.rp
>>>> m /usr/src/redhat/RPMS/i386/seamonkey-js-debugger-1.1.2-1.i386.rpm
>>>> /usr/src/redhat/RPMS/i386/seamonkey- dom-inspector-1.1.2-1.i386.rpm
>>>> Password:
>>>> Preparing...
>>>> ########################################### [100%]
>>>> 1:seamonkey
>>>> ########################################### [ 50%]
>>>> error: %post(seamonkey-1.1.2-1.i386) scriptlet failed, exit status 255
>>>> 2:seamonkey-mail
>>>> ########################################### [100%]
>>>> error: %post(seamonkey-mail-1.1.2-1.i386) scriptlet failed, exit
>>>> status 255
>>>> error: %preun(seamonkey-1.0.8-0.2.el4.i386) scriptlet failed, exit
>>>> status 255
>>>> 15:05 [summer@numbat ~]$
>>>>
>>>>
>>>> Is there a good way to see what the problem is?
>>>>
>>>
>>> rpm -qp --scripts /usr/src/redhat/RPMS/i386/seamonkey-1.1.2-1.i386.rpm
>>> rpm -qp --scripts
>>> /usr/src/redhat/RPMS/i386/seamonkey-mail-1.1.2-1.i386.rpm
>>>
>>> Note: You don't have to be root to look at the scripts.
>>
>> That tells me why I can't see why some of them didn't work. But take
>> this for example:
>> preuninstall scriptlet (using /bin/sh):
>> # is a final removal?
>> if [ "$1" == "0" ]; then
>> /bin/rm -rf /usr/lib/mozilla-seamonkey-1.0.8/chrome/overlayinfo
>> /bin/rm -f /usr/lib/mozilla-seamonkey-1.0.8/chrome/*.rdf
>> fi
>>
>> (it appears twice).
>> That should not produce any error unless something goes wrong and the
>> only thing I can think of is that root cannot delete those files.
>>
>
> If you are doing an upgrade, then the
>
> if [ "$1" == "0" ]; then
>
> fi
>
> will see that you are doing an upgrade and not run the code in there.
> Why this is failling ... I'm not positive.
I couldn't see why either path might fail, and I can't see what exit
code 255 might mean.
Since the version number's changing, stuff in there gets orphaned. I have:
06:23 [summer@Numbat ~]$ ls -dl /usr/lib/mozilla-*
drwxr-xr-x 11 root 4096 Jun 18 19:37 /usr/lib/mozilla-seamonkey-1.0.8
06:27 [summer@Numbat ~]$ rpm -q seamonkey
seamonkey-1.0.8-0.2.el4
seamonkey-1.1.2-1
06:27 [summer@Numbat ~]$
and on a CentOS4 box where I've been thoroughly conventional:
06:29 [summer@sysadmin ~]$ ls -dl /usr/lib/mozilla-*
drwxr-xr-x 2 4096 Sep 16 2006 /usr/lib/mozilla-seamonkey-1.0.3
drwxr-xr-x 3 4096 Dec 3 2006 /usr/lib/mozilla-seamonkey-1.0.5
drwxr-xr-x 3 4096 Jan 18 12:50 /usr/lib/mozilla-seamonkey-1.0.6
drwxr-xr-x 11 4096 Jun 21 15:31 /usr/lib/mozilla-seamonkey-1.0.7
06:29 [summer@sysadmin ~]$ rpm -q seamonkey
seamonkey-1.0.7-0.1.el4.centos4
06:30 [summer@sysadmin ~]$
--
Cheers
John
-- spambait
[log in to unmask] [log in to unmask]
Please do not reply off-list
|
|
|