Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 83704

Summary: x11-misc/lineakd-0.8.2 installs misnamed (and thus garbled) man-page
Product: Gentoo Linux Reporter: Lars Wendler (Polynomial-C) (RETIRED) <polynomial-c>
Component: Current packagesAssignee: Portage team <dev-portage>
Status: RESOLVED FIXED    
Severity: minor CC: desktop-misc, genstef
Priority: High Keywords: InVCS
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description Lars Wendler (Polynomial-C) (RETIRED) gentoo-dev 2005-03-01 10:59:50 UTC
Hi,

after installation of lineakd-0.8.2 the man-page of lineakd is misnamed and thus being shown garbled (man lineakd).

when portage calls "make install" on the package the file lineakd.1.bz2 gets copied into the image-directory:
/bin/install -c -p -m 644 ./lineakd.1.bz2 /var/tmp/portage/lineakd-0.8.2/image//usr/share/man/man1/lineakd.1.bz2

But after qmerge is done the man-page looks like this:

/usr/share/man/man1/lineakd.1.bz2.gz

It's been packed once again with gzip.

My first idea was to add these lines at the end of the ebuild but maybe there is a cleaner solution for this problem:

pkg_postinst() {
        einfo "Fixing man-page"
        gunzip /usr/share/man/man1/lineakd.1.bz2.gz
}

Poly

Reproducible: Always
Steps to Reproduce:
1. emerge lineakd
2. ls /usr/share/man/man1/lineakd*
Comment 1 Brian Harring (RETIRED) gentoo-dev 2005-03-01 12:23:12 UTC
post 51.18 commited, so either 51.19 or a .51.18.-rN release
Comment 2 Stefan Schweizer (RETIRED) gentoo-dev 2005-07-03 05:10:31 UTC
Still happens with portage-cvs for me :(

>>> /usr/share/man/man1/lineakd.1.bz2.gz
>>> /usr/share/man/man1/evtest.1.bz2.gz
--- /usr/share/man/man8/
>>> /usr/share/man/man8/send_to_keyboard.8.bz2.gz
Comment 3 Jason Stubbs (RETIRED) gentoo-dev 2005-07-14 05:47:31 UTC
Fixed on or before 2.0.51.22-r1 
Comment 4 Jason Stubbs (RETIRED) gentoo-dev 2005-07-14 06:58:20 UTC
Looking through the batch of bugs, I'm not sure that some of these are 
actually fixed in stable. Others, the requirements have possibly changed after 
the initial fix was committed. 
 
If you think this bug has been closed incorrectly, please reopen or ask that 
it be reopened.