Bug 136973 - cancel-cups man page missing from errata package
Summary: cancel-cups man page missing from errata package
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: redhat-rpm-config   
(Show other bugs)
Version: 3.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Elliot Lee
QA Contact:
URL: https://rhn.redhat.com/network/softwa...
: 138284 139333 140898 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2004-10-24 16:26 UTC by Andrew Schultz
Modified: 2007-11-30 22:07 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-01-12 18:47:17 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2005:013 normal SHIPPED_LIVE Important: cups security update 2005-01-12 05:00:00 UTC

Description Andrew Schultz 2004-10-24 16:26:22 UTC
The cancel-cups man page (/usr/share/man/man1/cancel-cups.1.gz)  is
missing from security errata package (cups-1.1.17-13.3.16), but the
link (cancel.1.gz) is still created.

Comment 1 Tim Waugh 2004-10-27 13:39:27 UTC
This is put into %{buildroot} and listed in the manifest
(%{_mandir}/man?/*) so there's nothing I can do to fix this in the
spec file.

For some reason rpm is ignoring this symlink.  Note that it is a
symlink to a target that does not exist at package build time (but
does after package install).

Comment 2 Andrew Schultz 2004-10-27 14:29:36 UTC
rebuilding from the .spec worked (included cancel-cups.1.gz) with rpm

But cancel-cups.1.gz is a symlink to lp.1.gz.  Shouldn't it be a
symlink to lp-cups.1.gz?

Comment 3 Tim Waugh 2004-10-27 14:35:57 UTC
lp.1.gz should be (and was) fine.  It is provided by the alternatives
program post-install.

If this is a change in build configuration it might have more
widespread consequences, so we need to know what the change was and
why it was made.

Comment 4 Andrew Schultz 2004-10-27 15:13:30 UTC
> lp.1.gz should be (and was) fine.  It is provided by the alternatives
> program post-install.

certainly.  But logically, shouldn't it point to lp-cups.1.gz?

Comment 5 Tim Waugh 2004-10-27 15:27:18 UTC
Yes, it probably should.

Comment 6 Tim Waugh 2004-11-08 16:42:29 UTC
Duplicate: bug #138284.

Comment 7 Tim Waugh 2004-11-15 11:25:47 UTC
*** Bug 138284 has been marked as a duplicate of this bug. ***

Comment 8 Tim Waugh 2004-11-15 11:26:12 UTC
*** Bug 139333 has been marked as a duplicate of this bug. ***

Comment 10 John Caruso 2004-11-16 00:21:32 UTC
I was about to file a bug on this same issue, but then I happened to 
do the right search to find this one.  So: what is the status?  Based 
on comment 1 it looks like there may be no plan to fix this?  It 
doesn't seem like it should be difficult to address (and it wasn't a 
problem in the previous cups RPM).

Comment 11 Tim Waugh 2004-11-16 09:08:25 UTC
Actually comment #4 has a probable workaround.  I'm waiting for an
analysis of the build system change before proceeding.

Comment 12 Tim Waugh 2004-11-26 10:58:16 UTC
*** Bug 140898 has been marked as a duplicate of this bug. ***

Comment 13 Matthew Saltzman 2004-11-28 16:07:12 UTC
This all works fine in FC3, where the chain of links is 

$man/cancel.1.gz -> $alt/print-cancelman -> $man/cancel-cups.1.gz ->
$man/lp.1.gz -> $alt/print-lpman -> $man/lp-cups.1.gz 

where $man is /usr/share/man/man1 and $alt is /etc/alternatives.

In RHEL, the link $man/cancel-cups.1.gz is missing, but the rest of
the chain is intact.

This isn't to say that the links are done in the most appropriate way,
just that they are all there in FC3, so comparing that spec file and
this one should give a clue.

Comment 14 Tim Waugh 2004-11-28 19:41:22 UTC
No -- the change was in the build system, not the spec file.

Comment 17 Josh Bressers 2005-01-12 18:47:17 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. 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.