Re: apt update fails - The repository does not have a Release file

On paź 31, Hartmut Goebel wrote: The 'apt' role tries to detect existing APT sources from the diverted sources.list file and creates a new set of sources based on them. The fact script which does this should detect the security repositories and filter them out; I suspect that https:// prefix could have caused that repository to be misinterpreted. In any case, the fact script should be updated to detect this particular repository as the security repository to avoid creating the set of sources with <codename>, <codename>-updates, <codename>-backports suites which are incorrect in this case. I'll try to fix the script on my end ASAP. To avoid this, you could modify the sources.list file on the host before applying the DebOps roles - just comment the security repository, it should be sufficient. Best Regards, Maciej Delmanowski