[Bug 1051262] Re: nfs-common < 1.2.6 idmapd.conf parsing errors

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be fixed for that release ** Changed in: nfs-utils (Ubuntu Precise) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.la

[Bug 1051262] Re: nfs-common < 1.2.6 idmapd.conf parsing errors

2012-09-26 Thread Steve Langasek
Thanks. The point of having a reproducible test case is to confirm that the change fixes the problem you're experienced. It also helps us assess the practical impact of the bug. In this particular case, it sounds like this bug only impacts users who are using local versions of Ubuntu packages.

Re: [Bug 1051262] Re: nfs-common < 1.2.6 idmapd.conf parsing errors

2012-09-18 Thread JiriHorky
Hi, I could not resist to say that pointing at a quite common bug in a C program (non terminating string with a 0 character) together with a link to the fix should be enough in my opinion. As the exact result of the idmapd behavior with this bug depends on a way glibc/kernel allocates the memo

[Bug 1051262] Re: nfs-common < 1.2.6 idmapd.conf parsing errors

2012-09-18 Thread Steve Langasek
Jiri, Could you provide a reproducible test case demonstrating the problem? ** Changed in: nfs-utils (Ubuntu) Status: New => Fix Released ** Also affects: nfs-utils (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: nfs-utils (Ubuntu Precise) Status: New =