On Thursday, July 07, 2016 03:36:27 PM Lucas Nussbaum wrote: > On 10/06/16 at 15:31 +0200, Piotr Ożarowski wrote: > > [Raphael Hertzog, 2016-06-10] > > > > > We just need to rebuild the package build-depending on dh-python, > > > and then grep buildlogs on "E: no package to act on" to find out how > > > many > > > are affected. Is that correct? > > > > correct > > Hi, > > Please find below a list of packages whose build log contains "no > package to act on". No packages contain the same string prepended by > "E: " as pointed in the message above. > > I can provide the build logs if useful. > ... > sip4_4.18+dfsg-1 ...
Since I maintain several of the affected packages, I thought I'd pick one to look at. For sip4, this error is caused by dh_python3 being called in both binary-arch and binary-indep since it didn't need to be separated before. Only it is used for -arch, but not -indep. Without more investigation, I'm sure that's the case for at least three other packages on the list. Just because this error was raised, doesn't mean the dh_python3 isn't used at some point. Scott K
