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
2024-11-22 10:00:27.608 Refreshing repositories
2024-11-22 10:00:27.608 Executing: ['apt-get', 'update']
2024-11-22 10:00:27.615 :: E: Conflicting values set for option Signed-By regarding source https://archive.ubuntu.com/ubuntu/ noble: /etc/apt/keyrings/craft-991BC93C.gpg != /usr/share/keyrings/ubuntu-archive-keyring.gpg
2024-11-22 10:00:27.615 :: E: The list of sources could not be read.
From the logs, it looks like craft-archives is reading the existing sources but ignoring them because their url is http and not https:
2024-11-22 10:00:27.601 Looking for existing sources files for url 'https://archive.ubuntu.com/ubuntu' and suites ['noble']
2024-11-22 10:00:27.601 Reading sources in '/etc/apt/sources.list.d/ubuntu.sources' looking for 'https://archive.ubuntu.com/ubuntu/'
2024-11-22 10:00:27.602 Source does not have a matching url: http://archive.ubuntu.com/ubuntu/
2024-11-22 10:00:27.602 Source does not have a matching url: http://security.ubuntu.com/ubuntu/
2024-11-22 10:00:27.602 No existing sources found
Apt does not take the scheme (e.g. http vs https) into account when parsing
sources, which means that, for the purposes of finding existing keys,
'https://archive.ubuntu.com' and 'http://archive.ubuntu.com' should be
considered the same.
Fixes#139
Apt does not take the scheme (e.g. http vs https) into account when parsing
sources, which means that, for the purposes of finding existing keys,
'https://archive.ubuntu.com' and 'http://archive.ubuntu.com' should be
considered the same.
Fixes#139
Bug Description
Related to #129 , the following specification on noble:
... fails with:
From the logs, it looks like craft-archives is reading the existing sources but ignoring them because their url is
http
and nothttps
:To Reproduce
.
part yaml
Relevant log output
.
The text was updated successfully, but these errors were encountered: