Github messages for voidlinux
 help / color / mirror / Atom feed
From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] openvswitch: update to 2.14.2.
Date: Thu, 11 Feb 2021 04:28:03 +0100	[thread overview]
Message-ID: <20210211032803.MIFmlDC90AT0Pu3I0cpinyZr87BLbQqoQoVIlCnslIA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28652@inbox.vuxu.org>

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

There is an updated pull request by ericonr against master on the void-packages repository

https://github.com/ericonr/void-packages vswi
https://github.com/void-linux/void-packages/pull/28652

openvswitch: update to 2.14.2.
Fixes CVE-2020-35498.

@renatoaguiar 

<!-- 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?
- [ ] 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? 
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] 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/28652.patch is attached

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

From af264930bd22cd7a5ad07f6281c375b8a8f088aa Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=89rico=20Rolim?= <erico.erc@gmail.com>
Date: Wed, 10 Feb 2021 15:10:08 -0300
Subject: [PATCH] openvswitch: update to 2.14.2.

Fixes CVE-2020-35498.
---
 srcpkgs/openvswitch/template | 11 +++++++++--
 1 file changed, 9 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/openvswitch/template b/srcpkgs/openvswitch/template
index 0231037bb4f..65f816ea9a2 100644
--- a/srcpkgs/openvswitch/template
+++ b/srcpkgs/openvswitch/template
@@ -1,6 +1,6 @@
 # Template file for 'openvswitch'
 pkgname=openvswitch
-version=2.14.0
+version=2.14.2
 revision=1
 archs="i686* x86_64* ppc64*"
 build_style=gnu-configure
@@ -14,11 +14,18 @@ maintainer="Renato Aguiar <renato@renatoaguiar.net>"
 license="Apache-2.0"
 homepage="http://openvswitch.org/"
 distfiles="http://openvswitch.org/releases/${pkgname}-${version}.tar.gz"
-checksum=4171e52a8c0ffe160c1daa6687219d902a2a6969b296d223d8dac980ab99a260
+checksum=65f420f954e250d895fb2db22a132e1cb560bc5e2b9051e834511348108e597a
 python_version=3
 _completiondir="/usr/share/bash-completion/completions"
 make_install_args+=" completiondir=${_completiondir}"
 
+do_check() {
+	if [ "$XBPS_CHECK_PKGS" = full ]; then
+		# test can hang in containers
+		make check ${makejobs}
+	fi
+}
+
 post_install() {
 	for cmd in ovs-appctl ovs-vsctl; do
 		chmod 0644 ${DESTDIR}${_completiondir}/$cmd-bashcomp.bash

  reply	other threads:[~2021-02-11  3:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-10 21:27 [PR PATCH] " ericonr
2021-02-11  3:28 ` ericonr [this message]
2021-02-11  3:50 ` [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=20210211032803.MIFmlDC90AT0Pu3I0cpinyZr87BLbQqoQoVIlCnslIA@z \
    --to=ericonr@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).