Description of problem:
/usr/local/var should be /var/log, no?
Version-Release number of selected component (if applicable):
Steps to Reproduce:
*** Bug 234555 has been marked as a duplicate of this bug. ***
*** Bug 237148 has been marked as a duplicate of this bug. ***
RCS file: /cvs/dist/rpms/setroubleshoot/devel/setroubleshoot.logrotate,v
retrieving revision 1.4
diff -u -r1.4 setroubleshoot.logrotate
--- setroubleshoot.logrotate 20 Mar 2007 15:25:50 -0000 1.4
+++ setroubleshoot.logrotate 25 Apr 2007 15:28:22 -0000
@@ -1,4 +1,4 @@
This is still not fixed in Fedora 7 Test 4. I know it seems like a trivial
matter, but the fix should also be equally trivial, and it's the sort of
unpolished thing that makes new users go "whaaaaat?". I hope you'll fix it
before final release.
fixed in 1.9.5
*** Bug 238539 has been marked as a duplicate of this bug. ***
*** Bug 238546 has been marked as a duplicate of this bug. ***
*** Bug 238850 has been marked as a duplicate of this bug. ***
What a lot of duplicates! When is 1.9.5 going to get pushed out to the development repository?
That might cut down on the repeat reports.
FYI: it is also fixed in 1.9.4-2 (the current F7 version)
*** Bug 239552 has been marked as a duplicate of this bug. ***
Ah, you must be talking about the current *internal* F7 version. Us mere
mortals on the outside have only F7 Test 4 and rawhide to try out, and rawhide
hasn't had any updates pushed out in just over a week. Is it customary to stop
updating rawhide during a pre-release feature freeze? Seems it would be useful
to get the bug fix updates out to rawhide for testing by the community.
Re comment #12: no, it is not normal for rawhide to be unavailable. The Fedora
Project is the middle of merging "core" and "extras" into a single unified
Fedora release, during this one time merge process rawhide was suspended. There
have been volumes of mail concerning the process on various Fedora mailing
lists. The release engineering team is working very hard to bring rawhide back
online as soon as possible.
*** Bug 239641 has been marked as a duplicate of this bug. ***