First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 83641
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Gentoo's Team for Core System packages <base-system@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Meder Bakirov <bakirov@transfer.kg>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
logwatch-6.0.1.ebuild logwatch-6.0.1.ebuild text/plain Meder Bakirov 2005-02-28 23:13 0000 1.31 KB Details
logwatch.cron Logwatch Daily Cron file text/plain Meder Bakirov 2005-02-28 23:17 0000 92 bytes Details
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 83641 depends on: Show dependency tree
Bug 83641 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2005-02-28 23:12 0000 
A new version bump for sys-apps/logwatch.

6.0 -> 6.0.1 (stable)
A few small cleanup changes.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.




Also I removed the following function from the ebuild:

pkg_postinst() {
        einfo
        einfo "you have to manually add ${PN} to cron..."
        einfo "0 0 * * * /usr/sbin/logwatch.pl 2>&1 > /dev/null"
        einfo
}

and added logwatch.cron file instead.

------- Comment #1 From Meder Bakirov 2005-02-28 23:13:59 0000 ------- 
Created an attachment (id=52348) [edit]
logwatch-6.0.1.ebuild

------- Comment #2 From Meder Bakirov 2005-02-28 23:17:37 0000 ------- 
Created an attachment (id=52351) [edit]
Logwatch Daily Cron file

This one goes into ${FILESDIR}.

I removed the next function from the ebuild:

pkg_postinst() {
	einfo
	einfo "you have to manually add ${PN} to cron..."
	einfo "0 0 * * * /usr/sbin/logwatch.pl 2>&1 > /dev/null"
	einfo
}

and added logwatch cron file instead - I think it's more convenient and
*nix-way :p

------- Comment #3 From Darren Davison 2005-04-01 17:12:46 0000 ------- 
works for me.  Is logwatch not being maintained in portage atm?  The current
stable version in the tree (4.3.2) is over 2 yrs old now :(

------- Comment #4 From Daniel Webert 2005-04-02 07:19:09 0000 ------- 
using 6.0.1 on 5 x86 overhere for 4 weeks now - no probs - plz dump

------- Comment #5 From Daniel Webert 2005-04-28 16:43:18 0000 ------- 
ping - works fine overhere for 2 months ...

------- Comment #6 From SpanKY 2005-04-28 18:42:45 0000 ------- 
no, no one is really maintaining logwatch because no one cares about it

6.0.2 now in portage
First Last Prev Next    No search results available      Search page      Enter new bug