Github messages for voidlinux
 help / color / mirror / Atom feed
From: FollieHiyuki <FollieHiyuki@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] grub-btrfs: update to 4.10.1
Date: Mon, 27 Sep 2021 13:09:26 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33155@inbox.vuxu.org> (raw)

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

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

https://github.com/FollieHiyuki/void-packages grub-btrfs
https://github.com/void-linux/void-packages/pull/33155

grub-btrfs: update to 4.10.1
<!-- Mark items with [x] where applicable -->

#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)

#### Have the results of the proposed changes been tested?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [x] I generally don't use the affected packages but briefly tested this PR

<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!-- 
#### Does it build and run successfully? 
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] 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/33155.patch is attached

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

From 7ae7fad5cc03850f798a79acfbb26b534fbc9137 Mon Sep 17 00:00:00 2001
From: FollieHiyuki <folliekazetani@protonmail.com>
Date: Mon, 27 Sep 2021 18:02:57 +0700
Subject: [PATCH 1/2] grub-btrfs: update to 4.10.1

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

diff --git a/srcpkgs/grub-btrfs/template b/srcpkgs/grub-btrfs/template
index 0e646c9c3f82..9579e0a51e0e 100644
--- a/srcpkgs/grub-btrfs/template
+++ b/srcpkgs/grub-btrfs/template
@@ -1,6 +1,6 @@
 # Template file for 'grub-btrfs'
 pkgname=grub-btrfs
-version=4.9
+version=4.10.1
 revision=1
 build_style=gnu-makefile
 depends="grub bash"
@@ -9,7 +9,7 @@ maintainer="Anjandev Momi <anjan@momi.ca>"
 license="GPL-3.0-or-later"
 homepage="https://github.com/Antynea/grub-btrfs"
 distfiles="https://github.com/Antynea/grub-btrfs/archive/v${version}.tar.gz"
-checksum=62461133c697643e98a608239773f500edee3e4055c5729fef6639d1cd610243
+checksum=3ef53f16a7bc0fdd5a5ac2216a41bf1b2f4fd2283717c5c240415d5d24d3734b
 
 post_install() {
 	rm -rf -- "${DESTDIR}"/usr/lib/systemd

From defc5f4b49f098b4aee63f8131bb74f1579ab9e5 Mon Sep 17 00:00:00 2001
From: FollieHiyuki <folliekazetani@protonmail.com>
Date: Mon, 27 Sep 2021 18:07:10 +0700
Subject: [PATCH 2/2] grub-btrfs-runit: rename to runit-grub-btrfs

This commit make the name inlined with other runit packages in the repo
---
 srcpkgs/grub-btrfs/template | 8 +++++++-
 srcpkgs/runit-grub-btrfs    | 1 +
 2 files changed, 8 insertions(+), 1 deletion(-)
 create mode 120000 srcpkgs/runit-grub-btrfs

diff --git a/srcpkgs/grub-btrfs/template b/srcpkgs/grub-btrfs/template
index 9579e0a51e0e..582550bb1eda 100644
--- a/srcpkgs/grub-btrfs/template
+++ b/srcpkgs/grub-btrfs/template
@@ -15,7 +15,7 @@ post_install() {
 	rm -rf -- "${DESTDIR}"/usr/lib/systemd
 }
 
-grub-btrfs-runit_package() {
+runit-grub-btrfs_package() {
 	depends="wendy ${sourcepkg}>=${version}_${revision}"
 	short_desc+=" - runit service"
 
@@ -23,3 +23,9 @@ grub-btrfs-runit_package() {
 		vsv grub-btrfs
 	}
 }
+
+grub-btrfs-runit_package() {
+	depends="runit-grub-btrfs>=${version}_${revision}"
+	short_desc+=" - runit service (transitional dummy package)"
+	build_style=meta
+}
diff --git a/srcpkgs/runit-grub-btrfs b/srcpkgs/runit-grub-btrfs
new file mode 120000
index 000000000000..ad9b415a9d84
--- /dev/null
+++ b/srcpkgs/runit-grub-btrfs
@@ -0,0 +1 @@
+grub-btrfs
\ No newline at end of file

             reply	other threads:[~2021-09-27 11:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-27 11:09 FollieHiyuki [this message]
2021-09-27 11:13 ` [PR PATCH] [Updated] " FollieHiyuki
2021-09-27 11:18 ` FollieHiyuki
2021-09-27 12:44 ` [PR PATCH] [Updated] " FollieHiyuki
2021-09-27 14:14 ` ericonr
2021-09-27 15:39 ` [PR PATCH] [Updated] " FollieHiyuki
2021-09-27 15:40 ` FollieHiyuki
2021-09-27 16:28 ` teldra
2021-10-02 19:50 ` [PR REVIEW] " ericonr
2021-10-03 13:48 ` FollieHiyuki
2021-10-03 17:23 ` ericonr
2021-10-04  9:33 ` [PR PATCH] [Updated] " FollieHiyuki
2021-10-04  9:34 ` FollieHiyuki
2021-10-04  9:35 ` [PR REVIEW] " FollieHiyuki
2021-10-04 13:18 ` [PR PATCH] [Merged]: " ericonr

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-33155@inbox.vuxu.org \
    --to=folliehiyuki@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).