From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pierre Neidhardt Subject: Re: Maintaining GNU Jami package for Guix Date: Sun, 20 Oct 2019 13:48:09 +0200 Message-ID: <87a79vd4ee.fsf@ambrevar.xyz> References: <20191018205608.45b264dc@kompiuter> <87ftjpyhsz.fsf@devup.no> <87mudxhzv8.fsf@ambrevar.xyz> <20191019223821.71b6dd45@interia.pl> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:38419) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iM9h2-0006hl-9x for guix-devel@gnu.org; Sun, 20 Oct 2019 07:48:17 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iM9h0-0001tO-LK for guix-devel@gnu.org; Sun, 20 Oct 2019 07:48:15 -0400 Received: from relay8-d.mail.gandi.net ([217.70.183.201]:39905) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iM9h0-0001tA-AR for guix-devel@gnu.org; Sun, 20 Oct 2019 07:48:14 -0400 In-Reply-To: <20191019223821.71b6dd45@interia.pl> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Jan Wielkiewicz Cc: guix-devel@gnu.org --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Jan Wielkiewicz writes: >> Jami used to depend on their own fork of pjproject (as packaged in >> Guix). >> However it seems that recent versions have dropped the fork to use >> upstream instead. _This needs to be confirmed._ > It seems the latest version still has patches for pjproject in the > source code, but I can ask the devs about it.=20 Don't hesitate to post on the issue tracker, in my experience they are responsive and helpful. >> If this is the case, switching the pjproject input to use upstream >> should work when updating Jami. > I've tried updating Jami, but pjproject seems to be a problem - > don't know what have changed, but now even the currently packaged > version of pjproject won't compile. Here's the log: > > starting phase `autoconf' > autoconf: error: invalid option `-vfi' > Try `autoconf --help' for more information. > command "autoconf" "-vfi" "-o" "aconfigure" "aconfigure.ac" failed with > status 1 I remember this error, but I don't know if it was for Jami or some unrelated package. It's an issue with some versions of autoconf. I think you have to use '-v -f -i' instead, and maybe leave out one offending option. > I've also tried updating pjproject to the current version Jami uses - > 2.8, it throws the same error. I managed to skip that by removing the > "-vfi" options by commenting it out like this: > > (add-before 'patch-source-shebangs 'autoconf > (lambda _ > (invoke "autoconf" "-o" ;"-vfi" > "aconfigure" "aconfigure.ac"))) See above, don't leave out everything. > But then it fails later, while doing "make dep": > > make[2]: Entering directory > '/tmp/guix-build-pjproject-2.8.drv-0/pjproject-2.8/third_party/build' > make[2]: *** gsm: No such file or directory. Stop. make[2]: Leaving > directory > '/tmp/guix-build-pjproject-2.8.drv-0/pjproject-2.8/third_party/build' > make[1]: *** [Makefile:7: dep] Error 1 make[1]: Leaving directory > '/tmp/guix-build-pjproject-2.8.drv-0/pjproject-2.8/third_party/build' > make: *** [Makefile:14: dep] Error 1 command "make" "dep" failed with > status 2 > > Why are third party directories removed if they're necessary to build > pjproject? Should I package contents of these folders as separate > package?=20 This is the whole trick about packaging Jami: we remove all the embedded dependencies, and instead build against our own. If you look at the package definitions, you'll see that we explicitly skip building the third_party, and instead we expose them as inputs. > Also something is causing builds of Jami to be irreproducible > - every time I run guix upgrade, Jami gets upgraded to the same > version. Is there a way to check what exactly is unstable? Try running `guix build --check ...` against Jami specific-inputs, like pjproject, libring, libring-client, etc. =2D-=20 Pierre Neidhardt https://ambrevar.xyz/ --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEUPM+LlsMPZAEJKvom9z0l6S7zH8FAl2sSXkACgkQm9z0l6S7 zH9wPAf/WNUPJAgaxPs4QZSOTqT57gGrCIito7dzW6ZXVqfvLYD72sLN2pmq3Z6w CApPDRsr+krMqftsdaW1R+l//JZpwh/syxFdJ+A7eldoToJJ4qWB3A31flbISUPV clNmhy9nTIGT+ZFdbUGxBkqtHxWN4Ct/qXN/FG67h5TEcEBAnP18MWpCVfpBXGid 4hmIAGwcIHvkTK+bOKWgODnCgX2fCwHoI3LbaMi3IpV4gQcvjE/j+2gtSyqFplnC YmJjfo6K3SVyEZR4pZcMSsYsHqSLeOCT/pp71iSlbd4x8WVsBho8RqwXdJEefYq/ 3c0g8TLxLCg6IOu9zH7hzGlQO7PxvA== =kGjP -----END PGP SIGNATURE----- --=-=-=--