Hello, On 25 Mar, 2013, at 6:00 PM, Martin Lambev <[email protected]> wrote:
On 25 Mar, 2013, at 4:59 PM, Lawrence Velázquez <[email protected]> wrote: > On Mar 25, 2013, at 4:17 AM, Martin Lambev <[email protected]> wrote: > >> So my question is should I uninstall/remove all ports and try to do clean >> install again? Anyway meanwhile I did it… following the http://guide.macports.org/#installing.macports.uninstalling and then installed using the Mountain Lion package, and selfupdate, and then install only wget and still the same… > > This should not be necessary. > >> I looked wget bug they mention this issue but could not find working >> solution altho they claim that this bug is fixed in recent version of wget? > > Can you provide a link to this information? http://savannah.gnu.org/bugs/?21042 Duplicate of this one: https://savannah.gnu.org/bugs/?21714 > > vq > Found another one: http://savannah.gnu.org/bugs/?38281 I think this one is more closer to my case, and it's recent so it's not solved. But unfortunately the solution in this bug does not work on Mac (using tmp/ folder does not work either). By accident I found out if I copy the file to external HDD ( FAT32 formatted) wget --continue can continue with the interrupted file no more "Cannot write to ‘foo.avi’ (Success)." So I guess it's something to do with my Mac file system - Mac OS Extended (Journaled) FS??? Oh, here is worth mentioning that I'm using File Vault ( Full disk encryption) so my guess is that this is the main problem. Because there is some changes in "Mountain Lion File Vault " Martin
_______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
