emerge sync reported errors trying to update binary packages, this is starting to happen rather too frequently. The error message is wrong and misleading, the destination does not exist. The problem is that the new directory, sys-fs in this example, does not exist and emerge/fixpackages is not creating. The move fails and is incorrectly reported. Cannot update binary: Destination exists. !!! sys-apps/devfsd-1.3.25-r3 -> sys-fs/devfsd-1.3.25-r3 nm-a1% ls -l /usr/portage/packages/sys-fs/* zsh: no matches found: /usr/portage/packages/sys-fs/* nm-a1% ls -l /usr/portage/packages/sys-fs/. ls: /usr/portage/packages/sys-fs/.: No such file or directory nm-a1% ls -l /usr/portage/packages/sys-apps/devfsd* lrwxrwxrwx 1 portage portage 28 Apr 16 00:58 /usr/portage/packages/sys-apps/devfsd-1.3.25-r3.tbz2 -> ../All/devfsd-1.3.25-r3.tbz2 lrwxrwxrwx 1 portage portage 25 Apr 16 00:58 /usr/portage/packages/sys-apps/devfsd-1.3.25.tbz2 -> ../All/devfsd-1.3.25.tbz2 nm-a1% ls -l /usr/portage/packages/All/devfsd* -rw-r--r-- 1 portage portage 37224 Sep 6 16:32 /usr/portage/packages/All/devfsd-1.3.25-r3.tbz2 nm-a1% epm -q portage portage-2.0.49-r3 Reproducible: Always Steps to Reproduce: 1.emerge sync 2. 3. Actual Results: Cannot update binary: Destination exists. !!! sys-apps/devfsd-1.3.25-r3 -> sys-fs/devfsd-1.3.25-r3 .@!!! Cannot update binary: Destination exists. !!! sys-apps/e2fsprogs-1.32-r2 -> sys-fs/e2fsprogs-1.32-r2 !!! Cannot update binary: Destination exists. !!! sys-apps/e2fsprogs-1.33 -> sys-fs/e2fsprogs-1.33 ............!!! Cannot update binary: Destination exists. !!! sys-apps/reiserfsprogs-3.6.8 -> sys-fs/reiserfsprogs-3.6.8 Expected Results: fixpackages should check if the destination directory exists and if not create it prior to trying to move the package file.
exist-check is fixed now... Wasn't checking existance correctly... as it was checking source and dest filenames... Which rarely change. fixed in cvs
*** Bug 29158 has been marked as a duplicate of this bug. ***
