Mailing List Archive: manually creating manifests with RESTRICT="fetch"

manually creating manifests with RESTRICT="fetch"

chrisfriedt at gmail

Aug 12, 2011, 11:48 AM

Post #1 of 8 (3606 views)

I'm trying to create a couple of ebuilds (for embedded devices) where
the files from SRC_URI must be manually downloaded after accepting the
conditions of a license.

Even after I've downloaded the files, to DISTDIR
(/usr/portage/distfiles), ensuring that they are entered in my SRC_URI
variable, with the RESTRICT=fetch keyword, I'm unable to generate
manifests for the files using "ebuild A/B/B.ebuild digest" because it
tries to fetch the files anyway.

Is there any way to generate the manifest file using 'ebuild' so that
it will just read the files from my DISTDIR rather than trying to
fetch them?

The "--force" option does not help, nor does the
FEATURES="assume-digest" or FEATURES="digest".

"arm*-emerge --version" is

Portage 2.1.9.42 (default/linux/arm/10.0, gcc-4.4.5, unavailable, 3.0.0 x86_64

Cheers,

Chris

Re: manually creating manifests with RESTRICT="fetch" [ In reply to ]

chrisfriedt at gmail

Aug 12, 2011, 11:55 AM

Post #2 of 8 (3571 views)

On Fri, Aug 12, 2011 at 2:48 PM, Christopher Friedt
<chrisfriedt@gmail.com> wrote:
> Is there any way to generate the manifest file using 'ebuild' so that
> it will just read the files from my DISTDIR rather than trying to
> fetch them?

Got it...

FETCHCOMMAND="echo" ebuild A/B/B.ebuild digest

Re: Re: manually creating manifests with RESTRICT="fetch" [ In reply to ]

lavi.kfir at gmail

Aug 12, 2011, 2:23 PM

Post #3 of 8 (3563 views)

On Fri, Aug 12, 2011 at 9:55 PM, Christopher Friedt
<chrisfriedt@gmail.com>wrote:

> On Fri, Aug 12, 2011 at 2:48 PM, Christopher Friedt
> <chrisfriedt@gmail.com> wrote:
> > Is there any way to generate the manifest file using 'ebuild' so that
> > it will just read the files from my DISTDIR rather than trying to
> > fetch them?
>
> Got it...
>
> FETCHCOMMAND="echo" ebuild A/B/B.ebuild digest
>
> But this is not the solution!
I have the same tree for my embedded systems, and I do the same as you.
My header looks like this:
EAPI="3"
inherit cmake-utils flag-o-matic
MY_P="${P}-Source"
SRC_URI="${MY_P}.tar.bz2"
RESTRICT="fetch" # This file resides locally and can't be fetched

Please check the EAPI you use, maybe it needs to change.
Also look close on the SRC_URI, it has just the name of the file.
I'm also using repoman to generate all my manifests like this:
cd portage_local_tree; repoman -f manifest

This is much better way to do it.

Regards,
Kfir

Re: Re: manually creating manifests with RESTRICT="fetch" [ In reply to ]

chrisfriedt at gmail

Aug 12, 2011, 4:00 PM

Post #4 of 8 (3564 views)

On Fri, Aug 12, 2011 at 5:23 PM, Kfir Lavi <lavi.kfir@gmail.com> wrote:
> But this is not the solution!
> I have the same tree for my embedded systems, and I do the same as you.
> My header looks like this:
> EAPI="3"
> inherit cmake-utils flag-o-matic
> MY_P="${P}-Source"
> SRC_URI="${MY_P}.tar.bz2"
> RESTRICT="fetch" # This file resides locally and can't be fetched
>
> Please check the EAPI you use, maybe it needs to change.
> Also look close on the SRC_URI, it has just the name of the file.
> I'm also using repoman to generate all my manifests like this:
> cd portage_local_tree; repoman -f manifest

Hmm... I'm using EAPI=4 in this ebuild. The SRC_URI is OK, since it
works with FETCHCOMMAND=echo and properly hashes the files in DISTDIR.
The inherit line is unnecessary AFAIK.

I wouldn't doubt that it was a bug in the portage version I'm using.
It's been 43 days since my last emerge --sync, but I can't update ATM
because I don't want to break any APIs in the (rather large) project
I'm building right now.

Oh well - problem has been solved anyway.

C

Re: Re: manually creating manifests with RESTRICT="fetch" [ In reply to ]

lavi.kfir at gmail

Aug 13, 2011, 12:14 AM

Post #5 of 8 (3567 views)

On Sat, Aug 13, 2011 at 2:00 AM, Christopher Friedt
<chrisfriedt@gmail.com>wrote:

> On Fri, Aug 12, 2011 at 5:23 PM, Kfir Lavi <lavi.kfir@gmail.com> wrote:
> > But this is not the solution!
> > I have the same tree for my embedded systems, and I do the same as you.
> > My header looks like this:
> > EAPI="3"
> > inherit cmake-utils flag-o-matic
> > MY_P="${P}-Source"
> > SRC_URI="${MY_P}.tar.bz2"
> > RESTRICT="fetch" # This file resides locally and can't be fetched
> >
> > Please check the EAPI you use, maybe it needs to change.
> > Also look close on the SRC_URI, it has just the name of the file.
> > I'm also using repoman to generate all my manifests like this:
> > cd portage_local_tree; repoman -f manifest
>
> Hmm... I'm using EAPI=4 in this ebuild. The SRC_URI is OK, since it
> works with FETCHCOMMAND=echo and properly hashes the files in DISTDIR.
> The inherit line is unnecessary AFAIK.
>
> I wouldn't doubt that it was a bug in the portage version I'm using.
> It's been 43 days since my last emerge --sync, but I can't update ATM
> because I don't want to break any APIs in the (rather large) project
> I'm building right now.
>
> Oh well - problem has been solved anyway.
>
> C
>
> Yes you right, the inherit line is not needed.
What I was trying to say is that I'm not using FETCHCOMMAND=echo,
and it works for me.

I would also forward this message to gentoo-dev.

Regards,
Kfir

Re: Re: manually creating manifests with RESTRICT="fetch" [ In reply to ]

Aug 13, 2011, 5:17 AM

Post #6 of 8 (3556 views)

Ð’ Ð¡Ð±Ñ‚, 13/08/2011 Ð² 10:14 +0300, Kfir Lavi Ð¿Ð¸ÑˆÐµÑ‚:
> I wouldn't doubt that it was a bug in the portage version I'm
> using.
> It's been 43 days since my last emerge --sync, but I can't
> update ATM
> because I don't want to break any APIs in the (rather large)
> project
> I'm building right now.

Upgrading portage does not breaks API.

> Oh well - problem has been solved anyway.

If something still requires FETCHCOMMAND, I really encourage you to open
bug at bugs.gentoo.org.

> I would also forward this message to gentoo-dev.

Oh, no! :) Bug reports should go to bugs.gentoo.org.

With kind regards,
--
Peter.

Re: Re: manually creating manifests with RESTRICT="fetch" [ In reply to ]

chrisfriedt at gmail

Aug 13, 2011, 5:26 AM

Post #7 of 8 (3557 views)

On Sat, Aug 13, 2011 at 8:17 AM, Peter Volkov <pva@gentoo.org> wrote:
> Oh, no! :) Bug reports should go to bugs.gentoo.org.

Well... I was hoping I could just let this one slide by ... but ok

C

Re: Re: manually creating manifests with RESTRICT="fetch" [ In reply to ]

chrisfriedt at gmail

Aug 13, 2011, 7:23 AM

Post #8 of 8 (3563 views)

Odd... now that I'm trying it again, it's working fine... and I
haven't even touched my PC since yesterday except for email.

Oh well - problem solved in any case.

C

On Sat, Aug 13, 2011 at 8:26 AM, Christopher Friedt
<chrisfriedt@gmail.com> wrote:
> On Sat, Aug 13, 2011 at 8:17 AM, Peter Volkov <pva@gentoo.org> wrote:
>> Oh, no! :) Bug reports should go to bugs.gentoo.org.
>
> Well... I was hoping I could just let this one slide by ... but ok
>
> C
>