Sean
try to "export VERSION=3.0" before building.
J.
On 10/03/16 19:26, Filip Pytloun wrote:
Hello,
What you see on that Launchpad page are source packages from which
binary packages are made (one source package can produce multiple binary
packages).
If you click on "View package details" and expand, eg. `contrail`. You
will see all binary packages built from contrail source.
https://launchpad.net/~opencontrail/+archive/ubuntu/r2.20/+packages
or direct link:
https://launchpad.net/~opencontrail/+archive/ubuntu/r2.20/+sourcepub/5741522/+listing-archive-extra
For a little intro on Debian packaging, check my slides here:
https://fpy.cz/pub/slides/debian-packaging/
..so your package list is just fine :-)
We are fixing versioning in our builds so the versions are more
meaningful, eg.:
contrail - 3.0+0~1456178959.8~1.5f0acaa
<version>+<revision>~<timestamp>.<build_number>~1.<git_revision>
https://github.com/tcpcloud/jenkins-jobs/blob/master/contrail-build/contrail_build_source.sh#L83
Yes, you can use our PPA in the similar way as described in the link.
Or just use already built contrail packages that we maintain.
Filip
On 2016/03/10 18:11, Winn, Sean wrote:
Hi Filip,
Thanks for the response.
When I build packages (using Œmake -f packages.make all¹) I end up with an
array of packages that appear to be for the wrong version, and I end up
with these same packages regardless of the branch I select during the repo
init phase:
contrail-analytics_1.1master~acf4c45_amd64.deb
contrail-analytics-dbg_1.1master~acf4c45_amd64.deb
contrail-config_1.1master~acf4c45_amd64.deb
contrail-config-openstack_1.1master~acf4c45_amd64.deb
contrail-control_1.1master~acf4c45_amd64.deb
contrail-control-dbg_1.1master~acf4c45_amd64.deb
contrail-dns_1.1master~acf4c45_amd64.deb
contrail-docs_1.1master~acf4c45_amd64.deb
contrail-lib_1.1master~acf4c45_amd64.deb
contrail-nodemgr_1.1master~acf4c45_amd64.deb
contrail-nova-driver_1.1master~acf4c45_amd64.deb
contrail-utils_1.1master~acf4c45_amd64.deb
contrail-vrouter-agent_1.1master~acf4c45_amd64.deb
contrail-vrouter-agent-dbg_1.1master~acf4c45_amd64.deb
contrail-vrouter-dkms_1.1master~acf4c45_amd64.deb
contrail-vrouter-source_1.1master~acf4c45_amd64.deb
contrail-vrouter-utils_1.1master~acf4c45_amd64.deb
contrail-web-controller_1.1master~acf4c45_all.deb
contrail-web-core_1.1master~acf4c45_amd64.deb
ifmap-server_0.3.2-1contrail2_all.deb
python-contrail_1.1master~acf4c45_amd64.deb
python-contrail-vrouter-api_1.1master~acf4c45_amd64.deb
python-opencontrail-vrouter-netns_1.1master~acf4c45_amd64.deb
According to the 2.2 PPA, I should end up with just 4 packages.
https://launchpad.net/~opencontrail/+archive/ubuntu/r2.20
To be clear - if I wanted to build using your PPA, I just follow the same
steps (http://juniper.github.io/contrail-vnc/README.html) but instead of
using the contrail ppa in step 4, use yours?
On 3/10/16, 1:04 AM, "Filip Pytloun" <[email protected]> wrote:
Hello Sean,
opencontrail build was and still is a little bit tricky.
We build dependencies on our own, all of them (and more) are available
in our Launchpad repository [1]
I believe most of these dependencies will be available in upcomming
Ubuntu 16.04 (Xenial) so it won't be necessary to use 3rd party repo for
them.
R3.0 packages are ready here [2]
And should be working fine with juno, kilo, liberty (but we are testing
only kilo and liberty at the moment).
_______________________________________________
Dev mailing list
[email protected]
http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org
_______________________________________________
Dev mailing list
[email protected]
http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org
