From: tibequadorian <tibequadorian@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] ddgr: update to 2.0.
Date: Mon, 07 Mar 2022 13:32:02 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36019@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1214 bytes --]
There is a new pull request by tibequadorian against master on the void-packages repository
https://github.com/tibequadorian/void-packages ddgr
https://github.com/void-linux/void-packages/pull/36019
ddgr: update to 2.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/36019.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-ddgr-36019.patch --]
[-- Type: text/x-diff, Size: 1140 bytes --]
From f310368cb9a75495ab2e79325156b177e90e8bf0 Mon Sep 17 00:00:00 2001
From: tibequadorian <tibequadorian@posteo.de>
Date: Mon, 7 Mar 2022 13:30:23 +0100
Subject: [PATCH] ddgr: update to 2.0.
---
srcpkgs/ddgr/template | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/srcpkgs/ddgr/template b/srcpkgs/ddgr/template
index b53bfe8196b3..99e88022e36b 100644
--- a/srcpkgs/ddgr/template
+++ b/srcpkgs/ddgr/template
@@ -1,13 +1,13 @@
# Template file for 'ddgr'
pkgname=ddgr
-version=1.9
-revision=2
+version=2.0
+revision=1
build_style=gnu-makefile
-depends="python3-requests"
+depends="python3"
short_desc="DuckDuckGo from the terminal"
maintainer="Orphaned <orphan@voidlinux.org>"
license="GPL-3.0-or-later"
homepage="https://github.com/jarun/ddgr"
-changelog="https://github.com/jarun/ddgr/raw/master/CHANGELOG"
+changelog="https://raw.githubusercontent.com/jarun/ddgr/main/CHANGELOG"
distfiles="https://github.com/jarun/ddgr/archive/v${version}.tar.gz"
-checksum=3dfe82fab649f1cec904a1de63f78692be329a3b6928c1615f22c76f6e21c36f
+checksum=7e46430b0a8c479a5feca832adb73f2f09804bf603dedc50f4cf2e1da4c75f88
next reply other threads:[~2022-03-07 12:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 12:32 tibequadorian [this message]
2022-06-27 2:16 ` github-actions
2022-06-28 14:56 ` [PR PATCH] [Merged]: " Duncaen
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-36019@inbox.vuxu.org \
--to=tibequadorian@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).