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

Release 1.0.3 into ubuntu bionic #129

Closed
jschleicher opened this issue Jul 8, 2019 · 9 comments
Closed

Release 1.0.3 into ubuntu bionic #129

jschleicher opened this issue Jul 8, 2019 · 9 comments

Comments

@jschleicher
Copy link

Please release version 1.0.3 also into bionic-updates (currently in disco)

Since this solves the (very popular) issue with RViz ros-visualization/rviz#1249 (comment), also discussed here in #119.

I can confirm, that the rendering in RViz is fixed with a source build of urdfdom_headers version 1.0.3 and urdfdom version 1.0.3 on my melodic installation (Ubuntu bionic).

@scpeters
Copy link
Contributor

scpeters commented Jul 8, 2019

cc @j-rivero

@jschleicher
Copy link
Author

@j-rivero any updates / comments?

@j-rivero
Copy link
Contributor

j-rivero commented Aug 6, 2019

To get the update into Bionic we will need to create a SRU issue: https://wiki.ubuntu.com/StableReleaseUpdates . The process needs a good bunch of documentation, I can deal with most of it but it would be good if we can have a test use case (better if it does not need manual inspection, a Dockerfile could work well for this).

@gavanderhoorn
Copy link

@j-rivero: isn't this essentially the same issue as #119? That has a Dockerfile available that clearly exhibits the problem.

@j-rivero
Copy link
Contributor

j-rivero commented Aug 6, 2019

@j-rivero: isn't this essentially the same issue as #119? That has a Dockerfile available that clearly exhibits the problem.

I have no idea if we are speaking about the same bug or a different one. @jschleicher ?

@gavanderhoorn
Copy link

The first post by @jschleicher that started this issue references #119.

@j-rivero
Copy link
Contributor

j-rivero commented Aug 6, 2019

The first post by @jschleicher that started this issue references #119.

you are right, my bad sorry.

@gavanderhoorn
Copy link

So what's the status on #119? :)

@jschleicher
Copy link
Author

Thanks for looking into the release and I'm looking forward for a fixed package.

Closing here as duplicate of #119.

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