Github messages for voidlinux
 help / color / mirror / Atom feed
From: the-maldridge <the-maldridge@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] lurch: revert patch from #26757
Date: Mon, 30 Nov 2020 22:28:00 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26843@inbox.vuxu.org> (raw)

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

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

https://github.com/the-maldridge/void-packages revert-26757
https://github.com/void-linux/void-packages/pull/26843

lurch: revert patch from #26757
The patch was erroneously applied after a github user claimed it to be
a security issue, and later it was determined that this user was going
around tricking various projects into applying their patch that had
been exlicitly declined by upstream (xsf/xeps#894).

There's probably a dialog to happen here around relative security of
accepting unverified patches in the name of 'security' but this is
neither the time nor the place.

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

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

From f1b0c673cf88c1ca68f82028c0f69b9d21549f11 Mon Sep 17 00:00:00 2001
From: Michael Aldridge <maldridge@VoidLinux.org>
Date: Mon, 30 Nov 2020 13:21:58 -0800
Subject: [PATCH] lurch: revert patch from #26757

The patch was erroneously applied after a github user claimed it to be
a security issue, and later it was determined that this user was going
around tricking various projects into applying their patch that had
been exlicitly declined by upstream (xsf/xeps#894).

There's probably a dialog to happen here around relative security of
accepting unverified patches in the name of 'security' but this is
neither the time nor the place.
---
 srcpkgs/lurch/template | 6 +-----
 1 file changed, 1 insertion(+), 5 deletions(-)

diff --git a/srcpkgs/lurch/template b/srcpkgs/lurch/template
index b5f1bd3e4d2..207c49d3ec5 100644
--- a/srcpkgs/lurch/template
+++ b/srcpkgs/lurch/template
@@ -1,7 +1,7 @@
 # Template file for 'lurch'
 pkgname=lurch
 version=0.6.8
-revision=3
+revision=4
 build_style=gnu-makefile
 make_use_env=yes
 hostmakedepends="cmake pkg-config"
@@ -14,7 +14,3 @@ distfiles="https://github.com/gkdr/lurch/releases/download/v${version}/lurch-${v
 checksum=2e2447b5fe6b1ae4f08d8c79a2a846c70290685d6e338bf5ea8f59705bd2b19f
 
 LDFLAGS="-L${XBPS_CROSS_BASE}/usr/lib/purple-2"
-
-post_patch() {
-	vsed -e '/#define OMEMO_AES_GCM_IV_LENGTH/s/16/12/' -i lib/libomemo/src/libomemo.h
-}

             reply	other threads:[~2020-11-30 21:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-30 21:28 the-maldridge [this message]
2020-11-30 21:43 ` Vaelatern
2020-12-01  2:20 ` [PR PATCH] [Merged]: " the-maldridge

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-26843@inbox.vuxu.org \
    --to=the-maldridge@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).