Github messages for voidlinux
 help / color / mirror / Atom feed
From: aurieh <aurieh@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] dub: update to 1.27.0
Date: Mon, 25 Oct 2021 02:56:42 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33737@inbox.vuxu.org> (raw)

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

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

https://github.com/aurieh/void-packages dub-1.27.0
https://github.com/void-linux/void-packages/pull/33737

dub: update to 1.27.0
<!-- 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? 
- [X] I built this PR locally for my native architecture, (x86_64-glibc)



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

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

From 14db4654ebdd27579573881dea31e93af16ac635 Mon Sep 17 00:00:00 2001
From: Auri <me@aurieh.me>
Date: Sun, 24 Oct 2021 04:05:47 +0300
Subject: [PATCH] dub: update to 1.27.0

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

diff --git a/srcpkgs/dub/template b/srcpkgs/dub/template
index c717ee5d0005..f80d21bb90a2 100644
--- a/srcpkgs/dub/template
+++ b/srcpkgs/dub/template
@@ -1,6 +1,6 @@
 # Template file for 'dub'
 pkgname=dub
-version=1.23.0
+version=1.27.0
 revision=1
 hostmakedepends="dmd dtools"
 makedepends="libcurl-devel"
@@ -10,7 +10,7 @@ maintainer="Follpvosten <wolfi@karpador.xyz>"
 license="MIT"
 homepage="https://github.com/dlang/dub"
 distfiles="${homepage}/archive/v${version}.tar.gz"
-checksum=9c7196fd76efce50e8606b3f0ab103bb8b3984842dcc7c0970eb07aba63dbaa5
+checksum=fb800f3355f167ac7f997f77e31e331db9d33477779fdaaf2851b3abcecc801a
 nocross="requires dmd"
 
 do_build() {

             reply	other threads:[~2021-10-25  0:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-25  0:56 aurieh [this message]
2021-10-25  0:59 ` [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-33737@inbox.vuxu.org \
    --to=aurieh@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).