* [PR PATCH] pijul: update to 1.0.0-beta.2
@ 2022-05-10 10:23 leesongun
2022-05-10 21:32 ` classabbyamp
` (4 more replies)
0 siblings, 5 replies; 6+ messages in thread
From: leesongun @ 2022-05-10 10:23 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 809 bytes --]
There is a new pull request by leesongun against master on the void-packages repository
https://github.com/leesongun/void-packages pijul
https://github.com/void-linux/void-packages/pull/37072
pijul: update to 1.0.0-beta.2
This PR updates pijul from 0.12.2 to 1.0.0-beta.2, preparing for 1.0.0.
But since it seems there was non-[backward-compatible](https://pijul.org/posts/2021-06-28-two-changes/) [format change](https://pijul.org/posts/2021-01-05-how-to-survive/) since 0.12.2 and [1.0.0-beta guarantees format stability](https://pijul.org/posts/2022-01-08-beta/), this could be better than current version.
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### Local build testing
A patch file from https://github.com/void-linux/void-packages/pull/37072.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-pijul-37072.patch --]
[-- Type: text/x-diff, Size: 2150 bytes --]
From ef754c4d101f778cae84407049b06530798bbfd1 Mon Sep 17 00:00:00 2001
From: leesongun <12179851+leesongun@users.noreply.github.com>
Date: Tue, 10 May 2022 19:17:21 +0900
Subject: [PATCH] pijul: update to 1.0.0-beta.2
---
srcpkgs/pijul/patches/bindgen.patch | 9 ---------
srcpkgs/pijul/template | 12 +++++-------
2 files changed, 5 insertions(+), 16 deletions(-)
delete mode 100644 srcpkgs/pijul/patches/bindgen.patch
diff --git a/srcpkgs/pijul/patches/bindgen.patch b/srcpkgs/pijul/patches/bindgen.patch
deleted file mode 100644
index 04ccc8381aae..000000000000
--- a/srcpkgs/pijul/patches/bindgen.patch
+++ /dev/null
@@ -1,9 +0,0 @@
---- a/Cargo.toml
-+++ b/Cargo.toml
-@@ -133,3 +133,6 @@
- version = "2.0"
- [target."cfg(unix)".dependencies.tokio-uds]
- version = "0.2"
-+
-+[patch.crates-io]
-+"sequoia-rfc2822" = {path = '/builddir/sequoia-v0.9.0/rfc2822'}
diff --git a/srcpkgs/pijul/template b/srcpkgs/pijul/template
index 53fb1c83ebe5..6ef851f43569 100644
--- a/srcpkgs/pijul/template
+++ b/srcpkgs/pijul/template
@@ -1,19 +1,17 @@
# Template file for 'pijul'
pkgname=pijul
-version=0.12.2
-revision=5
+version=1.0.0-beta.2
+revision=1
build_style=cargo
_sequoia_ver=0.9.0
hostmakedepends="pkg-config clang"
-makedepends="libsodium-devel openssl-devel nettle-devel"
+makedepends="libgcc-devel openssl-devel libsodium-devel libzstd-devel xxHash-devel"
short_desc="Distributed version control system based on patches"
maintainer="Toyam Cox <Vaelatern@voidlinux.org>"
license="GPL-2.0-only"
homepage="https://pijul.org/"
-distfiles="https://crates.io/api/v1/crates/pijul/${version}/download>pijul-${version}.tar.gz
- https://gitlab.com/sequoia-pgp/sequoia/-/archive/v${_sequoia_ver}/sequoia-v${_sequoia_ver}.tar.gz"
-checksum="f92a3f4063e780ca45c161ceb0f42baf34dfeddf3359ebf6c2e0442d9abb5889
- 71823c88b9666611f3cfa6b1d923bd66fda92fa6a53368b195bd2f962fdf7f4b"
+distfiles="https://crates.io/api/v1/crates/pijul/${version}/download>pijul-${version}.tar.gz"
+checksum="9e0870af813cdab0a8f8f3687f545714fc0f6aeee47a2447bea3bf3ce6706dc5"
# We only want to install the binary, so don't run cargo install
do_install() {
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: pijul: update to 1.0.0-beta.2
2022-05-10 10:23 [PR PATCH] pijul: update to 1.0.0-beta.2 leesongun
@ 2022-05-10 21:32 ` classabbyamp
2022-05-10 23:03 ` classabbyamp
` (3 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: classabbyamp @ 2022-05-10 21:32 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 266 bytes --]
New comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/pull/37072#issuecomment-1122893196
Comment:
how does using the beta solve the compat issues? wouldn't the same compat issue exist when going from 0.12 to 1.0beta?
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: pijul: update to 1.0.0-beta.2
2022-05-10 10:23 [PR PATCH] pijul: update to 1.0.0-beta.2 leesongun
2022-05-10 21:32 ` classabbyamp
@ 2022-05-10 23:03 ` classabbyamp
2022-05-10 23:05 ` [PR REVIEW] " classabbyamp
` (2 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: classabbyamp @ 2022-05-10 23:03 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 364 bytes --]
New comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/pull/37072#issuecomment-1122893196
Comment:
how does using the beta solve the compat issues? wouldn't the same compat issue exist when going from 0.122 to 1.0.0-beta? I read the pages you linked to say that 1.0.0-beta onward will have a stable format guarantee.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PR REVIEW] pijul: update to 1.0.0-beta.2
2022-05-10 10:23 [PR PATCH] pijul: update to 1.0.0-beta.2 leesongun
2022-05-10 21:32 ` classabbyamp
2022-05-10 23:03 ` classabbyamp
@ 2022-05-10 23:05 ` classabbyamp
2022-08-10 2:09 ` github-actions
2022-08-24 2:15 ` [PR PATCH] [Closed]: " github-actions
4 siblings, 0 replies; 6+ messages in thread
From: classabbyamp @ 2022-05-10 23:05 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 181 bytes --]
New review comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/pull/37072#discussion_r869742485
Comment:
version cannot have `-` in it
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: pijul: update to 1.0.0-beta.2
2022-05-10 10:23 [PR PATCH] pijul: update to 1.0.0-beta.2 leesongun
` (2 preceding siblings ...)
2022-05-10 23:05 ` [PR REVIEW] " classabbyamp
@ 2022-08-10 2:09 ` github-actions
2022-08-24 2:15 ` [PR PATCH] [Closed]: " github-actions
4 siblings, 0 replies; 6+ messages in thread
From: github-actions @ 2022-08-10 2:09 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 305 bytes --]
New comment by github-actions[bot] on void-packages repository
https://github.com/void-linux/void-packages/pull/37072#issuecomment-1210068509
Comment:
Pull Requests become stale 90 days after last activity and are closed 14 days after that. If this pull request is still relevant bump it or assign it.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PR PATCH] [Closed]: pijul: update to 1.0.0-beta.2
2022-05-10 10:23 [PR PATCH] pijul: update to 1.0.0-beta.2 leesongun
` (3 preceding siblings ...)
2022-08-10 2:09 ` github-actions
@ 2022-08-24 2:15 ` github-actions
4 siblings, 0 replies; 6+ messages in thread
From: github-actions @ 2022-08-24 2:15 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 681 bytes --]
There's a closed pull request on the void-packages repository
pijul: update to 1.0.0-beta.2
https://github.com/void-linux/void-packages/pull/37072
Description:
This PR updates pijul from 0.12.2 to 1.0.0-beta.2, preparing for 1.0.0.
But since it seems there was non-[backward-compatible](https://pijul.org/posts/2021-06-28-two-changes/) [format change](https://pijul.org/posts/2021-01-05-how-to-survive/) since 0.12.2 and [1.0.0-beta guarantees format stability](https://pijul.org/posts/2022-01-08-beta/), this could be better than current version for future compatibility.
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### Local build testing
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2022-08-24 2:15 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-05-10 10:23 [PR PATCH] pijul: update to 1.0.0-beta.2 leesongun
2022-05-10 21:32 ` classabbyamp
2022-05-10 23:03 ` classabbyamp
2022-05-10 23:05 ` [PR REVIEW] " classabbyamp
2022-08-10 2:09 ` github-actions
2022-08-24 2:15 ` [PR PATCH] [Closed]: " github-actions
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).