pleroma.debian.social

Anyone experienced with , , and optionally ? I could use some help creating a WSDL file for debbugs. python-debianbts, the library that reportbug depends on, needs to migrate away from an unmaintained SOAP library, and the proposed candidate requires an WSDL file.

https://venthur.de/2024-04-20-wsdl-for-debbugs.html

@venthur do you have some machine readable file that describes the API in something other than WSDL?

@alexanderkjall Not really, there is my python library (https://github.com/venthur/python-debianbts) that queries the SOAP, and there is debbugs (https://github.com/dondelelcaro/debbugs). Maybe @dondelelcaro knows some more?

@venthur @dondelelcaro Right, so someone would need to reverse engineer that perl code :(

That is a fair bit more pain than I had scheduled for this weekend. I think I have to pass on that one.

@venthur @alexanderkjall one of the nice things about the perl soap client is that it doesn't need a WSDL file, so I never wrote one. Unfortunately, that also means that I've never found a good way to programmatically generate one either. I have a patch written by the emacs folks to distribute one that I'll try to dig up. It doesn't support all of the endpoints, though.

@venthur @dondelelcaro it would seem that adding a REST API to debbugs would be a better use of time. With lots of debbugs consumer experience, you could do a lot of the design work, even without Perl experience to implement it

@jmtd @dondelelcaro I believe that's the long term plan anyways. However, short term we still need to deal with this dying Python SOAP library that python-debianbts needs to migrate away from.

@venthur @dondelelcaro this got me thinking on the nature of "long term" or "short term" in FOSS/volunteer projects. If nobody steps up to do the WSDL work, is that still "short term"?
replies
0
announces
0
likes
0