From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Opkg removing not-really-orphaned files during opkg upgrade
Date: Wed, 02 Jun 2010 15:06:39 +0200 [thread overview]
Message-ID: <hu5l0v$2p2$1@dough.gmane.org> (raw)
In-Reply-To: <20100602111548.GD16035@jama>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 02-06-10 13:15, Martin Jansa wrote:
> Hi,
>
> few times I've run to strange issues with missing files after opkg
> upgrade, now I have simple case there I can guess what happened. Please
> comment if I'm doing something wrong or if it's known issue (but not
> fixed because it's to hard without changing lot of opkg internals?).
Could you respond to
http://groups.google.com/group/opkg-devel/browse_thread/thread/53e8215d02e303d/cda5a90d98cc6e31?lnk=gst&q=orphaned#cda5a90d98cc6e31
with your test case?
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFMBldfMkyGM64RGpERAnOpAJ98JjJ83NDtwVSW58CdiqDQshvLYwCgtc/6
cEGI7GVH84vbU8tL6X1XHbo=
=3QUi
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-06-02 13:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 11:15 Opkg removing not-really-orphaned files during opkg upgrade Martin Jansa
2010-06-02 13:06 ` Koen Kooi [this message]
2010-06-08 1:14 ` Graham Gower
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='hu5l0v$2p2$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox