Ryan Carsten Schmidt

> Can you advice on how I can add my changes to this PR? https://trac.macports.org/wiki/WorkingWithGit#WorkingwithsomeoneelsespullrequestthroughitsID

> protobuf no longer ships with its own `setup.py` prohibiting building py-protobuf directly from the github sources. Is there something that speaks against using the prebuilt source package made available...

> the `py3*protobuf3` version number went from `4.21.12` to `24.4` That is not so. When you wrote this comment, the version number of the python module was 4.24.4. Now, the...

Per https://protobuf.dev/support/version-support/#cpp, as of protobuf 22.x, the version number for the C++ bindings goes from 3 to 4. The protobuf3-cpp port, given the 3 in its name, is intended to...

> When you wrote this comment, the version number of the python module was 4.24.4 This makes me wonder if py-protobuf3 should ever have been updated to 4.x in 6d94469cc87ff68c2f64f364442b6b2989ea07a6....

>> Is there something that speaks against using the prebuilt source package made available through pypi instead? > > We don't want to do that @reneeotten Why not? It's acceptable...

> Fixes "fatal error: 'ov-scalar.h' file not found" which occurred due to failure to locate Octave's include directory. > > Closes: https://trac.macports.org/ticket/69246 Based on the CI build failure on macOS...

Closing. This doesn't fix the issue. Nobody develops this software anymore so it will never be fixed.

> I'm not sure that there's anything I can do to address these logged CI errors: > > > ```shell > > Error: Failed to install dependencies for pure-gen >...

Thanks. Does this fix https://trac.macports.org/ticket/64532? If so, the commit message should say so. The commit message should begin with `portname:`, not `category/portname:`. Let's see what upstream says about your PR...