Arch Linux User Repository

I have finally updated the package to 2.1.0. It was a bit of a PITA, since it requires older versions of gssdp and gupnp, but those are in the AUR now, too.

Fax printer setup is greatly simplified in Roger Router 2, you just need to run:

lpadmin -p Roger-Router-Fax -m drv:///sample.drv/generic.ppd -v socket://localhost:9100/ -E -o PageSize=A4

No need to fiddle with groups or spooling device anymore.

Apart from that I am actually looking for someone who is willing to co-maintain this package with me. The last months made it clear that I lack the time to do bigger updates, and the changes with Roger Router 2 are quite significant. Also upstream, understandible, is focusing on the Flatpak distribution, hence build requirements and build procedure are no longer as clearly documented. For now I think this PKGBUILD is fine, but there could be some tuning in regards to what dependencies are really needed on runtime.

@MiLeon You need libhandy >=1, but this has only landed in Manjaro testing yet. Manually install https://www.archlinux.org/packages/extra/x86_64/libhandy/ or wait for the next stable release.

Hello. A error while building from version 2.1.6-1 to 2.2.1-1

Build output: Preliminary CMake check failed. Aborting. Run-time dependency libhandy-1 found: NO (tried pkgconfig and cmake) "meson.build:57:0: ERROR: Dependency "libhandy-1" not found, tried pkgconfig and cmake"

I have libhandy manual installed after build error. But this was no solution. pacman -Ss libhandy community/libhandy 0.0.13-2 [installed]

uname -r 5.9.1-1-MANJARO

Roger Router, recently, fails to find some of its libraries:

roger: error while loading shared libraries: libgupnp-1.0.so.4: cannot open shared object file: No such file or directory
roger: error while loading shared libraries: libgssdp-1.0.so.3: cannot open shared object file: No such file or directory

Solution:

sudo ln -sf /usr/lib/libgupnp-1.2.so.0 /usr/lib/libgupnp-1.0.so.4
sudo ln -sf /usr/lib/libgssdp-1.2.so.0 /usr/lib/libgssdp-1.0.so.3

I updated the PKGBUILD to the most recent release v2.1.5. It can be found here: https://github.com/jensrudolf/PKGBUILD/tree/master/roger-router

The dependency 'librm' should be used from here https://github.com/jensrudolf/PKGBUILD/tree/master/librm as the one in aur is currently broken due to a missing dependency.

@phw: Would you please update the package? Thank you.

Hi @phw, any plans to update the aur package to 2.1.5 (upstream released a new version on 2019-09-23)?

URL is https://gitlab.com/tabos/rogerrouter/-/archive/v2.1.5/rogerrouter-v2.1.5.tar.gz

Works great on my machine here. Thanks a lot.

Thanks a lot for update Philipp Compiles and runs smooth now

I have finally updated the package to 2.1.0. It was a bit of a PITA, since it requires older versions of gssdp and gupnp, but those are in the AUR now, too.

Fax printer setup is greatly simplified in Roger Router 2, you just need to run:

lpadmin -p Roger-Router-Fax -m drv:///sample.drv/generic.ppd -v socket://localhost:9100/ -E -o PageSize=A4

No need to fiddle with groups or spooling device anymore.

Apart from that I am actually looking for someone who is willing to co-maintain this package with me. The last months made it clear that I lack the time to do bigger updates, and the changes with Roger Router 2 are quite significant. Also upstream, understandible, is focusing on the Flatpak distribution, hence build requirements and build procedure are no longer as clearly documented. For now I think this PKGBUILD is fine, but there could be some tuning in regards to what dependencies are really needed on runtime.

The post-install message seems to be misleading.

According to upstream documentation at https://www.tabos.org/installation-unter-linux/ (German only – second grey box with lpadmin command) a generic PPD is (now?) used.

No /usr/share/cups/model/roger-fax.ppd after installation. Someone can confirm?

Just an update: I will update the package, but I ran into some issues and time constraints. Also upstream does not seem to make separate source releases available anymore, so the package will be built directly from git.