[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#34135: dpkg-source -x fails on NFS mounted dirs



Jules Bean wrote:

Note: I am not the official maintaier of dpkg-dev.

>If I try to use dpkg-source -x on an NFS mounted volume, I get:
>
>jules@pear% dpkg-source -x fnlib_0.4-0.1.dsc
>9:06AM
>dpkg-source: extracting fnlib in fnlib-0.4
>patch: **** can't create file `Fnlib/Makefile.am.orig.dpkg-orig' : Stale
>NFS file handle
>dpkg-source: failure: patch gave error exit status 2
>
>I do all my package building on a file server (not enough local disk
>space).
>
>I don't have any problems with any other operation - dpkg-source -b,
>dpkg-buildpackage and friends all work fine.  But I have to expand source
>packages by hand..

Does it matter what source package you use?

> dpkg-source -x ~ftp/files/linux/hurd-i386/src/ssh_1.2.26-1.2.dsc
dpkg-source: extracting ssh in ssh-1.2.26

Although NFS here isn't super reliable (I often get errors "rm /tmp/*:
Device or resource busy", especially when running dpkg --info), the
above works fine here; all directories are NFS mounted:

[504] [huey:bam] /tmp >df
Filesystem         1024-blocks  Used Available Capacity Mounted on
snoopy:/tftpboot/192.168.87.133
                      432479  379308    30088     93%   /
snoopy:/var/lib/diskless/chocbit/192.168.87.133/etc
                      432479  379308    30088     93%   /etc
/dev/md0              198977      43   188659      0%   /mnt
snoopy:/var/lib/diskless/chocbit/192.168.87.133/dev
                      432479  379308    30088     93%   /dev
snoopy:/var/lib/diskless/chocbit/192.168.87.133/var
                      432479  379308    30088     93%   /var
snoopy:/var/lib/diskless/chocbit/192.168.87.133/tmp
                      432479  379308    30088     93%   /tmp
snoopy:/home          452805  175633   253787     41%   /home
snoopy:/usr           432479  379308    30088     93%   /usr

The NFS server is running Linux 2.2.2, and the client is running
Linux 2.2.1

Brian May <bam@snoopy.apana.org.au>


Reply to: