On Thu, Jul 7, 2016 at 11:34 PM, Daniel Kahn Gillmor <d...@fifthhorseman.net> wrote:
> ------------- > # https://bugs.debian.org/806033 -- dh_clideps expects to see > # dh_makeshlibs called before it, but dh_makeshlibs is never called > # when building only arch-indep packages. So we force the issue by > # making a phony shlibs.local file that dh_clideps will accept, if no > # others exist: > override_dh_clideps: > if ! grep -q . debian/*/DEBIAN/shlibs; then echo libgmime-2.6 0 > libgmime-2.6-0 > debian/shlibs.local; fi > dh_clideps > rm -f debian/shlibs.local > ------------- > > But it would be better to have the problem fixed in the > debhelper/cli-common-dev toolchain, so i've cloned this bug report and > assigned it to cli-common-dev. > I disagree that the bug is in dh_clideps and thus cli-common-dev. The implementation is on par with the specification, defined in the Debian CLI Policy section 6.2.1 [0]: dh_clideps is used to discover the native and managed dependencies of the > packages. It uses the clilibs control files > <https://pkg-mono.alioth.debian.org/cli-policy/ch-packaging.html#s-clilibs-control-file>, > the .config of assemblies and the shlibs files created by dh_makeshlibs. > The discovered dependencies are written into the ${cli:Depends} variable. > *dh_shlibdeps must be run > before dh_clideps. dh_makeshlibs and dh_makeclilibs must be run > before dh_clideps*. If not, when two binary packages from the same source > package depend on one another, dh_clideps will not be able to determine > the dependencies. This is a simple design issue and thus limtation. dh_clideps can only know the correct binary dependencies if the shlibs files of the called native library (moduelrefs) is available. If you do not build the arch-dependent portion first, then you can not obtain the needed metadata from it. [0]: https://pkg-mono.alioth.debian.org/cli-policy/ch-appendix.html#s-dh_clideps > Are there any other source packages that build an arch:any C library > package and arch:all cli bindings for it that use this toolchain? I > would think all such packages would run into this bug if they are > submitted as source-only uploads. > > --dkg > Best regards, Mirco (meebey) Bauer FOSS Hacker mee...@meebey.net https://www.meebey.net/ Debian Developer mee...@debian.org http://www.debian.org/ GNOME Foundation Member mmmba...@gnome.org http://www.gnome.org/ CTO @ GSD Software Design GmbH m.ba...@gsd-software.net .NET Foundation Advisory Council Member http://www.dotnetfoundation.org/ PGP-Key ID 0xEEF946C8 https://meebey.net/pubkey.asc
