From: cinerea0 <cinerea0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] eludris: fix fetch
Date: Fri, 25 Aug 2023 20:53:19 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45763@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 696 bytes --]
There is a new pull request by cinerea0 against master on the void-packages repository
https://github.com/cinerea0/void-packages eludris
https://github.com/void-linux/void-packages/pull/45763
eludris: fix fetch
#### Testing the changes
- I tested the changes in this PR: N/A
---
Upstream repo has disappeared. From the devs:
> Unfortunately there will not be any tool for managing Eludris
> instances in the near future until Eludris potentially sorts out its
> business model, to avoid a continuous net financial loss. For now
> Eludris has become proprietary and will not be self-hostable.
A patch file from https://github.com/void-linux/void-packages/pull/45763.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-eludris-45763.patch --]
[-- Type: text/x-diff, Size: 1456 bytes --]
From fc5d61eff8c3240696d9e28f43b34b46e141ef2b Mon Sep 17 00:00:00 2001
From: cinerea0 <cinerea0@disroot.org>
Date: Fri, 25 Aug 2023 14:50:54 -0400
Subject: [PATCH] eludris: fix fetch
Upstream repo has disappeared. From the devs:
> Unfortunately there will not be any tool for managing Eludris
> instances in the near future until Eludris potentially sorts out its
> business model, to avoid a continuous net financial loss. For now
> Eludris has become proprietary and will not be self-hostable.
---
srcpkgs/eludris/template | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/eludris/template b/srcpkgs/eludris/template
index 6215920c922c4..04b78c9f4bdbd 100644
--- a/srcpkgs/eludris/template
+++ b/srcpkgs/eludris/template
@@ -11,8 +11,10 @@ makedepends="openssl-devel"
short_desc="Simple CLI to help with setting up and managing your Eludris instance"
maintainer="Oliver Wilkes <oliverwilkes2006@icloud.com>"
license="MIT"
-homepage="https://github.com/eludris/eludris/tree/main/cli"
-distfiles="https://github.com/eludris/eludris/archive/refs/tags/v${version}.tar.gz"
+homepage="https://eludris.com/"
+# distfiles="https://github.com/eludris/eludris/archive/refs/tags/v${version}.tar.gz"
+# Upstream repo is gone, project is now proprietary
+distfiles="https://sources.voidlinux.org/eludris-${version}/v${version}.tar.gz"
checksum=e204969d056e147a97cb8d1b2a0c16b7e4d06c5895ef9bb939884ddc0ecdb3c2
post_install() {
next reply other threads:[~2023-08-25 18:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-25 18:53 cinerea0 [this message]
2023-09-12 5:43 ` [PR PATCH] [Merged]: " classabbyamp
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45763@inbox.vuxu.org \
--to=cinerea0@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).