From: Leo Famulari <leo@famulari.name>
To: guix-devel@gnu.org
Subject: Re: 03/03: gnu: elogind: Update to 232.3.
Date: Wed, 6 Sep 2017 17:04:26 -0400 [thread overview]
Message-ID: <20170906210426.GA4908@jasmine.lan> (raw)
In-Reply-To: <20170905145954.AE51C20335@vcs0.savannah.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 999 bytes --]
On Tue, Sep 05, 2017 at 10:59:54AM -0400, Ricardo Wurmus wrote:
> rekado pushed a commit to branch master
> in repository guix.
>
> commit fa67d5654176b4b815832eaf259188e1486c65ab
> Author: Ricardo Wurmus <rekado@elephly.net>
> Date: Tue Jul 25 10:15:58 2017 +0200
>
> gnu: elogind: Update to 232.3.
>
> * gnu/packages/freedesktop.scm (elogind): Update to 232.3.
> [home-page]: Use new upstream home page.
> [arguments]: Disable tests, add new required configure flags; add build phase
> "autogen".
> [native-inputs]: Add autoconf, automake, libtool, and python.
According to `git bisect`, this update broke several packages related to
FreeDesktop and GNOME.
Specifically, those packages all require libcap to be available now. The
list of affected packages can be found with `git grep libcap`, since
they all had libcap added to their inputs.
I found that propagating libcap from elogind fixed some of the build
failures and not others.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next parent reply other threads:[~2017-09-06 21:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170905145953.17202.3144@vcs0.savannah.gnu.org>
[not found] ` <20170905145954.AE51C20335@vcs0.savannah.gnu.org>
2017-09-06 21:04 ` Leo Famulari [this message]
[not found] ` <CADh9keW-SUVOtvXHU+6QXLU9Cv-x5mUTSsw91iBYyewGWfVMKQ@mail.gmail.com>
[not found] ` <CADh9keUwWOq6za7xzpPc6-1f0R28hK6YHMx+6UTuR8urBwQtXw@mail.gmail.com>
2017-09-06 21:18 ` 03/03: gnu: elogind: Update to 232.3 Peter Mikkelsen
2017-09-07 12:11 ` Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170906210426.GA4908@jasmine.lan \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.