Hi, On Sat, Jun 21, 2014 at 01:50:39PM -0400, GUO Yixuan wrote: > On Sat, Jun 07, 2014 at 01:18:53AM +0900, Osamu Aoki wrote: ... > > This seems to be not-so-correct package dependency in the debian/control > > case which breaks with binNMU. > > It seems to be no binNMU-safe way for a maximum version dependency (<=), > from arch: all to arch: any. [1] However, we can change librime-dev to > be arch: any, and solve this problem. (This is also required for an > migration to multiarch.) > > [1] https://wiki.debian.org/binNMU
Here is my summary in my debmake package documentation. http://people.debian.org/~osamu/debmake.html#control For the safe binNMU, the dependency among binary packages from a same source package needs attention if there are both "Architecture: any" and "Architecture: all" packages involved in it. "Architecture: any" package depends on "Architecture: any" foo package Depends: foo (== ${binary:Version}) "Architecture: any" package depends on "Architecture: all" bar package Depends: bar (== ${source:Version} "Architecture: all" package depends on "Architecture: any" baz package Depends: baz (>= ${source:Version}) (This is good enough for most cases.) So do not put the max version limitation. Also, as you pointed out, make this multiarch and fix pkgconfig file and make this arch: any package. Then use Depends: foo (== ${binary:Version}) As I checked this source, I see windows platform binaries included in the upstream source. (exe and dll) I do not see source for curl.exe in this package. So at least we should remove this in the source to be DFSG. I have not spend time to do the full review but this is FYI. Regards, Osamu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org