OpenPrinting / OpenPrinting/foomatic-db

Outdated Lexmark PPDs from 2018 with newer ones available from lexmark.com

Open
#28 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
14
Forks
24
Avg merge
8m
Merged PRs (30d)
1

Description

[Hopefully, this is the correct forum to post this. Sorry, if not.]

Setting up a Lexmark CX920de on Debian sid/unstable, it took me a while to figure out to install openprinting-ppds. Before that, the search engines sent me to the Lexmark driver Web site, where the current DEB package is Lexmark-UPD-PPD-Files-1.0-05252022.amd64.deb from May 25th, 2022.

The PPD in foomatic-db was last changed in commit https://github.com/OpenPrinting/foomatic-db/commit/5f7182f6efb13146eeb161484e6a8f41f72147e8 in 2018. Unfortunately, there is no commit message, explaining the changes. There is, for example,

-*Throughput: "35"
+*Throughput: "25"

Comparing https://www.openprinting.org/download/PPD/Lexmark/Lexmark_CX920_Series.ppd from 9/21 with the PPD from lexmark.com there are some minor(?) differences. Throughput is set to 35 again, for example.

It would be great to have these updated PPDs in the OpenPrinting repository, so GNU/Linux users can easily get them using their distribution packages. Is the procedure documented somewhere? Can I just create a merge/pull request?

In the past, a Lexmark employee seems to have updated the PPD files. @Lexmark-bduffy, are you still active? Does somebody have contacts to Lexmark?

Contributor guide

No contributing guide indexed for this repository

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

Compare the repository's 2018 Lexmark PPD change at commit 5f7182f6efb13146eeb161484e6a8f41f72147e with the newer PPDs linked in the issue. First review the linked files and the project's contribution procedure, then verify which Lexmark entries need updating. Done means the applicable newer PPDs are incorporated according to the repository's process and their differences are validated.

Written by the indexing model from the issue text.

Assessment

Domain
database
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.