Bug#840927: nmu: llvm-toolchain-3.8_1:3.8.1-12
On Mon, 17 Oct 2016 00:38:00 +0200 Emilio Pozuelo Monfort wrote: > 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. Hi, I originally filed #839033 and included mips64el in the list. I just noticed that I still had the dak output from that time in the history, and according to that I didn't expect any problems: anbe@coccia:~$ dak rm -Rn -a mips64el llvm-toolchain-snapshot W: -a/--architecture implies -p/--partial. Will remove the following packages from unstable: clang-modernize-3.8 | 1:3.8~svn254193-1 | mips64el llvm-toolchain-snapshot | 1:3.7~svn230892-1 | source llvm-toolchain-snapshot | 1:3.8~svn247576-1 | source llvm-toolchain-snapshot | 1:3.8~svn254193-1 | source llvm-toolchain-snapshot | 1:4.0~svn279916-1 | source python-lldb-3.8 | 1:3.8~svn254193-1 | mips64el Maintainer: LLVM Packaging Team --- Reason --- -- Checking reverse dependencies... No dependency problem found. Andreas
Bug#840927: nmu: llvm-toolchain-3.8_1:3.8.1-12
On Mon, Oct 17, 2016 at 00:38:00 +0200, Emilio Pozuelo Monfort wrote: > Keeping this bug opened here as Julien wanted to look at how we got here. I Mostly I wanted ftpteam to know about this and maybe patch dak rm to not remove stuff from different versions, or something to that effect. Cheers, Julien
Bug#840927: nmu: llvm-toolchain-3.8_1:3.8.1-12
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 mips64el. 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. Cheers, Emilio
Bug#840927: nmu: llvm-toolchain-3.8_1:3.8.1-12
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 thanks Gianfranco