Bug#1004488: Update grpc to new upstream version 1.37
Hi Pirate, On Thu, Dec 8, 2022 at 12:27 PM Pirate Praveen wrote: > I can see protobuf 1.21 has migrated to testing. Any other blockers to > upload grpc to unstable? Release Manager decision [1]? :) Cheers, Laszlo/GCS [1] https://bugs.debian.org/1025541
Bug#1004488: Update grpc to new upstream version 1.37
On Fri, 9 Sep 2022 14:58:28 +0200 =?UTF-8?B?TMOhc3psw7MgQsO2c3rDtnJtw6lueWkgKEdDUyk=?= wrote: > Hi, > > On Sat, Aug 27, 2022 at 2:09 PM Pirate Praveen wrote: > > Any update of the protobuf transition? We have just 4 months for > > bookworm transition freeze [1] so giving more time for people to fix > > broken packages is better than giving less time I think :) > It's my bad that it's me who tries to fix those broken packages. > Could do it now, just need to submit bugs/patches. > Unfortunately I won't have time for those this weekend. But I will do > it next week. Hi Laszlo, I can see protobuf 1.21 has migrated to testing. Any other blockers to upload grpc to unstable? thanks praveen > Regards, > Laszlo/GCS > >
Bug#1004488: Update grpc to new upstream version 1.37
Hi, On Sat, Aug 27, 2022 at 2:09 PM Pirate Praveen wrote: > Any update of the protobuf transition? We have just 4 months for > bookworm transition freeze [1] so giving more time for people to fix > broken packages is better than giving less time I think :) It's my bad that it's me who tries to fix those broken packages. Could do it now, just need to submit bugs/patches. Unfortunately I won't have time for those this weekend. But I will do it next week. Regards, Laszlo/GCS
Bug#1004488: Update grpc to new upstream version 1.37
On Sun, Jun 5, 2022 at 6:30 PM Pirate Praveen wrote: > On Fri, 01 Apr 2022 03:17:18 +0530 Pirate Praveen > wrote: > > I will update here once I can test gitlab. > > gitlab seems to be working fine with this version of grpc. Cool, thanks for the update. > Any update on this? Are you planning to upload this to unstable soon? It will need the protobuf transition first. Started building locally back then and mostly it's OK. > I'd like to remove ruby-uglifier from the archive, but that require me > to upload gitlab/gitaly in experimental to unstable and these needs > grpc/protobuf from experimental. I'm going to restart the protobuf transition checking soon and will report back. Regards, Laszlo/GCS
Bug#1004488: Update grpc to new upstream version 1.37
On Fri, Mar 25, 2022 at 9:45 PM Pirate Praveen wrote: > With ruby-grpc-tools 1.30.2, > > (debian-sid)pravi@mahishi:~$ dpkg -L ruby-grpc-tools > /usr/share/rubygems-integration/all/gems/grpc-tools-1.30.2/platform_check.rb > /usr/share/rubygems-integration/all/gems/grpc-tools-1.30.2/version.rb > > and with 1.44.0 > > (debian-sid)pravi@mahishi:~$ dpkg -L ruby-grpc-tools [...] > So looks like two .rb files are missing from the deb. Update and recheck. Please note that armel can't build gRPC at the moment due to GCC ICE and neither mipsel due to a GCC memory allocation problem. Other than that it should be OK. But of course need to be find out how to do the transition when GCC has compilation issues on its own. Regards, Laszlo/GCS
Bug#1004488: Update grpc to new upstream version 1.37
On Wed, Mar 16, 2022 at 2:53 PM Pirate Praveen wrote: > László Böszörményi (GCS) wrote: > I think you can upload to experimental directly and we can do more > testing in experimental. Uploaded to experimental, accepted and built. Well, it FTBFS on i386 at the moment but seems easy to fix. Other than that, it should be fine. Please test it soon and let me know if you find any problems. Regards, Laszlo/GCS
Bug#1004488: Update grpc to new upstream version 1.37
On Mon, Mar 7, 2022 at 8:50 AM Pirate Praveen wrote: > I was not able to build on my laptop due to lack of disk space (40 GB was not > sufficient). I was hoping to build it on a vps but temporarily using gem > install in gitlab as gitlab is in contrib anyway. I think you are a DD and can use any porterbox to build packages. > Can you share the debs ? or it could take a few days for me to build it. OK, I have uploaded those to p.d.o [1]. Small local testing shows those might be in good shape. Please report back in some days how you see the status. Regards, Laszlo/GCS [1] https://people.debian.org/~gcs/grpc/
Bug#1004488: Update grpc to new upstream version 1.37
On Tue, Feb 1, 2022 at 1:36 PM Pirate Praveen wrote: > On ചൊ, ഫെബ്രു 1 2022 at 07:29:13 രാവിലെ > +0100 +0100, László Böszörményi (GCS) wrote: > > A work in progress packaging is available [1]. It's mostly OK, but > > the Ruby bindings still need work. > > Thanks, I will give it a try. What's your status? > > Would it be better to split that out and you can update that as a > > standalone package whenever you need? > > I think keeping this in sync with grpc is best option. I usually get > between one to three months of time to update it depending on which > version I currently have. I've further updated the package [1]. Now Ruy bindings look OK. Please test it and let me know the result. Then I can upload it to experimental. Regards, Laszlo/GCS [1] dget -x https://people.debian.org/~gcs/grpc_1.44.0-1.dsc
Bug#1004488: Update grpc to new upstream version 1.37
Hi Pirate, On Fri, Jan 28, 2022 at 10:21 PM Pirate Praveen wrote: > While trying to update ruby-gitlab-labkit I got this error > Could not find 'grpc' (>= 1.37) - did find: [grpc-1.30.2] > (Gem::MissingSpecVersionError) > > Please update grpc to 1.37. I'd be happy to help with the update too. A work in progress packaging is available [1]. It's mostly OK, but the Ruby bindings still need work. Would it be better to split that out and you can update that as a standalone package whenever you need? Regards, Laszlo/GCS [1] dget -x https://people.debian.org/~gcs/grpc_1.43.2-1.dsc
