Github messages for voidlinux
 help / color / mirror / Atom feed
From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: NetworkManager: update to 1.40.0
Date: Wed, 31 Aug 2022 21:56:42 +0200	[thread overview]
Message-ID: <20220831195642.fE3a0BIbqMymUqdLoqY_RDaC6gXSelOSBYwOuS0txs8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39003@inbox.vuxu.org>

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

New comment by paper42 on void-packages repository

https://github.com/void-linux/void-packages/pull/39003#issuecomment-1233360414

Comment:
> The errors appear to be most commonly caused by appstream not being present. The following configurations have resulted in failure:
> 
>     * `AppStream` in hostmakedepends
> 
>     * `appstream-glib` in hostmakedepends and `appstream-glib-devel` in makedepends
> 
>     * `appstream-glib` and `appstream-glib-devel` in makedepends

the error message is about a polkit policy file, not an appstream file, add polkit-devel to hostmakedepends

  parent reply	other threads:[~2022-08-31 19:56 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-31 15:32 [PR PATCH] " cinerea0
2022-08-31 17:42 ` [PR PATCH] [Updated] " cinerea0
2022-08-31 17:53 ` cinerea0
2022-08-31 18:17 ` [PR PATCH] [Closed]: " cinerea0
2022-08-31 18:17 ` [PR PATCH] [Updated] " cinerea0
2022-08-31 18:19 ` cinerea0
2022-08-31 18:44 ` cinerea0
2022-08-31 19:19 ` cinerea0
2022-08-31 19:55 ` cinerea0
2022-08-31 19:55 ` [PR REVIEW] " paper42
2022-08-31 19:56 ` paper42 [this message]
2022-08-31 19:58 ` [PR PATCH] [Updated] " cinerea0
2022-08-31 20:01 ` cinerea0
2022-08-31 20:03 ` [PR REVIEW] " cinerea0
2022-08-31 20:28 ` paper42
2022-08-31 20:29 ` paper42
2022-09-01 14:06 ` [PR PATCH] [Updated] " cinerea0
2022-09-01 14:46 ` cinerea0
2022-09-01 15:11 ` cinerea0
2022-09-01 17:47 ` [PR PATCH] [Merged]: " paper42

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=20220831195642.fE3a0BIbqMymUqdLoqY_RDaC6gXSelOSBYwOuS0txs8@z \
    --to=paper42@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).