Github messages for voidlinux
 help / color / mirror / Atom feed
From: tuxliban <tuxliban@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] file: update to 5.41
Date: Tue, 26 Oct 2021 06:14:28 +0200	[thread overview]
Message-ID: <20211026041428.YQClg5zJCnlGNnicpt5HWqOjrPzhrXrTtVu6laceDxQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33631@inbox.vuxu.org>

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

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

https://github.com/tuxliban/void-packages file
https://github.com/void-linux/void-packages/pull/33631

file: update to 5.41
<!-- 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?
- [x] 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/33631.patch is attached

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

From e053d03852c57f66af4304816ed2946dc0bbf150 Mon Sep 17 00:00:00 2001
From: Tuxliban Torvalds <tenshalito@gmail.com>
Date: Tue, 19 Oct 2021 00:15:59 -0500
Subject: [PATCH] file: update to 5.41

---
 srcpkgs/file/template | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/srcpkgs/file/template b/srcpkgs/file/template
index a3213b20ecc4..a7e080f143ba 100644
--- a/srcpkgs/file/template
+++ b/srcpkgs/file/template
@@ -1,7 +1,7 @@
 # Template file for 'file'
 pkgname=file
-version=5.40
-revision=3
+version=5.41
+revision=1
 bootstrap=yes
 build_style=gnu-configure
 configure_args="--enable-static $(vopt_enable libseccomp)"
@@ -9,9 +9,9 @@ makedepends="zlib-devel $(vopt_if libseccomp libseccomp-devel)"
 short_desc="File type identification utility"
 maintainer="Enno Boland <gottox@voidlinux.org>"
 license="BSD-2-Clause"
-homepage="http://www.darwinsys.com/file/"
+homepage="https://www.darwinsys.com/file/"
 distfiles="https://astron.com/pub/file/file-${version}.tar.gz"
-checksum=167321f43c148a553f68a0ea7f579821ef3b11c27b8cbe158e4df897e4a5dd57
+checksum=13e532c7b364f7d57e23dfeea3147103150cb90593a57af86c10e4f6e411603f
 
 build_options="libseccomp"
 

  parent reply	other threads:[~2021-10-26  4:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-19  5:17 [PR PATCH] " tuxliban
2021-10-24 20:48 ` [PR REVIEW] " ericonr
2021-10-26  4:14 ` tuxliban [this message]
2021-10-26  4:19 ` tuxliban
2021-10-28  8:17 ` [PR PATCH] [Updated] " tuxliban
2021-10-29  3:51 ` zdykstra
2021-10-29  4:05 ` [PR PATCH] [Closed]: " ericonr
2021-10-29  4:06 ` 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=20211026041428.YQClg5zJCnlGNnicpt5HWqOjrPzhrXrTtVu6laceDxQ@z \
    --to=tuxliban@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).