Bug#1022003: transition: gssdp/gupnp 1.2->1.6 (+ rygel 0.42.0)
On Wed, Oct 19, 2022 at 09:17:41PM +0200, Sebastian Ramacher wrote:
> Control: block -1 by 1019353
[...]
> Let's see where we are after the perl transition. Depending on how
> responsive librm upstream is, that might give them enough time to fix
> the remaining issues.
[...]
ACK, but I'd also like to say that's probably not very likely to happen.
The support for gssdp/gupnp 1.6 was merged to librm upstream master 10
months ago. They've apparently never even tried to compile-test it
before or after this merge.
Relevant popcon link says basically noone even uses it:
https://qa.debian.org/popcon-graph.php?packages=librm0%2Croger-router&show_installed=on&show_vote=on&want_legend=on&want_ticks=on&from_date=&to_date=&hlght_date=&date_fmt=%25Y-%25m&beenhere=1
While I have no personal interest in roger-router/librm beyond this
transition, I've quickly looked at what's involved in porting librm to
libsoup-3.0 and it's more changes needed then I'm comforable doing
without having any way to test the result.
(I probably could also not keep my hands away from fixing memory leaks,
off-by-one errors, and other quality issues in the code that I
immediately noticed while poking at it which would further extend how
much work it would need.)
I guess we'll just have to wait and hope....
(I could probably ask gupnp upstream about help since he's usually very
helpful, but I'm not sure it's a useful activity for him to spend time
on.)
Regards,
Andreas Henriksson
Reply to: