Github messages for voidlinux
 help / color / mirror / Atom feed
From: kruceter <kruceter@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] fortune-mod-void: update to 20230121.
Date: Sat, 21 Jan 2023 14:44:40 +0100	[thread overview]
Message-ID: <20230121134440.u0dw1bc79VKyEuEJ1I04m6B2P_HT3D2m2s5UIKR8KhA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41767@inbox.vuxu.org>

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

There is an updated pull request by kruceter against master on the void-packages repository

https://github.com/kruceter/void-packages oreo-crossy-road
https://github.com/void-linux/void-packages/pull/41767

fortune-mod-void: update to 20230121.
#### 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/41767.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-oreo-crossy-road-41767.patch --]
[-- Type: text/x-diff, Size: 1741 bytes --]

From cd4a4100f93743d796e56a5526b185e070d94bde Mon Sep 17 00:00:00 2001
From: Krul Ceter <kruceter@proton.me>
Date: Sat, 21 Jan 2023 08:40:03 +0300
Subject: [PATCH] fortune-mod-void: update to 20230121.

"Crossy road" is an arcade "gen z" endless runner game heavily inspired
by "Frogger" from 1981.

In this case "crossy" can refer to cross-compilers being built for a
long time with the involved risk of dying due to unexpected error
(running out of storage, network connection failure, non-intentionally
overlooked parts of committed changes, etc).

Once the error is fixed, the build machines are triggered again with
the new run in hope that all frogs will get to their destination.
---
 srcpkgs/fortune-mod-void/files/void | 3 +++
 srcpkgs/fortune-mod-void/template   | 4 ++--
 2 files changed, 5 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/fortune-mod-void/files/void b/srcpkgs/fortune-mod-void/files/void
index a63f22069787..27fd1256ac75 100644
--- a/srcpkgs/fortune-mod-void/files/void
+++ b/srcpkgs/fortune-mod-void/files/void
@@ -187,3 +187,6 @@ aedinius: if work has taught me anything i can worry about y2038 starting around
 q66: better fs would be false advertising
 q66: should be called wrsfs
 %
+ahesford: the builders seem to be playing crossy road
+abby: oreo installed frogger on them
+%
diff --git a/srcpkgs/fortune-mod-void/template b/srcpkgs/fortune-mod-void/template
index cac177dc6b19..03446dd705f0 100644
--- a/srcpkgs/fortune-mod-void/template
+++ b/srcpkgs/fortune-mod-void/template
@@ -1,7 +1,7 @@
 # Template file for 'fortune-mod-void'
 pkgname=fortune-mod-void
-version=20200307
-revision=2
+version=20230121
+revision=1
 create_wrksrc=yes
 hostmakedepends="fortune-mod"
 depends="${hostmakedepends}"

  reply	other threads:[~2023-01-21 13:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-21  6:12 [PR PATCH] " kruceter
2023-01-21 13:44 ` kruceter [this message]
2023-01-22 21:17 ` ahesford
2023-01-22 21:17 ` [PR PATCH] [Closed]: " ahesford

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=20230121134440.u0dw1bc79VKyEuEJ1I04m6B2P_HT3D2m2s5UIKR8KhA@z \
    --to=kruceter@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).