all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Peter Mikkelsen <petermikkelsen10@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: 03/03: gnu: elogind: Update to 232.3.
Date: Wed, 6 Sep 2017 23:18:09 +0200	[thread overview]
Message-ID: <CADh9keVvp23+DwgMsiDc3GRHfFBO1ZNq5MUbfAGuZGAJ6HjtMQ@mail.gmail.com> (raw)
In-Reply-To: <CADh9keUwWOq6za7xzpPc6-1f0R28hK6YHMx+6UTuR8urBwQtXw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1264 bytes --]

Hi leo,

Den 6. sep. 2017 23.04 skrev "Leo Famulari" <leo@famulari.name>:

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.


I have sent a patch which updates elogind to 232.4, and at least, that
allows med to login to my system, which wasn't possible before. I have not
checked if it does anything about the libcap issue though.

Cheers,
Peter

[-- Attachment #2: Type: text/html, Size: 2029 bytes --]

  parent reply	other threads:[~2017-09-06 21:18 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   ` 03/03: gnu: elogind: Update to 232.3 Leo Famulari
     [not found]     ` <CADh9keW-SUVOtvXHU+6QXLU9Cv-x5mUTSsw91iBYyewGWfVMKQ@mail.gmail.com>
     [not found]       ` <CADh9keUwWOq6za7xzpPc6-1f0R28hK6YHMx+6UTuR8urBwQtXw@mail.gmail.com>
2017-09-06 21:18         ` Peter Mikkelsen [this message]
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=CADh9keVvp23+DwgMsiDc3GRHfFBO1ZNq5MUbfAGuZGAJ6HjtMQ@mail.gmail.com \
    --to=petermikkelsen10@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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.