Bug #14334
open
Bug #14324: Upgrading an ubuntu distro installed with rudder-setup lead to incorrect repository definition
Make the use of rudder-apt.list/rudder.list globally consistant (doc, rudder-setup, apt repo technique)
Description
See comments on https://github.com/Normation/rudder-tools/pull/460 for context.
APT repo technique v3 and 3.1 use `/etc/apt/sources.list.d/rudder-apt.list`.
Documentation uses `/etc/apt/sources.list.d/rudder.list`.
Since the above PR, `rudder-setup` uses `/etc/apt/sources.list.d/rudder.list` (but it was using `/etc/apt/sources.list.d/rudder-apt.list` before.
Updated by François ARMAND almost 6 years ago
- Subject changed from Revert rudder-apt.list change in rudder-setup script to Make the use of rudder-apt.list/rudder.list globally consistant (doc, rudder-setup, apt repo technique)
- Description updated (diff)
So, the only referance in Rudder code to `/etc/apt/sources.list.d/rudder-apt.list` seems to be in technique package management for apt and in rudder-setup prior to the pull request linked above.
The documentation (install, updated) tells to use `/etc/apt/sources.list.d/rudder.list`. So it is likely that a lot of people have one or the other rudder repos.
Moreover, for consistency with redhat ditribution which uses "rudder.repo", we should use `/etc/apt/sources.list.d/rudder.list`. Can the technique use `rudder.list` by defaut and look for `/etc/apt/sources.list.d/rudder-apt.list` too?