On 20 March 2013 20:26, Wido den Hollander <wido@widodh.nl> wrote:
>
>
> On 03/20/2013 12:19 PM, Prasanna Santhanam wrote:
>>
>> On Wed, Mar 13, 2013 at 02:19:57PM +0530, Prasanna Santhanam wrote:
>>>
>>> On Wed, Mar 13, 2013 at 01:45:46PM +0530, prasanna wrote:
>>>>
>>>> On 13 March 2013 12:56, Pradeep Soundararajan
>>>> <pradeep.soundararajan@citrix.com> wrote:
>>>>>
>>>>> David,
>>>>>
>>>>> I did not come across this issue "cpio: Bad magic" even before or after
>>>>> your doc changes. I am doing the build and packaging daily on both 4.1
and
>>>>> master.
>>>>>
>>>>> I suspect it could be the setup issue.
>>>>>
>>>>
>>>> Can you tell us the following from your build machine:
>>>> 1) rpmbuild version
>>>> 2) cat /etc/redhat-release
>>>> 3) cpio version?
>>>>
>>>> I'll hook you up with the machines so you can take a look. I can't
>>>> figure this one out.
>>>
>>>
>>> Nevermind, it looks like this magically fixed itself. I uninstalled
>>> the tomcat6 installed on the build node and installed the one from the
>>> repos and it worked fine.
>>>
>>> awful error message from cpio.
>>>
>>
>> This broke again couple of days back with the same cpio error. It's
>> the same issue and tomcat looks to be in order. Someone with more
>> packaging knowledge will have to take a look at this.
>>
>
> I just fixed this issue in the 4.1 branch, it should be working now again.
>
> This got lost during the merge from master to 4.1 with the packaging stuff.
> It's resolved in the 4.1 branch now but was already fixed in master.
>
Wrong subject actually : this is not related to the package fix you
made for adjusting jna classpath. There's an issue on the build
environment that causes the rpmbuild to fail with an obscure error
saying cpio : Bad magic. I was referring to that.