Github messages for voidlinux
 help / color / mirror / Atom feed
From: r-ricci <r-ricci@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] incus: fix typo in README.voidlinux
Date: Sun, 19 Jan 2025 23:44:45 +0100	[thread overview]
Message-ID: <20250119224445.69334212AC@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-53666@inbox.vuxu.org>

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

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

https://github.com/r-ricci/void-packages incus-typo
https://github.com/void-linux/void-packages/pull/53666

incus: fix typo in README.voidlinux
<!-- 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/53666.patch is attached

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

From e84acb4354c44a137915dcfe0be78ada31490023 Mon Sep 17 00:00:00 2001
From: Roberto Ricci <io@r-ricci.it>
Date: Tue, 24 Dec 2024 17:01:46 +0100
Subject: [PATCH] incus: fix typo in README.voidlinux

---
 srcpkgs/incus/files/README.voidlinux | 2 +-
 srcpkgs/incus/template               | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/incus/files/README.voidlinux b/srcpkgs/incus/files/README.voidlinux
index 31a55a3415ece8..d08532b3e1f42f 100644
--- a/srcpkgs/incus/files/README.voidlinux
+++ b/srcpkgs/incus/files/README.voidlinux
@@ -14,4 +14,4 @@ variable in `/etc/rc.conf` be set to `unified`.
 Optional dependencies:
 
 To run virtual machines, install `qemu` and `edk2-ovmf`.
-To run OCI containers, install `spokeo` and `umoci`.
+To run OCI containers, install `skopeo` and `umoci`.
diff --git a/srcpkgs/incus/template b/srcpkgs/incus/template
index a7c8e9bfda226a..b5599a00807f0b 100644
--- a/srcpkgs/incus/template
+++ b/srcpkgs/incus/template
@@ -1,7 +1,7 @@
 # Template file for 'incus'
 pkgname=incus
 version=6.6.0
-revision=2
+revision=3
 build_style=go
 build_helper=qemu
 go_import_path=github.com/lxc/incus/v6

  parent reply	other threads:[~2025-01-19 22:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-24 16:04 [PR PATCH] incus: fix typo in README.voidlinux r-ricci
2024-12-31 16:22 ` duskmoss
2025-01-19 22:44 ` r-ricci [this message]
2025-01-23 15:43 ` [PR PATCH] [Merged]: " leahneukirchen

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=20250119224445.69334212AC@inbox.vuxu.org \
    --to=r-ricci@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).