On 20 August 2017 at 17:10, Abhijith PA <abhij...@hacari.org> wrote: > > > The latest version of libgit2 is 0.26 and it has been uploaded to > > experimental. Is ruby-rugged 0.26 compatible with GitLab? > > > > > > -- > > Cheers, > > Russell Sim > > No, ruby-rugged need one to one matching with libgit2 version. Current > upstream version of ruby-rugged is 0.26, but there is a strong chance > packaging latest version will break the current gitlab version that we > are targeting. > > >From what i can see GitLab 9.5 uses 0.26. Is there any reason not to target this version instead? I realize this may not suite your original plans but it will be less work in the long term.
Theoretically, if we did change the epoch and then release version 0.25 into experimental, we would then need to do a full library transition of all libgit2 dependent packages only to immediately afterwards, do another full library transition to 0.26 since it's the current version. So either way you'll end up having to package 9.5 or greater, after you package your choice of GitLab 9.1-9.4. There are also other dependent packages that have already started packaging for 0.26 such as pygit2. -- Cheers, Russell Sim
