Gentoo Archives: gentoo-portage-dev

From: Zac Medico <zmedico@g.o>
To: gentoo-portage-dev@l.g.o
Subject: Re: [gentoo-portage-dev] Error notification when PORTAGE_BINHOST unreachable?
Date: Tue, 07 Apr 2009 16:22:45
Message-Id: 49DB7DBA.40206@gentoo.org
In Reply to: [gentoo-portage-dev] Error notification when PORTAGE_BINHOST unreachable? by Amit Dor-Shifer
1 -----BEGIN PGP SIGNED MESSAGE-----
2 Hash: SHA1
3
4 Amit Dor-Shifer wrote:
5 > Hi.
6 > I'm trying to emerge a binary package I've put on a remote host.
7 > Initially I couldn't get the package to emerge:
8 >
9 > amit0 Common # emerge -pvg =app-editors/vim-7.1.266
10 >
11 > These are the packages that would be merged, in order:
12 >
13 > Calculating dependencies -
14 > Fetching bininfo from http://package-repo/binpkg
15 > cache miss: '0' --- cache hit: '0'
16 > ... done!
17 >
18 > emerge: there are no ebuilds to satisfy "=app-editors/vim-7.1.266".
19 >
20 > This happens because the Packages index on the remote host wasn't
21 > readable to non-root.
22 >
23 > After I've fixed this, emerge works as-expected:
24 >
25 > amit0 Common # emerge -pvg =app-editors/vim-7.1.266
26 >
27 > These are the packages that would be merged, in order:
28 >
29 > Calculating dependencies... done!
30 > [binary N ] app-editors/vim-core-7.1.266 USE="bash-completion nls
31 > -acl -livecd"
32 > [binary N ] app-editors/vim-7.1.266 USE="bash-completion gpm nls
33 > perl python -acl -cscope -minimal -ruby -vim-pager -vim-with-x"
34 > [ebuild N ] app-vim/gentoo-syntax-20090220 USE="-ignore-glep31" 18 kB
35 >
36 > Total: 3 packages (3 new), Size of downloads: 18 kB
37 >
38 > Is the "cache miss: '0' --- cache hit: '0'" message suppose to indicate
39 > the error in fetching binpkg data? Is it considered at-all an error? If
40 > so, I'd suggest a more-clear error message.
41
42 That's not an error. However, the output indicates that it's using
43 the older binhost protocol. This means that
44 http://package-repo/binpkg/Packages doesn't exist for some reason.
45 This could mean that you've shared the wrong directory. You should
46 be sharing the $PKGDIR directory in order for the new protocol to
47 work. If that directory doesn't contain a Packages file, or some of
48 the packages were built with less than portage-2.1.6, then you
49 should run `emaint --fix binhost` on the server. That will ensure
50 that the Packages file contains all of the appropriate metadata for
51 all of your packages.
52 - --
53 Thanks,
54 Zac
55 -----BEGIN PGP SIGNATURE-----
56 Version: GnuPG v2.0.11 (GNU/Linux)
57
58 iEYEARECAAYFAknbfbkACgkQ/ejvha5XGaOjrwCeNQ0jRLpNGgX3UYh5dN6CWpF5
59 NHkAoOK1cplV+Os3e+Yzzjx1sWRvuCdO
60 =1lQV
61 -----END PGP SIGNATURE-----