mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Robert Schwebel <r.schwebel@pengutronix.de>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [ANNOUNCE] PTXdist 2023.07.1 released
Date: Fri, 28 Jul 2023 10:08:32 +0200	[thread overview]
Message-ID: <ZMN3gBYkAP6M+Dnd@pengutronix.de> (raw)
In-Reply-To: <ZKzogT0cDd39HUwX@pengutronix.de>

Hi,

On Tue, Jul 11, 2023 at 07:28:33AM +0200, Robert Schwebel wrote:
> On Wed, Jul 05, 2023 at 03:51:02PM +0200, Michael Olbrich wrote:
> > I'm happy to announce that I've just released ptxdist-2023.07.0.
> 
> It turned out that there is a bug in the 'nested ptxdist execution'
> feature that lets 'ptxdist platform <path-to-platformconfig>' and
> similar operations return a non-zero retval, which (while the actual
> operation still works) breaks at automatic builds in our test farm.
> 
> As Michael is currently on vacation, we decided yesterday to revert the
> offending commit and release a ptxdist-2023.07.1, which is now on the
> server.
> 
> A proper fix will follow later on.
> 
> Shortlog:
> 
> Marc Kleine-Budde (1):
>       Revert "add support for nested PTXdist execution"

Note that the problem is mostly cosmetic. You get a non-zero return value,
but the actual operations works. The affected code is actually there for
"ptxdist menu". In that case, ptxdist remains running when a new
platformconfig is selected, so it must be configured again and this
triggers the bug. In this case, ptxdist exits and "ptxdist menu" must be
started again. Anyways, this should now be properly fixed with
a0f7c9471ddf6edf1ebfd48f1d5ff7bac40c4a63 ("ptxdist: fix nested ptxdist
sanity check") in master.

Regards,
Michael

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



      reply	other threads:[~2023-07-28  8:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-05 13:51 [ptxdist] [ANNOUNCE] PTXdist 2023.07.0 released Michael Olbrich
2023-07-11  5:28 ` [ptxdist] [ANNOUNCE] PTXdist 2023.07.1 released Robert Schwebel
2023-07-28  8:08   ` Michael Olbrich [this message]

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=ZMN3gBYkAP6M+Dnd@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    --cc=r.schwebel@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