Re: Bug#580152: dpkg: trigger - W: Unable to read /etc/apt/preferences.d/ - FileExists (2: No such file or directory)
David Kalnischkies <kalnischkies+debian@gmail.com> writes:
> Hi *,
>
> 2010/5/4 Raphael Hertzog <hertzog@debian.org>:
>> On Mon, 03 May 2010, Jonathan Nieder wrote:
>>> > Processing triggers for menu ...
>>> > W: Unable to read /etc/apt/preferences.d/ - FileExists (2: No such file or directory)
At least the warning should be fixed. Is the error that it exists and
since when is a directory a file? Or that it doesn't? The two errors
contradict each other.
>>> > Could this be caused by the fact that here the /etc/apt is a symlink and
>>> > points to another location?
>>>
>>> To my untrained eye, this looks like a message from APT. Any insights?
>>
>> But it might an apt tool called from the menu trigger processing code.
>
> While this would be possible it is apt's normal behavior to print errors
> and/or warnings at the end so this is to 99% an error of the "main" apt.
>
> Still, i don't know what this bugreport actually asks for:
> The directory is included in the apt package so in a normal environment
> it should be available after the correct installation of 0.7.22 and above.
> And in an unnormal environment (in which directories magically disappear)
> the warning is important? (user configuration could be disappeared too)
>
> A linked /etc/apt isn't a problem (at least not for me).
> The dir is btw by default empty - as is sources.list.d and trusted.gpg.d ?
>
> Best regards,
>
> David Kalnischkies
MfG
Goswin
Reply to: