From: anjandev <anjandev@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] Manual: added link to xtools' xbump
Date: Fri, 17 Apr 2020 23:07:18 +0200 [thread overview]
Message-ID: <20200417210718.YVb056J70375OXmkt50ONzmM4JHnhhnBFPi7hKe9gl4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21087@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 326 bytes --]
There is an updated pull request by anjandev against master on the void-packages repository
https://github.com/anjandev/void-packages manual
https://github.com/void-linux/void-packages/pull/21087
Manual: added link to xtools' xbump
A patch file from https://github.com/void-linux/void-packages/pull/21087.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-manual-21087.patch --]
[-- Type: text/x-diff, Size: 3700 bytes --]
From 208ebf51080ea70d5117dd761bfe504320e59040 Mon Sep 17 00:00:00 2001
From: Anjandev Momi <anjan@momi.ca>
Date: Fri, 17 Apr 2020 10:40:07 -0700
Subject: [PATCH] Manual: Removed redundant contributing explanation and linked
instead
---
Manual.md | 26 +-------------------------
srcpkgs/gnome-authenticator/template | 22 +++++++++++-----------
2 files changed, 12 insertions(+), 36 deletions(-)
diff --git a/Manual.md b/Manual.md
index 92b57b1b2c2..c2508a4b8bf 100644
--- a/Manual.md
+++ b/Manual.md
@@ -1958,31 +1958,7 @@ otherwise the `debug` packages won't have debugging symbols.
<a id="contributing"></a>
### Contributing via git
-Fork the voidlinux `void-packages` git repository on github and clone it:
-
- $ git clone git@github.com:<user>/void-packages.git
-
-You can now make your own commits to the `forked` repository:
-
- $ git add ...
- $ git commit ...
- $ git push ...
-
-To keep your forked repository always up to date, setup the `upstream` remote
-to pull in new changes:
-
- $ git remote add upstream git://github.com/void-linux/void-packages.git
- $ git pull upstream master
-
-Once you've made changes to your `forked` repository you can submit
-a github pull request; see https://help.github.com/articles/fork-a-repo for more information.
-
-For commit messages please use the following rules:
-
-- If you've imported a new package use `"New package: <pkgname>-<version>"`.
-- If you've updated a package use `"<pkgname>: update to <version>."`.
-- If you've removed a package use `"<pkgname>: removed ..."`.
-- If you've modified a package use `"<pkgname>: ..."`.
+For information about contributing see [CONTRIBUTING.md](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md).
<a id="help"></a>
## Help
diff --git a/srcpkgs/gnome-authenticator/template b/srcpkgs/gnome-authenticator/template
index b91f05ebea2..a62d5aed8c9 100644
--- a/srcpkgs/gnome-authenticator/template
+++ b/srcpkgs/gnome-authenticator/template
@@ -1,24 +1,24 @@
# Template file for 'gnome-authenticator'
pkgname=gnome-authenticator
-version=0.2.4
-revision=3
+version=3.32.2
+revision=1
_libgd_hash=7ae254bfc5f641c60566614e08245176f7bc5aa8
wrksrc="Authenticator-${version}"
build_style=meson
build_helper="gir"
pycompile_module="Authenticator"
-hostmakedepends="appstream-glib desktop-file-utils git glib-devel pkg-config"
-makedepends="gobject-introspection gtk+3-devel libglib-devel python3"
+hostmakedepends="appstream-glib desktop-file-utils git glib-devel pkg-config cmake"
+makedepends="gobject-introspection gtk+3-devel libglib-devel python3 libsecret-devel python3-pyzbar"
depends="python3-pyzbar python3-Pillow python3-pyotp"
short_desc="Two-factor authentication code generator for GNOME"
maintainer="Enno Boland <gottox@voidlinux.org>"
license="GPL-2.0-or-later"
homepage="https://gitlab.gnome.org/World/Authenticator"
-distfiles="${homepage}/-/archive/${version}/Authenticator-${version}.tar.gz
- https://gitlab.gnome.org/GNOME/libgd/-/archive/${_libgd_hash}/libgd-${_libgd_hash}.tar.bz2"
-checksum="5757ab4f097b6ed5855224d06ec5d6cd4c9748cc42733f32d425ca2b2325903a
- 2bf6cd82b48f62d2725d7c52a77cc091958877e1cff5af303bdd9a7d364da00a"
+distfiles="${homepage}/-/archive/${version}/Authenticator-${version}.tar.gz"
+ #https://gitlab.gnome.org/GNOME/libgd/-/archive/${_libgd_hash}/libgd-${_libgd_hash}.tar.bz2"
+checksum="d7250fbef1de2dcb599a55ff3d40dcc6ed5618fe89d50ec795281d8ba3123d5b"
+ # 2bf6cd82b48f62d2725d7c52a77cc091958877e1cff5af303bdd9a7d364da00a"
-pre_configure() {
- mv ../libgd-${_libgd_hash}/* subprojects/libgd
-}
+# pre_configure() {
+# mv ../libgd-${_libgd_hash}/* subprojects/libgd
+# }
next prev parent reply other threads:[~2020-04-17 21:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 17:44 [PR PATCH] " anjandev
2020-04-17 19:39 ` Chocimier
2020-04-17 21:07 ` anjandev [this message]
2020-04-17 21:08 ` anjandev
2020-04-17 21:28 ` Chocimier
2020-04-17 22:05 ` [PR PATCH] [Updated] " anjandev
2020-04-19 1:11 ` anjandev
2020-04-19 1:15 ` anjandev
2020-04-19 1:16 ` anjandev
2020-04-19 1:18 ` anjandev
2020-04-19 1:18 ` anjandev
2020-04-19 1:19 ` [PR PATCH] [Updated] " anjandev
2020-04-20 18:43 ` Chocimier
2020-04-20 18:43 ` [PR PATCH] [Closed]: " Chocimier
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=20200417210718.YVb056J70375OXmkt50ONzmM4JHnhhnBFPi7hKe9gl4@z \
--to=anjandev@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).