On 24.09.2012 05:38, Jamie Heilman wrote: > I'm currious, do you think there's any chance this issue will be > resolved for the Wheezy release? While using the "fstype=nfs4" > workaround is doable, it'd be nice not to introduce the regression of > "vers=4" failing for a stable release.
Well. There are lots of other issues present in autofs, so this bug isn't alone... ;) The change to fix this bug is rather large. I'd love to push it to wheezy, but it all depends on the release team. I already asked them several times what we can do and what is, to their view, is allowed or not. Got no reply so far, so the only thing left to do is to wait and hope for the best. I'd rather upload whole 5.0.7 thing, since it contains a ton of bugfixes (including this one), and just one feature (extra map type) which is self-contained. 5.0.7 plus all current past-5.0.7 patches, because, well, all these fixes are important. But since so far I have no answer from the releae team (I think it is due to lack of manpower/time, nothing more), I can't proceed further. Well. Maybe I can. Let me review all the stuff changed upstream since last debian respin and see it from a debian release team point of view. Maybe it isn't really that scary... Someone else want to comment on this? Dmitry? Dmitrijs? How about we uploading whole 5.0.7 + remaining upstream patches and request to unblock _that_ ? The problem is that the wheezy release date is approaching, and we don't have a chance for numerous unblocks anymore. Thanks, /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
