From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [ANNOUNCE] PTXdist 2014.07.0 released
Date: Fri, 4 Jul 2014 12:56:14 +0200 [thread overview]
Message-ID: <20140704105614.GG5390@pengutronix.de> (raw)
In-Reply-To: <ed797096efa99e13758cfce7c12c0b59@idefix.lespocky.dyndns.org>
Hi,
On Fri, Jul 04, 2014 at 09:44:00AM +0200, Alexander Dahl wrote:
> 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
>
>
> :-/
Should be fixed in master now. So collections are broken in
ptxdist-2014.07.0 :-(
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-07-04 10:56 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
2014-07-04 10:56 ` Michael Olbrich [this message]
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=20140704105614.GG5390@pengutronix.de \
--to=m.olbrich@pengutronix.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