From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] dpkg: failed to open package info file `/var/lib/dpkg/status' for reading: No such file or directory
Date: Tue, 24 Mar 2009 22:23:51 +0200 [thread overview]
Message-ID: <200903242223.52108.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <49C93FAE.8000904@gmail.com>
On Tuesday 24 March 2009 22:16:46 Alexander Pilipovsky wrote:
> Why not use the ebuild for app-cdr/nero?
>
>
>
> I used nero in previous listing as example to install, but I get these
> errors for any deb :(
I find it's useful to look at error messages. It often tells you what is
wrong:
dpkg: error processing nerolinux-3.5.0.1-x86.deb (--install):
package architecture (i386) does not match system ()
dpkg does nto want ot install that .deb on your system as the arch is wrong.
It makes sense, it wouldn't install sparc binaries either. Gentoo doesn't have
an i386 arch, it has x86 and amd64.
But I still feel your whole approach is wrong. Two package managers on one
system? Therein lies madness, and file collisions that will leave you
scratching your head wondering wtf?
The solution is simple:
alien
I know it doesn't do the whole pre- and post- install thing right, but that
doesn't matter as they probably aren't suitable on gentoo anyway. You want the
binaries and a way to extract them.
--
alan dot mckinnon at gmail dot com
next prev parent reply other threads:[~2009-03-24 20:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 18:36 [gentoo-user] dpkg: failed to open package info file `/var/lib/dpkg/status' for reading: No such file or directory Alexander Pilipovsky
2009-03-24 18:41 ` Alan McKinnon
2009-03-24 18:57 ` Alexander Pilipovsky
2009-03-24 19:31 ` Paul Hartman
2009-03-24 20:16 ` Alexander Pilipovsky
2009-03-24 20:23 ` Alan McKinnon [this message]
2009-03-24 20:33 ` Paul Hartman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200903242223.52108.alan.mckinnon@gmail.com \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@lists.gentoo.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