Skip to content

Note caveat about release repos file #1120

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.

Sign up for GitHub

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

Closed
wants to merge 1 commit into from
Closed

Note caveat about release repos file #1120

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions source/Installation/Maintaining-a-Source-Checkout.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,6 +52,11 @@ If you wish to update a particular release, you can get its repository list by s

The format of the name of the release comes from the tag associated with the release `here <https://github.com/ros2/ros2/tags>`__.

.. note::

The release versions in the ros2.repos file may become out-of-sync with their Debian packages, as maintainers make periodic releases of individual packages.
This means if you are installing Debian packages on Ubuntu, then you may have newer versions of some packages compared to the version listed in the ros2.repos file.
Comment on lines +57 to +58
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think I understand what you are trying to say here (essentially that the debian packages may be ahead of the previous patch release), but I'm not sure this is the right file to say this in. That is, this file seems to mostly deal with building from source, in which case a comparison to what is in the binary debian packages seems a bit weird.

On the other hand, I don't think we have good instructions anywhere for the following scenario a user may run into:

  1. The user is working with Foxy.
  2. The user runs into a bug on Foxy.
  3. The user wants to download the sources for the package they are using to debug it.

How would the user go about doing that? That seems like useful information, and also seems to be the appropriate place to put a note like this. What do you think?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I put the note here because it seems like the only place that references the *-release repo files. I agree that it would be better to have an article that discusses how to checkout the source for a particular distro for the purposes of contributing a fix. A section under "Contributing", perhaps.


Release development branches
^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Expand Down