Hi Simon, Le mardi 25 octobre 2016 18:55:39 EDT, vous avez écrit : > So while this seems to have migrated into unstable, when building in the > Zesty proposed pocket, it failed to build. > > This FTBFS is only on ppc64el and seems to be caused by symbols > problems. You can take a look for yourself here: > - https://launchpad.net/ubuntu/+source/taglib/1.11.1-0.1 > - > https://launchpadlibrarian.net/290827635/buildlog_ubuntu-zesty-ppc64el.tagli > b_1.11.1-0.1_BUILDING.txt.gz > > Is this something Ubuntu-specific (in which case I'll fix this) or is it > something you guys missed?
This is unrelated to the ncmpcpp problem; in this case it seems to be architecture-dependent symbols not existing on this architecture. The fix would be to tag the symbols in question (e.g. arch=!ppc64el). The odd thing is, taglib 1.11.1-0.1 has been built successfully on ppc64el on Debian [1], so I'm not sure what is happening here. I don't think it would be right to disable the symbols in Debian, because it would likely break the package on that architecture for us. Please keep me posted on your findings (by private email or on a new bug report, since #839767 is not concerned). Cheers, Matteo [1] https://buildd.debian.org/status/fetch.php? pkg=taglib&arch=ppc64el&ver=1.11.1-0.1&stamp=1477391033
signature.asc
Description: This is a digitally signed message part.
