#include <hallo.h>
* Tim Freeman [Sat, Jun 25 2005, 07:06:27PM]:
> >Tomorrow didn't work, ftp-master server is moving. You can get them from
> >rootfs.net/encfs if you wish to test them.
>
> I'm wondering what the normal procedure is in this case. If encfs is
> used with a bad version of fuse, then encfs shows a symptom that's
> really a bug in fuse. Do you declare encfs to be incompatible with
> the buggy version of fuse, so people with a current encfs are
> guaranteed to see good behavior, or do you just pass the buck to fuse
> and let people decide for themselves which versions they want to run?
I have no control over it, the best thing I can do is reassigning your
report to fuse-source and hope that Bartosz will deal with it.
What (realisticaly) can I do anyways? The user can install any fuse
version, even an old incompatible one. I can only rely on the sanity (or
luck) of the one admin.
IMO we have a typical example of a Debian Stable Problem here. Upstream
version had an ugly bug and it has been fixed in our development branch
but it won't be fixed in Debian Stable forever because the problem is
not "that bad".
Regards,
Eduard.
--
Immerhin meint die Filmförderungsanstalt, im Jahr 2002 seien 59
Millionen CD-Rohlinge von 5,9 Millionen Nutzern mit Filmen bespielt
worden, im Durchschnitt also zwölf Rohlinge pro Anwender.
-- <http://www.heise.de/newsticker/data/see-08.04.03-000/>
