Hi,
The ordering here would be:
- dpkg will be uploaded to experimental with 64-bit time_t in the default
flags
- the source packages which need an ABI change
("source-packages"+"lfs-and-depends-time_t") and do not already have
versions in experimental, will have sourceful NMUs to experimental with
the new binary package names in order to clear binary NEW, in coordination
- once these packages have all cleared binary NEW, the new dpkg defaults
will be uploaded to unstable
And in the meanwhile in experimental it will be built with the old time_t on other architectures.
Since the new dpkg won't be picked up.
Not in the experimental builders unstable+experimental chroots which only install experimental packages when Build-Depends: need them.
(For an undefined time given how much the packages later in the
chain wait in NEW)
Especially on armhf which is affected. Or will you do the source NMUs on armhf/i386? (For some packages where some features are disabled on 32bit this is probably not a good idea)
Regards,
Rene