[arch-dev-public] nfs-utils 1.1.0
This has been around for a few weeks, and is described as a "fairly significant new release". So standard practice would be to put it in testing, wait for bug reports, fix them , move to current - right? Except for one thing - who runs testing on a NFS server? I know I don't. I've built it (against current) and installed it here, and all's fine so far, but mine is a very straightforward setup. Would I just put out a call for testers, who can then pacman -U it from somewhere? Or are there better ways to handle this? T.
On 6/1/07, Tom K <tom@archlinux.org> wrote:
This has been around for a few weeks, and is described as a "fairly significant new release". So standard practice would be to put it in testing, wait for bug reports, fix them , move to current - right? Except for one thing - who runs testing on a NFS server? I know I don't.
I've built it (against current) and installed it here, and all's fine so far, but mine is a very straightforward setup. Would I just put out a call for testers, who can then pacman -U it from somewhere? Or are there better ways to handle this?
I just built it and will give it a try. Is there a changelog anywhere that is easy to see? The one in the package looks woefully outdated. In addition, I think a configure flag can be dropped- --enable-nfsv3 is the default. -Dan
Dan McGee wrote:
On 6/1/07, Tom K <tom@archlinux.org> wrote:
This has been around for a few weeks, and is described as a "fairly significant new release". So standard practice would be to put it in testing, wait for bug reports, fix them , move to current - right? Except for one thing - who runs testing on a NFS server? I know I don't.
I've built it (against current) and installed it here, and all's fine so far, but mine is a very straightforward setup. Would I just put out a call for testers, who can then pacman -U it from somewhere? Or are there better ways to handle this?
I just built it and will give it a try. Is there a changelog anywhere that is easy to see? The one in the package looks woefully outdated.
http://sourceforge.net/project/shownotes.php?release_id=507588&group_id=14
In addition, I think a configure flag can be dropped- --enable-nfsv3 is the default.
Thanks. T.
On 6/1/07, Tom K <tom@archlinux.org> wrote:
Dan McGee wrote:
On 6/1/07, Tom K <tom@archlinux.org> wrote:
This has been around for a few weeks, and is described as a "fairly significant new release". So standard practice would be to put it in testing, wait for bug reports, fix them , move to current - right? Except for one thing - who runs testing on a NFS server? I know I don't.
I've built it (against current) and installed it here, and all's fine so far, but mine is a very straightforward setup. Would I just put out a call for testers, who can then pacman -U it from somewhere? Or are there better ways to handle this?
I just built it and will give it a try. Is there a changelog anywhere that is easy to see? The one in the package looks woefully outdated.
No problems since I installed, and I've rebooted at least once without problems. -Dan
On 6/4/07, Dan McGee <dpmcgee@gmail.com> wrote:
On 6/1/07, Tom K <tom@archlinux.org> wrote:
Dan McGee wrote:
On 6/1/07, Tom K <tom@archlinux.org> wrote:
This has been around for a few weeks, and is described as a "fairly significant new release". So standard practice would be to put it in testing, wait for bug reports, fix them , move to current - right? Except for one thing - who runs testing on a NFS server? I know I don't.
I've built it (against current) and installed it here, and all's fine so far, but mine is a very straightforward setup. Would I just put out a call for testers, who can then pacman -U it from somewhere? Or are there better ways to handle this?
I just built it and will give it a try. Is there a changelog anywhere that is easy to see? The one in the package looks woefully outdated.
No problems since I installed, and I've rebooted at least once without problems.
-Dan
Is this going to make it to current at some point? Don't want it to get forgotten. -Dan
Dan McGee wrote:
On 6/4/07, Dan McGee <dpmcgee@gmail.com> wrote:
On 6/1/07, Tom K <tom@archlinux.org> wrote:
Dan McGee wrote:
This has been around for a few weeks, and is described as a "fairly significant new release". So standard practice would be to put it in testing, wait for bug reports, fix them , move to current - right? Except for one thing - who runs testing on a NFS server? I know I don't.
I've built it (against current) and installed it here, and all's fine so far, but mine is a very straightforward setup. Would I just put out a call for testers, who can then pacman -U it from somewhere? Or are there better ways to handle this? I just built it and will give it a try. Is there a changelog anywhere
On 6/1/07, Tom K <tom@archlinux.org> wrote: that is easy to see? The one in the package looks woefully outdated. No problems since I installed, and I've rebooted at least once without problems.
-Dan
Is this going to make it to current at some point? Don't want it to get forgotten.
-Dan
Yes, it's on the way - apologies for delays caused by time- and energy-consuming real life stuff. If anyone needs it in a hurry, please go ahead and do it. We need to fix FS#7368 while we're there. T.
participants (2)
-
Dan McGee
-
Tom K