Issue #2730 has been updated by ftigeot.
The package system is set up to only produce packages for release branches of
DragonFly, the release branches having an even subversion number.
DragonFly 4.1 is the new development version and will in time become DragonFly
4.2.
When a new DragonFly
Issue #2730 has been updated by masu.
OK, this is intentional and not a bug. Thanks for clarifying.
It would be nice to add a few sentences to the handbook expaining what to do in
these cases since it is kind of surprising for new users not being able to
install packages out of the box.
Issue #2730 has been updated by ftigeot.
The current -master branch has a pkg ABI version of dragonfly:4.2:x86:64.
Given that no DragonFly 4.2 packages have been produced yet, you should indeed
force the ABI to dragonfly:4.0:x86:64 in pkg.conf for the moment.
Howewer, pkg on DragonFly 4.0-RC
Issue #2730 has been updated by masu.
Thanks for the quick answer!
Yes, ABI version dragonfly:4.2:x86:64 is used in a fresh 4.0.0-RC install.
Regards
Matthias
Am 07.11.2014 um 11:08 schrieb bugtracker-ad...@leaf.dragonflybsd.org:
Issue #2730 has been updated by ftigeot.
The current
Issue #2730 has been updated by ftigeot.
The /bin/sh file from the -RC4 iso image is not a DragonFly 4.0 executable:
# file sh
sh: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked
(uses shared libs), for DragonFly 3.0.901, stripped
This is what it should look like (from
