From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [ANNOUNCE] PTXdist 2014.07.0 released
Date: Fri, 04 Jul 2014 09:44:00 +0200 [thread overview]
Message-ID: <ed797096efa99e13758cfce7c12c0b59@idefix.lespocky.dyndns.org> (raw)
In-Reply-To: <20140703160934.GF5390@pengutronix.de>
Hei hei,
Am 2014-07-03 18:09, schrieb Michael Olbrich:
> - With the new option '--auto-version' PTXdist will execute the correct
> PTXdist version as defined by the ptxconfig. <prefix>/bin/ptxdist is now
> a wrapper script that adds this option. This is useful when working with
> multiple PTXdist versions.
This means you have to explicitly use e.g. `ptxdist-2014.07.0 migrate`
if you want to migrate a project to a new version, because `ptxdist
migrate` would lead to calling the current version to be called with
migrate, which is (hopefully) a no-op. ;-)
Anyway, starting from a ptxdist 2014.06.0 BSP, `ptxdist-2014.07.0
migrate` leads to the following error here:
#
# configuration written to .config
#
/usr/local/lib/ptxdist-2014.07.0/config/collection/Kconfig:30: can't
open file "generated/ptx_collection.in"
ptxdist: 'collection oldconfig' returned with an error
:-/
Not tried the other things yet.
Greets
Alex
--
»With the first link, the chain is forged. The first speech censured,
the first thought forbidden, the first freedom denied, chains us all
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601 D1D5 8FBA 7744 CC87 10D0 ***
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-07-04 7:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-03 16:09 Michael Olbrich
2014-07-04 7:44 ` Alexander Dahl [this message]
2014-07-04 10:56 ` Michael Olbrich
2014-07-04 12:34 ` Alexander Dahl
2014-07-04 20:35 ` Michael Olbrich
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=ed797096efa99e13758cfce7c12c0b59@idefix.lespocky.dyndns.org \
--to=post@lespocky.de \
--cc=ptxdist@pengutronix.de \
/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