All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.kabel.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: RFC: splitting deploy/ipk into subarchs
Date: Tue, 20 Feb 2007 14:48:40 +0100	[thread overview]
Message-ID: <45DAFC38.40000@dominion.kabel.utwente.nl> (raw)
In-Reply-To: <45DAAEF4.50701@dominion.kabel.utwente.nl>

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

Koen Kooi schreef:

> Marcin and I merged a slightly different version of this today.

As some people found out, their upload scripts broke with this change. I'm sorry that
happened, but those scripts are more easily fixed than ipkg-utils :(
Due to bug in ipkg-utils being I haven't been using a straight rsync for a while now, so
for the curious:

rsync -az . user@remote.host:/feed/location/unsorted ; ssh user@remote.host 'cd
feed/location/unsorted ; sh sort.sh'

where sort.sh is http://www.angstrom-distribution.org/unstable/feed/unsorted/sort.sh.txt

And while you're at it, check wether your rsync uses --delete, and if not, check if you
remove Packages* before running ipkg-make-index. If that wasn't the case you have been
unknowingly suffering for a buggy Packages* for a while now. Combined with ipkg .163 on
the device I suspect 'ipkg upgrade' doesn't behave as deterministically as you might think.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFF2vw3MkyGM64RGpERAv9OAJ4ij31yxqCC8M855mQ8hUvhdj56UQCfVk4z
zfpTSMD0IajJc9VRF2dyuQA=
=rvcF
-----END PGP SIGNATURE-----



  reply	other threads:[~2007-02-20 13:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-19 11:18 RFC: splitting deploy/ipk into subarchs Koen Kooi
2007-02-19 11:59 ` Marcin Juszkiewicz
2007-02-19 12:30   ` Koen Kooi
2007-02-20  8:19     ` Koen Kooi
2007-02-20 13:48       ` Koen Kooi [this message]
2007-02-23  2:26         ` Matthias Hentges
2007-02-23  8:05           ` Koen Kooi
2007-02-24  0:03             ` Matthias Hentges
2007-02-24 11:18             ` Michael Rozdoba

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=45DAFC38.40000@dominion.kabel.utwente.nl \
    --to=koen@dominion.kabel.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.