Hi. There recently was a transition for a new gsoap version: libgsoap-2.8.91 → libgsoap-2.8.104 While this worked as expected for the official architectures, it was badly executed for some of the ports architectures. The following binnmus, run in order to pick up the new gsoap version, were in fact run before the new gsoap version had been compiled on that architecture, therefore ending up as rebuilds with the old version instead: cgsi-gsoap (1.3.11-1+b3) on m68k cgsi-gsoap (1.3.11-1+b3) on sh4 gridsite (3.0.0~20180202git2fdbc6f-3+b1) on m68k kopanocore (8.7.0-7+b2) on m68k voms (2.1.0~rc0-6+b2) on m68k Can these be run again? Why are the transition binnmus not scheduled with an dep-wait on the new soname? For kfreebsd-*, the build environment is currently broken (debhelper is not installable), but both the new gsoap build and the binnmus have been queued, so potentially these may end up being built in the wrong order. Mattias
Attachment:
signature.asc
Description: This is a digitally signed message part