During upgrade under unstable:

       Processing triggers for menu ...
       W: Unable to read /etc/apt/preferences.d/ - FileExists (2: No such file or directory)

Could this be caused by the fact that here the /etc/apt is a symlink and
points to another location?

reassign 580152 apt apt/0.7.25.3
thanks

Hi APT team,

Jari Aalto wrote:

To my untrained eye, this looks like a message from APT.  Any insights?

Full system information is at http://bugs.debian.org/580152

Thanks,
Jonathan

Hi,

But it might an apt tool called from the menu trigger processing code.

Cheers,

I checked all the menu-methods in Debian and none of them are calling
an apt tool, but you can try to run update-menus as root to see if that
displays this warning.

Cheers,

Hi *,

2010/5/4 Raphael Hertzog <hertzog@debian.org>:
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

David Kalnischkies <kalnischkies+debian@gmail.com> writes:

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.

MfG
        Goswin

2010/5/5 Goswin von Brederlow <goswin-v-b@web.de>:
E/W: generic apt error - method used (errno: strerror() with "exact" reason)

The plain reason is that we have a waste amount of possibilities why a file
is not readable: doesn't exist, broken link, insufficient rights, …
writing a message for all of them in APT would be insane.
On the other hand some of the error messages given by strerror() aren't
verbose and/or exact enough to be used alone, so the middle way was chosen.
(I think the Methodname is their to enable Error to do something special
with certain failures as noted in the Description of the file, but it is
unused so far - but from time to time useful to map (translated) error
messages to their untranslated equivalent in bugreports.


I have convert now this and a few other calls from FileExists() to
DirectoryExists() which was added recently to check if it is really a
directory and not a file, but this doesn't change much…

Any further suggestions?


Best regards,

David Kalnischkies

David Kalnischkies <kalnischkies+debian@gmail.com> writes:
signify that the first is a location (the function causing the error)
and not the error message itself. Or:

W: Unable to read /etc/apt/preferences.d/ in FileExists(): (2) No such file or directory

More usefull I guess would be the name of the calling function since, as
you say, lots of places will check if a file exists.

MfG
        Goswin

Hello,

Good morning,

We have gone through your samples from a partner and Here is our  Order
List. Please do bear in mind that we are very much in  need of this
order, quote your competitive prices.

Kindly send the Order confirmation.

Your early reply will be much appreciated.

Best Regards,

Maryanah Erwin.

PT FINDORA INTERNUSA

Jln Pahlawan 66 Kec. Arjawinangun

45162 CIREBON West-Java INDONESIA

tel : +62 231 357334

fax: +62 231 357260

email: marketing@findora.com

I ran into this recently.

For .d directories like /etc/apt/preferences.d, it'd be nice if apt were
silent about the directory not existing, and if it just treated that the
same as an empty directory.

Refer to attachment for more information.



Thanks. Regards