Github messages for voidlinux
 help / color / mirror / Atom feed
From: TeddyDD <TeddyDD@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] delve: update to 1.8.0.
Date: Sat, 01 Jan 2022 17:37:24 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34799@inbox.vuxu.org> (raw)

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

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

https://github.com/TeddyDD/void-packages-1 update-delve
https://github.com/void-linux/void-packages/pull/34799

delve: update to 1.8.0.
<!-- Uncomment relevant sections and delete options which are not applicable -->

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

<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](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, (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/34799.patch is attached

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

From 3d193b3a2a2adfc9356f87ae098fb5ac32221760 Mon Sep 17 00:00:00 2001
From: Daniel Lewan <vision360.daniel@gmail.com>
Date: Sat, 1 Jan 2022 17:36:43 +0100
Subject: [PATCH] delve: update to 1.8.0.

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

diff --git a/srcpkgs/delve/template b/srcpkgs/delve/template
index 43e09ec913c0..893a95ecfc75 100644
--- a/srcpkgs/delve/template
+++ b/srcpkgs/delve/template
@@ -1,6 +1,6 @@
 # Template file for 'delve'
 pkgname=delve
-version=1.7.1
+version=1.8.0
 revision=1
 build_style=go
 go_import_path=github.com/go-delve/delve/cmd/dlv
@@ -9,7 +9,7 @@ maintainer="Renato Aguiar <renato@renatoaguiar.net>"
 license="MIT"
 homepage="https://github.com/go-delve/delve"
 distfiles="https://github.com/go-delve/delve/archive/v${version}.tar.gz"
-checksum=0734b86d48291749ba2537fa6c03e4c3451628f630055c877789e0346db8d67d
+checksum=086106a4776fa155bf20c37d27b9caed55255be6359c7f0bda1893d3adbb614e
 
 case "$XBPS_TARGET_MACHINE" in
 	i686*|arm*|ppc*) broken=yes ;;

             reply	other threads:[~2022-01-01 16:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-01 16:37 TeddyDD [this message]
2022-01-01 17:00 ` [PR REVIEW] " paper42
2022-01-01 17:00 ` paper42
2022-01-01 17:01 ` [PR PATCH] [Updated] " TeddyDD
2022-01-01 17:01 ` [PR REVIEW] " TeddyDD
2022-01-01 17:07 ` [PR PATCH] [Updated] " TeddyDD
2022-01-01 17:15 ` [PR PATCH] [Merged]: " paper42

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