Bug#522698: Exclude kfreebsd architecture from openntpd build?
Hi Dererk, I'm afraid it's not yet so easy to debug on kfreebsd-* flavors, as the port lack most common (unless for me) debugging tools, therefore, you might understand it's not a matter like noone cares. Ok, so I understand you are having problems debugging on kfreebsd for reasons that are beyond you. I would say this is even more reason to exclude kfreebsd from the build until the situation gets better. On the other hand, against what common sense could tell you, openntpd doesn't adjust the system's clock rate (it uses adjtime()), although Its something you take for granted when you install a software like this, it really ends up being more painful than useful for end-users that just want their sandboxes clocked (#306106). I understand that there may be other problems with the openntpd package, but I do not see them tagged 'grave' at this point. Therefore I do not think that bringing them into discussion here will change anything w.r.t. to this bug. Unfortunately, the only patch I could manage to get running on replacing adjtime() with adjtimex() didn't work as expected. [ OT for this bug ] Do you mean this patch? http://dtucker.freeshell.org/openntpd/patches/openntpd-3.6.1p1-linux-adjtimex.patch What is the problem with it? Regards, Robbert -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#522698: Exclude kfreebsd architecture from openntpd build?
Hi, For a while, noone seems to care about this grave openntpd bug on the kfreebsd platform. Because of this, the package was eventually removed from testing. For people running on different architectures than kfreebsd this is very unfortunate, because they did not suffer from this grave bug. Can't we just exclude kfreebsd-* from the Architecture field in debian/control so that we don't build the package for kfreebsd (pending the kfreebsd bug getting fixed)? Regards, Robbert -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#394097: libapache2-mod-auth-pam: doesnt work with Apache 2.1
Since the auth mechanisms were changed in Apache 2.1 this module does not work any more. It probably should be replaced by mod_authn_pam available at http://mod-auth.sourceforge.net/docs/mod_authn_pam/ It works for me. Can you be more specific? I am going to lower this to 'important' as I am still able to use the package with apache 2.2.3-2, and would not like it to disappear while there's no mod_authn_pam package yet. Regards, Robbert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#388386: [patch]
Hi Eduard, I am a LUFS user too, so a few comments on this. Eduard Bloch wrote: Stupid question: why do you need LUFS? I consider requesting its removal because almost everything has moved to FUSE or can be used with lufis, the fuse/lufs bridge. There is no lufis Debian package :( Does curlftp do what you need? See http://frank.thomas-alfeld.de/download/debian/curlftpfs/ Curlftpfs is buggy itself (see bts). I find it freezing now and then, while LUFS has worked perfectly for a long time. It would be nice if LUFS can stay, at least until there is a working substitute in Debian. Regards, Robbert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
