** Description changed: + == SRU Justification == + + [Impact] + + Not recollecting the full history but at least in 22.04/Jammy LTS Ubuntu + supported access to DNLA services for example via rhythmbox through + grilo. At some point (before 24.04 Noble LTS) this was disabled (compile + time configuration) upstream support was expected to have gone away. + This changed now and support has been turned on again in Plucky. + + This leaves a gap where upgrading from Jammy to Noble regresses user- + experience. That could be avoided by simply restoring the configuration + to what is was in Jammy. + + I double checked the setup and found that Jammy had the exact same + packaging as it is being proposed. The split of grilo-plugins-0.3-base + (main) and grilo-plugins-0.3-extra (universe) did exist and also the + recommends for dleyna-server by grilo-plugins-0.3-extra. + + [Test Plan] + + This requires a DLNA source (eg. minidlna) being present in the local + network. With the current version of grilo-plugins-*-extra this will not + be detected when starting rhythmbox. With the proposed changes it will + find the DLNA source. + + I did apply the proposed diff to the current grilo-plugins in Noble, + compiled them and was able to access my DLNA music files again. + + [Where Problems Could Occur] + + This will likely re-instate some/all previously known issues with DLNA + support. + + In my case there is a very minor issue that the self-made NAS which also + runs the DLNA service shows up twice. But that is because its exposed + through a .local and made-up local domain. All my fault here. + + Otherwise this does not really change code, merely modify the configure + run before compiling to enable support as it was before. + + [Other Info] + + grilo-plugins-0.3-extra | 0.3.14-1ubuntu2 | jammy/universe | amd64, arm64, armhf, ppc64el, riscv64, s390x + grilo-plugins-0.3-extra | 0.3.16-1.1ubuntu6 | noble/universe | amd64, arm64, armhf, ppc64el, riscv64, s390x + + https://launchpad.net/~smb/+archive/ubuntu/noble/+sourcepub/17113585/+listing- + archive-extra + + --- Original Description -- + The dLeyna grilo plugin was disabled because the dleyna-server package was dropped in Ubuntu after being deprecated upstream. However dleyna now has a new maintainer upstream and is maintained in Ubuntu at https://launchpad.net/ubuntu/+source/dleyna, so it can be enabled again. This will be part of the grilo-plugins-0.3-extra package (universe), like before it was dropped.
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to grilo-plugins in Ubuntu. https://bugs.launchpad.net/bugs/2093324 Title: Re-enable dLeyna grilo plugin Status in grilo-plugins package in Ubuntu: Fix Released Status in grilo-plugins source package in Noble: Triaged Status in grilo-plugins source package in Oracular: Triaged Bug description: == SRU Justification == [Impact] Not recollecting the full history but at least in 22.04/Jammy LTS Ubuntu supported access to DNLA services for example via rhythmbox through grilo. At some point (before 24.04 Noble LTS) this was disabled (compile time configuration) upstream support was expected to have gone away. This changed now and support has been turned on again in Plucky. This leaves a gap where upgrading from Jammy to Noble regresses user- experience. That could be avoided by simply restoring the configuration to what is was in Jammy. I double checked the setup and found that Jammy had the exact same packaging as it is being proposed. The split of grilo-plugins-0.3-base (main) and grilo-plugins-0.3-extra (universe) did exist and also the recommends for dleyna-server by grilo-plugins-0.3-extra. [Test Plan] This requires a DLNA source (eg. minidlna) being present in the local network. With the current version of grilo-plugins-*-extra this will not be detected when starting rhythmbox. With the proposed changes it will find the DLNA source. I did apply the proposed diff to the current grilo-plugins in Noble, compiled them and was able to access my DLNA music files again. [Where Problems Could Occur] This will likely re-instate some/all previously known issues with DLNA support. In my case there is a very minor issue that the self-made NAS which also runs the DLNA service shows up twice. But that is because its exposed through a .local and made-up local domain. All my fault here. Otherwise this does not really change code, merely modify the configure run before compiling to enable support as it was before. [Other Info] grilo-plugins-0.3-extra | 0.3.14-1ubuntu2 | jammy/universe | amd64, arm64, armhf, ppc64el, riscv64, s390x grilo-plugins-0.3-extra | 0.3.16-1.1ubuntu6 | noble/universe | amd64, arm64, armhf, ppc64el, riscv64, s390x https://launchpad.net/~smb/+archive/ubuntu/noble/+sourcepub/17113585/+listing- archive-extra --- Original Description -- The dLeyna grilo plugin was disabled because the dleyna-server package was dropped in Ubuntu after being deprecated upstream. However dleyna now has a new maintainer upstream and is maintained in Ubuntu at https://launchpad.net/ubuntu/+source/dleyna, so it can be enabled again. This will be part of the grilo-plugins-0.3-extra package (universe), like before it was dropped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grilo-plugins/+bug/2093324/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
