From: f-fr <f-fr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: fpc: update to version 3.2.2
Date: Fri, 24 Jan 2025 20:53:04 +0100 [thread overview]
Message-ID: <20250124195304.129D721707@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-54095@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 494 bytes --]
New comment by f-fr on void-packages repository
https://github.com/void-linux/void-packages/pull/54095#issuecomment-2613274424
Comment:
Ok, I definitely need some help here. Maybe starting with the error on x86_64 ... there seems to be a conflict with another package installing a binary `/usr/bin/plex`. What is the right way to handle this? Should the binary from `fpc` be installed to some other location? Or be renamed? Something else? (I'm not sure how difficult this would be, though).
next prev parent reply other threads:[~2025-01-24 19:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-24 16:36 [PR PATCH] " f-fr
2025-01-24 19:53 ` f-fr [this message]
2025-01-25 8:12 ` [PR PATCH] [Updated] " f-fr
2025-04-26 2:05 ` github-actions
2025-05-10 2:07 ` [PR PATCH] [Closed]: " github-actions
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=20250124195304.129D721707@inbox.vuxu.org \
--to=f-fr@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).