On 16/10/16 10:56, Gianfranco Costamagna wrote:
> Package: release.debian.org
> User: release.debian....@packages.debian.org
> Usertags: binnmu
> Severity: normal
> nmu llvm-toolchain-3.8_1:3.8.1-12 . mips64el . unstable . -m "rebuild to fix 
> wrongly removed binaries (cfr: #839033)"
> yes, such packages have been wrongly removed with the llvm-toolchain-snapshot 
> decruft.
> And now they are preventing 3.8 from migration.
> Please binNMU them when you got why they have been removed, or whenever you 
> prefer

I have binNMUed it as this is blocking rdeps from building, including those that
depend on unversioned llvm packages, as llvm-defaults is now uninstallable on

Keeping this bug opened here as Julien wanted to look at how we got here. I
think the problem was that #839033's subject mentioned mips64el, but that
information was outdated, and that confused the ftp team member. The fact that
llvm-toolchain-snapshot builds versioned binaries that later get taken over by
llvm-toolchain-X.Y didn't help here.


Reply via email to