roger-router does not start, unresolved symbols

Output of ldd -d -r /usr/bin/roger

undefined symbol: rm_router_load_journal_finish (/usr/bin/roger)
undefined symbol: rm_router_load_voice_mail_async (/usr/bin/roger)
undefined symbol: rm_journal_free (/usr/bin/roger)
undefined symbol: rm_router_load_voice_mail_finish (/usr/bin/roger)
undefined symbol: rm_router_load_journal_async (/usr/bin/roger)

FTR, I found https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987938 as the reason for the previous revert by Debian. Looks like it was due to a "library transition" without regard to roger-router only.

I added this note:

> [racb] However there may be users linking to librm from their own local builds, and bumping librm will regress them. On balance bumping seems like the best idea still, but this is a known path to regression if such users exist.

Because of this, I'd like a +1 from another SRU team member before accepting this.

In the meantime, any chance you could add "Actual behaviour" and "Expected behaviour" to your test plan please? It's not clear to me what those should be. Also, if there's a CLI (looks like there is), would a dep8 test be a good idea? Presumably you care as you synced this from experimental during the Jammy cycle. A dep8 test would have stopped the issue arising in Ubuntu in the first place.

On the other hand, downgrading roger-router the version present previously would presumably fix the issue without risking regressing anything unrelated.

> and bumping librm will regress them.

I don't see any information here about regressions from the new upstream version; this seems more like it *may* regress them.

Anyway, on balance having the sole package in the archive that links against the library fixed so that it can be run trumps the risk of a local binary build (possibly) regressing, so +1.

(Also from the library description it appears this exists to specifically service roger-router and related software...)

Hello andik, or anyone else affected,

Accepted librm into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/librm/2.2.2+really2.2.2-0ubuntu0.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Steve,

Thanks for your work. Unfortunately I already have moved to Kinectic, so trying the binaries in a different environment will fail.

But just a pointer to a new problem with roger-router in the Kinetic version:

https://bugs.launchpad.net/bugs/1995022

roger-router also does not start in this version, also due to a library missconfiguration.
But it's related to libsoup this time.

I installed librm 2.2.2+really2.2.2-0ubuntu0.1 on Ubuntu 22.04 LTS and verified that the Roger Router app now works.

This bug was fixed in the package librm - 2.2.2+really2.2.2-0ubuntu0.1

---------------
librm (2.2.2+really2.2.2-0ubuntu0.1) jammy; urgency=medium

  * Use the matching version for roger-router 2.4.0 (LP: #1980567)

 -- Jeremy Bicha <email address hidden> Fri, 26 Aug 2022 14:59:36 -0400

The verification of the Stable Release Update for librm has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.