From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Jan Wielkiewicz <tona_kosmicznego_smiecia@interia.pl>
Cc: guix-devel@gnu.org
Subject: Re: Maintaining GNU Jami package for Guix
Date: Sun, 20 Oct 2019 13:48:09 +0200 [thread overview]
Message-ID: <87a79vd4ee.fsf@ambrevar.xyz> (raw)
In-Reply-To: <20191019223821.71b6dd45@interia.pl>
[-- Attachment #1: Type: text/plain, Size: 2956 bytes --]
Jan Wielkiewicz <tona_kosmicznego_smiecia@interia.pl> 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.
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?
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.
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-10-20 11:48 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 18:56 Maintaining GNU Jami package for Guix Jan
2019-10-18 19:28 ` Marius Bakke
2019-10-19 9:02 ` Pierre Neidhardt
2019-10-19 20:38 ` Jan Wielkiewicz
2019-10-19 20:52 ` Ricardo Wurmus
2019-10-19 22:37 ` Jan
2019-10-20 11:14 ` Ricardo Wurmus
2019-10-20 11:51 ` Pierre Neidhardt
2019-10-20 11:48 ` Pierre Neidhardt [this message]
2019-10-25 15:03 ` Pierre Neidhardt
2019-10-25 19:44 ` Jan Wielkiewicz
2019-10-26 10:12 ` Pierre Neidhardt
2019-10-26 23:24 ` Jan Wielkiewicz
2019-10-28 7:53 ` Pierre Neidhardt
2019-10-27 18:13 ` Jan Wielkiewicz
2019-10-27 18:18 ` Pierre Neidhardt
2019-10-27 19:23 ` Jan Wielkiewicz
2019-10-27 21:52 ` Jan Wielkiewicz
2019-10-31 20:19 ` Jan Wielkiewicz
2019-10-31 21:37 ` Pierre Neidhardt
2019-10-31 22:26 ` Marius Bakke
2019-11-01 12:01 ` Jan Wielkiewicz
2019-11-01 19:02 ` Pierre Neidhardt
2019-11-01 20:42 ` Jan Wielkiewicz
2019-11-02 9:38 ` Pierre Neidhardt
2019-11-03 16:37 ` Marius Bakke
2019-11-03 17:43 ` Jan
2019-11-03 18:06 ` Marius Bakke
2019-11-01 12:29 ` Jan Wielkiewicz
2019-11-01 19:01 ` Pierre Neidhardt
2019-11-01 23:16 ` Jan Wielkiewicz
2019-11-03 10:15 ` Pierre Neidhardt
2019-11-03 10:54 ` Jan Wielkiewicz
2019-11-04 10:02 ` Gábor Boskovits
2019-11-03 10:59 ` Jan Wielkiewicz
2019-11-03 17:07 ` Marius Bakke
2019-11-03 17:47 ` Jan
2019-11-03 18:12 ` Marius Bakke
2019-11-03 18:27 ` Jan
2019-11-03 18:52 ` Marius Bakke
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a79vd4ee.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=guix-devel@gnu.org \
--cc=tona_kosmicznego_smiecia@interia.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).