MIME-Version: 1.0
From: Shashank Taliwal <shashanktaliwal07@gmail.com>
Date: Wed, 25 Feb 2026 14:20:40 +0530
Message-ID: <CAMU01kvhXwGds6i5b=PvMOxv0Udy1JsV1L9VL3b0br1fVk7T=w@mail.gmail.com>
Subject: Inquiry regarding v3 (ADB) migration timeline for third-party
 registry support
To: ~alpine/apk-tools@lists.alpinelinux.org
Content-Type: multipart/alternative; boundary="000000000000fab21b064ba2197c"

--000000000000fab21b064ba2197c
Content-Type: text/plain; charset="UTF-8"

Hi Team,

I am currently working on implementing native support for the v3 package
and index format for Artifactory. To ensure our users have a seamless
transition, we have a few questions regarding the upstream roadmap:

   1.

   *Samples:* Are there any reference repositories currently serving the
   binary ADBd index (0x41 0x44 0x42 0x64) and Zstd-compressed packages
   that we can use for interoperability testing?
   2.

   *Upstream Timeline:* We see that Alpine 3.23.0 has transitioned the
   package manager to v3 but kept the v2 index/package format for now. Is
   there a target release (e.g., v3.24) when the upstream mirrors will start
   serving v3 ADB indices by default?
   3.

   *V2 Deprecation:* When do you anticipate the v2 plaintext APKINDEX.tar.gz
   will be considered obsolete or removed from the official mirrors?
   4.

   *Implementation Detail:* For our indexing logic, we are looking to
   utilize the --pkgname-spec (Slot 13) for deduplication. Is there any
   formal documentation on the binary alignment/constraints for this specific
   slot in the ADB schema?

Thank you for the incredible work on v3.0.0!"


Thank you

Shashank Taliwal

--000000000000fab21b064ba2197c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><p>Hi Team,</p><p>I am currently working on implementing n=
ative support for the v3 package and index format for Artifactory. To ensur=
e our users have a seamless transition, we have a few questions regarding t=
he upstream roadmap:</p><ol start=3D"1"><li><p><b>Samples:</b> Are there an=
y reference repositories currently serving the binary <code>ADBd</code> ind=
ex (0x41 0x44 0x42 0x64) and Zstd-compressed packages that we can use for i=
nteroperability testing?</p></li><li><p><b>Upstream Timeline:</b> We see th=
at Alpine 3.23.0 has transitioned the package manager to v3 but kept the v2=
 index/package format for now. Is there a target release (e.g., v3.24) when=
 the upstream mirrors will start serving v3 ADB indices by default?</p></li=
><li><p><b>V2 Deprecation:</b> When do you anticipate the v2 plaintext <cod=
e>APKINDEX.tar.gz</code> will be considered obsolete or removed from the of=
ficial mirrors?</p></li><li><p><b>Implementation Detail:</b> For our indexi=
ng logic, we are looking to utilize the <code>--pkgname-spec</code> (Slot 1=
3) for deduplication. Is there any formal documentation on the binary align=
ment/constraints for this specific slot in the ADB schema?</p></li></ol><p>=
Thank you for the incredible work on v3.0.0!&quot;</p><p><br></p><p>Thank y=
ou</p><p>Shashank Taliwal</p></div>

--000000000000fab21b064ba2197c--