Re: [oe-commits] org.oe.dev sane-srcrev: wind back opkg-native to 4452 *again*

Re: [oe-commits] org.oe.dev sane-srcrev: wind back opkg-native to 4452 *again*

[Michael 'Mickey' Lauer]

Am Montag 16 Juni 2008 16:28:16 schrieb koen commit:
> sane-srcrev: wind back opkg-native to 4452 *again*

Koen, what kind of problem are you seeing? If it's the "could not create 
administrative lock", this has been fixed by me days ago.

If not, please point me to the bug entry for your problem?

-- 
:M:

Re: org.oe.dev sane-srcrev: wind back opkg-native to 4452 *again*

[Koen Kooi]

Michael 'Mickey' Lauer wrote:
> Am Montag 16 Juni 2008 16:28:16 schrieb koen commit:
>> sane-srcrev: wind back opkg-native to 4452 *again*
>
> Koen, what kind of problem are you seeing? If it's the "could not create
> administrative lock", this has been fixed by me days ago.

The "could not create administrative lock" is still present with 
packaged-staging yesterday evening.

> If not, please point me to the bug entry for your problem?

No bug entry, since bugs get closed on an arbitrary basis anyway

Re: org.oe.dev sane-srcrev: wind back opkg-native to 4452 *again*

[Rolf Leggewie]

Koen Kooi wrote:
> No bug entry, since bugs get closed on an arbitrary basis anyway

Are they?

I'd be interested to learn about who you are accusing of doing such
things.  Please point out some examples, so I can take a look at the
history and make sure the user in question respects the well-being of
the OE bug tracker.

Re: org.oe.dev sane-srcrev: wind back opkg-native to 4452 *again*

[Michael 'Mickey' Lauer]

Am Montag 16 Juni 2008 17:25:44 schrieb Koen Kooi:
> Michael 'Mickey' Lauer wrote:
> > Am Montag 16 Juni 2008 16:28:16 schrieb koen commit:
> >> sane-srcrev: wind back opkg-native to 4452 *again*
> >
> > Koen, what kind of problem are you seeing? If it's the "could not create
> > administrative lock", this has been fixed by me days ago.
>
> The "could not create administrative lock" is still present with
> packaged-staging yesterday evening.

Ok, then I suggest fixing it modelled after the fix I did to 
rootfs_ipk.bbclass: 
http://git.openembedded.net/?p=org.openembedded.dev.git;a=commitdiff;h=91b5ad2ddfa2322165d90e6cedece480bd38d18b                

The alternative is pinpointing it 4452 forever since it's unlikely the 
behaviour of needing its libdir during 'update' will be changed.

> > If not, please point me to the bug entry for your problem?
>
> No bug entry, since bugs get closed on an arbitrary basis anyway

Oh, sure. *yawn*

-- 
:M:

Re: org.oe.dev sane-srcrev: wind back opkg-native to 4452 *again*

[Rod Whitby]

Koen Kooi wrote:
> Michael 'Mickey' Lauer wrote:
>> If not, please point me to the bug entry for your problem?
> 
> No bug entry, since bugs get closed on an arbitrary basis anyway

 From http://dominion.thruhere.net/koen/cms/community-interaction
(Koen's Blog):

<quote author=Koen>
I have given up on trying to get people to file bugs at the right 
bugtracker and have adopted the rather cynical filosophy of "If you 
don't care enough to file a bug, I don't care enough to look into your 
supposed problem".
</quote>

Classic.

-- Rod

Re: org.oe.dev sane-srcrev: wind back opkg-native to 4452 *again*

[Rolf Leggewie]

Rolf Leggewie wrote:
> Koen Kooi wrote:
>> No bug entry, since bugs get closed on an arbitrary basis anyway
> 
> Are they?

no, of course not.  Just as I thought a bunch of bogus claims from
someone trying to thinly cover his ass.