On 2016-04-20 03:26 +0900, Roger Shimizu wrote:
> Dear Sven,
>
> On Fri, Apr 15, 2016 at 3:00 AM, Sven Joachim <svenj...@gmx.de> wrote:
>> It doesn't help. I have filed a bug against dpkg-shlibdeps (#821025),
>> you should have received a copy of that report.
>
> Thanks for the report on #821025.
>
> I read comment from Guillem, but have no idea on the words below:
>
>> But in your case I think simply using -x with the name of the two
>> multilib paclages should be enough, as the undesirable dependency is
>> simply a self-depends masked as a multilib one. And this can be done
>> right now.
>
> This seems to be quick fix, but do you know how to do it exactly?
Probably something like this in debian/rules (untested):
,----
| dh_shlibdeps -s -N$(package-ti)-udeb
| dh_shlibdeps -p$(package-ti)-udeb -- -x$(package-ti-64)
-x$(package-ti-32)
`----
But I have a different fix in mind, will send an update tomorrow.
Cheers,
Sven
