| Message ID | 20221228230326.3799157-1-JoelsonCarl@gmail.com |
|---|---|
| State | Accepted |
| Headers | show |
| Series | [1/1] package/capnproto: bump version to 0.10.3 | expand |
On Wed, 28 Dec 2022 16:03:26 -0700 Joel Carlson <joelsoncarl@gmail.com> wrote: > The 0.10 line offers minor improvements and bug fixes. > > The previous security bump from 0.9.1 to 0.9.2 fixed CVE-2022-46149, > which was also present in 0.10.2, but is fixed within 0.10.3. > > Signed-off-by: Joel Carlson <JoelsonCarl@gmail.com> > --- > package/capnproto/capnproto.hash | 2 +- > package/capnproto/capnproto.mk | 2 +- > 2 files changed, 2 insertions(+), 2 deletions(-) Applied to master, thanks. Thomas
Hey Joel, Cool. Did you manage to get it to compile on all platforms? I tried a while ago to bump the version, but sadly ran into compilation failures on a handful of platforms, which is why I never submitted a patch. I didn't have the time to figure out why it failed, what would be needed to make it pass or how to patch the configuration requirements to not show up on the affected platforms. I guess we'll find out soon enough, when I start getting mails from the automated build system that it's failing (or not). Just in case, I currently and in the near future do not have the time to diagnose any failures that might result from bumping the version. Hope that if they do fail, you can have a look. It's probably best if I remove myself as a maintainer for this package, perhaps you'd like to take over? Apologies, Koen On 29-12-2022 00:03, Joel Carlson wrote: > The 0.10 line offers minor improvements and bug fixes. > > The previous security bump from 0.9.1 to 0.9.2 fixed CVE-2022-46149, > which was also present in 0.10.2, but is fixed within 0.10.3. > > Signed-off-by: Joel Carlson <JoelsonCarl@gmail.com> > --- > package/capnproto/capnproto.hash | 2 +- > package/capnproto/capnproto.mk | 2 +- > 2 files changed, 2 insertions(+), 2 deletions(-) > > diff --git a/package/capnproto/capnproto.hash b/package/capnproto/capnproto.hash > index c3233e7c8b..0faf69d069 100644 > --- a/package/capnproto/capnproto.hash > +++ b/package/capnproto/capnproto.hash > @@ -1,3 +1,3 @@ > # Locally calculated > -sha256 4fe1ca8ab90859f33f08d2c4fcd7099e2983b0b946beecebd2fe051e3a64c67e capnproto-0.9.2.tar.gz > +sha256 e07446f56043c983e009038e69d18ff86a2924909f0b518ccf47eccf5ac03919 capnproto-0.10.3.tar.gz > sha256 9564998c8d7f270a61a8b89869a8d17a9d5e3783b64027788b5e339ec8479e10 LICENSE > diff --git a/package/capnproto/capnproto.mk b/package/capnproto/capnproto.mk > index 23f128455a..84acf5fc65 100644 > --- a/package/capnproto/capnproto.mk > +++ b/package/capnproto/capnproto.mk > @@ -4,7 +4,7 @@ > # > ################################################################################ > > -CAPNPROTO_VERSION = 0.9.2 > +CAPNPROTO_VERSION = 0.10.3 > CAPNPROTO_SITE = $(call github,capnproto,capnproto,v$(CAPNPROTO_VERSION)) > CAPNPROTO_LICENSE = MIT > CAPNPROTO_LICENSE_FILES = LICENSE
On Thu, Dec 29, 2022 at 6:36 AM Koen Martens <gmc@sonologic.nl> wrote: > > Hey Joel, > > Cool. Did you manage to get it to compile on all platforms? I tried a > while ago to bump the version, but sadly ran into compilation failures > on a handful of platforms, which is why I never submitted a patch. I > didn't have the time to figure out why it failed, what would be needed > to make it pass or how to patch the configuration requirements to not > show up on the affected platforms. I used "./utils/test-pkg -a" and of the 44 toolchains that it goes through, they were all OK or SKIPPED. I don't test much beyond that. If that isn't mostly inclusive of all the variations, then we'll soon know through the autobuilder reports. > I guess we'll find out soon enough, when I start getting mails from the > automated build system that it's failing (or not). Just in case, I > currently and in the near future do not have the time to diagnose any > failures that might result from bumping the version. Hope that if they > do fail, you can have a look. > > It's probably best if I remove myself as a maintainer for this package, > perhaps you'd like to take over? I am actually already in DEVELOPERS for capnproto, as I revived and pushed through your original patch to add it that had stalled at the time. So I'll still remain on DEVELOPERS for capnproto if you remove yourself. Though I'll admit, my responsiveness to the packages I'm listed for is fairly slow (cmocka has had a build error on one toolchain for I don't know how long now...). And I honestly haven't used capnproto since adding it. We thought we were gonna use it on our system back when I added the package to buildroot, but then ended up using a different library. So yeah... that doesn't answer the question super well, but if you drop yourself, there will still be at least me (very slowly) eventually responding to issues for capnproto. =) -Joel > > Apologies, > > Koen > > On 29-12-2022 00:03, Joel Carlson wrote: > > The 0.10 line offers minor improvements and bug fixes. > > > > The previous security bump from 0.9.1 to 0.9.2 fixed CVE-2022-46149, > > which was also present in 0.10.2, but is fixed within 0.10.3. > > > > Signed-off-by: Joel Carlson <JoelsonCarl@gmail.com> > > --- > > package/capnproto/capnproto.hash | 2 +- > > package/capnproto/capnproto.mk | 2 +- > > 2 files changed, 2 insertions(+), 2 deletions(-) > > > > diff --git a/package/capnproto/capnproto.hash b/package/capnproto/capnproto.hash > > index c3233e7c8b..0faf69d069 100644 > > --- a/package/capnproto/capnproto.hash > > +++ b/package/capnproto/capnproto.hash > > @@ -1,3 +1,3 @@ > > # Locally calculated > > -sha256 4fe1ca8ab90859f33f08d2c4fcd7099e2983b0b946beecebd2fe051e3a64c67e capnproto-0.9.2.tar.gz > > +sha256 e07446f56043c983e009038e69d18ff86a2924909f0b518ccf47eccf5ac03919 capnproto-0.10.3.tar.gz > > sha256 9564998c8d7f270a61a8b89869a8d17a9d5e3783b64027788b5e339ec8479e10 LICENSE > > diff --git a/package/capnproto/capnproto.mk b/package/capnproto/capnproto.mk > > index 23f128455a..84acf5fc65 100644 > > --- a/package/capnproto/capnproto.mk > > +++ b/package/capnproto/capnproto.mk > > @@ -4,7 +4,7 @@ > > # > > ################################################################################ > > > > -CAPNPROTO_VERSION = 0.9.2 > > +CAPNPROTO_VERSION = 0.10.3 > > CAPNPROTO_SITE = $(call github,capnproto,capnproto,v$(CAPNPROTO_VERSION)) > > CAPNPROTO_LICENSE = MIT > > CAPNPROTO_LICENSE_FILES = LICENSE > > -- > Software architecture & engineering: https://www.sonologic.se/ > Sci-fi: https://www.koenmartens.nl/ >
On 29-12-2022 19:19, Joel Carlson wrote: > On Thu, Dec 29, 2022 at 6:36 AM Koen Martens <gmc@sonologic.nl> wrote: >> Hey Joel, >> >> Cool. Did you manage to get it to compile on all platforms? I tried a >> while ago to bump the version, but sadly ran into compilation failures >> on a handful of platforms, which is why I never submitted a patch. I >> didn't have the time to figure out why it failed, what would be needed >> to make it pass or how to patch the configuration requirements to not >> show up on the affected platforms. > I used "./utils/test-pkg -a" and of the 44 toolchains that it goes > through, they were all OK or SKIPPED. I don't test much beyond that. > If that isn't mostly inclusive of all the variations, then we'll soon > know through the autobuilder reports. Oh, great. That's what I did too, but with an older version (10.2 perhaps, or maybe 10.1). I guess whatever was broken got fixed in 10.3 then! >> I guess we'll find out soon enough, when I start getting mails from the >> automated build system that it's failing (or not). Just in case, I >> currently and in the near future do not have the time to diagnose any >> failures that might result from bumping the version. Hope that if they >> do fail, you can have a look. >> >> It's probably best if I remove myself as a maintainer for this package, >> perhaps you'd like to take over? > I am actually already in DEVELOPERS for capnproto, as I revived and > pushed through your original patch to add it that had stalled at the > time. > > So I'll still remain on DEVELOPERS for capnproto if you remove > yourself. Though I'll admit, my responsiveness to the packages I'm > listed for is fairly slow (cmocka has had a build error on one > toolchain for I don't know how long now...). And I honestly haven't > used capnproto since adding it. We thought we were gonna use it on our > system back when I added the package to buildroot, but then ended up > using a different library. > > So yeah... that doesn't answer the question super well, but if you > drop yourself, there will still be at least me (very slowly) > eventually responding to issues for capnproto. =) Well, let's keep things as they are then, since it seems we're both in the same position :) I'm not actually using buildroot for anything at all at the moment, but I do love the project, so I'll continue to do my part whenever possible to keep the two packages I'm maintaining somewhat up to date :) Between you and me, we should be able to keep capnproto going. Cheers, Koen > > -Joel > >> Apologies, >> >> Koen >> >> On 29-12-2022 00:03, Joel Carlson wrote: >>> The 0.10 line offers minor improvements and bug fixes. >>> >>> The previous security bump from 0.9.1 to 0.9.2 fixed CVE-2022-46149, >>> which was also present in 0.10.2, but is fixed within 0.10.3. >>> >>> Signed-off-by: Joel Carlson <JoelsonCarl@gmail.com> >>> --- >>> package/capnproto/capnproto.hash | 2 +- >>> package/capnproto/capnproto.mk | 2 +- >>> 2 files changed, 2 insertions(+), 2 deletions(-) >>> >>> diff --git a/package/capnproto/capnproto.hash b/package/capnproto/capnproto.hash >>> index c3233e7c8b..0faf69d069 100644 >>> --- a/package/capnproto/capnproto.hash >>> +++ b/package/capnproto/capnproto.hash >>> @@ -1,3 +1,3 @@ >>> # Locally calculated >>> -sha256 4fe1ca8ab90859f33f08d2c4fcd7099e2983b0b946beecebd2fe051e3a64c67e capnproto-0.9.2.tar.gz >>> +sha256 e07446f56043c983e009038e69d18ff86a2924909f0b518ccf47eccf5ac03919 capnproto-0.10.3.tar.gz >>> sha256 9564998c8d7f270a61a8b89869a8d17a9d5e3783b64027788b5e339ec8479e10 LICENSE >>> diff --git a/package/capnproto/capnproto.mk b/package/capnproto/capnproto.mk >>> index 23f128455a..84acf5fc65 100644 >>> --- a/package/capnproto/capnproto.mk >>> +++ b/package/capnproto/capnproto.mk >>> @@ -4,7 +4,7 @@ >>> # >>> ################################################################################ >>> >>> -CAPNPROTO_VERSION = 0.9.2 >>> +CAPNPROTO_VERSION = 0.10.3 >>> CAPNPROTO_SITE = $(call github,capnproto,capnproto,v$(CAPNPROTO_VERSION)) >>> CAPNPROTO_LICENSE = MIT >>> CAPNPROTO_LICENSE_FILES = LICENSE >> -- >> Software architecture & engineering: https://www.sonologic.se/ >> Sci-fi: https://www.koenmartens.nl/ >>
diff --git a/package/capnproto/capnproto.hash b/package/capnproto/capnproto.hash index c3233e7c8b..0faf69d069 100644 --- a/package/capnproto/capnproto.hash +++ b/package/capnproto/capnproto.hash @@ -1,3 +1,3 @@ # Locally calculated -sha256 4fe1ca8ab90859f33f08d2c4fcd7099e2983b0b946beecebd2fe051e3a64c67e capnproto-0.9.2.tar.gz +sha256 e07446f56043c983e009038e69d18ff86a2924909f0b518ccf47eccf5ac03919 capnproto-0.10.3.tar.gz sha256 9564998c8d7f270a61a8b89869a8d17a9d5e3783b64027788b5e339ec8479e10 LICENSE diff --git a/package/capnproto/capnproto.mk b/package/capnproto/capnproto.mk index 23f128455a..84acf5fc65 100644 --- a/package/capnproto/capnproto.mk +++ b/package/capnproto/capnproto.mk @@ -4,7 +4,7 @@ # ################################################################################ -CAPNPROTO_VERSION = 0.9.2 +CAPNPROTO_VERSION = 0.10.3 CAPNPROTO_SITE = $(call github,capnproto,capnproto,v$(CAPNPROTO_VERSION)) CAPNPROTO_LICENSE = MIT CAPNPROTO_LICENSE_FILES = LICENSE
The 0.10 line offers minor improvements and bug fixes. The previous security bump from 0.9.1 to 0.9.2 fixed CVE-2022-46149, which was also present in 0.10.2, but is fixed within 0.10.3. Signed-off-by: Joel Carlson <JoelsonCarl@gmail.com> --- package/capnproto/capnproto.hash | 2 +- package/capnproto/capnproto.mk | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)