Bug 131430 - Current isdn4k docs include many cvs files and there is no logrotate entry
Current isdn4k docs include many cvs files and there is no logrotate entry
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: isdn4k-utils (Show other bugs)
rawhide
All Linux
medium Severity low
: ---
: ---
Assigned To: Ngo Than
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-09-01 08:04 EDT by Matthias Saou
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-09-01 10:28:37 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 Matthias Saou 2004-09-01 08:04:37 EDT
Description of problem:
The current isdn4k-utils docs include many "CVS" directories and a
.cvsignore file. Also, the program seems to include the possibility to
produce some log files, but no logrotate entry is included.

Version-Release number of selected component (if applicable):
isdn4k-utils-3.2-16.p1.1

How reproducible:
Always.

Steps to Reproduce:
1. rpm -qd isdn4k-utils
2. rpm -ql isdn4k-utils | grep logrotate
  
Actual results:
Some CVS directories and a .cvsignore file.

Expected results:
No CVS files but a /etc/logrotate.d/ entry.

Additional info:
Simply adding something like this to the %prep section is enough for
the CVS and .cvsignore files :

# Clean up CVS files, to not have them in the included docs
find . -name CVS -o -name .cvsignore -exec rm -rf {} \;

As for the logrotate entry, I'm not exactly sure which files exactly
can be created, but all could be grouped in a single entry, without
forgetting to put them as "missingok". There is at least a
/var/log/vbox directory (empty by default) and also /var/log/isdnctrl
referenced in the init script.
Comment 1 Ngo Than 2004-09-01 10:28:37 EDT
it's fixed in isdn4k-utils-3.2-17.p1.1. Thanks for your report.

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