SCIENTIFIC-LINUX-USERS Archives

July 2014

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV
Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
Re: rpm problem
From:
Nico Kadel-Garcia <[log in to unmask]>
Reply To:
Nico Kadel-Garcia <[log in to unmask]>
Date:
Fri, 25 Jul 2014 06:39:25 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (59 lines) 
On Thu, Jul 24, 2014 at 3:00 PM, ToddAndMargo <[log in to unmask]> wrote:
> On 07/23/2014 09:05 AM, Mark Stodola wrote:
>>
>> On 07/23/2014 10:43 AM, ToddAndMargo wrote:
>>>
>>> Hi All,
>>>
>>> I am having trouble installing the PDF Studio RPM.
>>>
>>> https://www.dropbox.com/s/slgrnolcsktaezz/PDFStudio_v9_0_2_linux.rpm
>>>
>>> # cat /etc/redhat-release
>>> Scientific Linux release 6.5 (Carbon)
>>>
>>> # uname -r
>>> 2.6.32-431.20.3.el6.x86_64
>>>
>>> # rpm -ivh PDFStudio_v9_0_2_linux.rpm
>>> Preparing... ########################################### [100%]
>>>      1:PDFStudio ########################################### [100%]
>>> error: unpacking of archive failed on file .pdfstudio9/:
>>> cpio: Archive file not in header
>>>
>>> Any way to fix this?


By using s cluebat on the package author. It's.... not a good package.
It's misnamed, it drops everything in a relative directory, and there
is no license. This is not a safe thing to install anywhere.

>>> Many thanks,
>>> -T
>>
>>
>> I would first check the integrity of the file.
>> I downloaded it here (not installed it, as I don't have SL6.5).
>> It unpacked fine though using "rpm2cpio filename.rpm | cpio -idmv"
>> I have the following checksum on it:
>>
>> MD5: f39d0ef9c4fd74cbfcbffa37f0ee18f2  PDFStudio_v9_0_2_linux.rpm
>> SHA1: 2e69d1b564cfebcac5cba9244bd04f64cedc959f  PDFStudio_v9_0_2_linux.rpm
>>
>> It has an odd directory structure, it seems to put everything in
>> /pdfstudio9.

No, it puts it all in 'pdfstudio9'. Like I said, the author of the RPM
needs a cluebat applied.

I'd suggest "mkdir /opt", then run 'rpm2cpio" there to get the
directory contents. But I'd sooner stick my hand in a blender than
trust this thing, gods alone know what they put in the RPM
pre-scripts. and post-scripts.

In general, RPM's should not be trusted without the relevant SRPM
available, and both signed by a trusted developer or company. RPM's
are installed as root, and can ruin or erase importent system
components and configurations by accident or by malice. One may as
well open an attached zip file on a Windows box.

ATOM RSS1 RSS2