Commit Graph

34 Commits

Author SHA1 Message Date
Vladyslav M
e853b90763
pijul: 1.0.0-alpha.21 -> 1.0.0-alpha.24 2020-12-20 18:04:51 +02:00
Vladyslav M
7bb1035037
pijul: 1.0.0-alpha.17 -> 1.0.0-alpha.21 2020-12-11 22:53:48 +02:00
Vladyslav M
8de71d243b
pijul: 1.0.0-alpha.11 -> 1.0.0-alpha.17 2020-12-05 16:06:43 +02:00
Vladyslav M
f107a46bac
pijul: 1.0.0-alpha.8 -> 1.0.0-alpha.11 2020-12-01 00:09:57 +02:00
Vladyslav M
fe79e0abed
pijul: 1.0.0-alpha.5 -> 1.0.0-alpha.8 2020-11-26 22:12:00 +02:00
Vladyslav M
4b453515f1
pijul: 1.0.0-alpha.3 -> 1.0.0-alpha.5 2020-11-22 15:27:10 +02:00
Vladyslav M
65e0474c7a
pijul: 1.0.0-alpha.1 -> 1.0.0-alpha.3 2020-11-16 21:49:15 +02:00
Vladyslav M
a429039a1f
pijul: 1.0.0-alpha -> 1.0.0-alpha.1 2020-11-14 23:21:01 +02:00
Vladyslav M
2e1400173b
pijul: 0.12.0 -> 1.0.0-alpha 2020-11-09 21:05:03 +02:00
zowoq
473536e3b5 buildRustPackage: remove platform.all from packages 2020-08-16 12:48:18 +10:00
Michael Reilly
84cf00f980
treewide: Per RFC45, remove all unquoted URLs 2020-04-10 17:54:53 +01:00
Benjamin Hipple
201d464f12 pijul: fix build by migrating off legacy fetchCargo
Currently broken; see #79975 for details. Would also be fixed by #80153
eventually, but since we want to upgrade either way we might as well do so now.

https://hydra.nixos.org/job/nixpkgs/trunk/pijul.x86_64-linux
2020-02-16 09:36:17 -08:00
Benjamin Hipple
eb11feaa0b treewide: change fetchCargoTarball default to opt-out
Changes the default fetcher in the Rust Platform to be the newer
`fetchCargoTarball`, and changes every application using the current default to
instead opt out.

This commit does not change any hashes or cause any rebuilds. Once integrated,
we will start deleting the opt-outs and recomputing hashes.

See #79975 for details.
2020-02-13 22:41:37 -08:00
Michael Weiss
434ff94e73
pijul: Fix the build (broke due to a more recent Rust version)
This uses an upstream patch [0] to fix a compatibility error with a new
version of Rust. Fix #79150.

Unfortunately patching Rust dependencies in Nixpkgs turned out to be way
more hacky than I expected (maybe there is a nicer way?), but it should
be fine for now.

A new release might follow soonish [1] so that we can drop the patches.

References:
- https://nest.pijul.com/pijul_org/pijul/discussions/401
- https://nest.pijul.com/pijul_org/thrussh/discussions/31

[0]: https://nest.pijul.com/pijul_org/thrussh:master/patches/AsyuWkJg4jAwNaG3H1yv1kbECx5E3GQAtjzXWBDB8yEGMswyfKbxKvYmAGWCohTVaTipdvF8mHh63yU5PTr5F9py
[1]: https://discourse.pijul.org/t/is-this-project-still-active-yes-it-is/451
2020-02-04 14:05:02 +01:00
Mario Rodas
31a9f6a341 pijul: fix build 2019-11-21 19:08:06 -08:00
volth
7bb6b373ab treewide: name -> pname (#67513) 2019-08-31 07:41:22 -04:00
Vladyslav M
0f2e9c00f7
pijul: fix darwin build 2019-05-23 16:06:25 +03:00
Will Dietz
11fc7674b9 pijul: 0.11.0 -> 0.12.0
https://pijul.org/posts/2019-04-23-pijul-0.12/

* add new dep on nettle, all the crypto libraries :)
* libclang needed
* clang input is not quite right AFAIK, but fixes the build.
  idea from other package,
  seems to resolve problems finding headers via libclang?
2019-05-20 10:38:42 +01:00
RohanHart
25e7f59516 pijul: 0.10.0 -> 0.11.0 (#50870) 2018-11-22 07:32:17 +00:00
Jörg Thalheim
1246c31761
pijul: 0.8.0 -> 0.10.0 2018-10-28 10:45:58 +00:00
Joerg Thalheim
72163a64c4 pijul: 0.7.3 -> 0.8.0 2017-11-19 09:01:47 +00:00
Kevin Cox
5f8cf0048e rust: update cargo builder to fetch registry dynamically
The biggest benefit is that we no longer have to update the registry
package. This means that just about any cargo package can be built by
nix. No longer does `cargo update` need to be feared because it will
update to packages newer then what is available in nixpkgs.

Instead of fetching the cargo registry this bundles all the source code
into a "vendor/" folder.

This also uses the new --frozen and --locked flags which is nice.

Currently cargo-vendor only provides binaries for Linux and
macOS 64-bit. This can be solved by building it for the other
architectures and uploading it somewhere (like the NixOS cache).

This also has the downside that it requires a change to everyone's deps
hash. And if the old one is used because it was cached it will fail to
build as it will attempt to use the old version. For this reason the
attribute has been renamed to `cargoSha256`.

Authors:
* Kevin Cox <kevincox@kevincox.ca>
* Jörg Thalheim <Mic92@users.noreply.github.com>
* zimbatm <zimbatm@zimbatm.com>
2017-10-23 00:30:47 +01:00
dywedir
7c696a08ce pijul: 0.6.0 -> 0.7.3 2017-08-27 02:28:30 +02:00
Florent Becker
1951578395 pijul: 0.4.4 -> 0.6.0 2017-06-12 13:37:14 +02:00
Florent Becker
dcca9b17e3 pijul: 0.4.1 -> 0.4.4 2017-04-13 15:25:25 +02:00
Florent Becker
3699a545fd pijul: 0.3.3 -> 0.4.1 2017-04-03 15:04:04 +02:00
Florent Becker
20542a2028 pijul: 0.3 -> 0.3.3 2017-03-22 17:26:04 +01:00
Florent Becker
ea80c91bd3 pijul: init at 0.3.0 (re-init) 2017-03-20 10:27:38 +01:00
Florent Becker
0a840d4f41 pijul: remove
This version is not working, and it is not even a release upstream
2017-02-21 15:34:28 +01:00
Tadas Barzdzius
d27a658846 pijul: mark as broken 2016-12-29 09:57:39 +02:00
Domen Kožar
d6a4a30fb1 pijul: build only on 64bit platforms
(cherry picked from commit 8479962862)
Signed-off-by: Domen Kožar <domen@dev.si>
2016-09-13 10:37:55 +02:00
Tadas Barzdzius
a2973df033 pijul: use stable rustPlatform 2016-04-20 15:08:12 +03:00
Brian McKenna
93328bbd62 pijul: 0.2-6ab9ba
Maintainer has been working with us, this commit was given by them.
2016-02-17 07:28:26 +11:00
Brian McKenna
c6c1d3f777 pijul: init at 0.1 2015-10-21 21:35:02 +11:00