On Friday, November 07, 2014 10:15:59 Matthew Dillon wrote:
I'm fairly sure that the token release bug has been fixed since 3.6/3.7. I
suggest taking the time to fully upgrade the system (which will also mean
fully upgrading the installed packages once you've rebooted into an
upgraded
From my experience, the odd numbers are the current/testing versions, so
with 4.0RC being RELEASE, I'd say 4.1.
On Fri, Nov 7, 2014 at 11:22 AM, Pierre Abbat p...@leaf.dragonflybsd.org
wrote:
On Friday, November 07, 2014 10:15:59 Matthew Dillon wrote:
I'm fairly sure that the token release
On Friday, November 07, 2014 11:27:26 Zachary Crownover wrote:
From my experience, the odd numbers are the current/testing versions, so
with 4.0RC being RELEASE, I'd say 4.1.
Where do I change it? It's inside a variable called ABI.
Pierre
--
La sal en el mar es más que en la sangre.
Le sel
You're interpolating it in the file, but you can optionally hard code it. I
think the reporting of 4.2 is a bug.
On Fri, Nov 7, 2014 at 11:36 AM, Pierre Abbat p...@leaf.dragonflybsd.org
wrote:
On Friday, November 07, 2014 11:27:26 Zachary Crownover wrote:
From my experience, the odd numbers
cat /usr/local/etc/pkg/repos/df-latest.conf
# If multiple repositories are enabled, packages are taken in order in which
# the enabled repositories are listed.
Avalon: {
url : http://mirror-master.dragonflybsd.org/dports/${ABI}/LATEST,
mirror_type : NONE,
signature_type : NONE,
pubkey :
On Friday, November 07, 2014 11:41:33 Zachary Crownover wrote:
cat /usr/local/etc/pkg/repos/df-latest.conf
I changed it to 4.1 and got the same error. I changed it to 4.0 and got this:
Updating repository catalogue
digests.txz 100% 1838KB 612.7KB/s 1.1MB/s 00:03
