Github messages for voidlinux
 help / color / mirror / Atom feed
From: newbluemoon <newbluemoon@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] treeline: update to 3.1.5
Date: Mon, 26 Sep 2022 06:44:11 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39472@inbox.vuxu.org> (raw)

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

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

https://github.com/newbluemoon/void-packages treeline
https://github.com/void-linux/void-packages/pull/39472

treeline: update to 3.1.5
<!-- 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**|**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, (x86_64)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  (it’s python3 only, no actual compiling)
  - armv7l-musl


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

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

From 5b3d1dbae5a0d840e997be9f062e1e12c1e2d268 Mon Sep 17 00:00:00 2001
From: newbluemoon <blaumolch@mailbox.org>
Date: Mon, 26 Sep 2022 06:37:20 +0200
Subject: [PATCH] treeline: update to 3.1.5

---
 srcpkgs/treeline/template | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/treeline/template b/srcpkgs/treeline/template
index 92cbd5c97185..b234ec8c8e0c 100644
--- a/srcpkgs/treeline/template
+++ b/srcpkgs/treeline/template
@@ -1,7 +1,7 @@
 # Template file for 'treeline'
 pkgname=treeline
-version=3.1.4
-revision=2
+version=3.1.5
+revision=1
 wrksrc="TreeLine-${version}"
 pycompile_dirs="usr/share/treeline"
 hostmakedepends="python3"
@@ -11,7 +11,7 @@ maintainer="newbluemoon <blaumolch@mailbox.org>"
 license="GPL-2.0-or-later"
 homepage="http://treeline.bellz.org/"
 distfiles="https://github.com/doug-101/TreeLine/archive/v${version}.tar.gz"
-checksum=bc6918f7bc892ab00cfc9293236c2d03021d64a5b6190594501048f2590572ab
+checksum=8bef3c3819dab7968f8cd46e3a1e817a06259270d3d01f4eb9f22b1821094650
 python_version=3
 
 do_install() {

             reply	other threads:[~2022-09-26  4:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-26  4:44 newbluemoon [this message]
2022-09-26 13:04 ` [PR PATCH] [Merged]: " classabbyamp

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