Hello, I just updated some ports without pushing the packages to the server. I prefer to wait, because it's needed the rebuild of some of others depending in the ones updated (not all). I have the packages in the server but not in the pkg repo. The list of updated ports is: [ports/opt-cross.git/2.6] whois: updated to 5.0.5 [ports/opt-cross.git/2.6] alsa-lib: updated to 1.0.23 [ports/opt-cross.git/2.6] alsa-utils: updated to 1.0.23 [ports/opt-cross.git/2.6] libpcap: updated to 1.1.1 [ports/opt-cross.git/2.6] glib: updated to 2.24.0 [ports/opt-cross.git/2.6] wgetpaste: updated to 2.16 [ports/opt-cross.git/2.6] tcpdump: updated to 4.1.1 [ports/opt-cross.git/2.6] ntp: updated to 4.2.6p1 [ports/opt-cross.git/2.6] libxml2: updated to 2.7.7 [ports/opt-cross.git/2.6] fetchmail: updated to 6.3.17 [ports/opt-cross.git/2.6] htop: 0.8.3 [ports/opt-cross.git/2.6] libpng: updated to 1.2.44 [ports/opt-cross.git/2.6] libtiff: updated to 3.9.4 [ports/opt-cross.git/2.6] lua: updated to 5.1.4 Along today and this weeked I'll try to make the updates of opt-cross and if I'm able I'll start with other collections (the core collection can be a good one to sync but may be when the current problems in the RC5 will be solved to prepare the final release synced with the last CRUX 2.6 state, explained in the next paragraph). We need to think about the final CRUX-ARM release. I think can be a good choice to bump all ports to the version used in the last stage of CRUX 2.6 and then rebuild the packages from all collections to fix the new updates and let all collections in a stable state (CRUX 2.7 is near, and soon all branches will be "closed", then it could be good time to make a sync between CRUX and CRUX-ARM for 2.6 version) Waiting for comments. Regards, Victor. --- Learning bit by bit Victor Martinez | http://lokalix.dyndns.org