Package Details: gazebo 11.14.0-2

Git Clone URL: https://aur.archlinux.org/gazebo.git (read-only, click to copy)
Package Base: gazebo
Description: A multi-robot simulator for outdoor environments
Upstream URL: https://classic.gazebosim.org/
Licenses: Apache
Submitter: None
Maintainer: acxz
Last Packager: acxz
Votes: 35
Popularity: 0.000134
First Submitted: 2008-10-18 22:59 (UTC)
Last Updated: 2023-12-11 14:35 (UTC)

Pinned Comments

billypilgrim commented on 2022-05-09 16:04 (UTC)

Development is on Github: https://github.com/acxz/gazebo-arch Please open issues and PRs there instead of commenting.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 12 .. 33 Next › Last »

julianoes commented on 2021-04-19 10:18 (UTC) (edited on 2021-04-19 10:19 (UTC) by julianoes)

I ran into this problem:

[  0%] Generating gzprop.1
/usr/lib/ruby/3.0.0/rubygems.rb:281:in `find_spec_for_exe': can't find gem ronn (>= 0.a) with executable ronn (Gem::GemNotFoundException)
    from /usr/lib/ruby/3.0.0/rubygems.rb:300:in `activate_bin_path'
    from /usr/bin/ronn:23:in `<main>'

...

-- Set runtime path of "/home/julianoes/.cache/yay/gazebo/pkg/gazebo/usr/bin/gzserver-11.4.0" to ""
CMake Error at gazebo/cmake_install.cmake:79 (file):
  file INSTALL cannot find
  "/home/julianoes/.cache/yay/gazebo/src/gazebo-11.4.0/build/gazebo/gzserver.1.gz":
  No such file or directory.
Call Stack (most recent call first):
  cmake_install.cmake:100 (include)

I could workaround this by installing the required ronn gem:

gem install ronn

pandaero commented on 2021-03-29 17:21 (UTC)

I installed gazebo properly, but when I ran the gazebo command, the following error showed up: libcdt.so.5:cannot open shared object file: No such file or directory

It turns out I did not have the libcdt library under /usr/lib64/

I searched for a package that provided that, and I installed graphviz

Directly after installing this, I could run gazebo properly. I think it should be listed as a dependency.

billypilgrim commented on 2020-12-11 12:05 (UTC)

Ahh, mystery solved. Nvm then :-)

Nim65s commented on 2020-12-11 09:55 (UTC)

If one tries to install sdformat-9 before upgrading sdformat to 10, they conflict. Otherwise, if installed / updated in the right order, that's OK :)

acxz commented on 2020-12-11 00:45 (UTC)

@acxz Ah my bad. It does conflict for sdformat though (I tested it), so it would be good to set the conflicts array for that package.

Really? I have both sdformat-9 and sdformat installed. Can you post the error message you get?

billypilgrim commented on 2020-12-10 22:36 (UTC)

@acxz Ah my bad. It does conflict for sdformat though (I tested it), so it would be good to set the conflicts array for that package.

acxz commented on 2020-12-10 17:37 (UTC)

@billypilgrim I think the provides field should be populated but conflicts should remain empty as the two versions shouldn't be conflicting each other. Ignition libraries version their installation directories.

billypilgrim commented on 2020-12-10 11:04 (UTC)

nxxxx: Thanks! That's super helpful :-). Otherwise I'd have ended up doing it myself.

One small suggestion: if you add the original package's name to the provides=() and conflicts=() arrays in the PKGBUILD, it makes it easier for people to upgrade (because pacman knows to e.g. uninstall sdformat before installing sdformat-9).

You can do it like this: provides=(sdformat=$pkgver) conflicts=(sdformat)

Homalozoa commented on 2020-12-10 07:38 (UTC) (edited on 2020-12-10 08:31 (UTC) by Homalozoa)

I found it would configure failed because of the version of packages :sdformat, ignition-msgs, ignition-transport and ignition-fuel_tools. So I uploaded sdformat-9(https://aur.archlinux.org/packages/sdformat-9/), ignition-msgs-5(https://aur.archlinux.org/packages/ignition-msgs-5/), ignition-transport-8(https://aur.archlinux.org/packages/ignition-transport-8/) and ignition-fuel_tools-4(https://aur.archlinux.org/packages/ignition-fuel_tools-4/) to resolve the problem temporarily.

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 12 .. 33 Next › Last »