You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of the maintenance tasks of an RMT server is to find potentially stale repositories. This can be done as shown in issue #1136. One could parse the rmt-cli mirror [args] output, to get a list of "active" repositories. Everything else is potentially stale.
It would be nice to have an API to query the download locations. Perhaps as additional column in the rmt-cli repos [custom] list --cvs output. This removes to the need to parse a logfile to find the same information. In the end, rmt-cli already knows upfront where repository content will be stored.
The text was updated successfully, but these errors were encountered:
There is a slight regression in 2.17, compared to 2.15 and earlier:
In 2.15 the output of rmt-cli mirror for each repository was: INFO -- : Mirroring repository $something to /usr/share/rmt/public/repo/$somewhere, followed by success of failure messages.
In 2.17 the output of rmt-cli mirror changed. The lines INFO -- : Mirroring repository $something to /usr/share/rmt/public/repo/$somewhere are only shown if the URL can be reached. Like not right now, because $dist ist down.
As a result the mapping about what is enabled and what exists on disk is out of sync, in external tooling.
One of the maintenance tasks of an RMT server is to find potentially stale repositories. This can be done as shown in issue #1136. One could parse the
rmt-cli mirror [args]
output, to get a list of "active" repositories. Everything else is potentially stale.It would be nice to have an API to query the download locations. Perhaps as additional column in the
rmt-cli repos [custom] list --cvs
output. This removes to the need to parse a logfile to find the same information. In the end, rmt-cli already knows upfront where repository content will be stored.The text was updated successfully, but these errors were encountered: