Thanks Andrey. On Tue, Sep 29, 2020 at 8:39 AM Andrey Rahmatullin wrote: > > On Tue, Sep 29, 2020 at 08:30:33AM -0400, Tong Sun wrote: > > So `libgit2-dev` only shows up once in calligra's debian/control file. > You need to check actual dependencies of binary packages (e.g. by looking at > debs with dpkg-deb -f), not your debian/control. > And libgit2-dev is a development package, binaries will depend on the > package that contains the library itself. > > > I.e., none of the packages actually depends on it, which is kind of > > what I found. Is it true? > Yes, packages that link against a lib shouldn't depend on a -dev. No, you > cannot see binary package deps in debian/control. > > > Can I safely say that all calligra packages are fine with libgit2-dev's new > > v1.0.0? > No. > > > Also, one dependent of libgit2-dev is librust-libgit2-sys-dev. and I see > > > > $ grep -B10 libgit2-dev debian/control > > Build-Depends: debhelper (>= 11), > > dh-cargo (>= 18), > > cargo:native <!nocheck>, > > rustc:native <!nocheck>, > > libstd-rust-dev <!nocheck>, > > librust-cc-1+default-dev (>= 1.0.42-~~) <!nocheck>, > > librust-cc-1+parallel-dev (>= 1.0.42-~~) <!nocheck>, > > librust-libc-0.2+default-dev <!nocheck>, > > librust-libz-sys-1+default-dev (>= 1.0.22-~~) <!nocheck>, > > librust-pkg-config-0.3+default-dev (>= 0.3.7-~~) <!nocheck>, > > libgit2-dev <!nocheck> > What do you mean by this?
Same train of thoughts as above. Is there anything special that you picked this particular section out?