Hello! Thank you very much for helping!
It looks like you made your changes alongside updates to the upstream source. Sadly I won't merge any changes to the upstream sources. I'll handle these myself with git-buildpackage. Can you please submit your opendht changes again, this time only including the changes in the debian/ folder? Then, we will move on to Jami. Cheers, -- Alexandre Viau av...@debian.org On Fri, 25 Sep 2020 at 10:20, Amin Bandali <amin.band...@savoirfairelinux.com> wrote: > > Hello Alexandre, all, > > I recently joined the Jami team at SFL, and I'm also the newly-appointed > GNU (co)maintainer for Jami. I would like to help improve the situation > with the Jami package in the official Debian repositories however I can. > I think the first step would be getting more recent versions of the Jami > Debian package to build. > > I opened a number of merge requests against Debian's package sources for > OpenDHT and Jami, including changes with which I've been able to build > the WIP update to the jami_20191214.1.07edb5e version. The merge > requests are as follows: > > - New upstream version 2.1.6: > https://salsa.debian.org/debian/opendht/-/merge_requests/3 > - pristine-tar data for opendht_2.1.6.orig.tar.gz: > https://salsa.debian.org/debian/opendht/-/merge_requests/4 > - Update to new upstream version 2.1.6, along with tweaks useful for > building newer versions of jami: > https://salsa.debian.org/debian/opendht/-/merge_requests/5 > > - Fix build with jami_20191214.1.07edb5e: > https://salsa.debian.org/pkg-voip-team/ring/-/merge_requests/2 > > In essence, I pulled the latest version of OpenDHT into the Debian > source repo for it, and tweaked the CONFIGURE_FLAGS and the Libs link > flags in pkgconfig-static.patch to make the package useful for linking > and building newer Jami against. On the Jami side, I updated the file > name for the jami-gnome manpage, and also changed some (non-existent) > 'distclean' instances to 'clean' so that the build wouldn't fail with a > non-clean tree. > > I'd appreciate it if y'all would take my changes for a spin and see if > you're able to build jami_20191214.1.07edb5e with them. If yes, and if > everyone's happy with the changes and they're merged, next we could try > building the most recent version of Jami and see how that goes. > > Best, > > -- > Amin Bandali > Free Software Consultant > Savoir-faire Linux > GNU Jami: bandali