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

blacklist a few packages on kinetic #38

Merged
merged 1 commit into from Apr 21, 2016
Merged

Conversation

jacquelinekay
Copy link
Contributor

@jacquelinekay jacquelinekay commented Apr 20, 2016

I am blacklisting packages that are failing to build for ARM on the Kinetic build farm that were also disabled for Jade or Indigo.

Maintainers, please contact us in the future if you have a solution for the failing arm builds and would like to reenable them on the farm. Thanks.

@mani-monaj (ardrone_autonomy)
@ahornung (octovis)
@kmhallen (ueye)

@kmhallen
Copy link

For the ueye package, only the arm64 build is failing because it can't detect the architecture and the manufacture doesn't provide binaries for arm64. The armhf build should be fine. I guess blacklisting works.

@jacquelinekay
Copy link
Contributor Author

It's a bit confusing, the configuration file for both armhf and arm64 files is called "release-armhf-build.yaml". So this PR will blacklist the package for both armhf and arm64.

@tfoote should it be renamed release-arm-build.yaml?

@tfoote
Copy link
Member

tfoote commented Apr 21, 2016

+1

It's renamed in the production branch, this should be cherry picked there too.

@jacquelinekay jacquelinekay merged commit 65d44e9 into master Apr 21, 2016
@jacquelinekay jacquelinekay deleted the kinetic_arm_blacklist branch April 21, 2016 00:06
@jacquelinekay
Copy link
Contributor Author

hmm, how would you cherry-pick the commit into production if the file has a different name? The only way I know how to that quickly would be to copy the changes into the file--you can do it if you have a better way

@tfoote
Copy link
Member

tfoote commented Apr 21, 2016

It was a rename so git might be able to track it. We should probably rename this branch to to keep it parallel.

@ahornung
Copy link

Looks like the Qt4-version of libqglviewer is missing for armhf: http://repositories.ros.org/ubuntu/building/pool/main/libq/libqglviewer/

Don't think it's a problem to blacklist octovis for armh, since it's just a visualization tool.

@jacquelinekay
Copy link
Contributor Author

That's fine with me.

nuclearsandwich pushed a commit to nuclearsandwich/ros_buildfarm_config that referenced this pull request Sep 11, 2019
Signed-off-by: Scott K Logan <logans@cottsay.net>
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

Successfully merging this pull request may close these issues.

None yet

4 participants