Bug#932793: cloud.debian.org: Vagrant image debian/buster64 v10.0.0: apt repos still use 'testing' suite
Le 23/07/2019 à 12:28, Jörg Sachse a écrit :
> Package: cloud.debian.org
> Severity: normal
>
> Dear Maintainer,
>
> * What led up to the situation?
>
> I tried to provision a new VM using Ansible/Molecule, Vagrant and VirtualBox.
> molecule/default/molecule.yml
> (...)
> platforms:
> - name: molecule-test
> box: debian/buster64
> memory: 512
> cpus: 1
> (...)
>
> I then tried to add additional repos:
> molecule/default/prepare.yml:
> (...)
> - name: add nonfree repos
> apt_repository:
> #repo: deb http://ftp2.de.debian.org/debian/ stretch main non-free contrib
> repo: deb http://ftp2.de.debian.org/debian/ buster main non-free contrib
> state: present
> update-cache: yes
> become: true
>
> But I only got this error message:
> fatal: [molecule-test]: FAILED! => {
> "changed": false,
> "msg": "Failed to auto-install python-apt. Error was:
> 'E: Repository 'http://security.debian.org/debian-security buster/updates InRelease' changed its 'Suite' value from 'testing' to 'stable'
> E: Repository 'http://deb.debian.org/debian buster InRelease' changed its 'Suite' value from 'testing' to 'stable''"
> }
>
> To investigate, I used "vagrant ssh <id>" and ran "sudo apt-get update" on the VM. The resulting output is shown below, arrows mark interesting lines:
> vagrant@molecule-test:~$ sudo apt update
> Get:1 http://security.debian.org/debian-security buster/updates InRelease [39.1 kB]
> Get:2 http://deb.debian.org/debian buster InRelease [118 kB]
> N: Repository 'http://security.debian.org/debian-security buster/updates InRelease' changed its 'Version' value from '' to '10' <====
> E: Repository 'http://security.debian.org/debian-security buster/updates InRelease' changed its 'Suite' value from 'testing' to 'stable' <====
> N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
> Do you want to accept these changes and continue updating from this repository? [y/N] y
> Get:3 http://security.debian.org/debian-security buster/updates/main Sources [24.7 kB]
> Get:4 http://security.debian.org/debian-security buster/updates/main amd64 Packages [49.4 kB]
> N: Repository 'http://deb.debian.org/debian buster InRelease' changed its 'Version' value from '' to '10.0' <====
> E: Repository 'http://deb.debian.org/debian buster InRelease' changed its 'Suite' value from 'testing' to 'stable' <====
> N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
> Do you want to accept these changes and continue updating from this repository? [y/N] y
> Get:5 http://deb.debian.org/debian buster/main Sources [7,827 kB]
> Get:6 http://deb.debian.org/debian buster/main amd64 Packages [7,897 kB]
> Fetched 15.8 MB in 34s (463 kB/s)
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> 39 packages can be upgraded. Run 'apt list --upgradable' to see them.
>
> * What was the outcome of this action?
>
> After this, I was able to add repositories myself.
>
> * What outcome did you expect instead?
>
> I'd expect the VM to run a repository configuration that points to the stable version of Debian Buster in out-of-the-box installations, thus enabling the user to use the box in automated workflows that don't require interactive user intervention.
>
>
> -- System Information:
> Debian Release: 10.0
> APT prefers stable
> APT policy: (500, 'stable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.19.0-5-amd64 (SMP w/1 CPU core)
> Kernel taint flags: TAINT_CRAP
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
>
Hi Jörg
Thanks for you interest for the Debian Vagrant boxes.
Are you sure the new vagrant environment you're starting is using the
10.0.0 box ?
What is the output of
vagrant box list | grep debian/buster64
on your system ?
--
You know an upstream is nice when they even accept m68k patches.
- John Paul Adrian Glaubitz, Debian OpenJDK maintainer
Reply to: