I believe that you are not supposed to delete the lock file. I had this problem at first when I had a shared debs directory between the machines on my local network.
I also had a problem with the lock file being on the nfs mounted system and got round the problem by linking it to a lock file on the real file system. Hope this helps... John. Brendon Baumgartner wrote: > I can't get access to my debs on my desktop over the network. This lock file > is getting in my way! > > Okay my laptop hostname is debian (just installed) and my desktop is viper. > For some reason when I do apt-get dist-upgrade, a lock file is created and > it won't delete it and complete the command. Also, my archive cache > directory has been changed to /mnt/debs on both machines. It works fine on > my desktop, but the laptop which accesses the debs via nfs doesn't like it. > Any ideas? > > debian:/mnt/debs# rm lock > debian:/mnt/debs# apt-get dist-upgrade > Reading Package Lists... Done > Building Dependency Tree... Done > Calculating Upgrade... Done > The following NEW packages will be installed: > perl-base > 39 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded. > E: Could not get lock /mnt/debs/lock - open (13 Permission denied) > E: Unable to lock the download directory >
