Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 594709 - Shouldn't ship /usr/share/foomatic/kitload.log
Shouldn't ship /usr/share/foomatic/kitload.log
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: gutenprint (Show other bugs)
All Linux
low Severity medium
: rc
: ---
Assigned To: Tim Waugh
Depends On:
Blocks: 594197
  Show dependency treegraph
Reported: 2010-05-21 08:26 EDT by Tim Waugh
Modified: 2010-11-10 15:37 EST (History)
3 users (show)

See Also:
Fixed In Version: gutenprint-5.2.5-2.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-11-10 15:37:54 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Tim Waugh 2010-05-21 08:26:25 EDT
Description of problem:
The kitload.log file is generated at build time and may vary between architectures.  We shouldn't ship it.

Version-Release number of selected component (if applicable):
Comment 2 RHEL Product and Program Management 2010-06-07 12:00:22 EDT
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
Comment 4 Jiri Popelka 2010-07-08 12:07:01 EDT
Fixed in gutenprint-5.2.5-2.el6

Comment 6 Miroslav Vadkerti 2010-07-16 05:12:35 EDT
Latest gutenprint-5.2.5-2.el6 doesn't ship /usr/share/foomatic/kitload.log:
Comment 7 releng-rhel@redhat.com 2010-11-10 15:37:54 EST
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.

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