I was able to do the PR (38861)!
Your guide was *extremely *helpful (already bookmarked 🙂) thank you
very much!
Best,
Tomás*
*
On 10/3/24 07:25, Matt Jolly wrote:
Hi Tomás,
Opening a Pull Request to resolve your bug is not just OK, it's
encouraged.
Reading up on the bug you provided, the suggestion is to depend on the
'3' slot of `dev-ruby/google-protobuf` - so it would look like this:
```
ruby_add_rdepend "
dev-ruby/google-protobuf:3
dev-ruby/googleapis-common-protos-types:1
"
```
Aside from that, if you're able to bump the package (update the version)
at the same time it's a real bonus.
There are a few steps to setup a Gentoo Git workflow - just some things
like package QA checks and GCO Signoff on commits. I've documented the
process here:
https://wiki.gentoo.org/wiki/User:Kangie/Zero_to_Gentoo_PR_Hero
It looks like you have a grounding in `git` so just skip down to
`pkgcheck and pkgdev`, fork the mirror, and submit a PR.
Don't worry about GPG signing your commit for now, but you can if
you want to!
Look forward to seeing your PR!
Cheers,
Matt
On 3/10/24 01:37, Tomás Carvalho wrote:
Hello folks,
The package app-emulation/vagrant-2.4.1 seems to break with the
latest (available in gentoo) dev-ruby/grpc (version 1.59.2), when I
"bumped" the version to the current one (local overlay) vagrant seems
to work fine :) (mainly changed the title of the ebuild file)
I opened a bug in bugs.gentoo.org (939826) but I'm not sure about the
meaning of the reply that I got...
I'm also not sure if I should just do a pull request to bump the
version of grpc or not...
Could anyone please help (regarding updating the gentoo's upstream)?
Thank you,
Tomás C.
🙂
