Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Aníbal Limón" <anibal.limon@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] busybox: fix upgrade problem with deb packages
Date: Thu, 09 Oct 2014 17:42:19 -0500	[thread overview]
Message-ID: <54370F4B.7030207@linux.intel.com> (raw)
In-Reply-To: <54358935.30909@opendreambox.org>

Andreas,

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?

Best regards.


On 08/10/14 13:57, Andreas Oberritter wrote:
> On 08.10.2014 20:00, Aníbal Limón wrote:
>> On 07/10/14 18:39, Andreas Oberritter wrote:
>>> On 08.10.2014 00:49, Aníbal Limón wrote:
>>>> I reviewed the patches and looks good, only i have a comment
>>>> in this file,
>>>>
>>>> http://git.openembedded.org/openembedded-core-contrib/commit/?h=obi/dora&id=a5f18409d1bf2877f898b902cafc317cbf7462e4
>>>>
>>>>
>>>>
>>>> I didn't know if the same apply for rpm and ipk.
>>> I guess so. I'm pretty certain that opkg behaves just like dpkg in this
>>> regard. I never used rpm, though.
>>>
>>> To reproduce the problem, boot an image containing busybox, but not
>>> bash. Then install bash and deinstall it again. Deinstallation fails,
>>> resulting in a dangling symlink (/bin/sh -> /bin/bash).
>>>
>>>> There are a lot of patches,  Do you have a plan to port them to master?
>>>>
>>>> I can help with that.
>>> I'd like to, but I won't have time to do any testing with master during
>>> the next weeks. I could rebase my patches onto master and provide a tree
>>> for you to test. Or you could cherry-pick whatever patches you like and
>>> submit them to the mailing list after testing. Most patches should apply
>>> without changes, but those touching rootfs_deb.bbclass and
>>> package_deb.bbclass will need some porting. What do you think?
>> I think we need to port these patches in small changes in order to do
>> a good review,
> I already rebased all patches today, and just pushed it to this untested
> branch:
>
> http://git.openembedded.org/openembedded-core-contrib/log/?h=obi/master
>
>> I propose,
>>
>> 1. dpkg update-alternatives offline
>> 2. apt-get upgrade version
>> 3. another minor changes like pkg-config
>>
>> Makes sense?
> OK. Here are some topic branches:
>
> http://git.openembedded.org/openembedded-core-contrib/log/?h=obi/dpkg-ua
> http://git.openembedded.org/openembedded-core-contrib/log/?h=obi/apt
> http://git.openembedded.org/openembedded-core-contrib/log/?h=obi/dpkg-misc
>
> Regards,
> Andreas



  reply	other threads:[~2014-10-09 22:44 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 [this message]
2014-10-09 23:31             ` Andreas Oberritter

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=54370F4B.7030207@linux.intel.com \
    --to=anibal.limon@linux.intel.com \
    --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