This web page collects issues in the apt
package which prevent the migration to APT 0.6, but are not directly related to implementation details of archive signature verification.
APT 0.6 introduces a new ABI. Therefore, all applications linked against the APT libraries have to recompiled. It seems that this does not require source code changes. Therefore, it should be possible to move APT 0.6 to unstable without major regressions, even though the frontends have to been updated to take archive signatures into account.
There are some pending translation updates, although this is not a real showstopper. (Source: Christian Perrier)
When viewed in context, these items do not appear to be major showstoppers. However, a coordinated effort is certainly needed for the ABI transition. At this stage, we should wait with the ABI transition until we know that the ABI is finalized (to avoid the need for yet another transition). This means that the transition should wait for the outcome of the general discussion about signature key management.
APT 0.6 contains few changes besides archive signature verification. The version currently in experimental is ready for release, except for the cryptography part and frontend integration testing. (Source: Michael Vogt)
APT frontends and the migration
APT frontends have to be modified to properly support archive signature verification. While most (if not all) frontends continue to work well when recompiled against the APT 0.6 libraries, changes are necessary so that the frontends properly informs the user about potential archive tampering.
This web page collects background information on the Debian's migration to APT version 0.6.
Showstoppers in the APT package
This web page collects issues in the apt
package which prevent the migration to APT 0.6, but are not directly related to implementation details of archive signature verification.