portsnap errors on current (r263382)

Ruslan Makhmatkhanov cvs-src at yandex.ru
Thu Mar 20 11:28:36 UTC 2014


have this weirdness. I'll try to remove the current portsnap snapshot, 
but this info may be useful for portsnap maintainer's in exception 
handling aspect.

# portsnap fetch update
Looking up portsnap.FreeBSD.org mirrors... none found.
Fetching snapshot tag from portsnap.FreeBSD.org... done.
[: -gt: unexpected operator
[: -eq: unexpected operator
[: =: unexpected operator
Fetching snapshot metadata... done.
date: option requires an argument -- r
usage: date [-jnu] [-d dst] [-r seconds] [-t west] [-v[+|-]val[ymwdHMS]] 
             [-f fmt date | [[[[[cc]yy]mm]dd]HH]MM[.ss]] [+format]
Updating from  to Thu Mar 20 15:07:48 MSK 2014.
Fetching 0 metadata patches. done.
Applying metadata patches... done.
Fetching 4 metadata files... done.
Fetching 0 patches.
dc: divide by zero
dc: divide by zero
(0/0) 0.00%  done.
Applying patches...
Fetching 904 new ports or files... done.
Removing old files and directories... done.
Extracting new files:
files/700bdf7f6cf43ee23eb9fd3342390bce8a126947e19d2ae7d8a4feed08252390.gz not 
found -- snapshot corrupt.


T.O.S. Of Reality

More information about the freebsd-ports mailing list