All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Oberritter <obi@opendreambox.org>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] busybox: fix upgrade problem with deb packages
Date: Fri, 10 Oct 2014 01:31:23 +0200	[thread overview]
Message-ID: <54371ACB.3020009@opendreambox.org> (raw)
In-Reply-To: <54370F4B.7030207@linux.intel.com>

On 10.10.2014 00:42, Aníbal Limón wrote:
> Now i'm testing dpkg-ua changes, my first impressions are,
> 
> Some work in order to use dpkg-ua version instead of opkg-utils (default),
> files meta/conf/layer.con and
> meta/recipes-core/packagegroups/packagegroup-self-hosted.bb.
> 
> Currently isn't created symlinks for tools in target image.
> 
> Comments?

Sounds like this problem:

http://comments.gmane.org/gmane.comp.handhelds.openembedded.core/47626

Did update-alternatives get staged correctly into your native sysroot?

If opkg-utils-native was built after dpkg-native, it may have
overwritten update-alternatives. To avoid this I've put the following
into my local.conf:

INHERIT += "blacklist"
PNBLACKLIST[opkg-utils-native] = "opkg-utils-native must not be built
when using debian packages"

I'm not sure whether this may cause a similar effect.

Regards,
Andreas



      reply	other threads:[~2014-10-09 23:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-07 20:00 [PATCH] busybox: fix upgrade problem with deb packages Aníbal Limón
2014-10-07 20:36 ` Andreas Oberritter
2014-10-07 22:49   ` Aníbal Limón
2014-10-07 23:39     ` Andreas Oberritter
2014-10-08 18:00       ` Aníbal Limón
2014-10-08 18:57         ` Andreas Oberritter
2014-10-09 22:42           ` Aníbal Limón
2014-10-09 23:31             ` Andreas Oberritter [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=54371ACB.3020009@opendreambox.org \
    --to=obi@opendreambox.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.