From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: org.oe.dev sane-srcrev: wind back opkg-native to 4452 *again*
Date: Mon, 16 Jun 2008 17:25:44 +0200 [thread overview]
Message-ID: <g360lp$bkf$2@ger.gmane.org> (raw)
In-Reply-To: <200806161641.50186.mickey@vanille-media.de>
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
next prev parent reply other threads:[~2008-06-16 15:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080616142816.5346618928D@amethyst.openembedded.net>
2008-06-16 14:41 ` [oe-commits] org.oe.dev sane-srcrev: wind back opkg-native to 4452 *again* Michael 'Mickey' Lauer
2008-06-16 15:25 ` Koen Kooi [this message]
2008-06-16 15:50 ` Rolf Leggewie
2008-07-04 13:37 ` Rolf Leggewie
2008-06-16 22:57 ` Michael 'Mickey' Lauer
2008-06-17 12:05 ` Rod Whitby
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='g360lp$bkf$2@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.