# Error when runiing \`pijul push\` on fedora 30

**URL:** <https://discourse.pijul.org/t/error-when-runiing-pijul-push-on-fedora-30/413>\
**Category:** Question\
**Created:** [September 17, 2019, 8:32am UTC](https://discourse.pijul.org/t/error-when-runiing-pijul-push-on-fedora-30/413 "2019-09-17T08:32:05Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![cad106uk](https://avatars.discourse-cdn.com/v4/letter/c/f08c70/32.png) [@cad106uk](https://discourse.pijul.org/u/cad106uk)\
**Post date:** [September 17, 2019, 8:32am UTC](https://discourse.pijul.org/t/error-when-runiing-pijul-push-on-fedora-30/413/1 "2019-09-17T08:32:05Z")

</div>

I am using Fedora version 30. I have used `rustup` and `cargo install pijul` to setup and install Pijul.

Whenever I run `pijul push` I get the following error. Does anyone else get this error, does anyone know what this error means?

> Shall I push this patch? [ynkad?] y  
> thread ‘main’ panicked at ‘called `Result::unwrap()` on an `Err` value: Error(IO(Custom { kind: UnexpectedEof, error: “early eof” }))’, src/libcore/result.rs:999:5  
> stack backtrace:  
> 0: backtrace::backtrace::libunwind::trace  
> at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.29/src/backtrace/libunwind.rs:88  
> 1: backtrace::backtrace::trace\_unsynchronized  
> at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.29/src/backtrace/mod.rs:66  
> 2: std::sys\_common::backtrace::\_print  
> at src/libstd/sys\_common/backtrace.rs:47  
> 3: std::sys\_common::backtrace::print  
> at src/libstd/sys\_common/backtrace.rs:36  
> 4: std::panicking::default\_hook::{{closure}}  
> at src/libstd/panicking.rs:200  
> 5: std::panicking::default\_hook  
> at src/libstd/panicking.rs:214  
> 6: std::panicking::rust\_panic\_with\_hook  
> at src/libstd/panicking.rs:477  
> 7: std::panicking::continue\_panic\_fmt  
> at src/libstd/panicking.rs:384  
> 8: rust\_begin\_unwind  
> at src/libstd/panicking.rs:311  
> 9: core::panicking::panic\_fmt  
> at src/libcore/panicking.rs:85  
> 10: core::result::unwrap\_failed  
> 11: pijul::commands::remote::Session::push  
> 12: pijul::commands::push::run  
> 13: pijul::main  
> 14: std::rt::lang\_start::{{closure}}  
> 15: std::rt::lang\_start\_internal::{{closure}}  
> at src/libstd/rt.rs:49  
> 16: std::panicking::try::do\_call  
> at src/libstd/panicking.rs:296  
> 17: \_\_rust\_maybe\_catch\_panic  
> at src/libpanic\_unwind/lib.rs:82  
> 18: std::panicking::try  
> at src/libstd/panicking.rs:275  
> 19: std::panic::catch\_unwind  
> at src/libstd/panic.rs:394  
> 20: std::rt::lang\_start\_internal  
> at src/libstd/rt.rs:48  
> 21: main  
> 22: \_\_libc\_start\_main  
> 23: \_start  
> note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.