Bug#437342: nfs mounts no longer work in testing after upgrade
Package: nfs-kernel-server Version: 1.1.0-11 Running: Debian Testing Kernel: 2.6.22 After apt-get upgrade, NFS no longer works: [ 2059.998309] nfs: server p34 not responding, still trying [ 2289.314682] nfs: server l2 not responding, still trying Aug 11 18:06:27 p34 mountd[6828]: Cannot export /, possibly unsupported filesystem or fsid= required Aug 11 18:06:26 l2 mountd[1825]: Cannot export /, possibly unsupported filesystem or fsid= required I am reading the new docs now but in Debian are things like this supposed to just break or should there be a warning about them in the changelog/etc-- or did I miss it? Justin. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#437342: nfs mounts no longer work in testing after upgrade
On Sat, Aug 11, 2007 at 06:53:39PM -0400, Justin Piszcz wrote: > After apt-get upgrade, NFS no longer works: Did you upgrade the server or the client? Which version did you upgrade from? What does your /etc/exports look like? /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#437342: nfs mounts no longer work in testing after upgrade
On Sun, 12 Aug 2007, Steinar H. Gunderson wrote: On Sat, Aug 11, 2007 at 06:53:39PM -0400, Justin Piszcz wrote: After apt-get upgrade, NFS no longer works: Did you upgrade the server or the client? Which version did you upgrade from? What does your /etc/exports look like? /* Steinar */ -- Homepage: http://www.sesse.net/ File: /etc/exports I upgraded from whichever version was pushed last Saturday (I upgrade once a week). 2007-04-14 04:30:24 status unpacked nfs-kernel-server 1:1.0.12-4+b1 2007-04-14 04:30:24 status unpacked nfs-kernel-server 1:1.0.12-4+b1 2007-06-23 04:32:40 status unpacked nfs-kernel-server 1:1.0.12-4+b1 2007-06-23 04:32:41 status unpacked nfs-kernel-server 1:1.1.0-4 2007-06-23 04:32:41 status unpacked nfs-kernel-server 1:1.1.0-4 2007-06-23 04:33:14 status unpacked nfs-kernel-server 1:1.1.0-4 2007-06-23 04:33:14 status unpacked nfs-kernel-server 1:1.1.0-4 2007-07-28 04:18:43 status unpacked nfs-kernel-server 1:1.1.0-4 2007-07-28 04:18:43 status unpacked nfs-kernel-server 1:1.1.0-11 BEFORE: /10.0.0.0/24(async,rw,no_root_squash,no_subtree_check) /r1 10.0.0.0/24(async,rw,no_root_squash,no_subtree_check) AFTER: /10.0.0.0/24(async,rw,no_root_squash,no_subtree_check,fsid=0) /r1 10.0.0.0/24(async,rw,no_root_squash,no_subtree_check,fsid=1) I had to put fsid=1 for the second one as it was still complaining until I did this and restart the nfs-kernel-server, so far it appears to be OK (have not seen any complaints in syslog yet). Justin. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#437342: nfs mounts no longer work in testing after upgrade
On Sun, Aug 12, 2007 at 04:08:21AM -0400, Justin Piszcz wrote: > 2007-07-28 04:18:43 status unpacked nfs-kernel-server 1:1.1.0-4 > 2007-07-28 04:18:43 status unpacked nfs-kernel-server 1:1.1.0-11 Uhm, are you saying that upgrading the server from 1:1.1.0-4 to 1:1.1.0-11 breaks rpc.mountd? That sounds very weird, as there's been exactly zero changes to mountd in that timeframe... /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#437342: nfs mounts no longer work in testing after upgrade
On Sun, 12 Aug 2007, Steinar H. Gunderson wrote: On Sun, Aug 12, 2007 at 04:08:21AM -0400, Justin Piszcz wrote: 2007-07-28 04:18:43 status unpacked nfs-kernel-server 1:1.1.0-4 2007-07-28 04:18:43 status unpacked nfs-kernel-server 1:1.1.0-11 Uhm, are you saying that upgrading the server from 1:1.1.0-4 to 1:1.1.0-11 breaks rpc.mountd? That sounds very weird, as there's been exactly zero changes to mountd in that timeframe... /* Steinar */ -- Homepage: http://www.sesse.net/ Well I did not change anything on the client, apt-get dist-upgrade once a week and from week1 -> week2 (after upgrade) is when I noticed it. Justin. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#437342: nfs mounts no longer work in testing after upgrade
On Sun, Aug 12, 2007 at 10:34:13AM -0400, Justin Piszcz wrote: >> Uhm, are you saying that upgrading the server from 1:1.1.0-4 to 1:1.1.0-11 >> breaks rpc.mountd? That sounds very weird, as there's been exactly zero >> changes to mountd in that timeframe... > Well I did not change anything on the client, apt-get dist-upgrade once a > week and from week1 -> week2 (after upgrade) is when I noticed it. Could you try downgrading nfs-common and nfs-kernel-server on the server and see if the problem goes away? /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#437342: nfs mounts no longer work in testing after upgrade
Hi. I'm using Debian sid and I upgraded the system today (the last complete upgrade was about one month ago). I get the "failed to contact portmap" errors. nfsd: unexporting all filesystems RPC: failed to contact portmap (errno -5). NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory NFSD: starting 90-second grace period I am stuck. I used the proposed workaround (fsid=0) and it didn't work. I tried downgrading nfs-kernel-server to 1:1.1.0-13, and I get the same error. This is what I get in the client side: Sending DHCP requests .., OK IP-Config: Got DHCP answer from 0.0.0.0, my address is 192.168.1.101 IP-Config: Unable to set interface netmask (-22). Looking up port of RPC 13/2 on 192.168.1.198 portmap: server 192.168.1.198 not responding, timed out Root-NFS: Unable to get nfsd port number from server, using default Looking up port of RPC 15/1 on 192.168.1.198 portmap: server 192.168.1.198 not responding, timed out Root-NFS: Unable to get mountd port number from server, using default mount: server 192.168.1.198 not responding, timed out Root-NFS: Server returned error -5 while mounting /bulk/emqbit/rootfs/oe VFS: Unable to mount root fs via NFS, trying floppy. VFS: Cannot open root device "nfs" or unknown-block(2,0) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0) Note that I also used only NFS v3, and not NFS v4. I was using this setup before the upgrade. Regards, Nelson.- -- http://arhuaco.org http://emQbit.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#437342: nfs mounts no longer work in testing after upgrade
On Sun, Aug 12, 2007 at 08:28:30PM -0500, Nelson Castillo wrote: > I'm using Debian sid and I upgraded the system today > (the last complete upgrade was about one month ago). > I get the "failed to contact portmap" errors. Is the portmapper running at all? (ps aux | grep portmap) > I am stuck. I used the proposed workaround (fsid=0) and it didn't work. I believe this is a separate bug. Please open a new one. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#437342: nfs mounts no longer work in testing after upgrade
In 8/12/07, Steinar H. Gunderson <[EMAIL PROTECTED]> wrote: > On Sun, Aug 12, 2007 at 08:28:30PM -0500, Nelson Castillo wrote: > > I'm using Debian sid and I upgraded the system today > > (the last complete upgrade was about one month ago). > > I get the "failed to contact portmap" errors. > > Is the portmapper running at all? (ps aux | grep portmap) Yes, it is. I'll open the bug. # ps ax|grep portmap daemon2594 0.0 0.0 1816 488 ?Ss 17:49 0:00 /sbin/portmap BTW, the NFS troubleshooting documentation references a rcpinfo binary. Is it obsoleted? Perhaps I need to install another package. Thanks. -- http://arhuaco.org http://emQbit.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#437342: nfs mounts no longer work in testing after upgrade
On Sun, Aug 12, 2007 at 09:35:48PM -0500, Nelson Castillo wrote: > BTW, the NFS troubleshooting documentation references a rcpinfo binary. > Is it obsoleted? Perhaps I need to install another package. You probably mean rpcinfo. It's included in the libc6 package, so it's definitely on your system. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#437342: nfs mounts no longer work in testing after upgrade
On 8/12/07, Steinar H. Gunderson <[EMAIL PROTECTED]> wrote: > On Sun, Aug 12, 2007 at 08:28:30PM -0500, Nelson Castillo wrote: > > I'm using Debian sid and I upgraded the system today > > (the last complete upgrade was about one month ago). > > I get the "failed to contact portmap" errors. > > Is the portmapper running at all? (ps aux | grep portmap) > > > I am stuck. I used the proposed workaround (fsid=0) and it didn't work. > > I believe this is a separate bug. Please open a new one. Done. I opened: Bug#437525: nfs-kernel-server: Kernel prints "RPC: failed to contact portmap (errno -5)" In my case, portmap was bound to the loopback address in /etc/default/portmap. Removing this option allowed me to do the remote mount. I don't know if #437525 is actually a bug, but at least the message is misleading and it's ok to have it documented somewhere. Thanks for your help. -- http://arhuaco.org http://emQbit.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#437342: nfs mounts no longer work in testing after upgrade
On Sun, Aug 12, 2007 at 04:37:01PM +0200, Steinar H. Gunderson wrote: >>> Uhm, are you saying that upgrading the server from 1:1.1.0-4 to 1:1.1.0-11 >>> breaks rpc.mountd? That sounds very weird, as there's been exactly zero >>> changes to mountd in that timeframe... >> Well I did not change anything on the client, apt-get dist-upgrade once a >> week and from week1 -> week2 (after upgrade) is when I noticed it. > Could you try downgrading nfs-common and nfs-kernel-server on the server and > see if the problem goes away? Apologies for the noise in the bug report; I hope we can get back to tracking this, as I don't seem to be able to reproduce it myself. Does a downgrade help? By the way, just on a random note, what architecture is this? (You did not use reportbug to report the bug, which leaves out a lot of information commonly useful in spotting non-obvious things about your configuration. :-) ) /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#437342: nfs mounts no longer work in testing after upgrade
On Thu, 16 Aug 2007, Steinar H. Gunderson wrote: On Sun, Aug 12, 2007 at 04:37:01PM +0200, Steinar H. Gunderson wrote: Uhm, are you saying that upgrading the server from 1:1.1.0-4 to 1:1.1.0-11 breaks rpc.mountd? That sounds very weird, as there's been exactly zero changes to mountd in that timeframe... Well I did not change anything on the client, apt-get dist-upgrade once a week and from week1 -> week2 (after upgrade) is when I noticed it. Could you try downgrading nfs-common and nfs-kernel-server on the server and see if the problem goes away? Apologies for the noise in the bug report; I hope we can get back to tracking this, as I don't seem to be able to reproduce it myself. Does a downgrade help? By the way, just on a random note, what architecture is this? (You did not use reportbug to report the bug, which leaves out a lot of information commonly useful in spotting non-obvious things about your configuration. :-) ) /* Steinar */ -- Homepage: http://www.sesse.net/ Arch = x86_64 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#437342: nfs mounts no longer work in testing after upgrade
On Thu, Aug 16, 2007 at 03:58:15AM -0400, Justin Piszcz wrote: > Arch = x86_64 And does a downgrade help? /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#437342: nfs mounts no longer work in testing after upgrade
On Thu, 16 Aug 2007, Steinar H. Gunderson wrote: On Thu, Aug 16, 2007 at 03:58:15AM -0400, Justin Piszcz wrote: Arch = x86_64 And does a downgrade help? /* Steinar */ -- Homepage: http://www.sesse.net/ Unsure, I have mounted with the options I mentioned earlier and that seems to have resolved the problems, all partitions are SW RAID 1 and 5 and the mount daemon/etc does not appear to know how to deal with them after last weekend's upgrades. Justin. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#437342: nfs mounts no longer work in testing after upgrade
On Thu, Aug 16, 2007 at 11:44:18AM -0400, Justin Piszcz wrote: > Unsure, I have mounted with the options I mentioned earlier and that seems > to have resolved the problems, all partitions are SW RAID 1 and 5 and the > mount daemon/etc does not appear to know how to deal with them after last > weekend's upgrades. Well, explicit fsid= should really not be needed. I haven't seen any other reports of this, though, and I haven't seen it myself on the NFS server at home, which does indeed serve off both RAID 1 and RAID 5 from md. I guess it's up to you, though -- if you think fsid= is an OK workaround for you, we can just close the bug. If not, we'll need to try to figure out what caused this to break, and the first logical step is a downgrade of nfs-common and nfs-kernel-server. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#437342: nfs mounts no longer work in testing after upgrade
On Thu, 16 Aug 2007, Steinar H. Gunderson wrote: On Thu, Aug 16, 2007 at 11:44:18AM -0400, Justin Piszcz wrote: Unsure, I have mounted with the options I mentioned earlier and that seems to have resolved the problems, all partitions are SW RAID 1 and 5 and the mount daemon/etc does not appear to know how to deal with them after last weekend's upgrades. Well, explicit fsid= should really not be needed. I haven't seen any other reports of this, though, and I haven't seen it myself on the NFS server at home, which does indeed serve off both RAID 1 and RAID 5 from md. I guess it's up to you, though -- if you think fsid= is an OK workaround for you, we can just close the bug. If not, we'll need to try to figure out what caused this to break, and the first logical step is a downgrade of nfs-common and nfs-kernel-server. /* Steinar */ -- Homepage: http://www.sesse.net/ You can resolve, it works with fsid=X, thanks. Justin. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#437342: nfs mounts no longer work in testing after upgrade
On Thu, 16 Aug 2007, Justin Piszcz wrote: On Thu, 16 Aug 2007, Steinar H. Gunderson wrote: On Thu, Aug 16, 2007 at 11:44:18AM -0400, Justin Piszcz wrote: Unsure, I have mounted with the options I mentioned earlier and that seems to have resolved the problems, all partitions are SW RAID 1 and 5 and the mount daemon/etc does not appear to know how to deal with them after last weekend's upgrades. Well, explicit fsid= should really not be needed. I haven't seen any other reports of this, though, and I haven't seen it myself on the NFS server at home, which does indeed serve off both RAID 1 and RAID 5 from md. I guess it's up to you, though -- if you think fsid= is an OK workaround for you, we can just close the bug. If not, we'll need to try to figure out what caused this to break, and the first logical step is a downgrade of nfs-common and nfs-kernel-server. /* Steinar */ -- Homepage: http://www.sesse.net/ You can resolve, it works with fsid=X, thanks. Justin. May need to re-open, happening even with fsid: Aug 18 18:53:36 p34 mountd[11986]: Cannot export /, possibly unsupported filesystem or fsid= required I will try to downgrade. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#437342: nfs mounts no longer work in testing after upgrade
On Sat, 18 Aug 2007, Justin Piszcz wrote: On Thu, 16 Aug 2007, Justin Piszcz wrote: On Thu, 16 Aug 2007, Steinar H. Gunderson wrote: On Thu, Aug 16, 2007 at 11:44:18AM -0400, Justin Piszcz wrote: Unsure, I have mounted with the options I mentioned earlier and that seems to have resolved the problems, all partitions are SW RAID 1 and 5 and the mount daemon/etc does not appear to know how to deal with them after last weekend's upgrades. Well, explicit fsid= should really not be needed. I haven't seen any other reports of this, though, and I haven't seen it myself on the NFS server at home, which does indeed serve off both RAID 1 and RAID 5 from md. I guess it's up to you, though -- if you think fsid= is an OK workaround for you, we can just close the bug. If not, we'll need to try to figure out what caused this to break, and the first logical step is a downgrade of nfs-common and nfs-kernel-server. /* Steinar */ -- Homepage: http://www.sesse.net/ You can resolve, it works with fsid=X, thanks. Justin. May need to re-open, happening even with fsid: Aug 18 18:53:36 p34 mountd[11986]: Cannot export /, possibly unsupported filesystem or fsid= required I will try to downgrade. ii nfs-common 1:1.0.10-6+etch.1 NFS support files common to client and serve ii nfs-kernel-server1:1.0.10-6+etch.1 Kernel NFS server support Using these for now and without fsid=, will see if it happens again. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#437342: nfs mounts no longer work in testing after upgrade
On Sat, Aug 18, 2007 at 07:00:54PM -0400, Justin Piszcz wrote: > Using these for now and without fsid=, will see if it happens again. OK. Are you implying that this only happens every now and then? From your initial description, it sounded like it was consistent. An strace of rpc.mountd at the moment it happens would probably be very useful. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#437342: nfs mounts no longer work in testing after upgrade
On Sun, 19 Aug 2007, Steinar H. Gunderson wrote: On Sat, Aug 18, 2007 at 07:00:54PM -0400, Justin Piszcz wrote: Using these for now and without fsid=, will see if it happens again. OK. Are you implying that this only happens every now and then? From your initial description, it sounded like it was consistent. An strace of rpc.mountd at the moment it happens would probably be very useful. /* Steinar */ -- Homepage: http://www.sesse.net/ Intermittent only it seems, so far it is good with the old version of nfs-kernel-server and nfs-common. Justin. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#437342: nfs mounts no longer work in testing after upgrade
On Sun, 19 Aug 2007, Justin Piszcz wrote: On Sun, 19 Aug 2007, Steinar H. Gunderson wrote: On Sat, Aug 18, 2007 at 07:00:54PM -0400, Justin Piszcz wrote: Using these for now and without fsid=, will see if it happens again. OK. Are you implying that this only happens every now and then? From your initial description, it sounded like it was consistent. An strace of rpc.mountd at the moment it happens would probably be very useful. /* Steinar */ -- Homepage: http://www.sesse.net/ Intermittent only it seems, so far it is good with the old version of nfs-kernel-server and nfs-common. Justin. Need to dig into this, it now happens on an x86 box, in particular, when you run find // across the root filesystem. Aug 20 04:41:58 l2 mountd[6342]: Cannot export /, possibly unsupported filesystem or fsid= required Can you try that and see if you have the same problem? Justin. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#437342: nfs mounts no longer work in testing after upgrade
On Mon, Aug 20, 2007 at 04:45:20AM -0400, Justin Piszcz wrote: > Need to dig into this, it now happens on an x86 box, in particular, when > you run find // across the root filesystem. This sounds awfully lot like a duplicate of #435056. Could you try the latest sid version and see if it fixes your problem? /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#437342: nfs mounts no longer work in testing after upgrade
On Mon, 20 Aug 2007, Steinar H. Gunderson wrote: On Mon, Aug 20, 2007 at 04:45:20AM -0400, Justin Piszcz wrote: Need to dig into this, it now happens on an x86 box, in particular, when you run find // across the root filesystem. This sounds awfully lot like a duplicate of #435056. Could you try the latest sid version and see if it fixes your problem? /* Steinar */ -- Homepage: http://www.sesse.net/ Could you please remind me of the command? apt-get install -t unstable nfs-kernel-server nfs-common? Justin. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#437342: nfs mounts no longer work in testing after upgrade
On Mon, Aug 20, 2007 at 12:15:50PM -0400, Justin Piszcz wrote: > Could you please remind me of the command? apt-get install -t unstable > nfs-kernel-server nfs-common? Assuming you've got unstable in your sources.list, that should do fine. (You don't really want to be using apt-get in 2007, though -- aptitude is a fine replacement.) /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#437342: nfs mounts no longer work in testing after upgrade
On Mon, 20 Aug 2007, Steinar H. Gunderson wrote: On Mon, Aug 20, 2007 at 12:15:50PM -0400, Justin Piszcz wrote: Could you please remind me of the command? apt-get install -t unstable nfs-kernel-server nfs-common? Assuming you've got unstable in your sources.list, that should do fine. (You don't really want to be using apt-get in 2007, though -- aptitude is a fine replacement.) /* Steinar */ -- Homepage: http://www.sesse.net/ Very impressive! This solves the find problem, I will let you know if I have any other issues. Is it safe to keep that version installed until the new-fixed version is rolled out in testing? Should I place a hold on those two packages in the meantime? Justin. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#437342: nfs mounts no longer work in testing after upgrade
On Mon, Aug 20, 2007 at 03:08:00PM -0400, Justin Piszcz wrote: > Very impressive! This solves the find problem, I will let you know if I > have any other issues. Great to hear that it's probably the same problem. :-) > Is it safe to keep that version installed until the new-fixed version is > rolled out in testing? Yes, I believe it should be relatively safe, even though it's a git snapshot. > Should I place a hold on those two packages in the meantime? aptitude won't downgrade unless there's something special going on, so I don't think that would be necessary. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#437342: nfs mounts no longer work in testing after upgrade
On Mon, 20 Aug 2007, Steinar H. Gunderson wrote: On Mon, Aug 20, 2007 at 03:08:00PM -0400, Justin Piszcz wrote: Very impressive! This solves the find problem, I will let you know if I have any other issues. Great to hear that it's probably the same problem. :-) Is it safe to keep that version installed until the new-fixed version is rolled out in testing? Yes, I believe it should be relatively safe, even though it's a git snapshot. Should I place a hold on those two packages in the meantime? aptitude won't downgrade unless there's something special going on, so I don't think that would be necessary. /* Steinar */ -- Homepage: http://www.sesse.net/ Thanks! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
