2017-09-30 11:30 GMT+02:00 Emilio Pozuelo Monfort <po...@debian.org>: > On 29/09/17 13:45, Matthias Klumpp wrote: >> 2017-09-29 13:38 GMT+02:00 Michael Biebl <bi...@debian.org>: >>> Package: release.debian.org >>> Severity: normal >>> User: release.debian....@packages.debian.org >>> Usertags: binnmu >>> >>> nmu gtk-d_3.6.5-2 . amd64 . unstable . -m "Rebuild against libphobos2-ldc74" > > I tried this a while ago against -ldc73, but it failed on amd64, see: > > https://buildd.debian.org/status/package.php?p=gtk-d > > Is this going to work now? If so, I should rebuild this on all architectures, > not just amd64, right?
Yes, it should work now. I got a report of sambamba failing to build, but that could have been an artifact of mixing runtimes again, so I think rebuilding everything in order is a very good idea at time. LDC was hit by a nasty LLVM bug, which we "resolved" by rebuilding LDC against LLVM 5.0 (instead of 4.0) - currently, all builds I do on amd64 with ldc 1:1.4.0-2 build & run without any issue. > Also, what about the other rdepends? Some of them failed to build too in the > past, so I eventually gave up, waiting for a bug like this to come up :) > > https://release.debian.org/transitions/html/auto-ldc.html That should work now as well - the important thing is that packages are rebuilt in the right order, so no package accidentally picks up symbols from an older runtime version. In order to do that, could you augment the LDC Ben tracker to consider anything depending on libphobos2-ldc72 to be bad as well? I think there are a few packages missing on the tracker (sambamba, for example). >> Agreed. Ideally we'd need to coordinate binNMUs on new ABI versions >> better, so thinks are rebuilt in order, and not randomly. > > Some coordination when things need special treatment is always good :) > > Let me know what is needed here and I'll help if I can. See above :-) Thank you for your work and sorry for the mess, this should have been a pretty easy transition - we didn't anticipate the whole world breaking with a weird crash in LLVM :P I hope it works now (but the only way to know for sure is to rebuild on all architectures - amd64 is fine, at least) Cheers, Matthias -- I welcome VSRE emails. See http://vsre.info/
