unable to download ports using portsnap fetch by remote server

srchi

Member

Reaction score: 1
Messages: 21

I'm trying to download ports(from remote server) using portsnap fetch but im getting error like "portsnap fetch should not be run non-interactively. Run portsnap cron instead". but i tried portsnap cron im able to download the compressed content inside /var/db/portsnap but seems its not the valid data. ive checked mail the output sees as per screenshot. kindly give suggestion how to download the ports from remote server.
Screenshot 2021-04-08 at 2.27.34 PM.png
 

bagas

Active Member

Reaction score: 5
Messages: 216

ports switched to git.
 

SirDice

Administrator
Staff member
Administrator
Moderator

Reaction score: 10,903
Messages: 36,809

ports switched to git.
Irrelevant for portsnap(8) users.

srchi Please don't post pictures of text output. They're impossible to copy/paste from.

As for the error, it looks like something got corrupted. Run rm -rf /var/db/portsnap/* to clear out the cache directory. The run portsnap fetch again.
 
OP
S

srchi

Member

Reaction score: 1
Messages: 21

portsnap cron is working but need to wait 5-8min to complete the download. may be i was checking mail incomplete download. i ran again waited for 8min then portsnap extract
 

recluce

Active Member

Reaction score: 39
Messages: 164

Irrelevant for portsnap(8) users.

srchi Please don't post pictures of text output. They're impossible to copy/paste from.

As for the error, it looks like something got corrupted. Run rm -rf /var/db/portsnap/* to clear out the cache directory. The run portsnap fetch again.
Is it? I have observed for a while now that the ports tree has become static with portsnap (or svn, for that matter). The only resolution is to switch to git, which appears not even to be fully documented. Not impressed with the way the project handled this switch.
 

richardtoohey2

Well-Known Member

Reaction score: 260
Messages: 495

It's been a bit of a bump ... but as a ports user (portsnap & portmaster) it boiled down to
Code:
cd /usr/ports/net/gitup
make install
<change gitup.conf to non-github version>
cd /usr
mv ports old-ports
mkdir ports
gitup ports
pkg version -vL=
portmaster -a
And since that, just
Code:
gitup ports
pkg version -vL=
portmaster -a

Seems to be working OK so far, and performance on par with portsnap (svnlite seemed a LOT slower, so I'm glad gitup is OK).

EDIT - And to try and tame the don't-use-portmaster crowd - the above is NOT recommended, especially if you are a new user. Use the pkg system and binary packages - don't touch ports unless you have to or want to.

I was planning on staying on portsnap, but gitup has so far been pretty painless, so I might as well make the move now.
 

SirDice

Administrator
Staff member
Administrator
Moderator

Reaction score: 10,903
Messages: 36,809

Is it? I have observed for a while now that the ports tree has become static with portsnap (or svn, for that matter).
The entire ports tree was more or less "frozen" for a few days. So yes, portsnap is going to be frozen too. If there are no changes in the ports tree then there isn't much for portsnap to make a diff from now is it?

The only resolution is to switch to git
No, it's not. If you previously used subversion, then yes.

Not impressed with the way the project handled this switch.
Send your complaints to freebsd-ports@. Nobody on the forums can do anything about it.
 
OP
S

srchi

Member

Reaction score: 1
Messages: 21

It's been a bit of a bump ... but as a ports user (portsnap & portmaster) it boiled down to
Code:
cd /usr/ports/net/gitup
make install
<change gitup.conf to non-github version>
cd /usr
mv ports old-ports
mkdir ports
gitup ports
pkg version -vL=
portmaster -a
And since that, just
Code:
gitup ports
pkg version -vL=
portmaster -a

Seems to be working OK so far, and performance on par with portsnap (svnlite seemed a LOT slower, so I'm glad gitup is OK).

EDIT - And to try and tame the don't-use-portmaster crowd - the above is NOT recommended, especially if you are a new user. Use the pkg system and binary packages - don't touch ports unless you have to or want to.

I was planning on staying on portsnap, but gitup has so far been pretty painless, so I might as well make the move now.
I'm getting below issue after doing make install
Code:
make: "/usr/share/mk/bsd.port.mk" line 32: Cannot open /usr/ports/Mk/bsd.port.mk
make: Fatal errors encountered -- cannot continue
make: stopped in /usr/ports/net/gitup
 

SirDice

Administrator
Staff member
Administrator
Moderator

Reaction score: 10,903
Messages: 36,809

I suggest you use the packages. Do you have good reason to build from ports in the first place?
 
Top