Github messages for voidlinux
 help / color / mirror / Atom feed
From: icp1994 <icp1994@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] rooster: update to 2.13.0.
Date: Thu, 18 Jan 2024 19:22:47 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48266@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1257 bytes --]

There is a new pull request by icp1994 against master on the void-packages repository

https://github.com/icp1994/void-packages rooster
https://github.com/void-linux/void-packages/pull/48266

rooster: update to 2.13.0.
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES**|**briefly**|**NO**

<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl
  - armv7l
  - armv6l-musl
-->


A patch file from https://github.com/void-linux/void-packages/pull/48266.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-rooster-48266.patch --]
[-- Type: text/x-diff, Size: 1129 bytes --]

From 9fdee6cfeba375ab32adee269a00ccb8afc3dee7 Mon Sep 17 00:00:00 2001
From: icp <pangolin@vivaldi.net>
Date: Sat, 13 Jan 2024 12:25:32 +0530
Subject: [PATCH] rooster: update to 2.13.0.

---
 srcpkgs/rooster/template | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/srcpkgs/rooster/template b/srcpkgs/rooster/template
index dba4a9eca43db..23d344065d4a9 100644
--- a/srcpkgs/rooster/template
+++ b/srcpkgs/rooster/template
@@ -1,13 +1,13 @@
 # Template file for 'rooster'
 pkgname=rooster
-version=2.11.0
-revision=2
+version=2.13.0
+revision=1
 build_style=cargo
 hostmakedepends="pkg-config python3"
-makedepends="libX11-devel libXmu-devel openssl-devel libsodium-devel"
+makedepends="libX11-devel libXmu-devel"
 short_desc="Simple password manager for geeks"
 maintainer="Orphaned <orphan@voidlinux.org>"
 license="Apache-2.0"
 homepage="https://crates.io/crates/rooster"
 distfiles="https://static.crates.io/crates/rooster/rooster-${version}.crate"
-checksum=3873e9024d3008e2fd61fdbeb13e20c61e8c2e3ff0a87c2197852989c899a154
+checksum=e928044f4a4bde1643bcd134c65c74d2d1856472546fa0cfdc76e94658f67468

             reply	other threads:[~2024-01-18 18:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-18 18:22 icp1994 [this message]
2024-01-19 19:52 ` [PR PATCH] [Updated] " icp1994
2024-01-20 19:01 ` icp1994
2024-01-20 19:03 ` rooster: update to 2.12.0 icp1994
2024-01-29 15:09 ` [PR PATCH] [Merged]: " cinerea0

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48266@inbox.vuxu.org \
    --to=icp1994@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /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 NNTP newsgroup(s).