Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] e2fsprogs: remove the extra dot from the recipe filename
Date: Wed, 22 Jun 2016 17:00:11 +0200	[thread overview]
Message-ID: <20160622150011.GB4153@jama> (raw)
In-Reply-To: <CAJTo0Lar56vj6VOo097yhbTMtAx78PsS7kU3Yeh_7xb-XpBy0g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 829 bytes --]

On Wed, Jun 22, 2016 at 03:45:27PM +0100, Burton, Ross wrote:
> On 22 June 2016 at 15:42, Martin Jansa <martin.jansa@gmail.com> wrote:
> 
> > WARNING: e2fsprogs-1.43-r0 do_packagedata: QA Issue: Package version for
> > package e2fsprogs-locale-uk went backwards which would break package feeds
> > from (0:1.43.-r0.1 to 0:1.43-r0.0) [version-going-backwards]
> >
> 
> Have you checked what opkg/rpm actually think about this?  Maybe the sanity
> test is broken.

No, but opkg-compare-versions from opkg-utils thinks the same:

OE @ ~/projects/opkg-utils $ ./opkg-compare-versions 0:1.43-r0.0 \>\> 0:1.43.-r0.0
OE @ ~/projects/opkg-utils $ echo $?
1

Also note that EXTENDPRAUTO is reset to 0, because of PV change (which
is saved by RPs PR bump).

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2016-06-22 14:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-21 10:01 [PATCH] e2fsprogs: remove the extra dot from the recipe filename Alexander Kanavin
2016-06-22 14:42 ` Martin Jansa
2016-06-22 14:45   ` Burton, Ross
2016-06-22 15:00     ` Martin Jansa [this message]
2016-06-23 12:47       ` Alexander Kanavin

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=20160622150011.GB4153@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /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