[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: "Invalid Release file" when setup autopkgtest env with autopkgtest-build-lxc



Hi,
On Tue, Apr 12, 2022 at 10:40:37PM +0200, Paul Gevers wrote:
Hi,

On 12-04-2022 22:20, Santiago Ruano Rincón wrote:
root@unmatched:~# grep net /var/lib/lxc/autopkgtest-unstable-riscv64/config
lxc.net.0.type = veth
lxc.net.0.link = lxcbr0
lxc.net.0.flags = up
lxc.net.0.hwaddr = 00:16:3e:00:00:00

This is the same mac address than the unmatched's lxcbr0. Try changing
it.

root@unmatched:~# grep hwaddr
/var/lib/lxc/autopkgtest-unstable-riscv64/config
lxc.net.0.hwaddr = 00:16:3e:00:00:01

root@unmatched:~# lxc-start -n autopkgtest-unstable-riscv64
root@unmatched:~# lxc-ls -f
NAME                         STATE   AUTOSTART GROUPS IPV4      IPV6
UNPRIVILEGED
autopkgtest-unstable-riscv64 RUNNING 0         -      10.0.3.17 -
false
root@unmatched:~# lxc-attach -n autopkgtest-unstable-riscv64
root@autopkgtest-unstable-riscv64:~# apt update
Ign:1 https://deb.debian.org/debian-ports unstable InRelease
Ign:1 https://deb.debian.org/debian-ports unstable InRelease
Ign:1 https://deb.debian.org/debian-ports unstable InRelease

It seems it's getting better, but it still doesn't want to find the
archive....

Great! I just to test it based paul's work and it seems work:

root@autopkgtest-unstable-riscv64:~# apt update
Get:1 http://deb.debian.org/debian-ports unstable InRelease [65.1 kB]
Get:2 http://deb.debian.org/debian-ports unstable/main riscv64 Packages [23.3 MB]
Fetched 23.3 MB in 20s (1,190 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
20 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: Skipping acquire of configured file 'main/source/Sources' as repository 'http://deb.debian.org/debian-ports unstable InRelease' does not seem to provide it (sources.list entry misspelt?)

In fact, I did some fix as below.

First, in my memory, The debian-ports does not support https(if I am wrong plz corrent me), so I hacked the file:
/var/lib/lxc/autopkgtest-unstable-riscv64/rootfs/etc/apt/sources.list to adopt s/http/https/.

root@autopkgtest-unstable-riscv64:~# apt update
Get:1 http://deb.debian.org/debian-ports unstable InRelease [65.1 kB]
Err:1 http://deb.debian.org/debian-ports unstable InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E852514F5DF312F6
  Fetched 65.1 kB in 2s (29.5 kB/s)
  Reading package lists... Done
  Building dependency tree... Done
  All packages are up to date.
  W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://deb.debian.org/debian-ports unstable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E852514F5DF312F6
  W: Failed to fetch http://deb.debian.org/debian-ports/dists/unstable/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E852514F5DF312F6
  W: Some index files failed to download. They have been ignored, or old ones used instead.

But it does not affect to install port-keying:

root@autopkgtest-unstable-riscv64:~# apt install debian-ports-archive-keyring
Reading package lists... Done
Building dependency tree... Done
The following NEW packages will be installed:
debian-ports-archive-keyring
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 29.7 kB of archives.
After this operation, 52.2 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian-ports unstable/main riscv64 debian-ports-archive-keyring all 2022.02.15 [29.7 kB]
Fetched 29.7 kB in 1s (38.3 kB/s)
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package debian-ports-archive-keyring.
(Reading database ... 9168 files and directories currently installed.)
Preparing to unpack .../debian-ports-archive-keyring_2022.02.15_all.deb ...
Unpacking debian-ports-archive-keyring (2022.02.15) ...
Setting up debian-ports-archive-keyring (2022.02.15) ...
root@autopkgtest-unstable-riscv64:~# apt update
Get:1 http://deb.debian.org/debian-ports unstable InRelease [65.1 kB]
Get:2 http://deb.debian.org/debian-ports unstable/main riscv64 Packages [23.3 MB]
Fetched 23.3 MB in 20s (1,190 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
20 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: Skipping acquire of configured file 'main/source/Sources' as repository 'http://deb.debian.org/debian-ports unstable InRelease' does not seem to provide it (sources.list entry misspelt?)

BTW, Because the Unmatched board does not have rtc, so it will display on unmatched board:

root@unmatched:~# apt update
Get:1 http://deb.debian.org/debian-ports unstable InRelease [65.1 kB]
Get:2 http://deb.debian.org/debian unstable InRelease [165 kB]
Get:3 http://deb.debian.org/debian-ports unreleased InRelease [46.4 kB]
Reading package lists... Done
E: Release file for http://deb.debian.org/debian-ports/dists/unstable/InRelease is not valid yet (invalid for another 24d 19h 44min 26s). Updates for this repository will not be applied.
E: Release file for http://deb.debian.org/debian/dists/unstable/InRelease is not valid yet (invalid for another 24d 14h 47min 49s). Updates for this repository will not be applied.
E: Release file for http://deb.debian.org/debian-ports/dists/unreleased/InRelease is not valid yet (invalid for another 24d 19h 44min 36s). Updates for this repository will not be applied.

And update time is ok:
root@unmatched:~# ntpdate cn.pool.ntp.org
15 Apr 07:55:15 ntpdate[425330]: step time server 111.230.189.174 offset +2146974.389164 sec

BR,
Bo


Paul




Reply to: