From: Alejandro del Castillo <alejandro.delcastillo@ni.com>
To: Stefan Agner <stefan@agner.ch>,
<openembedded-core@lists.openembedded.org>
Cc: Stefan Agner <stefan.agner@toradex.com>
Subject: Re: [PATCH][jethro] opkg: backport fix for double remove of packges
Date: Sat, 23 Apr 2016 15:44:39 -0500 [thread overview]
Message-ID: <571BDEB6.3010906@ni.com> (raw)
In-Reply-To: <1461269276-23269-1-git-send-email-stefan@agner.ch>
On 04/21/2016 03:07 PM, Stefan Agner wrote:
> From: Stefan Agner <stefan.agner@toradex.com>
>
> Backport the fix 7885da3974 ("pkg_get_provider_replacees: do not
> add installed pkg to replacee list"). This avoids opkg trying to
> remove a package twice e.g. when upgrading.
>
> Suggested-by: Alejandro del Castillo <alejandro.delcastillo@ni.com>
> Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
> ---
this bug also affects opkg 0.3.1 (included in krogoth)...can it be
applied to krogoth too?
--
Cheers,
Alejandro
next prev parent reply other threads:[~2016-04-23 20:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-21 20:07 [PATCH][jethro] opkg: backport fix for double remove of packges Stefan Agner
2016-04-23 20:44 ` Alejandro del Castillo [this message]
2016-04-25 17:50 ` Stefan Agner
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=571BDEB6.3010906@ni.com \
--to=alejandro.delcastillo@ni.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=stefan.agner@toradex.com \
--cc=stefan@agner.ch \
/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