Re: Verify the library transition
On Wed, Oct 28, 2020 at 3:47 AM Andrey Rahmatullin wrote:
> On Sat, Oct 17, 2020 at 3:27 PM Tong Sun <suntong001@users.sourceforge.net> wrote:
> > ... looking further into all those libgit2 related
> > packages that I've already built, I saw mixed results:
> >
> > -----------------------------------------------------
> > $ dpkg-deb -f gir1.2-ggit-1.0_0.28.0.1-2_amd64.deb Depends
> > gir1.2-glib-2.0, libgit2-glib-1.0-0 (>= 0.28.0.1)
> >
> > $ dpkg-deb -f golang-gopkg-libgit2-git2go.v28-dev_0.28.5-1_all.deb Depends
> > pkg-config, libgit2-dev (>> 0.28~)
> >
> > $ dpkg-deb -f libgit2-glib-1.0-0-dbgsym_0.28.0.1-2_amd64.deb Depends
> > libgit2-glib-1.0-0 (= 0.28.0.1-2)
> >
> > $ dpkg-deb -f libgit2-glib-1.0-0_0.28.0.1-2_amd64.deb Depends
> > libc6 (>= 2.14), libgit2-28 (>= 0.28.1), libglib2.0-0 (>= 2.44.0)
> >
> > $ dpkg-deb -f libgit2-glib-1.0-dev_0.28.0.1-2_amd64.deb Depends
> > gir1.2-ggit-1.0 (= 0.28.0.1-2), libgit2-glib-1.0-0 (= 0.28.0.1-2),
> > libgit2-dev (>= 0.26.0), libglib2.0-dev (>= 2.44.0)
> >
> > $ dpkg-deb -f librust-libgit2-sys+https-dev_0.10.0-1_amd64.deb Depends
> > librust-libgit2-sys-dev (= 0.10.0-1), librust-openssl-sys-0.9+default-dev
> >
> > $ dpkg-deb -f librust-libgit2-sys+libssh2-sys-dev_0.10.0-1_amd64.deb Depends
> > librust-libgit2-sys-dev (= 0.10.0-1),
> > librust-libssh2-sys-0.2+default-dev (>= 0.2.11-~~)
> >
> > $ dpkg-deb -f librust-libgit2-sys-dev_0.10.0-1_amd64.deb 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.,
> >
> > - some of them about built with libgit2-glib-1.0-0
> > - but some others are built with libgit2-28 (>= 0.28.1)
> > - and some I just literally don't know, e.g., libgit2-dev (>> 0.28~)
> >
> > I.e., I still haven't figured out how to control the lib a package
> > should links to.
> (it installed the -dev package from sid because you didn't add a version
> constraint to require the version from experimental)
Ok, to add a version constraint, is it OK that I use the following to
replace all libgit2 dependents from above, to make sure they require
the version from experimental (v1.0.0)?
libgit2-dev (>> 0.99)
> > PS, here are all libgit2 related packages installed in my system, and
> > their versions:
> >
> > libgit2-1.0:amd64_1.0.0+dfsg.1-1
> > libgit2-28:amd64_0.28.5+dfsg.1-1
> > libgit2-build-deps_1.0.0+dfsg.1-1
> > libgit2-dev:amd64_0.28.5+dfsg.1-1
> > libgit2-glib-1.0-0:amd64_0.28.0.1-2
> > libgit2-glib-1.0-dev:amd64_0.28.0.1-2
Moverover, give my specific case,
- single lib upgrade, and
- I've already installed the latest libgit2-1.0 into my sid
would it matter any more if I build in my sid host? I know building
with sbuild + experimental build-dep is ideal, but I can't think of
any reason why I can't do build in my sid host now, if I am to update
the dependent version constraints to all that package I'm building.
thanks
Reply to: