Hi, Has something changed with the way that EPEL5 packages are built that means man pages are no longer automatically compressed? I've just tried to build a new ncdu package (version 1.12) for EPEL5, but it failed: http://koji.fedoraproject.org/koji/taskinfo?taskID=15482900 The man page is installed uncompressed: > /usr/bin/install -c -m 644 ncdu.1 '/var/tmp/ncdu-1.12-1.el5-root-mockbuild/usr/share/man/man1' The build failed because ncdu.1.gz (which is meant to go into the RPMs) couldn't be found, and ncdu.1 (which shouldn't exist when the RPMs are created) was unpackaged. This wasn't an issue with the last build (1.11) I did in April 2015: http://koji.fedoraproject.org/koji/buildinfo?buildID=626540 Again the man page was installed uncompressed, but had been (automatically) compressed by the time the RPM was created. Comparing the build logs, these lines from the 1.11 build aren't present for the 1.12 build: > + /usr/lib/rpm/find-debuginfo.sh /builddir/build/BUILD/ncdu-1.11 > extracting debug info from /var/tmp/ncdu-1.11-1.el5-root-mockbuild/usr/bin/ncdu > 278 blocks > + /usr/lib/rpm/check-buildroot > + /usr/lib/rpm/redhat/brp-compress > + /usr/lib/rpm/redhat/brp-strip-static-archive /usr/bin/strip > + /usr/lib/rpm/redhat/brp-strip-comment-note /usr/bin/strip /usr/bin/objdump > + /usr/lib/rpm/brp-python-bytecompile > + /usr/lib/rpm/redhat/brp-java-repack-jars Thanks for any help! Rich -- Richard Fearn richardfearn@xxxxxxxxx _______________________________________________ epel-devel mailing list epel-devel@xxxxxxxxxxxxxxxxxxxxxxx https://lists.fedoraproject.org/admin/lists/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
