Github messages for voidlinux
 help / color / mirror / Atom feed
From: zen0bit <zen0bit@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] Update template
Date: Thu, 13 Jan 2022 07:45:36 +0100	[thread overview]
Message-ID: <20220113064536.vyPx-AfMGHCxpW8kwO21DSeR6YH6EXlM5eXbyDEeytA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34519@inbox.vuxu.org>

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

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

https://github.com/oSoWoSo/void-packages clearine
https://github.com/void-linux/void-packages/pull/34519

Update template
<!-- 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?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] 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.)
- [x] I built this PR locally for my native architecture, (x86_64 glibc)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
  - [ ] aarch64-musl
  - [ ] armv7l
  - [ ] armv6l-musl
-->


## Trying again

pull request #33537 

A patch file from https://github.com/void-linux/void-packages/pull/34519.patch is attached

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

From 18009ef2e43779d951983a3a2544e30f88d858fa Mon Sep 17 00:00:00 2001
From: zenobit <6384793+zen0bit@users.noreply.github.com>
Date: Tue, 14 Dec 2021 02:26:19 +0100
Subject: [PATCH 1/4] Update template

---
 srcpkgs/clearine/template | 13 ++++++-------
 1 file changed, 6 insertions(+), 7 deletions(-)

diff --git a/srcpkgs/clearine/template b/srcpkgs/clearine/template
index 9ab51e8d1d87..349d1f924136 100644
--- a/srcpkgs/clearine/template
+++ b/srcpkgs/clearine/template
@@ -1,17 +1,16 @@
 # Template file for 'clearine'
 pkgname=clearine
-version=0.7
-revision=4
+version=0.7.2
+revision=1
 build_style=python3-module
-pycompile_module="Clearine"
 hostmakedepends="python3-setuptools"
 depends="python3-gobject python3-cairo"
 short_desc="GTK3-based logout-window overlay for independent windowmanager"
-maintainer="Frank Steinborn <steinex@nognu.de>"
+maintainer="oSoWoSo <pm@osowoso.xyz>"
 license="MIT"
-homepage="https://github.com/yuune/clearine"
-distfiles="https://github.com/yuune/clearine/archive/${version}.tar.gz"
-checksum=18a1a6b8b726c430e848a6688c97cd095fc01d7b15907fac28a267155b69588d
+homepage="https://github.com/oSoWoSo/clearine"
+distfiles="https://github.com/oSoWoSo/${pkgname}/archive/${version}.tar.gz"
+checksum=732f22a0d4b60a2affc2f16eb37fe75a7ce283021d4ceaaade590bd2e341c8c7
 conf_files="/etc/clearine.conf"
 
 pre_build() {

From 07c06437d8127c838469631e7c518b6f94d7ecea Mon Sep 17 00:00:00 2001
From: zenobit <6384793+zen0bit@users.noreply.github.com>
Date: Wed, 12 Jan 2022 18:55:14 +0100
Subject: [PATCH 2/4] Update build.yaml

---
 .github/workflows/build.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/workflows/build.yaml b/.github/workflows/build.yaml
index 8ecd4d0e658a..fd664ac8c8d7 100644
--- a/.github/workflows/build.yaml
+++ b/.github/workflows/build.yaml
@@ -30,7 +30,7 @@ jobs:
     if: "!contains(github.event.pull_request.title, '[ci skip]') && !contains(github.event.pull_request.body, '[ci skip]')"
 
     container:
-      image: 'ghcr.io/void-linux/xbps-src-masterdir:20210313rc01-${{ matrix.config.bootstrap }}'
+      image: 'ghcr.io/void-linux/xbps-src-masterdir:v20211105RC01-${{ matrix.config.bootstrap }}'
       env:
         PATH: '/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/sbin:/usr/local/bin:/tmp/bin'
         ARCH: '${{ matrix.config.arch }}'

From 98e19df280faf27422854eeaa401194849442525 Mon Sep 17 00:00:00 2001
From: zenobit <6384793+zen0bit@users.noreply.github.com>
Date: Wed, 12 Jan 2022 18:59:04 +0100
Subject: [PATCH 3/4] Update fetch_upstream.sh

---
 common/travis/fetch_upstream.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/common/travis/fetch_upstream.sh b/common/travis/fetch_upstream.sh
index b1b06d9d54f9..09d6da7fef03 100755
--- a/common/travis/fetch_upstream.sh
+++ b/common/travis/fetch_upstream.sh
@@ -9,4 +9,4 @@ elif command -v git >/dev/null 2>&1; then
 fi
 
 /bin/echo -e '\x1b[32mFetching upstream...\x1b[0m'
-$GIT_CMD fetch --depth 200 git://github.com/void-linux/void-packages.git master
+$GIT_CMD fetch --depth 200 git://github.com/oSoWoSo/void-packages.git master

From 25790c683c447d39979208ff1132d7efae08f200 Mon Sep 17 00:00:00 2001
From: zenobit <6384793+zen0bit@users.noreply.github.com>
Date: Thu, 13 Jan 2022 07:42:44 +0100
Subject: [PATCH 4/4] Restore fetch_upstream.sh

---
 common/travis/fetch_upstream.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/common/travis/fetch_upstream.sh b/common/travis/fetch_upstream.sh
index 16ae2b379206..45315563e0b1 100755
--- a/common/travis/fetch_upstream.sh
+++ b/common/travis/fetch_upstream.sh
@@ -9,4 +9,4 @@ elif command -v git >/dev/null 2>&1; then
 fi
 
 /bin/echo -e '\x1b[32mFetching upstream...\x1b[0m'
-$GIT_CMD fetch --depth 200 https://github.com/oSoWoSo/void-packages.git master
+$GIT_CMD fetch --depth 200 https://github.com/void-linux/void-packages.git master

  parent reply	other threads:[~2022-01-13  6:45 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-14  1:28 [PR PATCH] " zen0bit
2021-12-14 13:19 ` Duncaen
2022-01-12 17:55 ` [PR PATCH] [Updated] " zen0bit
2022-01-12 17:59 ` zen0bit
2022-01-12 19:03 ` [PR REVIEW] " paper42
2022-01-12 19:05 ` [PR PATCH] [Updated] " zen0bit
2022-01-13  6:42 ` zen0bit
2022-01-13  6:45 ` zen0bit [this message]
2022-01-13  7:06 ` zen0bit
2022-01-13  7:16 ` zen0bit
2022-01-13  7:20 ` zen0bit
2022-01-13  7:43 ` zen0bit
2022-01-13  7:44 ` [PR REVIEW] " zen0bit
2022-01-13  8:13 ` [PR PATCH] [Closed]: " zen0bit
2022-01-14 12:19 ` paper42
2022-01-14 18:48 ` zen0bit
2022-01-14 18:59 ` [PR PATCH] [Updated] " zen0bit
2022-01-14 22:05 ` paper42
2022-01-30 15:24 ` [PR PATCH] [Updated] " zen0bit
2022-01-30 15:26 ` zen0bit
2022-01-30 17:02 ` paper42
2022-01-30 17:02 ` [PR PATCH] [Closed]: " paper42
2022-01-30 17:41 ` zen0bit
2022-01-30 17:41 ` paper42
  -- strict thread matches above, loose matches on Subject: below --
2021-05-04 19:00 [PR PATCH] " asymmetros
2021-05-04 19:18 ` [PR PATCH] [Updated] " asymmetros
2021-04-28 22:08 [PR PATCH] " grim-cypher
2021-04-28 23:08 ` [PR PATCH] [Updated] " grim-cypher
2021-04-29  0:25 ` grim-cypher

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=20220113064536.vyPx-AfMGHCxpW8kwO21DSeR6YH6EXlM5eXbyDEeytA@z \
    --to=zen0bit@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).