| Message ID | cover.1521507765.git.denys@ti.com |
|---|---|
| Headers | show |
| Series | Package upgrades | expand |
Ping. It's been 10 days - are there any issues with these updates? On Mon, Mar 19, 2018 at 09:11:06PM -0400, Denys Dmytriyenko wrote: > From: Denys Dmytriyenko <denys@ti.com> > > Upgrades for lzip, hdparm and lz4. > > The following changes since commit c94271d87d16323f920891344642f76dfb3c994f: > > buildperf: measure the size of core-image-sato rootfs (2018-03-16 03:42:03 -0700) > > are available in the git repository at: > > git://push.openembedded.org/openembedded-core-contrib denix/master > > Denys Dmytriyenko (3): > lzip: upgrade 1.19 -> 1.20 > hdparm: upgrade 9.53 -> 9.55 > lz4: upgrade 1.7.4 -> 1.8.1.2 > > .../hdparm/{hdparm_9.53.bb => hdparm_9.55.bb} | 4 +- > .../lzip/{lzip_1.19.bb => lzip_1.20.bb} | 4 +- > ...sts-Makefile-don-t-use-LIBDIR-as-variable.patch | 82 ---------------------- > .../lz4/{lz4_1.7.4.bb => lz4_1.8.1.2.bb} | 10 +-- > 4 files changed, 9 insertions(+), 91 deletions(-) > rename meta/recipes-extended/hdparm/{hdparm_9.53.bb => hdparm_9.55.bb} (90%) > rename meta/recipes-extended/lzip/{lzip_1.19.bb => lzip_1.20.bb} (88%) > delete mode 100644 meta/recipes-support/lz4/files/0001-tests-Makefile-don-t-use-LIBDIR-as-variable.patch > rename meta/recipes-support/lz4/{lz4_1.7.4.bb => lz4_1.8.1.2.bb} (79%) > > -- > 2.7.4 > > -- > _______________________________________________ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
On Thu, Mar 29, 2018 at 3:41 PM, Denys Dmytriyenko <denis@denix.org> wrote:
> Ping. It's been 10 days - are there any issues with these updates?
Only 10 days? :-)
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
On Thu, Mar 29, 2018 at 04:39:27PM -0700, Andre McCurdy wrote: > On Thu, Mar 29, 2018 at 3:41 PM, Denys Dmytriyenko <denis@denix.org> wrote: > > Ping. It's been 10 days - are there any issues with these updates? > > Only 10 days? :-) Yeah, I know, I'm too demanding... :) -- Denys -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
On Thu, Mar 29, 2018 at 5:17 PM, Denys Dmytriyenko <denis@denix.org> wrote: > On Thu, Mar 29, 2018 at 04:39:27PM -0700, Andre McCurdy wrote: >> On Thu, Mar 29, 2018 at 3:41 PM, Denys Dmytriyenko <denis@denix.org> wrote: >> > Ping. It's been 10 days - are there any issues with these updates? >> >> Only 10 days? :-) > > Yeah, I know, I'm too demanding... :) Ross does pick the patches from ml fairly quickly so always check http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=ross/mut or OE-Core's master-next http://git.openembedded.org/openembedded-core/log/?h=master-next from mut to master it might take a while since there are many patches coming in so integration takes time and sometimes there are issues with infra which can delay things, 10 days seems pretty darn good in some cases its years see https://github.com/projectNe10/Ne10/pull/143 in the end as long as it makes upstream. -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
On Thu, Mar 29, 2018 at 06:38:58PM -0700, Khem Raj wrote: > On Thu, Mar 29, 2018 at 5:17 PM, Denys Dmytriyenko <denis@denix.org> wrote: > > On Thu, Mar 29, 2018 at 04:39:27PM -0700, Andre McCurdy wrote: > >> On Thu, Mar 29, 2018 at 3:41 PM, Denys Dmytriyenko <denis@denix.org> wrote: > >> > Ping. It's been 10 days - are there any issues with these updates? > >> > >> Only 10 days? :-) > > > > Yeah, I know, I'm too demanding... :) > > Ross does pick the patches from ml fairly quickly so always check > > http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=ross/mut > > or OE-Core's master-next > > http://git.openembedded.org/openembedded-core/log/?h=master-next > > from mut to master it might take a while since there are many patches coming in > so integration takes time and sometimes there are issues with infra > which can delay > things, Yes, I'm quite aware of all the above - you don't have to mention all the details to me. Still, it's a standard practice to inquire about own patches once in a while. Especially since other similar non-critical updates are merged right away. This is the only way to know if there were any issues with the patches themselves, but Ross forgot or didn't have time to follow up yet. > 10 days seems pretty darn good in some cases its years see > > https://github.com/projectNe10/Ne10/pull/143 > > in the end as long as it makes upstream. Heh, I don't think we should take that as an example to follow... :) -- Denys -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
On 3/29/18 7:34 PM, Denys Dmytriyenko wrote: > On Thu, Mar 29, 2018 at 06:38:58PM -0700, Khem Raj wrote: >> On Thu, Mar 29, 2018 at 5:17 PM, Denys Dmytriyenko <denis@denix.org> wrote: >>> On Thu, Mar 29, 2018 at 04:39:27PM -0700, Andre McCurdy wrote: >>>> On Thu, Mar 29, 2018 at 3:41 PM, Denys Dmytriyenko <denis@denix.org> wrote: >>>>> Ping. It's been 10 days - are there any issues with these updates? >>>> >>>> Only 10 days? :-) >>> >>> Yeah, I know, I'm too demanding... :) >> >> Ross does pick the patches from ml fairly quickly so always check >> >> http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=ross/mut >> >> or OE-Core's master-next >> >> http://git.openembedded.org/openembedded-core/log/?h=master-next >> >> from mut to master it might take a while since there are many patches coming in >> so integration takes time and sometimes there are issues with infra >> which can delay >> things, > > Yes, I'm quite aware of all the above - you don't have to mention all the > details to me. I am glad thats the case. It was not clear from the message and some times this can be misconstrued. Still, it's a standard practice to inquire about own patches > once in a while. Especially since other similar non-critical updates are > merged right away. This is the only way to know if there were any issues with > the patches themselves, but Ross forgot or didn't have time to follow up yet. > > >> 10 days seems pretty darn good in some cases its years see >> >> https://github.com/projectNe10/Ne10/pull/143 >> >> in the end as long as it makes upstream. > > Heh, I don't think we should take that as an example to follow... :) > -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
On Thu, Mar 29, 2018 at 07:41:46PM -0700, Khem Raj wrote: > On 3/29/18 7:34 PM, Denys Dmytriyenko wrote: > >On Thu, Mar 29, 2018 at 06:38:58PM -0700, Khem Raj wrote: > >>On Thu, Mar 29, 2018 at 5:17 PM, Denys Dmytriyenko <denis@denix.org> wrote: > >>>On Thu, Mar 29, 2018 at 04:39:27PM -0700, Andre McCurdy wrote: > >>>>On Thu, Mar 29, 2018 at 3:41 PM, Denys Dmytriyenko <denis@denix.org> wrote: > >>>>>Ping. It's been 10 days - are there any issues with these updates? > >>>> > >>>>Only 10 days? :-) > >>> > >>>Yeah, I know, I'm too demanding... :) > >> > >>Ross does pick the patches from ml fairly quickly so always check > >> > >>http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=ross/mut > >> > >>or OE-Core's master-next > >> > >>http://git.openembedded.org/openembedded-core/log/?h=master-next > >> > >>from mut to master it might take a while since there are many patches coming in > >>so integration takes time and sometimes there are issues with infra > >>which can delay > >>things, > > > >Yes, I'm quite aware of all the above - you don't have to mention all the > >details to me. > > I am glad thats the case. It was not clear from the message and some > times this can be misconstrued. You are absolutely right! After 10+ years in the OE community my mind and memory are not as sharp as they used to be - I keep forgetting things and do not communicate as clearly as before... :-P > Still, it's a standard practice to inquire about own patches > >once in a while. Especially since other similar non-critical updates are > >merged right away. This is the only way to know if there were any issues with > >the patches themselves, but Ross forgot or didn't have time to follow up yet. > > > > > >>10 days seems pretty darn good in some cases its years see > >> > >>https://github.com/projectNe10/Ne10/pull/143 > >> > >>in the end as long as it makes upstream. > > > >Heh, I don't think we should take that as an example to follow... :) > > > -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
On Thu, 2018-03-29 at 18:41 -0400, Denys Dmytriyenko wrote:
> Ping. It's been 10 days - are there any issues with these updates?
We're past feature freeze at this point and M3 was built (finally, and
late). During stabilisation we're only taking upgrades "with a good
reason". Security fixes, bug fixes and issues with maintenance windows
(e.g. bind) are reasons we might see some upgrades going in now but in
general we're holding upgrades until 2.6 opens.
I think Ross has a "post sumo" branch which he may pull some of these
into but I'd really like people to focus on bug fixing for sumo right
now.
Ross is also on vacation so I'll be handling things over the next week
or so (when do I get one?!). I might push a master-next-2.6 to queue
things just to make it clearer what is being deferred. Rebasing can be
a nightmare though.
Cheers,
Richard
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
From: Denys Dmytriyenko <denys@ti.com> Upgrades for lzip, hdparm and lz4. The following changes since commit c94271d87d16323f920891344642f76dfb3c994f: buildperf: measure the size of core-image-sato rootfs (2018-03-16 03:42:03 -0700) are available in the git repository at: git://push.openembedded.org/openembedded-core-contrib denix/master Denys Dmytriyenko (3): lzip: upgrade 1.19 -> 1.20 hdparm: upgrade 9.53 -> 9.55 lz4: upgrade 1.7.4 -> 1.8.1.2 .../hdparm/{hdparm_9.53.bb => hdparm_9.55.bb} | 4 +- .../lzip/{lzip_1.19.bb => lzip_1.20.bb} | 4 +- ...sts-Makefile-don-t-use-LIBDIR-as-variable.patch | 82 ---------------------- .../lz4/{lz4_1.7.4.bb => lz4_1.8.1.2.bb} | 10 +-- 4 files changed, 9 insertions(+), 91 deletions(-) rename meta/recipes-extended/hdparm/{hdparm_9.53.bb => hdparm_9.55.bb} (90%) rename meta/recipes-extended/lzip/{lzip_1.19.bb => lzip_1.20.bb} (88%) delete mode 100644 meta/recipes-support/lz4/files/0001-tests-Makefile-don-t-use-LIBDIR-as-variable.patch rename meta/recipes-support/lz4/{lz4_1.7.4.bb => lz4_1.8.1.2.bb} (79%) -- 2.7.4 -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core