Launchpad itself

Depends: cmake (>= 3.18) but it is not going to be installed

Asked by Yunmei Li

I try to build a package use pbuilder, and then upload to Launchpad PPA.
My package depend cmake>=3.18.

And wherever i building my package with pbuilder or Launchpad PPA, it always gets the same error:
pbuilder-satisfydepends-dummy : Depends: cmake (>= 3.18) but it is not going to be installed.

Error details can be found:
https://launchpadlibrarian.net/575262803/buildlog_ubuntu-bionic-amd64.milvus_2.0.0-rc8-2_BUILDING.txt.gz

How should I solve the problem of depending on cmake>=3.18.

BTW, i use bionic dist.

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Colin Watson
Solved:
Last query:
Last reply:
Revision history for this message
Colin Watson (cjwatson) said : 		#1

You need to actually provide cmake >= 3.18 somehow. Simply depending on it doesn't cause it to come into existence (Launchpad can't for example assume that the version from hirsute is going to work on bionic).

Your options here are either to build a backport of a new enough version of cmake to bionic (I don't know how complicated that will be), or to modify your package's build system to work with the version of cmake in bionic.

Revision history for this message
Yunmei Li (milvusdb) said : 		#2

Thanks!

And can you share a few more details how to do build a backport of a new version cmake to bionic? Or is there a related reference tutorial？

Revision history for this message
Yunmei Li (milvusdb) said (last edit ): 		#3

Now I copy a package cmake3.18 to my PPA, but I don’t know how to make it a dependency of the package I’m building.

Revision history for this message
Best Colin Watson (cjwatson) said : 		#4

You can try starting by using the backportpackage tool from ubuntu-dev-tools, which works in trivial cases. If it gets more complicated than that, then backporting is generally a creative activity for which it's hard to write a tutorial; you'll need to look at whatever errors you get and tackle them one by one.

Revision history for this message
Yunmei Li (milvusdb) said : 		#5

Thanks Colin Watson, that solved my question.