Work logs for #238

[kenji-miyake]

I'll keep the work logs for #238 here.

[kenji-miyake]

From https://wiki.debian.org/SecureApt:

Note: apt-key is in the process of being deprecated, at least for the managing of keys. Discussion in Debian bug [851774](https://bugs.debian.org/851774) .

[kenji-miyake]

From man apt-key:

DEPRECATION
       Except for using apt-key del in maintainer scripts, the use of apt-key is deprecated. This section shows how to replace existing use of apt-key.

       If your existing use of apt-key add looks like this:

       wget -qO- https://myrepo.example/myrepo.asc | sudo apt-key add -

       Then you can directly replace this with (though note the recommendation below):

       wget -qO- https://myrepo.example/myrepo.asc | sudo tee /etc/apt/trusted.gpg.d/myrepo.asc

       Make sure to use the "asc" extension for ASCII armored keys and the "gpg" extension for the binary OpenPGP format (also known as "GPG key public ring"). The binary OpenPGP format works
       for all apt versions, while the ASCII armored format works for apt version >= 1.4.

       Recommended: Instead of placing keys into the /etc/apt/trusted.gpg.d directory, you can place them anywhere on your filesystem by using the Signed-By option in your sources.list and
       pointing to the filename of the key. See sources.list(5) for details. Since APT 2.4, /etc/apt/keyrings is provided as the recommended location for keys not managed by packages. When
       using a deb822-style sources.list, and with apt version >= 2.4, the Signed-By option can also be used to include the full ASCII armored keyring directly in the sources.list without an
       additional file.

[kenji-miyake]

It can be affected by keys that aren't added by Autoware.
So anyway, we have to ignore errors.

fatal: [localhost]: FAILED! => {"changed": false, "msg": "Failed to update apt cache: W:https://repo.skype.com/deb/dists/stable/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details., E:The repository 'http://packages.ros.org/ros/ubuntu jammy Release' does not have a Release file., W:Updating from such a repository can't be done securely, and is therefore disabled by default., W:See apt-secure(8) manpage for repository creation and user configuration details., W:https://packagecloud.io/slacktechnologies/slack/debian/dists/jessie/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details."}

[kenji-miyake]

Actually, this was the error. I'll replace this with the ros2 repository.

E: The repository 'http://packages.ros.org/ros/ubuntu jammy Release' does not have a Release file.

[kenji-miyake]

Will be resolved by #242.

[kenji-miyake]

https://www.sproutworkshop.com/2022/02/how-to-compile-opencv-4-5-5-with-cuda-11-6-and-cudnn-8-3-2-on-ubuntu-22-04-daily-build/

[kenji-miyake]

Resolved. (As a workaround)

- name: (tmp for Ubuntu 22.04) Add liburcu6 repository into sources.list
  become: true
  ansible.builtin.apt_repository:
    repo: deb http://jp.archive.ubuntu.com/ubuntu/ impish main restricted
    filename: impish
    state: present

[kenji-miyake]

NVIDIA's CUDA image for Ubuntu 22.04 isn't released yet.
https://gitlab.com/nvidia/container-images/cuda/-/issues/157

[kenji-miyake]

Resolved by putting COLCON_IGNORE to grid_map and grid_map_demos.

[kenji-miyake]

Did you source /opt/ros/humble/setup.bash before building the source? 🤔

[kminoda]

Yes, I did that too

[kenji-miyake]

Could you check the compile options?

cd autoware/build/accel_brake_map_calibrator
VERBOSE=1 make

[kminoda]

I executed your commands, and it worked. Now I can build the packages both with make and colcon build.
Not sure what happened, though,,.

Anyway, the above issue seems to be solved. Thank you for your help!

[kenji-miyake]

It's a mystery... 🤔 But great. 👍

[kenji-miyake]

[Humble] ROS_DISTRO is incorrect.

$ cat /opt/ros/humble/share/ros_environment/environment/0.ros_distro_check.sh
# generated from ros_environment/env-hooks/0.ros_distro.sh.in

if [ -n "$ROS_DISTRO" -a "$ROS_DISTRO" != "rolling" ]; then
  echo "ROS_DISTRO was set to '$ROS_DISTRO' before. Please make sure that the environment does not mix paths from different distributions."
fi