Expected Build Warnings

Expected Build Warning when building Kicksecure.

dpkg-source: warning: extracting unsigned source package

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

etc.

This does not affect the build. ^[1]

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

This does not affect the build. ^[2]

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

This does not affect the build. ^[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.

This does not affect the build. ^[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.

This does not affect the build. ^[5]

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

This does not affect the build. ^[6]

sudo: unable to resolve host host

This does not affect the build. ^[7]

Related forum topic:
Expected Build Warnings

Footnotes:

↑ https://forums.whonix.org/t/end-to-end-signed-debs-debsign-debsig-and-dpkg-sig/3446
↑ 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.
↑ KVM is installed as a dependency of the build dependency libguestfs-tools. KVM is not needed to build the actual images.
↑ 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 doesn't start VirtualBox, hence does not affect the build. The build script only uses VBoxManage for creation of virtual machine description files and that tool doesn't need VirtualBox kernel modules.
↑ This is caused by the same issue referenced above.
↑ 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.
↑ Hostname inside VM image gets changed intentionally to host inside the VM image. The cause probably is package anon-base-files postinst running hostname "$my_host_name" / hostname host. This change should only happen inside the change root chroot. We might get rid of this issue by porting form chroot to systemd-nspawn, but it is not very important.

Unfinished: This wiki is a work in progress. Please do not report broken links until this notice is removed, use Search Engines First and contribute improving this wiki.

Kicksecure A secure by default operating system with the latest security research in place.

Dark mode

FREE · PLUS · PREMIUM Support

At Kicksecure we value freedom and trust, supporting Open Source and Freedom Software

By using this website, you acknowledge you have read, understood, and agree to be bound by these these agreements: Terms of Service, Privacy Policy, Cookie Policy, E-Sign Consent, DMCA, Imprint Kicksecure

ENCRYPTED SUPPORT LP, 2023

Your support makes
all the difference!

We believe security software like Kicksecure needs to remain open source and independent. Would you help sustain and grow the project? Learn more about our 10 year success story and maybe DONATE!

[1] ttps://forums.whonix.org/t/end-to-end-signed-debs-debsign-debsig-and-dpkg-sig/3446

[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 doesn't start VirtualBox, hence does not affect the build. The build script only uses VBoxManage for creation of virtual machine description files and that tool doesn't 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] Hostname inside VM image gets changed intentionally to host inside the VM image. The cause probably is package anon-base-files postinst running hostname "$my_host_name" / hostname host. This change should only happen inside the change root chroot. We might get rid of this issue by porting form chroot to systemd-nspawn, but it is not very important.

[1]

[2]

[3]

[4]

[5]

[6]

[7]

Expected Build Warnings

Navigation menu