GentUser11
n00b
Joined: 23 Nov 2024
Posts: 1
|
 Posted: Sat Nov 23, 2024 5:20 pm Post subject: Unable to emerge binary packages/binpkgs [SOLVED] |
 |
|
Hello, just made this account for the problem I'm having right now. Portage does not, for the life of me, want to emerge binary packages (*.gpkg.tar).
| Code: | | *** You need to adjust PKGDIR to emerge this package: /var/cache/binpkgs/sys-kernel/dracut/dracut-103-r4-1.gpkg.tar |
My make.conf has PKGDIR="/var/cache/binpkgs" so the PKGDIR directory matches. So why would
| Code: | | emerge --usepkg <path to file>.gpkg.tar |
not work? I used to emerge tbz2 binpkgs without issue a few years back. Is it a possible bug? What could possibly be going wrong here?
EDIT:
The binpkgs install only on the exact drive they were compiled on. Which is not what I'm building binaries for. So when I do an install on a new drive and try to install the binaries I get the above mentioned error message. Same machine though, so no difference there at all.
EDIT 2:
If I do | Code: | | emerge --usepkgonly sys-kernel/dracut |
while having the binary in it's corresponding directory at /var/cache/binpkgs portage says there are no binary packages to satisfy <package>. I will probably open a bug report soon since this is obviously not normal or intentional behaviour.
EDIT 3: SOLVED
The problem is solved by running this after placing the binaries into PKGDIR
I still don't completely understand why that is. It generates a metadata index for binary packages in PKGDIR? As in the Packages file (which was of course there before)? Because /etc/portage/binrepos.conf/gentoobinhost.conf is still the same as before and has nothing to do with local binaries I think. |
|
Portage & Programming
