[solved] Aptly mirror


#1

HI,

I build with aptly from http://de.archive.ubuntu.com/ubuntu/ a mirror of the office repository.

This way I can snapshot the repo to a point of time. When I use this repo within MAAS. I get the following error, at the deploy and commission:

N: Repository ‘http://10.8.1.240/Ubuntu bionic-updates InRelease’ changed its ‘Version’ value from ‘18.04’ to ‘’
E: Repository ‘http://10.8.1.240/Ubuntu bionic-updates InRelease’ changed its ‘Codename’ value from ‘bionic’ to ‘bionic-updates’
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.

If I do “rm /var/lib/apt/lists/10*” and then an apt update. I don’t get any error.

I build the apt aptly with:

aptly -architectures=“amd64” mirror create bionic-backports-main http://de.archive.ubuntu.com/ubuntu/ bionic-backports main
aptly -architectures=“amd64” mirror create bionic-backports-restricted http://de.archive.ubuntu.com/ubuntu/ bionic-backports restricted
aptly -architectures=“amd64” mirror create bionic-backports-universe http://de.archive.ubuntu.com/ubuntu/ bionic-backports universe
aptly -architectures=“amd64” mirror create bionic-backports-multiverse http://de.archive.ubuntu.com/ubuntu/ bionic-backports multiverse
aptly -architectures=“amd64” mirror create bionic-main http://de.archive.ubuntu.com/ubuntu/ bionic main
aptly -architectures=“amd64” mirror create bionic-universe http://de.archive.ubuntu.com/ubuntu/ bionic universe
aptly -architectures=“amd64” mirror create bionic-multiverse http://de.archive.ubuntu.com/ubuntu/ bionic multiverse
aptly -architectures=“amd64” mirror create bionic-restricted http://de.archive.ubuntu.com/ubuntu/ bionic restricted
aptly -architectures=“amd64” mirror create bionic-security-main http://de.archive.ubuntu.com/ubuntu/ bionic main
aptly -architectures=“amd64” mirror create bionic-security-universe http://de.archive.ubuntu.com/ubuntu/ bionic universe
aptly -architectures=“amd64” mirror create bionic-security-multiverse http://de.archive.ubuntu.com/ubuntu/ bionic multiverse
aptly -architectures=“amd64” mirror create bionic-security-restricted http://de.archive.ubuntu.com/ubuntu/ bionic restricted
aptly -architectures=“amd64” mirror create bionic-updates-main http://de.archive.ubuntu.com/ubuntu/ bionic main
aptly -architectures=“amd64” mirror create bionic-updates-universe http://de.archive.ubuntu.com/ubuntu/ bionic universe
aptly -architectures=“amd64” mirror create bionic-updates-multiverse http://de.archive.ubuntu.com/ubuntu/ bionic multiverse
aptly -architectures=“amd64” mirror create bionic-updates-restricted http://de.archive.ubuntu.com/ubuntu/ bionic restricted

Then I do an update and make a snapshot.

I publish the snapshot with:

aptly publish snapshot -label=“Ubuntu” -component=, bionic-security-main-20190411 bionic-security-multiverse-20190411 bionic-security-universe-20190411 bionic-security-restricted-20190411 Ubuntu
aptly publish snapshot -label=“Ubuntu” -component=, bionic-updates-main-20190411 bionic-updates-multiverse-20190411 bionic-updates-universe-20190411 bionic-updates-restricted-20190411 Ubuntu
aptly publish snapshot -label=“Ubuntu” -component=, bionic-main-20190411 bionic-multiverse-20190411 bionic-universe-20190411 bionic-restricted-20190411 Ubuntu
aptly publish snapshot -label=“Ubuntu” -component=, bionic-backports-main-20190411 bionic-backports-multiverse-20190411 bionic-backports-universe-20190411 bionic-backports-restricted-20190411 Ubuntu

What is the best solution to solve this?


#2

After “upgrading”/reinstalling the maas server from 2.4 to 2.5 this issue has been solved.


#3

This is probably because 2.5 has fixes not available in 2.4 that were causing this.