Bug 45484 – Only integer values for price per page can be set

Bug 45484 - Only integer values for price per page can be set


Summary:	Only integer values for price per page can be set

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	Printserver - pykota
Version:	UCS 4.2
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:	UCS maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2017-10-05 09:15 CEST by Christina Scheinig
Modified:	2020-07-03 20:55 CEST (History)
CC List:	0 users

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	2: Improvement: Would be a product improvement
Who will be affected by this bug?:	2: Will only affect a few installed domains
How will those affected feel about the bug?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.046
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2017100321000601
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Christina Scheinig

2017-10-05 09:15:34 CEST

According to this Bug 45483 a customer wanted to set a float value for price per page. The UMC only allows integer values. 

But setting float values is possible via pkprinters (printers manager for PyKota) on command line.
Workaround (not explicitly verified) 

pkprinters -c 0.0082 <your_printer_name>

-c | --charge p[,j]  Sets the price per page and per job to charge.
                       Job price is optional.
                       If both are to be set, separate them with a comma.
                       Floating point and negative values are allowed.

And checking the values via:

pkprinters -l
repykota

Comment 1 Ingo Steuwer

2020-07-03 20:55:05 CEST

This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.