[14:24] <arraybolt3> Does anyone know of a CLI frontend to the software-properties subsystem, like software-properties-cli rather than software-properties-qt?
[14:25] <arraybolt3> looks like for automation, you're expected to use python3-software-properties, but I'm trying to modify an update manager related thing in a C++ app.
[14:29] <arraybolt3> meh, the code of python3-software-properties is quite straightforward, I can just reimplement what it's doing in C++.
[20:53] <kanashiro> vorlon: I am having some issues to add abi=time64 to DEB_BUILD_OPTIONS in gem2deb, when dh_ruby is called apparently the build flags are already defined. For instance, -D_TIME_BITS=64 is not included after that (I think this is what we want here)
[21:30] <kanashiro> since I will need to rebuild the ruby package another time to remove support of ruby3.1 (now I want to add support for ruby3.2), I am going to move on without this patch and next time we can fix this
[21:32] <kanashiro> FWIW ruby3.2 was built with DEB_BUILD_OPTIONS=abi=time64 already
[21:46] <vorlon> kanashiro: right, dh_ruby isn't going to be able to modify the environment of other parts of the makefile?
[21:46] <vorlon> kanashiro: anyway, ack
[21:50] <kanashiro> vorlon: the makefile is generated by the gem mkmf (defined by upstream each upstream project), I could try to patch the config for all packages but it would be a bit hacky. Right now, dh_ruby does not support that.