Package Details: ignition-transport 7.0.0-6

Git Clone URL: (read-only)
Package Base: ignition-transport
Description: The transport library combines ZeroMQ with Protobufs to create a fast and efficient message passing system. Asynchronous message publication and subscription is provided along with service calls and discovery.
Upstream URL:
Licenses: Apache
Groups: development
Submitter: bchretien
Maintainer: acxz
Last Packager: acxz
Votes: 12
Popularity: 0.026739
First Submitted: 2016-01-30 02:51
Last Updated: 2019-06-30 21:40

Latest Comments

1 2 3 4 Next › Last »

acxz commented on 2019-11-27 01:03

@joaocandre Go ahead and clean build all ignition-* packages, specifically ignition-msgs. That should fix it.

joaocandre commented on 2019-11-26 23:38

Suddenly I am encountering errors compiling this, apparently to recent protobuf updates:

/usr/include/ignition/msgs4/ignition/msgs/actuators.pb.h:17:2: error: #error This file was generated by an older version of protoc which is
   17 | #error This file was generated by an older version of protoc which is
      |  ^~~~~
/usr/include/ignition/msgs4/ignition/msgs/actuators.pb.h:18:2: error: #error incompatible with your Protocol Buffer headers. Please
   18 | #error incompatible with your Protocol Buffer headers. Please
      |  ^~~~~
/usr/include/ignition/msgs4/ignition/msgs/actuators.pb.h:19:2: error: #error regenerate this file with a newer version of protoc.
   19 | #error regenerate this file with a newer version of protoc.
      |  ^~~~~

acxz commented on 2019-08-13 14:53

No no not your fault, I was lazy and had only posted the warning on the ros-melodic-desktop-full page since I didn't really think people would install this package on its own. I realize now that I should have posted the warning here as well.

EDIT: libpgm has been patched with the fix to the error.

PedroHLC commented on 2019-08-13 14:47

@acxz Thanks for the fast response! Sorry for asking something that had a bug report.

PedroHLC commented on 2019-08-13 13:50

I'm getting:

CMake Error in src/CMakeLists.txt:
  Imported target "ZeroMQ::ZeroMQ" includes non-existent path

Is that a problem with ZeroMQ or something that needs fix here?

ank_s commented on 2019-06-30 16:34

@acxz Thanks. I'll report it upstream.

acxz commented on 2019-06-30 16:32

hmm, interesting. On my machine all the unit tests pass. I believe this issue would be better posted upstream directly to the ignition-transport repository.

Since this is a package and not development of ignition-transport I am fine with removing the unit testing.

EDIT: if you can post a link to the relevant upstream issue edited into your comment, that would be helpful for anyone else encountering the issue in the future.

ank_s commented on 2019-06-30 16:02

I tried yay, it does almost gets installed.

But, my system keeps failing UNIT_ign_TEST. What's 'UNIT_ign_TEST'?

99% tests passed, 1 tests failed out of 90

Total Test time (real) = 508.42 sec

The following tests FAILED:
     33 - UNIT_ign_TEST (Timeout)

acxz commented on 2019-06-30 14:02

@anks_s I apologize, I have fixed the requirements so that it has a check on the correct ignition* dependency version.

I tried doing >=2 & <3 (to future proof it), but yay will still prompt you on the available <3 versions first even if they are not >=2. Seems like an issue to take up with the yay project. However, since yay is the most popular AUR helper rn, I decided to leave the PKGBUILD slightly broken to accommodate for yay users.

ank_s commented on 2019-06-30 11:11

Still fails:

CMake Error at CMakeLists.txt:12 (find_package):
  By not providing "Findignition-cmake2.cmake" in CMAKE_MODULE_PATH this
  project has asked CMake to find a package configuration file provided by
  "ignition-cmake2", but CMake did not find one.

  Could not find a package configuration file provided by "ignition-cmake2"
  with any of the following names:


Add the installation prefix of "ignition-cmake2" to CMAKE_PREFIX_PATH or
  set "ignition-cmake2_DIR" to a directory containing one of the above files.
  If "ignition-cmake2" provides a separate development package or SDK, be
  sure it has been installed.