Package: release.debian.org Severity: normal X-Debbugs-Cc: [email protected] Control: affects -1 + src:ldc User: [email protected] Usertags: transition
ldc 1.42 was uploaded to unstable with a soname bump of the shared D runtime (libphobos2-ldc-shared111 -> libphobos2-ldc-shared112). It would be good to set up an auto transition tracker at https://release.debian.org/transitions/ to keep track, as is not possible fix all with a single binnmu. There are 8 source packages whose binaries link the shared D runtime and need to be rebuilt. I did a quick test rebuild of all of them in a clean sid chroot. These 4 rebuild cleanly against ldc 1.42 and can be binNMU'd directly (verified: the resulting binaries depend on libphobos2-ldc-shared112): diet-ng mir-core mustache-d sambamba Can you please do a binnmu of them? The other 4 are not ready for a plain binNMU: gir-to-d FTBFS with ldc 1.42. Its associative-array usage with an inout value type (source/gtd/LinkedHasMap.d) is rejected by the new templated AA implementation (core.internal.newaa): Error: variable core.internal.newaa.Entry!(string, inout(Node)*).Entry.value - only parameters or stack-based variables can be `inout` A source fix is required. This blocks the whole gtkD chain below. glib-d, gtk-d Build-depend on gir-to-d, so they cannot be test-rebuilt until gir-to-d is fixed and rebuilt (libphobos2-ldc-shared112 Conflicts libphobos2-ldc-shared111, so the old gir-to-d binary is not co-installable with the new toolchain). They need to be rebuilt after gir-to-d; whether they also need source changes is still TBD. tilix Build-depends on libgtkd-3-dev / libvted-3-dev (from gtk-d), so it can only be rebuilt after gtk-d. Ben file: title = "ldc"; is_affected = .depends ~ "libphobos2-ldc-shared111" | .depends ~ "libphobos2-ldc-shared112"; is_good = .depends ~ "libphobos2-ldc-shared112"; is_bad = .depends ~ "libphobos2-ldc-shared111";
