blob: be4635fdefaa3cfa2d3233adb936bc68ee77b526 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
|
files: 0.939
device: 0.831
other: 0.809
PID: 0.787
graphic: 0.718
socket: 0.656
semantic: 0.605
debug: 0.603
performance: 0.554
network: 0.546
vnc: 0.545
permissions: 0.530
boot: 0.391
KVM: 0.127
9p rootfs issues
Description of problem:
I've created qemu guest per https://wiki.qemu.org/Documentation/9p_root_fs guidelines. debootstrap fails on this guest.
Steps to reproduce:
```
root@ubuntu-dev:~# debootstrap --arch amd64 --variant=minbase noble /var/tmp/new_root/
I: Retrieving InRelease
I: Checking Release signature
E: Error executing gpgv to check Release signature
root@ubuntu-dev:~#
```
Additional information:
I noticed, that gpg key extracted by debootstrap from the InRelease is corrupted:
```
root@ubuntu-dev:~# head /var/tmp/new_root/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_noble_Release.gpg
-----BEGIN PGP SIGNATURE-----
-----BEGIN PGP SIGNATURE-----
-----BEGIN PGP SIGNATURE-----
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE9uyzdiR07anSG3Aihxkg0ZkbyTwFAmXkbkUACgkQhxkg0Zkb
-----BEGIN PGP SIGNATURE-----
-----BEGIN PGP SIGNATURE-----
root@ubuntu-dev:~#
```
I also noticed that on the 9p filesystem appending to files corrupts them:
```
root@ubuntu-dev:~# echo 1 >/var/tmp/test
root@ubuntu-dev:~# cat /var/tmp/test
1
root@ubuntu-dev:~# echo 2 >>/var/tmp/test
root@ubuntu-dev:~# cat /var/tmp/test
1
1
2
root@ubuntu-dev:~#
```
This is not happening on the tmpfs:
```
root@ubuntu-dev:~# echo 1 >/tmp/test
root@ubuntu-dev:~# cat /tmp/test
1
root@ubuntu-dev:~# echo 2 >>/tmp/test
root@ubuntu-dev:~# cat /tmp/test
1
2
root@ubuntu-dev:~#
```
|