Github messages for voidlinux
 help / color / mirror / Atom feed
From: make-file <make-file@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] enlightenment: update to 0.24.2
Date: Sat, 26 Dec 2020 12:13:19 +0100	[thread overview]
Message-ID: <20201226111319.qEWFtz6uj5N48aVWVxc3z2zSZbm5YljI-6XoOwRLWpQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27330@inbox.vuxu.org>

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

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

https://github.com/make-file/void-packages E
https://github.com/void-linux/void-packages/pull/27330

enlightenment: update to 0.24.2
since `signal.h` is included  into `e_util_suid.h` so it would be safe to remove patch

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

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

From bc8ac85cac388a6a74f3ac94f1a007adb3f48100 Mon Sep 17 00:00:00 2001
From: make-file <makefile@riseup.net>
Date: Sat, 26 Dec 2020 14:39:05 +0330
Subject: [PATCH] enlightenment: updated to 0.24.2

---
 srcpkgs/enlightenment/template | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/srcpkgs/enlightenment/template b/srcpkgs/enlightenment/template
index 9937e24f0f9..693996881ba 100644
--- a/srcpkgs/enlightenment/template
+++ b/srcpkgs/enlightenment/template
@@ -16,7 +16,7 @@ maintainer="q66 <daniel@octaforge.org>"
 license="BSD-2-Clause"
 homepage="http://enlightenment.org"
 distfiles="http://download.enlightenment.org/rel/apps/${pkgname}/${pkgname}-${version}.tar.xz"
-checksum=aee2b6178c918d71ebe661129f4008d773e70e5784651dadbcf56eec0a6d4a09
+checksum=be18e2f18d6c0b058f633e769863d3cbc4c07b629058ae670dec74cd7906dff1
 lib32disabled=yes
 build_options="wayland"
 build_options_default="wayland"

  parent reply	other threads:[~2020-12-26 11:13 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-21 20:09 [PR PATCH] " make-file
2020-12-22  0:16 ` ericonr
2020-12-22  7:30 ` [PR PATCH] [Updated] " make-file
2020-12-22  7:32 ` make-file
2020-12-22 11:05 ` q66
2020-12-22 11:41 ` make-file
2020-12-22 11:51 ` q66
2020-12-22 11:56 ` make-file
2020-12-22 12:03 ` q66
2020-12-22 12:22 ` [PR PATCH] [Updated] " make-file
2020-12-26  6:05 ` ericonr
2020-12-26 10:19 ` [PR PATCH] [Updated] " make-file
2020-12-26 10:20 ` make-file
2020-12-26 10:22 ` make-file
2020-12-26 10:55 ` [PR PATCH] [Updated] " make-file
2020-12-26 11:13 ` make-file [this message]
2020-12-26 11:20 ` make-file
2020-12-26 11:29 ` make-file
2020-12-26 11:29 ` make-file
2020-12-26 11:30 ` make-file
2020-12-26 11:31 ` make-file
2020-12-26 12:51 ` Anachron
2020-12-26 14:09 ` [PR PATCH] [Updated] " make-file
2020-12-26 14:23 ` make-file
2020-12-26 19:10 ` ericonr
2020-12-26 19:14 ` ericonr
2020-12-26 19:29 ` ericonr
2020-12-26 19:35 ` ericonr
2020-12-26 19:36 ` [PR PATCH] [Merged]: " ericonr
2020-12-27  5:51 ` make-file
  -- strict thread matches above, loose matches on Subject: below --
2020-12-21  9:24 [PR PATCH] " make-file
2020-12-21 16:42 ` [PR PATCH] [Updated] " make-file
2020-12-21 17:04 ` make-file
2020-12-21 17:26 ` make-file
2020-12-21 17:29 ` make-file

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=20201226111319.qEWFtz6uj5N48aVWVxc3z2zSZbm5YljI-6XoOwRLWpQ@z \
    --to=make-file@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).