Expected Build Warnings

From Whonix
< Dev
Jump to navigation Jump to search

Non-Issues[edit]

None of the following warnings affect the build. Refer to relevant footnotes for further information.


dpkg-source: warning: extracting unsigned source package
dpkg-source: warning: extracting unsigned source package (anon-gw-anonymizer-config_5.0-1.dsc)

[1]


Can not write log, openpty() failed (/dev/pts not mounted?)

[2]


[....] Your system does not have the CPU extensions required to use KVM. Not doing anything. ...[ FAIL ]

[3]


[....] Stopping VirtualBox kernel modules [ ok ].
[....] Starting VirtualBox kernel modules[....] No suitable module for running kernel found ...[ FAIL ]
invoke-rc.d: initscript virtualbox, action "restart" failed.

[4]


WARNING: The character device /dev/vboxdrv does not exist.
	 Please install the virtualbox-ose-dkms package and the appropriate
	 headers, most likely linux-headers-486.

	 You will not be able to start VMs until this problem is fixed.

[5]


dpkg: warning: failed to open configuration file '/root/.dpkg.cfg' for reading: Permission denied

[6]


sudo: unable to resolve host host

[7]

Related forum topic: Expected Build Warnings

Footnotes[edit]

  1. end-to-end signed debs. debsign, debsig and dpkg-sig
  2. This is nothing to be concerned about; it only happens because commands are run inside chroot. Research of this "issue" indicates it is purely cosmetic.
  3. KVM is installed as a dependency of the build dependency libguestfs-tools. KVM is not needed to build the actual images.
  4. This only means that VirtualBox cannot be started. VirtualBox kernel modules could not be compiled because the linux-headers-$(uname -r) package was not installed prior to installing VirtualBox (before starting Whonix's build script). The build script does not start VirtualBox, hence does not affect the build. The build script only uses VBoxManage for creation of virtual machine description files and that tool does not need VirtualBox kernel modules.
  5. This is caused by the same issue referenced above.
  6. This happens because debuild is run as user, not root. It is probably a bug in dpkg. Research of this issue reveals there are many similar bugs in dpkg.
  7. The hostname is changed intentionally to host inside the VM image. The cause is probably package anon-base-files postinst running hostname "$my_host_name" / hostname host. This change should only happen inside the change root chroot. This issue might be resolved by porting from chroot to systemd-nspawn, but it is not very important.