All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Paul Barker <paul@paulbarker.me.uk>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: opkg-0.2.2 release
Date: Sun, 06 Apr 2014 13:08:27 +0100	[thread overview]
Message-ID: <1396786107.24597.17.camel@ted> (raw)
In-Reply-To: <CANyK_8dPFDShPAvhYt+89j0Mr4fjzpeMt28HrwNAZrN8qfnS4w@mail.gmail.com>

On Tue, 2014-04-01 at 22:18 +0100, Paul Barker wrote:
> Hi all,
> 
> I've just released opkg-0.2.2 with the following bugfixes (issue
> numbers refer to the opkg issue list):
> 
> - Fix '--force-reinstall' flag so that it acts as an upgrade rather than
>   removing possibly critical packages before reinstall (issue 71)
> 
> - Symlinks are now correctly removed during package uninstall (issue 91)
> 
> - Fixed help and manual pages to reflect that shell globs not true regexps are
>   accepted by opkg (issue 107)
> 
> - The error message "no valid architecture" is no longer given when the
>   architecture of a package is valid but incompatible with the current system.
> 
> This is a bugfix only release with no other significant changes.
> 
> I have also rebased the patches against opkg in oe-core against the
> new release and checked that they still apply and that the result
> builds with recent oe-core master. The result was tested on qemuarm by
> running 'opkg update' against a package feed and installing a few new
> packages.

Thanks for checking this, it certainly helps and is appreciated!

> Do we want to try to get this in to the upcoming Yocto release or
> shall I delay the recipe upgrade until after the release? If you want
> it for the upcoming release I'll re-run my tests locally just to be
> sure it's looking good and then send a patch.

We're about to roll -rc3 so this is getting late in the cycle to change
the package manager. Having said that this sounds like bug fixes which
would be nice to have.

I think I'm leaning to not taking it right now as it is really too late
but I'm open to other views on this...

Cheers,

Richard




  reply	other threads:[~2014-04-06 12:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-01 21:18 opkg-0.2.2 release Paul Barker
2014-04-06 12:08 ` Richard Purdie [this message]
2014-04-06 15:36   ` Paul Barker

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=1396786107.24597.17.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul@paulbarker.me.uk \
    /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.