Bug#971571: transition: libgit2
Hey, On Wed, Dec 9, 2020 at 3:13 PM Utkarsh Gupta wrote: > I'll take a look at python-pygit2 today as well. So leaves us with > ruby-rugged. I'll come to that in next few days if no one beats me to > it. FWIW, I've uploaded both, thereby completing all the blockers. Hopefully this transition should complete soon :) Thanks to everybody who was involved here, especially Ximin and Sebastian! \o/ - u
Bug#971571: transition: libgit2
Hello, On Wed, Dec 9, 2020 at 2:23 AM Sebastian Ramacher wrote: > > So I conclude that it's probably fine to upload libgit2 1.1.0 to unstable > > now? > Okay, then let's do this now. Please go ahead. Awesome, uploaded! I'll take a look at python-pygit2 today as well. So leaves us with ruby-rugged. I'll come to that in next few days if no one beats me to it. - u
Bug#971571: transition: libgit2
On 2020-12-08 16:58:46 +0530, Utkarsh Gupta wrote:
> Hi Sebastian,
>
> On Tue, Dec 8, 2020 at 3:30 PM Sebastian Ramacher
> wrote:
> > v30 was accepted. Please perform a source-only upload for the arch: all
> > packages.
>
> That should be done now! \o/
>
> > > The only reverse-{,build-}dependency is gitaly, it seems. So I'm CCing
> > > Praveen so he gets a heads up.
> >
> > Filed #976820 against gitaly.
> >
> > In any case, I'll remove golang-gopkg-libgit2-git2go.v28 and
> > gitaly from testing to unblock this transition. gitaly is blocked by
> > ruby-faraday which is currently causing a bunch of autopkgtest
> > regressions.
>
> Great, thanks for this!
>
> I do have another (stupid) question :)
> libgit2 upstream has released 1.1.0 after 1.0.1 (which is the
> transition we're pusruing). However, libgit2 1.1.0 if backwards
> compatible *but* still a transition is needed for it.
> I've already worked on updating the same in experimental and it is now
> accepted as well. Do you think we can do a 1.1.0 transition along with
> this as well?
>
> Whilst I didn't build all the reverse-{build-}dependencies but I
> believe there shouldn't be much of a problem.
We could do these two transitions together, yes. But I'd prefer if you
could gives us a rough estimate on the number of expected build failures
in reverse dependencies.
Will it need another new version of golang-gopkg-libgit2-git2go?
Cheers
--
Sebastian Ramacher
signature.asc
Description: PGP signature
Bug#971571: transition: libgit2
On Tue, 8 Dec 2020 11:00:40 +0100 Sebastian Ramacher wrote: > Filed #976820 against gitaly. I will follow it up with upstream. > In any case, I'll remove golang-gopkg-libgit2-git2go.v28 and > gitaly from testing to unblock this transition. gitaly is blocked by > ruby-faraday which is currently causing a bunch of autopkgtest > regressions. ruby-faraday will be unblocked if ruby-puppet-forge is removed from testing (the other two packages failing autopkgtest are already removed from unstable)
Bug#971571: transition: libgit2
Hi Sebastian,
On Tue, Dec 8, 2020 at 3:30 PM Sebastian Ramacher wrote:
> v30 was accepted. Please perform a source-only upload for the arch: all
> packages.
That should be done now! \o/
> > The only reverse-{,build-}dependency is gitaly, it seems. So I'm CCing
> > Praveen so he gets a heads up.
>
> Filed #976820 against gitaly.
>
> In any case, I'll remove golang-gopkg-libgit2-git2go.v28 and
> gitaly from testing to unblock this transition. gitaly is blocked by
> ruby-faraday which is currently causing a bunch of autopkgtest
> regressions.
Great, thanks for this!
I do have another (stupid) question :)
libgit2 upstream has released 1.1.0 after 1.0.1 (which is the
transition we're pusruing). However, libgit2 1.1.0 if backwards
compatible *but* still a transition is needed for it.
I've already worked on updating the same in experimental and it is now
accepted as well. Do you think we can do a 1.1.0 transition along with
this as well?
Whilst I didn't build all the reverse-{build-}dependencies but I
believe there shouldn't be much of a problem.
- u
Bug#971571: transition: libgit2
On 2020-12-07 14:14:50 +0530, Utkarsh Gupta wrote:
> Hi Peter,
>
> On Sun, Dec 6, 2020 at 11:06 AM peter green wrote:
> > In addition to the packages mentioned here, it seems there is another
> > package involved: golang-gopkg-libgit2-git2go.v28 . It only builds
> > arch-all packages and does not directly depend on the library, but it
> > FTBFS and it's autopkgtest fails with the new version.
> >
> > The FTBFS was picked up in a rebuild test by Lucas and a bug report
> > was filed https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976522
>
> Yes, because v28 is only compatible with libgit2 v0.28. For libgit2
> v1.0, we need v30 for git2go. So I've uploaded
> golang-gopkg-libgit2-git2go.v30 to NEW and once accepted, I'll file an
> RM for v28.
v30 was accepted. Please perform a source-only upload for the arch: all
packages.
> The only reverse-{,build-}dependency is gitaly, it seems. So I'm CCing
> Praveen so he gets a heads up.
Filed #976820 against gitaly.
In any case, I'll remove golang-gopkg-libgit2-git2go.v28 and
gitaly from testing to unblock this transition. gitaly is blocked by
ruby-faraday which is currently causing a bunch of autopkgtest
regressions.
Cheers
--
Sebastian Ramacher
signature.asc
Description: PGP signature
Bug#971571: transition: libgit2
Hi Peter,
On Sun, Dec 6, 2020 at 11:06 AM peter green wrote:
> In addition to the packages mentioned here, it seems there is another
> package involved: golang-gopkg-libgit2-git2go.v28 . It only builds
> arch-all packages and does not directly depend on the library, but it
> FTBFS and it's autopkgtest fails with the new version.
>
> The FTBFS was picked up in a rebuild test by Lucas and a bug report
> was filed https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976522
Yes, because v28 is only compatible with libgit2 v0.28. For libgit2
v1.0, we need v30 for git2go. So I've uploaded
golang-gopkg-libgit2-git2go.v30 to NEW and once accepted, I'll file an
RM for v28.
The only reverse-{,build-}dependency is gitaly, it seems. So I'm CCing
Praveen so he gets a heads up.
Bug#971571: transition: libgit2
I've rebuilt the relevant reverse-build-dependencies from unstable In addition to the packages mentioned here, it seems there is another package involved: golang-gopkg-libgit2-git2go.v28 . It only builds arch-all packages and does not directly depend on the library, but it FTBFS and it's autopkgtest fails with the new version. The FTBFS was picked up in a rebuild test by Lucas and a bug report was filed https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976522
Bug#971571: transition: libgit2
Hi, On Sat, Dec 5, 2020 at 1:41 AM Sebastian Ramacher wrote: > Scheduled the binNMUs except for horizon-eda (involved in python3.9-defaults). Great, thank you! I've, meanwhile, uploaded python-pygit2 and libgit-raw-perl! Will hopefully get on to ruby-rugged, as well! \o/ - u
Bug#971571: transition: libgit2
On 2020-12-05 00:12:00, Utkarsh Gupta wrote: > Hi Sebastian, > > On Fri, Dec 4, 2020 at 10:54 PM Sebastian Ramacher > wrote: > > Please go ahead with the upload to unstable. > > Great, thanks, I did an upload just now! :) Scheduled the binNMUs except for horizon-eda (involved in python3.9-defaults). Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#971571: transition: libgit2
Hi Sebastian, On Fri, Dec 4, 2020 at 10:54 PM Sebastian Ramacher wrote: > Please go ahead with the upload to unstable. Great, thanks, I did an upload just now! :) - u
Bug#971571: transition: libgit2
Control: forwarded -1 https://release.debian.org/transitions/html/auto-libgit2.html Control: tags -1 confirmed On 2020-10-02 01:44:50 +0100, Ximin Luo wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > Control: block -1 by 971562 971563 971564 971565 971566 971567 971568 971569 > 971570 > > Hello release team! > > I'd like to request a transition slot for libgit2. > > libgit2 1.0.0 is in experimental and ready to start the transition from > 0.28 in unstable. > > I've rebuilt the relevant reverse-build-dependencies from unstable > > The following succeed and can be binNMU'd directly: > - calligra fritzing gnuastro horizon-eda > > The following succeed after patches, bugs have been filed: > - kup-backup > > The following could not be tested because they currently FTBFS: > - ktexteditor julia > > The following fail, but probably just need to be bumped to the latest > upstream version: > - libgit-raw-perl libgit2-glib-1.0-0 python-pygit2 ruby-rugged: bindings to > libgit2 > - gnome-builder: depends on libgit2-glib-1.0-0 > > The following fail, and probably need more invasive changes such as upgrading > to the new API; bugs have been filed: > - gall (low popcon 30), geany-plugins > > The following will be handled later by the rust team (including me): > - cargo (fixed in git), rust-* Please go ahead with the upload to unstable. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#971571: transition: libgit2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Control: block -1 by 971562 971563 971564 971565 971566 971567 971568 971569 971570 Hello release team! I'd like to request a transition slot for libgit2. libgit2 1.0.0 is in experimental and ready to start the transition from 0.28 in unstable. I've rebuilt the relevant reverse-build-dependencies from unstable The following succeed and can be binNMU'd directly: - calligra fritzing gnuastro horizon-eda The following succeed after patches, bugs have been filed: - kup-backup The following could not be tested because they currently FTBFS: - ktexteditor julia The following fail, but probably just need to be bumped to the latest upstream version: - libgit-raw-perl libgit2-glib-1.0-0 python-pygit2 ruby-rugged: bindings to libgit2 - gnome-builder: depends on libgit2-glib-1.0-0 The following fail, and probably need more invasive changes such as upgrading to the new API; bugs have been filed: - gall (low popcon 30), geany-plugins The following will be handled later by the rust team (including me): - cargo (fixed in git), rust-* Thanks, Ximin Ben file: title = "libgit2"; is_affected = .depends ~ "libgit2-2[0-9]" | .depends ~ "libgit2-1.0"; is_good = .depends ~ "libgit2-1.0"; is_bad = .depends ~ "libgit2-2[0-9]"; -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable'), (300, 'unstable'), (100, 'experimental'), (1, 'experimental-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
