From: "Klauer, Daniel" <Daniel.Klauer@gin.de>
To: Herve Jourdain <herve.jourdain@neuf.fr>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] smartpm: Don't ignore error if RPM transaction fails without problems
Date: Wed, 8 Jun 2016 15:43:20 +0000 [thread overview]
Message-ID: <1465400599707.30401@gin.de> (raw)
In-Reply-To: <02b101d1c184$93336d80$b99a4880$@neuf.fr>
Hello,
> You also need to add another check just before raising the error, or you
> would end up getting an "unknown error" raised there.
> I basically replaced:
> - if (probs is not None) and (not retry):
> + if (probs is not None) and ((len(probs) != 0) or not
> sysconf.has("attempt-install", soft=True)) and (not retry):
Hmm, it sounds like the attempt mode wants to ignore installation failures
(empty problems list) like before the patch, which makes sense to me. Afterall,
attempt mode wants to try installation and ignore failures. So it seems good to
fix this regression too.
However, I wonder why it never ignored a non-empty problems list, which would
also trigger an error. Maybe that case just never happens in practice, because
it's always just file conflicts. Those trigger a retry, which prevents the error
from being raised.
> BUT reflecting on the whole scheme, I'm wondering how it will work in case
> of file found conflict, since the problem package gets removed from the
> list, but the list is committed again, with most packages already
> installed...
> I therefore wonder that there could be the same error that I got in the end,
> i.e failing with package already installed - which should not fail for
> attempt only.
Indeed, I'm curious about that too...
If you could put together the patch, that would be great and fine with me.
Thanks,
Daniel
next prev parent reply other threads:[~2016-06-08 15:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 12:54 smartpm: Don't ignore error if RPM transaction fails without problems Klauer, Daniel
2016-05-17 12:58 ` [PATCH] " Klauer, Daniel
2016-06-07 13:17 ` Herve Jourdain
2016-06-08 11:35 ` Klauer, Daniel
[not found] ` <1465381435600.39214@gin.de>
2016-06-08 12:52 ` Herve Jourdain
2016-06-08 15:43 ` Klauer, Daniel [this message]
2016-06-08 16:00 ` Herve Jourdain
2016-06-08 16:05 ` Mark Hatle
2016-06-08 16:17 ` Herve Jourdain
2016-06-08 16:47 ` Mark Hatle
2016-06-09 7:47 ` ***SPAM*** " Herve Jourdain
2016-06-09 8:19 ` Klauer, Daniel
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=1465400599707.30401@gin.de \
--to=daniel.klauer@gin.de \
--cc=herve.jourdain@neuf.fr \
--cc=openembedded-core@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