# Pijul on macOS Fails with ssh/Nest – Seeking Nest Source Access and Contribution Opportunities

**URL:** <https://discourse.pijul.org/t/pijul-on-macos-fails-with-ssh-nest-seeking-nest-source-access-and-contribution-opportunities/1282>\
**Category:** Development\
**Created:** [April 3, 2025, 9:28pm UTC](https://discourse.pijul.org/t/pijul-on-macos-fails-with-ssh-nest-seeking-nest-source-access-and-contribution-opportunities/1282 "2025-04-03T21:28:51Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Asfolny](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/asfolny/32/627_2.png) [@Asfolny](https://discourse.pijul.org/u/Asfolny)\
**Post date:** [April 19, 2025, 3:19pm UTC](https://discourse.pijul.org/t/pijul-on-macos-fails-with-ssh-nest-seeking-nest-source-access-and-contribution-opportunities/1282/2 "2025-04-19T15:19:23Z")

</div>

Have you tried the fix mentioned here?

> [@Unable to push to the Nest](https://discourse.pijul.org/t/unable-to-push-to-the-nest/1214/10):
>
> The server-side has moved forward, while pijul remains stagnant. This can be easily fixed with a dirty hack at your own risk. cd pijul pijul remote I5GEGWCQIJKTINCFGJEEIVZXKU: https://nest.pijul.com/pijul/pijul pijul reset --force cargo update cd pijul-remote vi Cargo.toml # change thrussh = "0.34" to "0.35.6" cargo update cd .. cargo build --release cd pijul clone tankf33der@nest.pijul.com:tankf33der/picolisp # cloned cd picolisp # change something pijul rec -am"." pijul push -a # pushed P…

If that fixed it, the issue would likely be a version mismatch between nest and the versioned release of pijul, in my admittedly limited understanding of the problem; nest’s source code is not public (see [pijul/pijul - Discussion #963 - Thrussh should be updated to fix push command for nest](https://nest.pijul.com/pijul/pijul/discussions/963))

As for contributing, being new (this is my first interaction with people using pijul in fact, hi!), I can’t comment on how to contribute, I feel like the manual book wants to make me believe that the repo’s discussion section is the place for this to happen, but far as I can tell while it does get some talks going, it seems incredibly stale in the case of pijul/pijul itself, the above issue is merely a version bump, has been known since February, and still hasn’t been merged

---

_[View the full topic](https://discourse.pijul.org/t/pijul-on-macos-fails-with-ssh-nest-seeking-nest-source-access-and-contribution-opportunities/1282)._