From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: "Julien Lepiller" <julien@lepiller.eu>,
help-guix@gnu.org, "André A. Gomes" <andremegafone@gmail.com>,
"Gary Johnson" <lambdatronic@disroot.org>
Subject: Re: Run .deb or .rpm packages
Date: Fri, 10 Dec 2021 10:30:36 +0100 [thread overview]
Message-ID: <ee7ea8df-5a68-874a-fb4a-b319a9719307@crazy-compilers.com> (raw)
In-Reply-To: <3124813D-244F-4060-AA72-8778D3B612E2@lepiller.eu>
Hi,
Le 8 décembre 2021 14:46:24 GMT-05:00, "André A. Gomes"<andremegafone@gmail.com> a écrit :
> --8<---------------cut here---------------start------------->8---
> $ sudo dpkg -i foo-package.deb
> dpkg: error: unable to access the dpkg database directory /gnu/store/902w5i1j38r33l6p871dyhng19zj1phk-dpkg-1.20.9/var/lib/dpkg: Read-only file system
> --8<---------------cut here---------------end--------------->8---
>
> Any ideas? I don't know much about .deb or .rpm.
Beside Julien's objections: There might be legitimate use of installing
.deb or .rpm packages and they might even work. E.g. i one wants to
install free software provided as a .deb only and at the moment does not
have the time to create a package definition for it.
So, "dpkg" and "rpm" should at least work :-)
Regarding the error show above: One would need to add
"--localstatedir=/var" to the config flags (not sure whether this would
build, then, since most probably "make install" will try to create
"/var/lib/dpkg" which will fail in the build container.
--
Regards
Hartmut Goebel
| Hartmut Goebel |h.goebel@crazy-compilers.com |
|www.crazy-compilers.com | compilers which you thought are impossible |
next prev parent reply other threads:[~2021-12-10 9:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 15:30 Run .deb or .rpm packages André A. Gomes
2021-12-08 16:46 ` Gary Johnson
2021-12-08 19:46 ` André A. Gomes
2021-12-08 20:05 ` Julien Lepiller
2021-12-08 20:10 ` André A. Gomes
2021-12-08 20:46 ` Remco
2021-12-21 23:27 ` André A. Gomes
2021-12-22 4:13 ` Timmy Douglas
2021-12-10 9:30 ` Hartmut Goebel [this message]
2021-12-12 9:24 ` Efraim Flashner
2021-12-12 19:34 ` Vagrant Cascadian
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ee7ea8df-5a68-874a-fb4a-b319a9719307@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=andremegafone@gmail.com \
--cc=help-guix@gnu.org \
--cc=julien@lepiller.eu \
--cc=lambdatronic@disroot.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).