trusty ppa building from bazaar

Asked by Jörg Frings-Fürst

Hi,

since some days I got when build trusty-packages this errors:

###
dpkg-source: info: using options from recipe-{debupstream}-0~{revno}/debian/source/options: --extend-diff-ignore=(^|/)(config\.sub|config\.guess|config\.status|config\.log|Makefile|\.bzr/)$

dpkg-source: error: can't build with source format '3.0 (native)': native package version may not have a revision

dpkg-buildpackage: error: dpkg-source -i -I -b recipe-{debupstream}-0~{revno} gave error exit status 255
###

In debian/source/format stands 3.0 (quilt). And from teh same source the build of Precise, Quantal, Raring and Saucy
works fine.

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
William Grant (wgrant) said :
#1

bzr-builder will convert a 3.0 (quilt) package to 3.0 (native) if it's unable to recreate the upstream tarball using pristine-tar. This conversion previously worked fine in most cases, but dpkg in trusty recently started rejecting native packages with non-native versions, causing converted source packages with versions containing hyphens to fail to build.

You'll need to either switch to a native version string, or provide the necessary pristine-tar data in the branch, probably using 'bzr import-upstream' as described at <http://doc.bazaar.canonical.com/plugins/en/builddeb-plugin.html>.

Revision history for this message
Timmie (timmie) said :
#2

Hello,
I have the same isso with a launchpad recipe process:

https://code.launchpad.net/~pythonxy/+recipe/spyderlib-daily-via-github
https://code.launchpad.net/~pythonxy/+archive/pythonxy-devel/+recipebuild/624654/+files/buildlog.txt.gz

"
dpkg-source: error: can't build with source format '3.0 (native)': native package version may not have a revision
"

What can I do to keep the process going?

Kind regards.

Revision history for this message
Jörg Frings-Fürst (jff-de) said :
#3

Hello,

why bzr-builder will be convert from the newer quilt to the older native version:

I don't understand.

And a parameter description also does not help.

Revision history for this message
William Grant (wgrant) said :
#4

My first comment describes the situation, and how you can recover from it. Is there some part of it that you don't understand?

Revision history for this message
Timmie (timmie) said :
#5

@wgrant

May I ask:

Why do the PPA builder work for all Ubuntus except for Trusty?

Any how can I change my rules in order to let the Trusty wor again?

I also found this:
"

If you convert it to 3.0 (native), then the quilt patches won't be applied.

You could apply them buy using dh $@ --with quilt, if the package uses dh, or manually calling the patch and unpatch commands during the build.
"
http://askubuntu.com/a/213670

Revision history for this message
William Grant (wgrant) said :
#6

As I said in my first comment: "This conversion previously worked fine in most cases, but dpkg in trusty recently started rejecting native packages with non-native versions, causing converted source packages with versions containing hyphens to fail to build."

You cannot fix it with a change to debian/rules. The problem is that the most recent entry in debian/changelog has a hyphen in the version, which signifies that there is an upstream tarball (orig.tar.*). You need to remove the hyphen to make it a native package, or tell Launchpad how to construct the upstream tarball. bzr-builder uses pristine-tar to reconstruct the orig.tar.* from the branch; see http://doc.bazaar.canonical.com/plugins/en/builddeb-plugin.html#import-upstream for how to add the necessary metadata to your branch.

Can you help with this problem?

Provide an answer of your own, or ask Jörg Frings-Fürst for more information if necessary.

To post a message you must log in.