leafnode 1.19.22 is missing it lock file directory /var/lock/news with out it I gets: > fetchnews Cannot obtain lock file, aborting. I did: mkdir /var/lock/news chown news:news /var/lock/news And it works.
Hi Lars! I cannot reproduce this. This was a bug in leafnode-1.9.21 (see bug #1976) and is fixed with 1.9.22. On my machine /var/lock/news gets created with owner news:news and an empty .keep file in it. Did you unmerge some packages after installing leafnode? Maybe another news related package uses the same dir and removed it. It would be nice, if you could do the following test: - remove the /var/lock/news dir - re-emerge leafnode - tell me if the directory is still missing -Markus-
Here is what I have done: rm -rf /var/lock/news emerge leafnode From the emerge log: >>> Merging net-news/leafnode-1.9.22 to / ... --- /var/ --- /var/lock/ >>> /var/lock/news/ >>> /var/lock/news/.keep >>> Safely unmerging already-installed instance... --- !mtime obj /var/lock/news/.keep --- !empty dir /var/lock/news --- !empty dir /var/lock --- !empty dir /var That is OK and fetchnews works:-) and emerge leafnode again is also OK. Can it be caused by a sys-apps/baselayout update or portage bug? It has a 'keepdir /var/log/new'!
I just re-emerged baselayout to see what happens, but everything works as expected (/var/lock/news still here). So maybe there was a bug in the baselayout package or in an older version of portage, but everything seems to work now. So if you and Bruce agree, I think we can close this bug. -Markus-
It OK with me to close this bug.
