From: Chenxiong Qi <qcxhome@yahoo.com>
To: "libabigail@sourceware.org" <libabigail@sourceware.org>
Subject: Re: [Patch] selecting latest build in a stable way
Date: Fri, 01 Jan 2016 00:00:00 -0000 [thread overview]
Message-ID: <076199a8-dc5a-f15b-17d6-11b9d5a91da6@yahoo.com> (raw)
In-Reply-To: <adbd8c76-635a-9c7f-2021-4757304a6a2b@yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 814 bytes --]
On 06/08/2016 08:12 PM, Chenxiong Qi wrote:
>
>
> On 06/08/2016 09:19 AM, Chenxiong Qi wrote:
>> Hi,
>>
>> This patch aims to sort builds of a package by creation_event_id rather
>> than nvr to get the latest build. This is a stable way and a better
>> choice.
>>
>
> Well, while I'm on my way home, I just realized that getting the latest
> build by sorting creation_event_id is not a good choice. For example, a
> packager built package foo-2.0-1.fc25, and then he built an old version
> such as foo-1.0-2.fc25, obviously, the latest build should be the former
> one, which has a smaller creation_event_id than latter's. So, let me
> update patch with another way. Sorry for this.
>
It's done. rpm.labelCompare is used this time to compare two NVRs while
sorting builds by sorted.
--
Regards,
Chenxiong Qi
[-- Attachment #2: 0001-selecting-latest-build-in-a-stable-way.patch --]
[-- Type: application/octetstream, Size: 7935 bytes --]
prev parent reply other threads:[~2016-06-08 14:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-01 0:00 Chenxiong Qi
2016-01-01 0:00 ` Chenxiong Qi
2016-01-01 0:00 ` Dodji Seketeli
2016-01-01 0:00 ` Chenxiong Qi
2016-01-01 0:00 ` Dodji Seketeli
2016-01-01 0:00 ` Chenxiong Qi
2016-01-01 0:00 ` Dodji Seketeli
2016-01-01 0:00 ` Chenxiong Qi [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=076199a8-dc5a-f15b-17d6-11b9d5a91da6@yahoo.com \
--to=qcxhome@yahoo.com \
--cc=cqi@redhat.com \
--cc=libabigail@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).