New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Debian Templates: linux-headers-amd64 package installation fails #1353

Closed
adrelanos opened this Issue Oct 23, 2015 · 4 comments

Comments

Projects
None yet
2 participants
@adrelanos
Member

adrelanos commented Oct 23, 2015

Unpacking linux-headers-3.16.0-4-amd64 (3.16.7-ckt11-1+deb8u5) ...
dpkg: error processing archive /var/cache/apt/archives/linux-headers-3.16.0-4-amd64_3.16.7-ckt11-1+deb8u5_amd64.deb (--unpack):
 unable to clean up mess surrounding `./lib/modules/3.16.0-4-amd64' before installing another version: Read-only file system
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Selecting previously unselected package linux-headers-amd64.
Preparing to unpack .../linux-headers-amd64_3.16+63_amd64.deb ...
Unpacking linux-headers-amd64 (3.16+63) ...
Processing triggers for man-db (2.7.0.2-5) ...
Errors were encountered while processing:
 /var/cache/apt/archives/linux-headers-3.16.0-4-amd64_3.16.7-ckt11-1+deb8u5_amd64.deb
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)

Any idea?

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Oct 23, 2015

Member

/lib/modules is indeed mounted read-only. Same as the kernel, it is
provided by dom0, so VM have no influence on the kernel. So, in short
it is senseless to install kernel modules in the VM (using distro package).
What exactly linux-headers package try to write there? And why do you
want to install it?

Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

Member

marmarek commented Oct 23, 2015

/lib/modules is indeed mounted read-only. Same as the kernel, it is
provided by dom0, so VM have no influence on the kernel. So, in short
it is senseless to install kernel modules in the VM (using distro package).
What exactly linux-headers package try to write there? And why do you
want to install it?

Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

@adrelanos

This comment has been minimized.

Show comment
Hide comment
@adrelanos

adrelanos Oct 23, 2015

Member

Use cases:

  • Non-Qubes-Whonix builds try to install it (ok, that can be worked around)
  • kernel module development, I wanted to compile a kernel module.
Member

adrelanos commented Oct 23, 2015

Use cases:

  • Non-Qubes-Whonix builds try to install it (ok, that can be worked around)
  • kernel module development, I wanted to compile a kernel module.
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Oct 23, 2015

Member

On Fri, Oct 23, 2015 at 04:10:53AM -0700, Patrick Schleizer wrote:

  • kernel module development, I wanted to compile a kernel module.

That'd require having packaged headers exactly for kernel VM is using.
Currently we have them only as rpm package... So I think in practice the
only way to go is to get that rpm package (kernel-devel) and somehow
install it in Debian VM (either using "alien" or manually extracting to
some directory and pointing build scripts to use that).

This would be much easier when #1354 got implemented. I wonder why we
hadn't ticket for this already - the idea isn't anything new.

Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

Member

marmarek commented Oct 23, 2015

On Fri, Oct 23, 2015 at 04:10:53AM -0700, Patrick Schleizer wrote:

  • kernel module development, I wanted to compile a kernel module.

That'd require having packaged headers exactly for kernel VM is using.
Currently we have them only as rpm package... So I think in practice the
only way to go is to get that rpm package (kernel-devel) and somehow
install it in Debian VM (either using "alien" or manually extracting to
some directory and pointing build scripts to use that).

This would be much easier when #1354 got implemented. I wonder why we
hadn't ticket for this already - the idea isn't anything new.

Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

adrelanos added a commit to Whonix/Whonix that referenced this issue Oct 25, 2015

Fixed building Non-Qubes-Whonix inside Qubes Debian templates.
Workaround: Avoid installing linux_headers when Qubes detected.

Use '--no-install-recommends' when installing 'virtualbox' avoid installing kernel headers in Qubes, which would fail.

QubesOS/qubes-issues#1353
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Nov 2, 2015

Member

We'll go PV Grub way (#1354).

Member

marmarek commented Nov 2, 2015

We'll go PV Grub way (#1354).

@marmarek marmarek closed this Nov 2, 2015

@marmarek marmarek added the wontfix label Nov 2, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment