portmaster won't update ports

D

drhowarddrfine

Woke up this morning, turned my workstation on that was just updated to version 10.2-RELEASE-p5 yesterday, did a portsnap to get updates but, when I tried to update this list of ports, ports-mgmt/portmaster only re-installed them instead. What happened here?

Code: 
gdk-pixbuf2-2.32.1
php56-5.6.14
php56-hash-5.6.14
php56-openssl-5.6.14
php56-phar-5.6.14
automake-1.15_1
...
 
portsnap doesn't seem to reflect these recent port updates yet, at least for me.

Code: 
jrm@gly ~ % pkg version | egrep "^gdk-pixbuf"
gdk-pixbuf2-2.31.7                 =

jrm@gly ~ % sudo portsnap fetch update; pkg version -Ivl'<'
Looking up portsnap.FreeBSD.org mirrors... 7 mirrors found.
Fetching snapshot tag from ec2-eu-west-1.portsnap.freebsd.org... done.
Latest snapshot on server matches what we already have.
No updates needed.
Ports tree is already up to date.
 
Updating the ports by svn does grab the updates, so it seems portsnap is lagging behind. I'm not sure if this is normal lag or not.

Ports tree updated with portsnap
Code: 
jrm@gly ~ % grep PORTVERSION /usr/ports/graphics/gdk-pixbuf2/Makefile 
PORTVERSION=    2.31.7

Ports tree updated with svn
Code: 
jrm@storage2 ~ % grep PORTVERSION /usr/local/poudriere/ports/default/graphics/gdk-pixbuf2/Makefile 
PORTVERSION=    2.32.1
 
Not sure if it's relevant but 10.2 now uses the quarterly packages by default. This may also be the case for portsnap(8).
 
Does the ports tree you are building from have the newer version? Can you confirm by doing something like grep PORTVERSION /usr/ports/www/nghttp2/Makefile? Maybe your are using an INDEX to tell you a new version is available, but the INDEX is somehow slightly ahead of your tree.
 
For example, if you ran portsnap -I update.

Anyway, without confirmation of what you are running to update the ports tree and what your ports tree looks like, it's hard to do anything other than guess.
 
portsnap fetch update. I think I never run portsnap -I update. (I know webp ist updated from 0.4.3 to 0.44 and vim from 7.4.898 to 7.4.900). But portsnap shows uptodate. (On one system I have svn, that works correct). I have 4 different FreeBSD systems, and only the one with svn updates.
 
But what did your ports tree look like when you tried to run ports-mgmt/portmaster after the first portsnap fetch update? If you didn't rerun portsnap fetch update, you can tell us with, e.g., grep PORTVERSION /usr/ports/editors/vim/Makefile. If your ports tree still has (had) the older version, that will tell us something.

Another question: How did you determine a new version was available? For example, did you run pkg version -Ivl'<'? The I flag might also tell us something.
 
pkg version -Ivl'<'
vim-7.4.898 < needs updating (index has 7.4.900) (I have edit it, before it was a paste-error).
Code: 
grep PORTVERSION /usr/ports/editors//vim/Makefile
PORTVERSION=   7.4.898
VIM_VER=   ${PORTNAME}${PORTVERSION:R:S|.||g}
CPE_VERSION=   ${PORTVERSION:R}
 
NOTE: This post is no longer relevant since you corrected the previous post.

So pkg version is saying you have nothing new to update, and you ran portmaster, specifying a port. From portmaster(8):
By default portmaster updates the port you specify on the command line. This will occur whether there is a new version for it or not.
Click to expand...
This is all expected behaviour. The only thing of note is that portsnap is lagging a bit behind.
 
So now we're back to the other theory that the INDEX is indeed ahead of your tree. I think it says it all in the output. Your INDEX refers to 7.4.900, but your tree still has 7.4.898.
 
Right. We've come to the same conclusion. Why? I don't know, but considering there are at least two of you seeing the problem, I'd say it's something worth reporting.
 
On my system 7.4.898 is reported as up to date as well. I have no problem with beeing some time behind head. For myself it is just interesting to know how things work.
According to https://svnweb.freebsd.org/ports/head/editors/vim/?view=log
the step from 7.4.898 to 7.4.900 is just a few hours ago. I am not sure if everything can be synchronized by 100%. Is it possible that the index file comes from one source and portsnap gets its data from a different source?
 
I have the same problem:
Code: 
portsnap fetch update
Looking up portsnap.FreeBSD.org mirrors... 7 mirrors found.
Fetching snapshot tag from your-org.portsnap.freebsd.org... done.
Latest snapshot on server matches what we already have.
No updates needed.
Ports tree is already up to date.
 
If I comment out the sanity check of the date in /usr/sbin/portsnap, I get:
Code: 
Updating from Fri Oct 30 09:04:12 UTC 2015 to Thu Oct 29 03:18:28 UTC 2015.
 
You must log in or register to reply here.
Back
Top