Bug 435082 - CUPS backend should use CUPS exit codes
CUPS backend should use CUPS exit codes
Status: CLOSED UPSTREAM
Product: Fedora
Classification: Fedora
Component: bluez-utils (Show other bugs)
8
All Linux
low Severity low
: ---
: ---
Assigned To: David Woodhouse
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-02-27 04:21 EST by Tim Waugh
Modified: 2008-03-13 13:53 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-03-13 13:53:10 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Tim Waugh 2008-02-27 04:21:06 EST
Description of problem:
There are constants defined by CUPS for backend exit codes:

CUPS_BACKEND_OK
CUPS_BACKEND_FAILED
CUPS_BACKEND_HOLD
etc

Although the bluetooth CUPS backend only appears to exit with 0
(CUPS_BACKEND_OK) or 1 (CUPS_BACKEND_FAILED), it would be best practice to use
the macros.

Version-Release number of selected component (if applicable):
3.20-6.fc8
Comment 1 Bastien Nocera 2008-03-13 13:53:10 EDT
Fixed upstream. Should be in 3.29.

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