Github messages for voidlinux
 help / color / mirror / Atom feed
From: cinerea0 <cinerea0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] taplo: update to 0.9.0
Date: Fri, 02 Feb 2024 06:10:28 +0100	[thread overview]
Message-ID: <20240202051028.0BAB32562D@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48486@inbox.vuxu.org>

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

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

https://github.com/cinerea0/void-packages taplo
https://github.com/void-linux/void-packages/pull/48486

taplo: update to 0.9.0
#### Testing the changes
- I tested the changes in this PR: **YES**



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

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

From 6da4bc58c879e8cab45084d6f3df84af781ec5d9 Mon Sep 17 00:00:00 2001
From: cinerea0 <cinerea0@disroot.org>
Date: Fri, 2 Feb 2024 00:10:13 -0500
Subject: [PATCH] taplo: update to 0.9.0

---
 srcpkgs/taplo/patches/update-pprof.patch |  2 +-
 srcpkgs/taplo/template                   | 11 ++++++-----
 2 files changed, 7 insertions(+), 6 deletions(-)

diff --git a/srcpkgs/taplo/patches/update-pprof.patch b/srcpkgs/taplo/patches/update-pprof.patch
index f0abc5d6bb8ab..8a66c89d2f863 100644
--- a/srcpkgs/taplo/patches/update-pprof.patch
+++ b/srcpkgs/taplo/patches/update-pprof.patch
@@ -8,7 +8,7 @@ index 966ba1db30..7912352478 100644
  criterion = "0.3"
  difference = "2.0.0"
 -pprof = { version = "0.9.1", features = ["flamegraph", "criterion"] }
-+pprof = { version = "0.12.0", features = ["flamegraph", "criterion"] }
++pprof = { version = "0.13.0", features = ["flamegraph", "criterion"] }
  serde_json = "1"
  toml = "0.5"
  
diff --git a/srcpkgs/taplo/template b/srcpkgs/taplo/template
index ac172dc0367ff..91a98582bcd0b 100644
--- a/srcpkgs/taplo/template
+++ b/srcpkgs/taplo/template
@@ -1,7 +1,7 @@
 # Template file for 'taplo'
 pkgname=taplo
-version=0.8.1
-revision=2
+version=0.9.0
+revision=1
 build_style=cargo
 # no-default-features: allows selecting custom feature set
 # lsp: builds TOML language server
@@ -14,11 +14,12 @@ short_desc="TOML toolkit written in Rust"
 maintainer="cinerea0 <cinerea0@protonmail.com>"
 license="MIT"
 homepage="https://taplo.tamasfe.dev/"
-distfiles="https://github.com/tamasfe/taplo/archive/refs/tags/${version}.tar.gz"
-checksum=ec8dfdcfa33a6855803286413c0603140b21c06bc659ceab7e2ddc05baf1a8b3
+changelog="https://github.com/tamasfe/taplo/releases"
+distfiles="https://github.com/tamasfe/taplo/archive/refs/tags/release-taplo-cli-${version}.tar.gz"
+checksum=7d292f52c2d97d9e9c447a725d6d4e59096fce10e2f72ec6b80387034c20ba35
 
 post_patch() {
-	cargo update --package pprof@0.9.1 --precise 0.12.0
+	cargo update --package pprof@0.9.1 --precise 0.13.0
 }
 
 post_install() {

  reply	other threads:[~2024-02-02  5:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-02  2:27 [PR PATCH] " cinerea0
2024-02-02  5:10 ` cinerea0 [this message]
2024-02-02 21:07 ` [PR PATCH] [Merged]: " cinerea0

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=20240202051028.0BAB32562D@inbox.vuxu.org \
    --to=cinerea0@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).