Package: hyphen-zu
Version: 1:3.3.0-4
The encoding given at the first line of the hyph_zu_ZA.dic file is
ISO08859-1, which is not a valid alias for ISO-8859-1 according to
http://en.wikipedia.org/wiki/Iso-8859-1.
I assume that this is a simple typo when I look at 0 and - on a
qwerty keyboard ;).
According to man 4 hunspell, ISO8859-1 seems to be the right way to
spell the encoding.
signature.asc
Description: This is a digitally signed message part
Le mardi 25 décembre 2012 à 21:19 +0100, Slavko a écrit :
Hi Guillaume,
you are right about improper pam module. But it is only part of the
problem (see below).
First, solution about missing pam module is pretty simple - place the
downloaded pam.py (link in previous post - i tried the 1.3
The PAM authentication module is available in Radicale since version
0.7. PAM with older versions won't work.
For 0.7+, the module handling PAM authentication in Radicale is called
PAM.py, and can be used with [acl]type=PAM in the config file
(uppercase everywhere, no problem in the config file).
Hi Martin, hi Jonas,
First of all, thanks Jonas for your work, I really appreciate it.
[...]
A few comments in order to proceed:
* Regarding your FIXME: I don't really see an issue with $HOME, possibly
a lack of understanding. The initscript already (re-)creates the default
directories
Hi Martin, hi Jonas!
First of all, thanks Jonas for your work, I really appreciate it.
[...]
A few comments in order to proceed:
* Regarding your FIXME: I don't really see an issue with $HOME, possibly
a lack of understanding. The initscript already (re-)creates the default
directories
I've sent the mail twice to the list *and* to you, sorry.
Le jeudi 12 avril 2012 à 14:50 +0200, Martin Stigge a écrit :
Got your mail 4 times, weird.
On Thu, 2012-04-12 at 13:03 +0200, Guillaume Ayoub wrote:
* For the file-store path patch, I see what you are getting at, however,
my
Here are 2 init scripts sent by Łukasz (radicale.init +
radicale.default) and Nicolas (radicale). I've never written any init
script, but they seem to work quite well. Nicolas just said that his
version was not working if start was called twice: the pid of the
process does not change, but the pid
I hesitate, as I fear this will steal much attention when I dive into
it: Better with no init script than a badly implemented one.
You're right.
Best would be if Radicale could be perfected as a daemon. See e.g. at
http://0pointer.de/lennart/projects/libdaemon/#overview for what it
This bug is due to a missing space in the warning message. It has been
reported upstream on the courier users mailing list:
http://sourceforge.net/mailarchive/forum.php?thread_name=4BA4F266.3080603%40linuxia.deforum_name=courier-users
--
To UNSUBSCRIBE, email to
I tested the patch on my machine.
- applied on tar, it fixed tar;
- applied on coreutils, it fixed touch.
Everything seems to work now (postfix, apt-get, dpkg, etc.), but other
softwares calling futimens() may be affected.
Thanks a lot for your work,
--
Guillaume Ayoub
--
To UNSUBSCRIBE
Package: libc6
Version: 2.10.2-3
Severity: important
Hello,
Just after upgrading libc6 from 2.10.2-2 to 2.10.2-3, utime calls fail for
folders (not for regular files). This breaks main programs such as tar, dpkg,
touch and postfix.
Here are 2 examples:
$ ls -l
drwxr-xr-x 2 user users 4096
More information can be found at:
http://www.mail-archive.com/debian-u...@lists.debian.org/msg562576.html
As Sven says, the bug is caused by debian/patches/any/cvs-futimens.diff,
reporting the 'bad file descriptor' error. Without this patch, futimens()
failed silently, as utimensat() has been
Package: libc6
Version: 2.10.2-3
Severity: important
Hello,
Just after upgrading libc6 from 2.10.2-2 to 2.10.2-3, utime calls fail for
folders (not for regular files). This breaks main programs such as tar, dpkg,
touch and postfix.
Here are 2 examples:
$ ls -l
drwxr-xr-x 2 user users 4096
More information can be found at:
http://www.mail-archive.com/debian-u...@lists.debian.org/msg562576.html
As Sven says, the bug is caused by debian/patches/any/cvs-futimens.diff,
reporting the 'bad file descriptor' error. Without this patch, futimens()
failed silently, as utimensat() has been
This bug has been reported in Gnome Bugzilla, for Epiphany and Evolution:
http://bugzilla.gnome.org/show_bug.cgi?id=562535
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
16 matches
Mail list logo
