From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [PR PATCH] frr: update to 7.2.1.
Date: Tue, 28 Jan 2020 06:29:36 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18601@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 320 bytes --]
There is a new pull request by CameronNemo against master on the void-packages repository
https://github.com/CameronNemo/void-packages frr-7.2.1
https://github.com/void-linux/void-packages/pull/18601
frr: update to 7.2.1.
None
A patch file from https://github.com/void-linux/void-packages/pull/18601.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-frr-7.2.1-18601.patch --]
[-- Type: text/x-diff, Size: 1407 bytes --]
From 6d6a4ce04978f57e692f1607071a5558c5ceb4fd Mon Sep 17 00:00:00 2001
From: Cameron Nemo <cnemo@tutanota.com>
Date: Mon, 27 Jan 2020 21:28:21 -0800
Subject: [PATCH] frr: update to 7.2.1.
---
srcpkgs/frr/template | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/frr/template b/srcpkgs/frr/template
index f99872fb1e2..601ce5230b8 100644
--- a/srcpkgs/frr/template
+++ b/srcpkgs/frr/template
@@ -1,7 +1,7 @@
# Template file for 'frr'
pkgname=frr
-version=7.1
-revision=3
+version=7.2.1
+revision=1
wrksrc="${pkgname}-${pkgname}-${version}"
build_style=gnu-configure
# chroot-texinfo is not able to build frr's docs
@@ -17,11 +17,11 @@ hostmakedepends="pkg-config flex bison autoconf automake libtool
makedepends="pcre-devel libcap-devel json-c-devel pam-devel c-ares-devel
readline-devel python-devel python3-devel libyang-devel"
short_desc="IP routing protocol suite"
-maintainer="Cameron Nemo <camerontnorman@gmail.com>"
+maintainer="Cameron Nemo <cnemo@tutanota.com>"
license="GPL-2.0-or-later, LGPL-2.1-or-later"
homepage="https://frrouting.org"
distfiles="https://github.com/FRRouting/frr/archive/${pkgname}-${version}.tar.gz"
-checksum=1a66ab4fdb9718997170e9da79d52e5bfdaabc0dac396e4beb758af7bdd48e4f
+checksum=40fea6ff007453e27761a0372cde51fd8279f89984dff009092eebe2a7b29be3
nocross="http://ix.io/1rQ6"
system_groups="_frrvty"
system_accounts="_frr"
next reply other threads:[~2020-01-28 5:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 5:29 voidlinux-github [this message]
2020-01-28 14:51 ` [PR PATCH] [Merged]: " voidlinux-github
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-18601@inbox.vuxu.org \
--to=voidlinux-github@inbox.vuxu.org \
--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).