Bug 204160 - Portsnap doesn't fetch updated ports
Summary: Portsnap doesn't fetch updated ports
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: 10.2-RELEASE
Hardware: Any Any
: --- Affects Some People
Assignee: Colin Percival
URL:
Keywords: needs-qa
Depends on:
Blocks:
 
Reported: 2015-10-30 19:36 UTC by Walter Schwarzenfeld
Modified: 2016-12-26 22:44 UTC (History)
7 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Walter Schwarzenfeld 2015-10-30 19:36:58 UTC 
Portsnap don't update ports. After portsnap fetch update:
e.g.
pkg version -Ivl'<'
vim-7.4.898 < needs updating (index has 7.4.900)
----------------
grep PORTVERSION /usr/ports/editors//vim/Makefile
PORTVERSION=   7.4.898
(on 10-2 and 9.3 amd64 and i386).

It is discussed here:
https://forums.freebsd.org/threads/portmaster-wont-update-ports.53464/#post-302599
Comment 1 Walter Schwarzenfeld 2015-10-30 19:37:42 UTC 
On 10.2-RELEASE and 9.3-RELEASE both amd64 and i386.
Comment 2 Walter Schwarzenfeld 2015-10-31 00:12:23 UTC 
If I comment out the sanity check of the date in /usr/sbin/portsnap, I get:
Updating from Fri Oct 30 09:04:12 UTC 2015 to Thu Oct 29 03:18:28 UTC 2015.
Comment 3 Enji Cooper freebsd_committer freebsd_triage 2015-10-31 01:36:11 UTC 
(In reply to Walter Schwarzenfeld from comment #2)

Is your clock/timezone set correctly?
Comment 4 drhowarddrfine 2015-10-31 02:44:37 UTC 
(In reply to NGie Cooper from comment #3)
In the case of my server and workstation, yes, both times and zones are correct.
Comment 5 Walter Schwarzenfeld 2015-10-31 03:57:42 UTC 
(In reply to NGie Cooper from comment #3)
Yes, it is.
Comment 6 Walter Schwarzenfeld 2015-10-31 04:12:27 UTC 
I have 5 Systems (one has svn who is working correct). All other four have the problem.
Comment 7 lumiwa 2015-10-31 15:10:31 UTC 
I have the same problem on my FreeBSD 10.2-RELEASE-p5 (amd64):


grep PORTVERSION /usr/ports/editors/vim/Makefile
PORTVERSION=	7.4.898
VIM_VER=	${PORTNAME}${PORTVERSION:R:S|.||g}
CPE_VERSION=	${PORTVERSION:R}
Comment 8 Walter Schwarzenfeld 2015-10-31 18:25:47 UTC 
Works now again. Don't know what the error was. I am waiting for confirmation of others, before I close.
Comment 9 drhowarddrfine 2015-10-31 19:10:05 UTC 
As of a few moments ago, I was able to update all my ports. This happened previously as outlined in the link shown above.
Comment 10 drhowarddrfine 2015-10-31 19:10:59 UTC 
(In reply to Walter Schwarzenfeld from comment #8)
I would not close this. I believe the issue that initially caused this still exists and it will happen again.
Comment 11 Kubilay Kocak freebsd_committer freebsd_triage 2015-11-01 04:49:49 UTC 
Any issues with the portsnap 'service' rather than the 'binary' should go into Services:Portsnap category in Bugzilla, which will assign it to the service maintainer and cc cluster admin.

Assign to Colin who may be able to provide insight.
Comment 12 drhowarddrfine 2016-12-26 14:49:14 UTC 
One year later, here we are again with the same issue.
Comment 13 drhowarddrfine 2016-12-26 15:27:37 UTC 
The issue for me, this time, is that the server is not up-to-date or synced with the current versions. I find this happens once a year or so and I have to change servers in order to update. 

In this case, the out-of-date server is "sourcefire.portsnap.freebsd.org".
Comment 14 Colin Percival freebsd_committer freebsd_triage 2016-12-26 21:00:50 UTC 
Yes, the mirroring on the sourcefire portsnap mirror broke.  Hopefully Ryan will be able to fix it soon.

In the mean time, `portsnap -s your-org.portsnap.freebsd.org fetch` should do what you need.
Comment 15 Colin Percival freebsd_committer freebsd_triage 2016-12-26 22:44:51 UTC 
Fixed.  If another mirror breaks in the future please open a new PR.