Re: Verify the library transition

[Tong Sun <suntong001@users.sourceforge.net>]

On Tue, Sep 29, 2020 at 3:14 AM Andrey Rahmatullin wrote:
>
> On Mon, Sep 28, 2020 at 09:55:17PM -0400, Tong Sun wrote:
> > Of all the above 46 newly built binary-only packages, how can I tell
> > which .so from them will link to libgit2-dev, and whether the
> > libgit2-dev version linked is truly v1.0.0? Note this is more a
> > generic question and not specific for calligra.
> Check the package dependencies.

OK.

$ grep -B20 libgit2-dev debian/control
Source: calligra
Section: kde
Priority: optional
Maintainer: Debian Qt/KDE Maintainers <debian-qt-kde@lists.debian.org>
Uploaders: Adrien Grellier <perso@adrieng.fr>,
           Raúl Sánchez Siles <rasasi78@gmail.com>,
           Maximiliano Curia <maxy@debian.org>
Build-Depends: cmake,
               debhelper-compat (= 12),
               extra-cmake-modules (>= 5.19.0),
               gettext,
               kross-dev (>= 5.7.0),
               libboost-dev,
               libboost-system-dev,
               libeigen3-dev,
               libetonyek-dev,
               libfontconfig-dev,
               libfreetype-dev,
               libgit2-dev,

So `libgit2-dev` only shows up once in calligra's debian/control file.
I.e., none of the packages actually depends on it, which is kind of
what I found. Is it true? Can I safely say that all calligra packages
are fine with libgit2-dev's new v1.0.0?

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>
--
Package: librust-libgit2-sys-dev
Architecture: any
Multi-Arch: same
Depends:
 ${misc:Depends},
 librust-cc-1+default-dev (>= 1.0.42-~~),
 librust-cc-1+parallel-dev (>= 1.0.42-~~),
 librust-libc-0.2+default-dev,
 librust-libz-sys-1+default-dev (>= 1.0.22-~~),
 librust-pkg-config-0.3+default-dev (>= 0.3.7-~~),
 libgit2-dev

I.e., the package that actually depends on libgit2-dev is
librust-libgit2-sys-dev. However, when I check the build results under
.../libgit2-dev/dep/rust-libgit2-sys-0.10.0/debian/librust-libgit2-sys-dev:

$ find usr/
usr/
usr/share
usr/share/cargo
usr/share/cargo/registry
usr/share/cargo/registry/libgit2-sys-0.10.0
usr/share/cargo/registry/libgit2-sys-0.10.0/Cargo.toml
usr/share/cargo/registry/libgit2-sys-0.10.0/LICENSE-MIT
usr/share/cargo/registry/libgit2-sys-0.10.0/lib.rs
usr/share/cargo/registry/libgit2-sys-0.10.0/build.rs
usr/share/cargo/registry/libgit2-sys-0.10.0/.cargo_vcs_info.json
usr/share/cargo/registry/libgit2-sys-0.10.0/debian
usr/share/cargo/registry/libgit2-sys-0.10.0/debian/patches
usr/share/cargo/registry/libgit2-sys-0.10.0/debian/patches/abi-compat-0.28.3.patch
usr/share/cargo/registry/libgit2-sys-0.10.0/debian/patches/series
usr/share/cargo/registry/libgit2-sys-0.10.0/debian/patches/no-special-snowflake-env.patch
usr/share/cargo/registry/libgit2-sys-0.10.0/.cargo-checksum.json
usr/share/cargo/registry/libgit2-sys-0.10.0/LICENSE-APACHE
usr/share/doc
usr/share/doc/librust-libgit2-sys-dev
usr/share/doc/librust-libgit2-sys-dev/copyright
usr/share/doc/librust-libgit2-sys-dev/changelog.Debian.gz

I don't see any library built. So can I also safely say that it is
fine with libgit2-dev's new v1.0.0 as well?

thx