From: woshilapin <woshilapin@tuziwo.info>
To: sebastien <ml-dev@reycoyrehourcq.me>
Cc: "Ian Eure" <ian@retrospec.tv>,
"Marek Paśnikowski" <marek@marekpasnikowski.pl>,
help-guix@gnu.org, "Cayetano Santos" <csantosb@inventati.org>
Subject: Re: Packaging Proton Bridge: cryptic compilation failure
Date: Fri, 06 Dec 2024 13:34:52 +0000 [thread overview]
Message-ID: <rNVvvDT17kb20AE1q6EfqGCZaNsRPmKD1w6f88LpndQBpmvF9sXGFRrKij_wd5jlH1Ns7Iugqe7wT1oMawZw33wnQk4xTyzXaQmtSUnnrV8=@tuziwo.info> (raw)
In-Reply-To: <173341800403.6.14598806331512627250.521121694@reycoyrehourcq.me>
Hi,
> As a everyday user of ProtonMail/guix for work i'm also interested to help you on this task. Perhaps could you provide a chan that contain only the dependencies and manifest to build proton-bridge ?
>
Just chiming in, did you know there was also `hydroxide`[1], already packaged into `guix`, and that has worked perfectly well for me as a proton bridge?
[1] https://packages.guix.gnu.org/packages/hydroxide/0.2.29/
Hope this helps.
--
woshilapin aka Jean SIMARD
next prev parent reply other threads:[~2024-12-06 13:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-30 16:26 Packaging Proton Bridge: cryptic compilation failure Marek Paśnikowski
2024-11-30 17:29 ` Ian Eure
2024-11-30 18:08 ` Cayetano Santos
2024-11-30 18:56 ` Marek Paśnikowski
2024-11-30 19:22 ` Ian Eure
2024-12-05 16:37 ` sebastien
2024-12-06 13:34 ` woshilapin [this message]
2024-12-06 18:01 ` Marek Paśnikowski
2024-12-09 16:24 ` Packaging Proton Bridge: Progress Report #1 Marek Paśnikowski
2024-12-09 16:38 ` Ian Eure
2024-12-09 16:47 ` Marek Paśnikowski
2024-12-09 16:52 ` Ian Eure
2024-12-09 19:15 ` Marek Paśnikowski
2024-12-09 19:33 ` Ian Eure
2024-12-10 10:28 ` Packaging Proton Bridge: Progress Report #2 Marek Paśnikowski
2024-12-10 14:08 ` Suhail Singh
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='rNVvvDT17kb20AE1q6EfqGCZaNsRPmKD1w6f88LpndQBpmvF9sXGFRrKij_wd5jlH1Ns7Iugqe7wT1oMawZw33wnQk4xTyzXaQmtSUnnrV8=@tuziwo.info' \
--to=woshilapin@tuziwo.info \
--cc=csantosb@inventati.org \
--cc=help-guix@gnu.org \
--cc=ian@retrospec.tv \
--cc=marek@marekpasnikowski.pl \
--cc=ml-dev@reycoyrehourcq.me \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).