Github messages for voidlinux
 help / color / mirror / Atom feed
From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: New package: singularity-3.11.0
Date: Wed, 21 Jun 2023 03:57:03 +0200	[thread overview]
Message-ID: <20230621015703.gKQ-MkaiydOeXmCAPfvLft1_8ZfHbH_Wxh5njG1FBPs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42592@inbox.vuxu.org>

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

There's a closed pull request on the void-packages repository

New package: singularity-3.11.0
https://github.com/void-linux/void-packages/pull/42592

Description:
This is based on the work of @olafmersmann, https://github.com/void-linux/void-packages/pull/28129.
When merged, this should close https://github.com/void-linux/void-packages/issues/8135.

<!-- Uncomment relevant sections and delete options which are not applicable -->

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

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

<!-- 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, (x86_64-glibc)


      parent reply	other threads:[~2023-06-21  1:57 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-04 22:49 [PR PATCH] " snwnde
2023-03-04 22:53 ` [PR REVIEW] " classabbyamp
2023-03-04 23:14 ` snwnde
2023-03-06 20:50 ` [PR PATCH] [Updated] [WIP] " snwnde
2023-03-06 20:59 ` snwnde
2023-03-06 21:40 ` snwnde
2023-03-06 21:55 ` snwnde
2023-03-06 22:16 ` [PR PATCH] [Updated] " snwnde
2023-03-06 22:17 ` snwnde
2023-03-07 19:01 ` snwnde
2023-03-07 19:06 ` snwnde
2023-03-07 19:07 ` snwnde
2023-03-07 19:07 ` snwnde
2023-03-07 19:09 ` snwnde
2023-03-07 19:10 ` snwnde
2023-03-07 19:11 ` snwnde
2023-03-07 19:12 ` [PR REVIEW] " snwnde
2023-03-07 19:13 ` snwnde
2023-03-07 19:15 ` snwnde
2023-03-07 19:26 ` snwnde
2023-03-07 19:31 ` snwnde
2023-03-07 19:32 ` snwnde
2023-03-07 19:34 ` snwnde
2023-06-06  2:05 ` github-actions
2023-06-21  1:57 ` github-actions [this message]

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=20230621015703.gKQ-MkaiydOeXmCAPfvLft1_8ZfHbH_Wxh5njG1FBPs@z \
    --to=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).