openwrt / openwrt/packages

sane-backends,hplip,libcups: looking for maintainer

Open
#16,111 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

help wanted
Dominant language
Makefile
Stars
4.6k
Forks
4k
Avg merge
3d 12h
Merged PRs (30d)
134

Description

I recently lost my printer used for sane-backends and hplip tests. The new one uses proprietary HP driver not compiled for anything but arm/x86.

https://github.com/openwrt/packages/issues/14830
https://forum.openwrt.org/t/sane-issue-on-hp-laserjet-m1132/57698
https://developers.hp.com/printos/forum/proprietary-drivers-hplip-plugins-more-archs?language=ja

Even if HP provided the driver for mips and others, I'm not sure if it will work with OpenWrt nor if the router HW could withstand the driver needs.

I can continue maintaining the package but I'll only be able to test with fake printers (sane-test). However, most issues are with USB/hplip integration. It would be better to someone with real use to take the task.
As my new device is a network printer, I'm not going to use sane,hplip in OpenWrt anymore.

libcups is just a stripped cups used as hplip build requirements (until someone maintains the full cups for OpenWrt).

I'll ping previous committers @neheb @syssi

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the sane-backends, hplip, and libcups package definitions alongside the linked OpenWrt issue, forum thread, and HP discussion. The issue does not define a specific change; completion would require an interested maintainer to take responsibility and establish how these packages can be tested and maintained.

Written by the indexing model from the issue text.

Assessment

Domain
build-system, tooling
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.