opkg : angstrom fails console-image build

opkg : angstrom fails console-image build

[Marco Cavallini]

Anybody could explain what's happening with opkg in OE recently please?
I saw a patch in ML and I wonder if it will be pushed in order to solve
this problem.

 http://pastebin.com/NhtAP0Re

BTW The same problem occurs with other compilation configurations.
TIA

/marco

Re: opkg : angstrom fails console-image build

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 21-07-10 16:31, Marco Cavallini wrote:
> Anybody could explain what's happening with opkg in OE recently please?
> I saw a patch in ML and I wonder if it will be pushed in order to solve
> this problem.
> 
>  http://pastebin.com/NhtAP0Re

It looks like you have a local diff to install 'opkg' as well as
'opkg-nogpg-nocurl', which breaks. Solution: remove your local diff.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFMRxriMkyGM64RGpERAhK1AJ9ZUKTULkfpL82eLu2sAdYrzZKVngCfYJLy
vFWj3USeDL0KNk+/xqgdlKk=
=a3yG
-----END PGP SIGNATURE-----

Re: opkg : angstrom fails console-image build

[Marco Cavallini]

Koen Kooi ha scritto, Il 21/07/2010 18:05:
> On 21-07-10 16:31, Marco Cavallini wrote:
>> Anybody could explain what's happening with opkg in OE recently please?
>> I saw a patch in ML and I wonder if it will be pushed in order to solve
>> this problem.
> 
>>  http://pastebin.com/NhtAP0Re
> 
> It looks like you have a local diff to install 'opkg' as well as
> 'opkg-nogpg-nocurl', which breaks. Solution: remove your local diff.

Thank you for answering.

I'm sorry but I dont' understand what do you mean with "local diff", I'm
using a clean OE org.openembedded.dev branch.

TIA

/marco

Re: opkg : angstrom fails console-image build

[Graham Gower]

On 22 July 2010 06:08, Marco Cavallini <koansoftware@gmail.com> wrote:
> Koen Kooi ha scritto, Il 21/07/2010 18:05:
>> On 21-07-10 16:31, Marco Cavallini wrote:
>>> Anybody could explain what's happening with opkg in OE recently please?
>>> I saw a patch in ML and I wonder if it will be pushed in order to solve
>>> this problem.

I assume you're referring to my cleanup patch. This patch doesn't fix
any breakages, its just a simplification.

>>
>>>  http://pastebin.com/NhtAP0Re
>>
>> It looks like you have a local diff to install 'opkg' as well as
>> 'opkg-nogpg-nocurl', which breaks. Solution: remove your local diff.
>
> Thank you for answering.
>
> I'm sorry but I dont' understand what do you mean with "local diff", I'm
> using a clean OE org.openembedded.dev branch.

You have an 'opkg' package and an 'opkg-nogpg-nocurl' package. As far
as I can tell, if you had built from a clean dev tree then there would
be no 'opkg' package. Angstrom currently uses opkg-nogpg-nocurl, so
that is the only package you should have.

This indicates that you have a non clean dev tree, or have had a non
clean dev tree in the past. If you've done a build in the past with
patches applied, then you've reverted the patches, you probably need
to remove your temp dir and start the build again.

-Graham

Re: opkg : angstrom fails console-image build

[Jaap de Jong]

I've made a completely clean build last night and it breaks at the same 
problem.


> You have an 'opkg' package and an 'opkg-nogpg-nocurl' package. As far
> as I can tell, if you had built from a clean dev tree then there would
> be no 'opkg' package. Angstrom currently uses opkg-nogpg-nocurl, so
> that is the only package you should have.
>
> This indicates that you have a non clean dev tree, or have had a non
> clean dev tree in the past. If you've done a build in the past with
> patches applied, then you've reverted the patches, you probably need
> to remove your temp dir and start the build again.
>
> -Graham
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>    

Re: opkg : angstrom fails console-image build

[Graham Gower]

On 22 July 2010 15:47, Jaap de Jong <jaap.dejong@nedap.com> wrote:
> I've made a completely clean build last night and it breaks at the same
> problem.
>

Koen bumped the opkg SRCREV a couple of days ago. One of the recent
opkg changes was to return an error in some erroneous cases which were
incorrectly ignored previously (check_data_file_clashes errors are one
of these cases).

Its possible that this problem was there beforehand and its only now
being caught because of less dumb error checking. Sorry, I don't know
what is causing the issue - you probably need to look at the
dependency graph to see why both opkg and opkg-nogpg-nocurl packages
are being built and installed.

-Graham

Re: opkg : angstrom fails console-image build

[Graham Gower]

On 22 July 2010 16:41, Graham Gower <graham.gower@gmail.com> wrote:
> On 22 July 2010 15:47, Jaap de Jong <jaap.dejong@nedap.com> wrote:
>> I've made a completely clean build last night and it breaks at the same
>> problem.
>>
>
> Koen bumped the opkg SRCREV a couple of days ago. One of the recent
> opkg changes was to return an error in some erroneous cases which were
> incorrectly ignored previously (check_data_file_clashes errors are one
> of these cases).
>
> Its possible that this problem was there beforehand and its only now
> being caught because of less dumb error checking. Sorry, I don't know
> what is causing the issue - you probably need to look at the
> dependency graph to see why both opkg and opkg-nogpg-nocurl packages
> are being built and installed.
>
> -Graham
>

PS: pushing my opkg cleanup patch would probably fix this with no
further need to investigate...

Re: opkg : angstrom fails console-image build

[Martin Jansa]

On Thu, Jul 22, 2010 at 04:56:07PM +0930, Graham Gower wrote:
> On 22 July 2010 16:41, Graham Gower <graham.gower@gmail.com> wrote:
> > On 22 July 2010 15:47, Jaap de Jong <jaap.dejong@nedap.com> wrote:
> >> I've made a completely clean build last night and it breaks at the same
> >> problem.
> >>
> >
> > Koen bumped the opkg SRCREV a couple of days ago. One of the recent
> > opkg changes was to return an error in some erroneous cases which were
> > incorrectly ignored previously (check_data_file_clashes errors are one
> > of these cases).
> >
> > Its possible that this problem was there beforehand and its only now
> > being caught because of less dumb error checking. Sorry, I don't know
> > what is causing the issue - you probably need to look at the
> > dependency graph to see why both opkg and opkg-nogpg-nocurl packages
> > are being built and installed.
> >
> > -Graham
> >
> 
> PS: pushing my opkg cleanup patch would probably fix this with no
> further need to investigate...

I have your patch in my local branch and it's not enough (one has to
remove already staged opkg-nogpg(-nocurl) first).

Regards,
-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com