35313 – metalog still being used as logger despite being unmerged

Bug 35313 - metalog still being used as logger despite being unmerged

Summary: metalog still being used as logger despite being unmerged

Status:	RESOLVED INVALID

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	x86 Linux

Importance:	High normal (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:

Duplicates (1):	67982 (view as bug list)
Depends on:
Blocks:

Reported:	2003-12-07 23:15 UTC by Andrew Sayman
Modified:	2004-10-18 07:36 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

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

Description Andrew Sayman 2003-12-07 23:15:14 UTC

I have completely unmerged metalog and emerged sysklogd. I have removed metalog
from the inits and put sysklogd there.  On startup and every time I emerge
something I get this error: 
* Caching service dependencies...
 *  Service 'metalog' already provide 'logger'!;
 *  Not adding service 'sysklogd'...                                      [ ok ]

In addition, when I try to start my cron daemon I see this: 
 /etc/init.d/vcron start
 * Starting metalog...
start-stop-daemon: stat /usr/sbin/metalog: No such file or directory
 * Failed to start metalog                                                [ !! ]

 * ERROR:  Problem starting needed services.
 *         "vcron" was not started.

As this makes clear, metalog no longer exists. Why is portage caching a program
that isn't installed as my logger?

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

Comment 1 SpanKY gentoo-dev

2003-12-08 06:24:25 UTC

delete the init.d script in /etc/init.d

Comment 2 SpanKY gentoo-dev

2004-10-18 07:36:01 UTC

*** Bug 67982 has been marked as a duplicate of this bug. ***