| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
You need to 'ebuild libstdc++-v3-3.3.3-r1.ebuild digest' to create a new |
| 5 |
Manifest file. This will have to be done before any catalyst stuff, in |
| 6 |
the directory with the ebuild, and the base directory should be in your |
| 7 |
make.conf's PORTDIR_OVERLAY. |
| 8 |
|
| 9 |
Or, you could export FEATURES="-strict" in your catalyst envs to lower |
| 10 |
the amount of verification performed, but I recommend the first method. |
| 11 |
|
| 12 |
Robert |
| 13 |
|
| 14 |
Kosta Todorovic wrote: |
| 15 |
> I've added a portage overlay with a unmasked libstdc++ ebuild and |
| 16 |
> added libstdc++ to livecd-stage1.spec but when i build livecd-stage1 i |
| 17 |
> get the following error: |
| 18 |
> |
| 19 |
> !!! Digest verification Failed: |
| 20 |
> !!! /usr/portage/sys-libs/libstdc++-v3/libstdc++-v3-3.3.3-r1.ebuild |
| 21 |
> !!! Reason: Filesize does not match recorded size |
| 22 |
> |
| 23 |
> |
| 24 |
> |
| 25 |
> |
| 26 |
> |
| 27 |
> |
| 28 |
> |
| 29 |
> On 4/22/05, Chris Gianelloni <wolf31o2@g.o> wrote: |
| 30 |
> |
| 31 |
>>On Fri, 2005-04-22 at 19:18 +0400, Kosta Todorovic wrote: |
| 32 |
>> |
| 33 |
>>>I believe Chris was giving me a solution that meant not modifying my |
| 34 |
>>>live portage tree at all. But I guess its not a big deal if i unmask |
| 35 |
>>>it in package.keywords. Could even do it temporarily. |
| 36 |
>> |
| 37 |
>>portage_conf doesn't have to point to *your* /etc/portage, just a |
| 38 |
>>directory with the same layout. It could point to /tmp/portage or |
| 39 |
>>anywhere else that you wished. |
| 40 |
>> |
| 41 |
>> |
| 42 |
>>>On 4/22/05, derek tracy <tracyde@×××××.com> wrote: |
| 43 |
>>> |
| 44 |
>>>>Please correct me if I am wrong, but to solve your problem I would |
| 45 |
>>>>just create a package.keywords file to unmask libstdc++-v3 in your |
| 46 |
>>>>portage_conf directory. Read the examples that get emerged with |
| 47 |
>>>>catalyst if you need further help I can walk you through it but all |
| 48 |
>>>>documentation is included with catalyst. |
| 49 |
>>>> |
| 50 |
>>>>I beleive that the perk to rolling your own portage snapshot is that |
| 51 |
>>>>you can include your portage_overlay that you have setup on the |
| 52 |
>>>>computer that you are building the livecd from. |
| 53 |
>>>> |
| 54 |
>>>>e.g. |
| 55 |
>>>>I have sys-kernel/love-sources on my host computer's portage overlay |
| 56 |
>>>>directory and when I roll my own portage snapshot it includes that |
| 57 |
>>>>along with the normal portage snapshot. |
| 58 |
>> |
| 59 |
>>-- |
| 60 |
>>Chris Gianelloni |
| 61 |
>>Release Engineering - Strategic Lead/QA Manager |
| 62 |
>>Games - Developer |
| 63 |
>>Gentoo Linux |
| 64 |
>> |
| 65 |
>> |
| 66 |
>> |
| 67 |
> |
| 68 |
> |
| 69 |
-----BEGIN PGP SIGNATURE----- |
| 70 |
Version: GnuPG v1.2.4 (Darwin) |
| 71 |
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org |
| 72 |
|
| 73 |
iD8DBQFCbJdzZwjIiODIZ4oRAulHAJ42NxgPSHBrGxnnE5LfqWWViTLVuwCeJkM6 |
| 74 |
JZ9sGiqhjB3vhCUI+IwGrMU= |
| 75 |
=E/sS |
| 76 |
-----END PGP SIGNATURE----- |
| 77 |
-- |
| 78 |
gentoo-catalyst@g.o mailing list |
Archives