All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Burton, Ross" <ross.burton@intel.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] binutils: fix PV to respect upstream tag and also cve database
Date: Thu, 28 Mar 2019 13:17:11 +0000	[thread overview]
Message-ID: <CAJTo0LYwZ0WNNsA0Wm+uzAsuAHHiRzKOE=aGZZOkRfa56Furpg@mail.gmail.com> (raw)
In-Reply-To: <CAJTo0La3fza0yn=dcWYWjSh00oJD1NQg8UMDOYSN0w_y4qODXw@mail.gmail.com>

On Thu, 28 Mar 2019 at 13:15, Burton, Ross <ross.burton@intel.com> wrote:
> On Thu, 28 Mar 2019 at 12:07, Alexander Kanavin <alex.kanavin@gmail.com> wrote:
> > The problem with setting PV properly, is that 2.32 is less than 2.32.0
> > and will cause the 'version going backwards' problem. But if RP/Khem
> > are fine with it, I would prefer your patch.
>
> I just had a look at the code in bitbake and yes, it actually even
> tests that 1 < 1.0.  I'd say that there's an argument for handling .0
> releases specially and considering 2.32 == 2.32.0.

Of course that test exists for people using feeds, and at least dpkg
thinks 2.32 < 2.32.0, so even if we changed the test the feed would
still be broken.

Ross


  reply	other threads:[~2019-03-28 13:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-28 12:13 [PATCH 0/1] binutils: fix PV to respect upstream tag and also cve database Chen Qi
2019-03-28 12:13 ` [PATCH 1/1] " Chen Qi
2019-03-28 12:06   ` Alexander Kanavin
2019-03-28 13:15     ` Burton, Ross
2019-03-28 13:17       ` Burton, Ross [this message]
2019-03-28 13:46         ` Tom Rini
2019-03-28 13:50           ` Burton, Ross
2019-03-28 14:08             ` Alexander Kanavin
2019-03-28 14:25               ` Tom Rini
2019-03-28 14:38                 ` Burton, Ross
2019-03-28 14:56                   ` Tom Rini
2019-03-28 14:37               ` Burton, Ross

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='CAJTo0LYwZ0WNNsA0Wm+uzAsuAHHiRzKOE=aGZZOkRfa56Furpg@mail.gmail.com' \
    --to=ross.burton@intel.com \
    --cc=alex.kanavin@gmail.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 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.