Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build new debian packages from our fork #26

Open
scpeters opened this issue May 18, 2021 · 7 comments
Open

Build new debian packages from our fork #26

scpeters opened this issue May 18, 2021 · 7 comments

Comments

@scpeters
Copy link
Collaborator

Upstream dart has made a 6.10.0 release, but there is an API difference that causes ignition-physics to only build against our fork and not the upstream release. We added the missing upstream API to this fork in #23 but need new debs in order to start using the upstream API ( gazebosim/gz-physics#249).

In addition to #23, we have merged several other changes since the last debian packages were built:

cc @nkoenig @azeey @j-rivero

@azeey
Copy link
Collaborator

azeey commented May 18, 2021

I believe most of those changes do not affect behavior. #19 affects behavior by introducing joint velocity constraints, but I think that's a safe change (see #19 (review))

@scpeters
Copy link
Collaborator Author

@j-rivero is it possible to make a prerelease of the dart debian packages from the tip of our release-6.10 branch?

@j-rivero
Copy link

@j-rivero is it possible to make a prerelease of the dart debian packages from the tip of our release-6.10 branch?

Yes. Working on it.

@j-rivero
Copy link

@j-rivero
Copy link

I've renamed the lib package names to match soname (include 6.10 in names) following debian guidelines. Focal and Bionic packages are available into the PPA. I need to fix arm failures and import the packages to prerelease if that helps testing.

@j-rivero
Copy link

Packages have been imported to prerelease repository using #30 instructions. https://build.osrfoundation.org/job/reprepro_importer/41/

@chapulina
Copy link

What's the completion criteria for this issue? It's my understanding that we've made a few releases since May, right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants