Github messages for voidlinux
 help / color / mirror / Atom feed
From: tranzystorek-io <tranzystorek-io@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] cocogitto: update to 5.5.0
Date: Thu, 17 Aug 2023 16:32:42 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45637@inbox.vuxu.org> (raw)

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

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

https://github.com/tranzystorek-io/void-packages cocogitto
https://github.com/void-linux/void-packages/pull/45637

cocogitto: update to 5.5.0
<!-- Uncomment relevant sections and delete options which are not applicable -->

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

<!--
#### 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/45637.patch is attached

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

From 6dbcfc7d4abfa20ff1d70e67fb34fe9e5242b18b Mon Sep 17 00:00:00 2001
From: Marcin Puc <tranzystorek.io@protonmail.com>
Date: Thu, 17 Aug 2023 16:29:01 +0200
Subject: [PATCH] cocogitto: update to 5.5.0

---
 srcpkgs/cocogitto/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/cocogitto/template b/srcpkgs/cocogitto/template
index d539c000e0cee..5f3e962216af8 100644
--- a/srcpkgs/cocogitto/template
+++ b/srcpkgs/cocogitto/template
@@ -1,6 +1,6 @@
 # Template file for 'cocogitto'
 pkgname=cocogitto
-version=5.4.0
+version=5.5.0
 revision=1
 build_style=cargo
 build_helper=qemu
@@ -13,7 +13,7 @@ license="MIT"
 homepage="https://github.com/cocogitto/cocogitto"
 changelog="https://raw.githubusercontent.com/cocogitto/cocogitto/main/CHANGELOG.md"
 distfiles="https://github.com/cocogitto/cocogitto/archive/refs/tags/${version}.tar.gz"
-checksum=93065217191d3e1739e6bca78b0b6de7d7dd1b5334229702fff9e84162060feb
+checksum=709c54c6c64463af607590ac970dc5a45cbcc0236a5a15d609d9a77461f11325
 # Test suite is not atomic, relies on user environment such as git user configuration
 make_check=no
 

             reply	other threads:[~2023-08-17 14:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-17 14:32 tranzystorek-io [this message]
2023-08-17 17:11 ` icp1994
2023-08-17 17:17 ` tranzystorek-io
2023-08-18 21:09 ` [PR PATCH] [Updated] " tranzystorek-io
2023-08-20 21:16 ` [PR PATCH] [Merged]: " Duncaen

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-45637@inbox.vuxu.org \
    --to=tranzystorek-io@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).