On 07/24/2014 12:37 PM, Mark Stodola wrote:
> On 07/24/2014 02:30 PM, ToddAndMargo wrote:
>> On 07/24/2014 12:29 PM, Mark Stodola wrote:
>>> On 07/24/2014 02:19 PM, ToddAndMargo wrote:
>>>> On 07/24/2014 12:17 PM, Mark Stodola wrote:
>>>>> On 07/24/2014 02:00 PM, ToddAndMargo 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?
>>>>>>>>
>>>>>>>> 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.
>>>>>>>
>>>>>>> -Mark
>>>>>>>
>>>>>>
>>>>>>
>>>>>> Hi Mark,
>>>>>>
>>>>>> I get your same md5sum and I am able to to do the rpm2cpio
>>>>>> thing as well. But, still get the cpio error when trying
>>>>>> to install. Rats!
>>>>>>
>>>>>> -T
>>>>>
>>>>> Well, if the cpio works, extract it to / and run the postinstall
>>>>> portion
>>>>> from
>>>>> rpm -qp --scripts filename.rpm
>>>>>
>>>>> It looks like they are owned by 'root.root' in the rpm.
>>>>>
>>>>> Have you tried getting it directly from qoppa.com?
>>>>
>>>> "We are sorry but as previously mentioned we do not support
>>>> the RPM installer. We have other users that have been able
>>>> to successfully install using the RPM so I'm not sure
>>>> what that error could be."
>>>>
>>>>>
>>>>> -Mark
>>>>>
>>>>
>>>>
>>>
>>> Well, if it works by hand, it shouldn't be too hard to recreate the RPM
>>> from what you have. I would take a whack at it, but I'm already behind
>>> on preparing for extended travel. Someone else here could help with the
>>> finer details if you need.
>>>
>>> -Mark
>>>
>>
>> is [Desktop Entry] part of the post install script?
>
> Yes, if you look close, the lines right above that call xdg-open, and
> are echoing the [Desktop Entry] lines into a file (using the >>). It is
> basically creating a desktop icon entry in a common location.
>
> /bin/echo -e "#!/usr/bin/env xdg-open
> [Desktop Entry]
> Type=Application
> Name=PDF Studio 9
> Exec=/bin/sh \"$I4J_INSTALL_LOCATION/pdfstudio9\"
> Icon=$I4J_INSTALL_LOCATION/.install4j/pdfstudio9.png
> " >> "$I4J_INSTALL_LOCATION/pdfstudio9.desktop"
>
> That is all "one line" of a command essentially.
> It looks like the script just makes a few symlinks and ensures the newly
> created desktop icon is executable.
> The rest is just unpacking jar files, which I'm not as familiar with as
> I haven't touched java in close to a decade. It all looks straight
> forward.
>
> -Mark
>
Just for the fun of it, I ran the pdfstudio file directly from inside
the directory, and it runs.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Computers are like air conditioners.
They malfunction when you open windows
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
