Re: port selfupdate / port reclaim

2017-02-28 Thread Dave Horsfall
On Sun, 26 Feb 2017, Al Varnell wrote: > Not much of a secret, actually. It's the first item listed in the Change > Log under 2.4 > . > You will find several other "secrets" there. Thanks. -- Dave Horsfall DTM (VK2KFU) "T

Re: port selfupdate / port reclaim

2017-02-26 Thread Al Varnell
Not much of a secret, actually. It's the first item listed in the Change Log under 2.4 . You will find several other "secrets" there. Sent from Janet's iPad -Al- On Feb 26, 2017, at 9:18 PM, Dave Horsfall wrote: > On Sat, 2

Re: port selfupdate / port reclaim

2017-02-26 Thread Dave Horsfall
On Sat, 25 Feb 2017, Aljaž Srebrnič wrote: > It’s not a big bug, just `port reclaim` has failed to run. You can run > it again manually by executing `sudo port reclaim`. Reclaim will delete > outdated port archives and unused source tarballs. Hmmm... It noted that this is the first time that I

Re: port selfupdate / port reclaim

2017-02-26 Thread Mojca Miklavec
On 25 February 2017 at 19:55, Aljaž Srebrnič wrote: >> On 19 feb 2017, at 11:16, Mark Bestley wrote: >> >> You haven't run 'sudo port reclaim' in two weeks. It's recommended you run >> this regularly to reclaim disk space. Would you like to run it now? [Y/n]: Y >> Error: reclaim failed: wrong # ar

Re: port selfupdate / port reclaim

2017-02-25 Thread Aljaž Srebrnič
> On 19 feb 2017, at 11:16, Mark Bestley wrote: > > I just ran sudo port selfupdate and got this > > sudo port selfupdate > Password: > ---> Updating MacPorts base sources using rsync > MacPorts base version 2.4.0 installed, > MacPorts base version 2.4.0 downloaded. > ---> Updating the ports t