I agree that autofs-5.0.8, now in Debian unstable, is clearly broken.
Looking in what appears to be an upstream location (
https://www.kernel.org/pub/linux/daemons/autofs/v5/), I see evidence of
active, on-going development. There is not only an upstream version 5.0.9
that is mentioned in a
16.11.2014 00:29, Thomas Vaughan wrote:
On Fri, 14 Nov 2014 14:23:40 +0300 Michael Tokarev m...@tls.msk.ru
mailto:m...@tls.msk.ru wrote:
Sure, why not -- is `important' enough? I'd like to make it RC
so autofs is removed from debian finally, as it is just too
broken
.
If autofs might
On Fri, 14 Nov 2014 14:23:40 +0300 Michael Tokarev m...@tls.msk.ru wrote:
Sure, why not -- is `important' enough? I'd like to make it RC
so autofs is removed from debian finally, as it is just too
broken
.
If autofs might be removed from Debian, then I have a question.
Is there a
It appears that the upstream fix is
https://www.kernel.org/pub/linux/daemons/autofs/v5/patches-5.0.9/autofs-5.0.8-fix-ipv6-libtirpc-getport-proto-not-set.patch
and is in 5.0.9.
BTW, could you please increase the severity of the bug?
Regards, Pavel
--
To UNSUBSCRIBE, email to
Control: severity -1 important
14.11.2014 14:20, Pavel Cahyna wrote:
It appears that the upstream fix is
https://www.kernel.org/pub/linux/daemons/autofs/v5/patches-5.0.9/autofs-5.0.8-fix-ipv6-libtirpc-getport-proto-not-set.patch
Wow, a bug fixed upstream in autofs. Quite a rare case.
and
5 matches
Mail list logo
