From: Saul Wold <sgw@linux.intel.com>
To: Paul Barker <paul@paulbarker.me.uk>
Cc: Yocto Project Discussion <yocto@yoctoproject.org>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Package Upgrading for 1.8
Date: Thu, 30 Oct 2014 14:50:10 -0700 [thread overview]
Message-ID: <5452B292.6050204@linux.intel.com> (raw)
In-Reply-To: <CANyK_8cJA7F3CTZ8psAUaAz-qBG31cM2fJEsd6VLX-ALcxBoKg@mail.gmail.com>
On 10/30/2014 12:07 PM, Paul Barker wrote:
> On 30 October 2014 18:21, Saul Wold <sgw@linux.intel.com> wrote:
>>
>> Folks,
>>
>> Just a reminder now that master is open again for patches, now is a great
>> time to consider doing package Updates. Based on some rough estimates from
>> 1.7 we did around 300 updates from 34 contributors, that got us about 73%
>> packages upgrades.
>>
>> We currently have about 180 packages due to be updated based on the Package
>> Reporting from this last week, about 65 of those where not updated in 1.7 so
>> should be given some priority (see attached file), there are also 10 that
>> need maintainers, let me know if you are interested in any of them.
>
> I don't see opkg, opkg-utils or libarchive in those emails or on
> http://packages.yoctoproject.org/upgradepkgname. Any particular reason
> they're missing?
>
I will look into that, could be that the code in the fetcher is not
catching opkg correctly, we are working on updating that code to do a
better job.
> I'll send an upgrade to opkg v0.2.3 tomorrow, then further upgrades
> once they're available.
>
> Once I've merged a patch by Jian Liu to opkg-utils there will likely
> be an opkg-utils SRCREV update.
>
> I have my eye on libarchive as well as I'm using it within the
> development versions of opkg. I'm subscribed to their announcement
> mailing list so I'll know when a new release is made.
>
Thanks, saw your email earlier, thanks your hard work on the OPKG* know
it's appreciated.
Sau!
> Cheers,
>
WARNING: multiple messages have this Message-ID (diff)
From: Saul Wold <sgw@linux.intel.com>
To: Paul Barker <paul@paulbarker.me.uk>
Cc: Yocto Project Discussion <yocto@yoctoproject.org>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] Package Upgrading for 1.8
Date: Thu, 30 Oct 2014 14:50:10 -0700 [thread overview]
Message-ID: <5452B292.6050204@linux.intel.com> (raw)
In-Reply-To: <CANyK_8cJA7F3CTZ8psAUaAz-qBG31cM2fJEsd6VLX-ALcxBoKg@mail.gmail.com>
On 10/30/2014 12:07 PM, Paul Barker wrote:
> On 30 October 2014 18:21, Saul Wold <sgw@linux.intel.com> wrote:
>>
>> Folks,
>>
>> Just a reminder now that master is open again for patches, now is a great
>> time to consider doing package Updates. Based on some rough estimates from
>> 1.7 we did around 300 updates from 34 contributors, that got us about 73%
>> packages upgrades.
>>
>> We currently have about 180 packages due to be updated based on the Package
>> Reporting from this last week, about 65 of those where not updated in 1.7 so
>> should be given some priority (see attached file), there are also 10 that
>> need maintainers, let me know if you are interested in any of them.
>
> I don't see opkg, opkg-utils or libarchive in those emails or on
> http://packages.yoctoproject.org/upgradepkgname. Any particular reason
> they're missing?
>
I will look into that, could be that the code in the fetcher is not
catching opkg correctly, we are working on updating that code to do a
better job.
> I'll send an upgrade to opkg v0.2.3 tomorrow, then further upgrades
> once they're available.
>
> Once I've merged a patch by Jian Liu to opkg-utils there will likely
> be an opkg-utils SRCREV update.
>
> I have my eye on libarchive as well as I'm using it within the
> development versions of opkg. I'm subscribed to their announcement
> mailing list so I'll know when a new release is made.
>
Thanks, saw your email earlier, thanks your hard work on the OPKG* know
it's appreciated.
Sau!
> Cheers,
>
next prev parent reply other threads:[~2014-10-30 21:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 18:21 Package Upgrading for 1.8 Saul Wold
2014-10-30 18:51 ` Khem Raj
2014-10-30 18:51 ` [OE-core] " Khem Raj
2014-10-30 19:07 ` Paul Barker
2014-10-30 19:07 ` [OE-core] " Paul Barker
2014-10-30 21:50 ` Saul Wold [this message]
2014-10-30 21:50 ` Saul Wold
2014-10-30 20:14 ` akuster
2014-10-30 20:14 ` [OE-core] " akuster
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=5452B292.6050204@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul@paulbarker.me.uk \
--cc=yocto@yoctoproject.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.