Github messages for voidlinux
 help / color / mirror / Atom feed
From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] flatpak-builder: missing deps?
Date: Fri, 29 Apr 2022 04:13:23 +0200	[thread overview]
Message-ID: <20220429021323.uTJQAx4r0JbGOLggro9IMaupUT3-uVKcJ8O0W3Fb60A@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-16053@inbox.vuxu.org>

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

Closed issue by StreetStrider on void-packages repository

https://github.com/void-linux/void-packages/issues/16053

Description:
It seemes that `flatpak-builder` misses deps:
`elfutils`, `patch`.

I've tried to use flatpak-builder. It's hard to distinguish between errors related to build process and to package itself, but it seemes, that this deps are inherent to any build process with flatpak. Threads on the internet confirms that in other systems flatpak depends on them.

### System
* xuname: Void 5.2.21_1 x86_64 GenuineIntel notuptodate rrFF
* package:  flatpak-builder-1.0.9_1

### Steps to reproduce the behavior
Build with `flatpak-builder` which involves anything more complex than building an empty app and involves patches.


  parent reply	other threads:[~2022-04-29  2:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-02 14:06 [ISSUE] " voidlinux-github
2021-01-08 21:19 ` kawaiiamber
2021-01-08 21:19 ` kawaiiamber
2021-01-08 21:20 ` kawaiiamber
2021-01-17 20:38 ` StreetStrider
2021-01-17 20:38 ` StreetStrider
2021-01-17 20:47 ` kawaiiamber
2021-01-17 20:48 ` kawaiiamber
2021-01-17 20:50 ` StreetStrider
2021-04-14 16:43 ` thegarlynch
2022-04-15  2:12 ` github-actions
2022-04-29  2:13 ` github-actions [this message]
2022-04-29  6:48 ` kawaiiamber

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=20220429021323.uTJQAx4r0JbGOLggro9IMaupUT3-uVKcJ8O0W3Fb60A@z \
    --to=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).