unable to sign source package

Re your 1st problem:
Your error happens during building of the source package and not during the signing stage.
Your build process changed the file xxx/commons-logging-1.0.4.jar (why did it change?) and changes to binary files can't get expressed as diff files.

Re your 2nd problem:
The build servers don't have access to the internet (on purpose). You can't download anything from the internet but has to ship it in your source package. In this case it would be better to check if that jar is perhaps already packaged and reuse that package (depend on it) instead of duplicating that file.

The error message:

>> dpkg-source: error: cannot represent change to xxx/commons-logging-1.0.4.jar: binary file contents changed.

occurs when *building* a source package, not when *signing* a source package.

It occurs because it is not permitted to add or change non-text files in the packaging part of a debian source package, because the packaging part is represented as a textual diff.

It is hard to give more detailed advice without seeing a copy of your attempted source packaging. I recommend making it available, ideally in version control - e.g. a Bazaar branch on Launchpad - and then asking for further help, either here or in the IRC channel #ubuntu-packaging on FreeNode.

Hi Michael,

Thanks for your prompt reply, really appreciate that. Your answer help me get a clear view of my issue.

Best Regards

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Michael Bienia
Sent: Thursday, August 16, 2012 7:41 PM
To: Chen, Wei D
Subject: Re: [Question #205972]: unable to sign source package

Your question #205972 on Launchpad itself changed:
https://answers.launchpad.net/launchpad/+question/205972

Michael Bienia posted a new comment:
Re your 1st problem:
Your error happens during building of the source package and not during the signing stage.
Your build process changed the file xxx/commons-logging-1.0.4.jar (why did it change?) and changes to binary files can't get expressed as diff files.

Re your 2nd problem:
The build servers don't have access to the internet (on purpose). You can't download anything from the internet but has to ship it in your source package. In this case it would be better to check if that jar is perhaps already packaged and reuse that package (depend on it) instead of duplicating that file.

--
You received this question notification because you asked the question.

Hi Max,

Thanks for your prompt reply, really appreciate your help on this issue.

Best Regards

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Max Bowsher
Sent: Thursday, August 16, 2012 7:46 PM
To: Chen, Wei D
Subject: Re: [Question #205972]: unable to sign source package

Your question #205972 on Launchpad itself changed:
https://answers.launchpad.net/launchpad/+question/205972

    Status: Open => Answered

Max Bowsher proposed the following answer:
The error message:

>> dpkg-source: error: cannot represent change to xxx/commons-
logging-1.0.4.jar: binary file contents changed.

occurs when *building* a source package, not when *signing* a source package.

It occurs because it is not permitted to add or change non-text files in the packaging part of a debian source package, because the packaging part is represented as a textual diff.

It is hard to give more detailed advice without seeing a copy of your attempted source packaging. I recommend making it available, ideally in version control - e.g. a Bazaar branch on Launchpad - and then asking for further help, either here or in the IRC channel #ubuntu-packaging on FreeNode.

--
If this answers your question, please go to the following page to let us know that it is solved:
https://answers.launchpad.net/launchpad/+question/205972/+confirm?answer_id=1

If you still need help, you can reply to this email or go to the following page to enter your feedback:
https://answers.launchpad.net/launchpad/+question/205972

You received this question notification because you asked the question.

Hi Michael,

Thanks for your prompt reply, really appreciate that. Your answer help me get a clear view of my issue.

Best Regards

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Michael Bienia
Sent: Thursday, August 16, 2012 7:41 PM
To: Chen, Wei D
Subject: Re: [Question #205972]: unable to sign source package

Your question #205972 on Launchpad itself changed:
https://answers.launchpad.net/launchpad/+question/205972

Michael Bienia posted a new comment:
Re your 1st problem:
Your error happens during building of the source package and not during the signing stage.
Your build process changed the file xxx/commons-logging-1.0.4.jar (why did it change?) and changes to binary files can't get expressed as diff files.

Re your 2nd problem:
The build servers don't have access to the internet (on purpose). You can't download anything from the internet but has to ship it in your source package. In this case it would be better to check if that jar is perhaps already packaged and reuse that package (depend on it) instead of duplicating that file.

--
You received this question notification because you asked the question.

has been answered above