Tested on jammy using landscape-client version 23.02-0ubuntu1~22.04.5. I added the proposed source using a .sources file so that I could test it was moved to a .save file after repository profile application.
Registered with landscape-server and applied a repository profile. The resulting state on the client: ubuntu@thorough-albacore:~$ ls /etc/apt/sources.list.d/ landscape-2087852-test.list proposed.sources.save ubuntu@thorough-albacore:~$ cat /etc/apt/sources.list # Landscape manages repositories for this computer # Original content of sources.list can be found in sources.list.save I then removed the repository profile from the instance and verified that the state was restored to the original state: ubuntu@thorough-albacore:~$ ls /etc/apt/sources.list.d/ landscape-2087852-test.list.save proposed.sources.save ubuntu@thorough-albacore:~$ cat /etc/apt/sources.list ## Note, this file is written by cloud-init on first boot of an instance ## modifications made here will not survive a re-bundle. ## if you wish to make changes you can: ## a.) add 'apt_preserve_sources_list: true' to /etc/cloud/cloud.cfg ## or do the same in user-data ## b.) add sources in /etc/apt/sources.list.d ... So while the .sources file did get moved to a .save file, it did not get moved _back_ when the repository profile was removed. I think this fails validation, even though technically the original issue where the .sources files were not moved to .save is fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2087852 Title: [FFe][SRU] Repository profiles only act on .list files and do not affect .source files To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/2087852/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
