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
I expected it to replace sources.list with content provided, not create a new sources.list.d/ file
Steps to Reproduce
Steps to reproduce the behavior:
Create or add code in puppet like:
apt::source {
"archive.debian.org-${facts['os']['distro']['codename']}":
location => 'http://archive.debian.org/debian',
repos => 'main contrib non-free',
}
Assign manifest file to object in foreman.
Run puppet agent -t on client
Environment
Debian 9
Puppet 6
Additional Context
Im testing this out as i need to change to the archive repo on all debian 9 servers.
Documentation states that apt::source will edit sources.list.d , but examples say that it will replace sources.list.
It didnt replace sources.list :(
The text was updated successfully, but these errors were encountered:
With purge you mean? I have other repos not manage by the module so i wont want to do that, but I could do a file delete and let it create archive repo..
Describe the Bug
According to https://github.com/puppetlabs/puppetlabs-apt#replace-the-default-sourceslist-file i should be able to replace existing sources.list file with one containing the specified apt repositories.
This does not work, it will create a file in sources.list.d tho..
Expected Behavior
I expected it to replace sources.list with content provided, not create a new sources.list.d/ file
Steps to Reproduce
Steps to reproduce the behavior:
apt::source {
"archive.debian.org-${facts['os']['distro']['codename']}":
location => 'http://archive.debian.org/debian',
repos => 'main contrib non-free',
}
Environment
Additional Context
Im testing this out as i need to change to the archive repo on all debian 9 servers.
Documentation states that apt::source will edit sources.list.d , but examples say that it will replace sources.list.
It didnt replace sources.list :(
The text was updated successfully, but these errors were encountered: