DragonFlyBSD

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 should try to download 4.0 packages.
Did you get this behavior right after installation or did you update/modify the base system before running pkg ?

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-admin@leaf.dragonflybsd.org:

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 should try to download 4.0 packages.
Did you get this behavior right after installation or did you update/modify the base system before running pkg ?

----------------------------------------
Bug #2730: missing ABI 4.2 package versions in repos
http://bugs.dragonflybsd.org/issues/2730#change-12266

• Author: masu
• Status: New
• Priority: Normal
• Assignee:
• Category:
• Target version:
  ----------------------------------------
  Hi,

I have installed dfly 4.0.0RC (x86_64), enabled pkg mirror Schlundtech in df-latest.conf and tried to do a "pkg update" resulting in an error on missing files (meta.txz and digests.txz).

This is due to a wrong definition of ${ABI} in df-latest.conf which is set to 'dragonfly:4.2:x86:64'.
This directory does not exists on the pkg mirrors the latest is 'dragonfly:4.0:x86:64'.

Do I miss a step for an initial pkg repo fetch?

This issue remains after upgrading the machine to CURRENT.

Is it ok to set ${ABI} to 'dragonfly:4.0:x86:64' in pkg.conf in the meantime or will this be corrected shortly?

Regards
Matthias

The /bin/sh file from the -RC4 iso image is not a DragonFly 4.0 executable:

1. 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 a machine upgraded manually):
/bin/sh: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for DragonFly 4.0.0, stripped

At the moment v4.1.0.29.g06397 is running here after upgrading 4.0.0-RC from sources.

With this version, I get:

/bin/sh: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for DragonFly 4.0.100, stripped

Where does the 4.2 in ABI string come from then?

bugtracker-admin@leaf.dragonflybsd.org schrieb:

Issue #2730 has been updated by ftigeot.

The /bin/sh file from the -RC4 iso image is not a DragonFly 4.0 executable:

1. 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 a machine upgraded manually):
/bin/sh: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for DragonFly 4.0.0, stripped

----------------------------------------
Bug #2730: missing ABI 4.2 package versions in repos
http://bugs.dragonflybsd.org/issues/2730#change-12268

• Author: masu
• Status: New
• Priority: Normal
• Assignee:
• Category:
• Target version:
  ----------------------------------------
  Hi,

I have installed dfly 4.0.0RC (x86_64), enabled pkg mirror Schlundtech in df-latest.conf and tried to do a "pkg update" resulting in an error on missing files (meta.txz and digests.txz).

This is due to a wrong definition of ${ABI} in df-latest.conf which is set to 'dragonfly:4.2:x86:64'.
This directory does not exists on the pkg mirrors the latest is 'dragonfly:4.0:x86:64'.

Do I miss a step for an initial pkg repo fetch?

This issue remains after upgrading the machine to CURRENT.

Is it ok to set ${ABI} to 'dragonfly:4.0:x86:64' in pkg.conf in the meantime or will this be corrected shortly?

Regards
Matthias

--
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account

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 release is being made, the new development branch is not too different from the release branch and is typically able to use its packages for a while without any change (except for the configuration adjustment).

Thus, creating packages for the new development branch (the future N+1 release) is not a priority.

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".

Please tell me if I can volunteer.

Regards
Matthias