From: fnogcps <fnogcps@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] composer: update to 2.2.4.
Date: Thu, 20 Jan 2022 14:53:02 +0100 [thread overview]
Message-ID: <20220120135302.HGwe3GckIZcS_KxZGfEboQShjAf-q_zm20qeEzMFZtw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34999@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 385 bytes --]
There is an updated pull request by fnogcps against master on the void-packages repository
https://github.com/fnogcps/void-packages composer
https://github.com/void-linux/void-packages/pull/34999
composer: update to 2.2.4.
#### Testing the changes
- I tested the changes in this PR: **YES**
A patch file from https://github.com/void-linux/void-packages/pull/34999.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-composer-34999.patch --]
[-- Type: text/x-diff, Size: 1323 bytes --]
From 6d2eb28d5b3e8226fc8375e08405a0bb46b21bc9 Mon Sep 17 00:00:00 2001
From: Felipe Nogueira <contato.fnog@gmail.com>
Date: Wed, 19 Jan 2022 22:29:17 -0300
Subject: [PATCH] composer: update to 2.2.4.
---
srcpkgs/composer/template | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/composer/template b/srcpkgs/composer/template
index 43de0a369029..81da2bf03aa2 100644
--- a/srcpkgs/composer/template
+++ b/srcpkgs/composer/template
@@ -1,6 +1,6 @@
# Template file for 'composer'
pkgname=composer
-version=2.0.12
+version=2.2.4
revision=1
build_style=fetch
depends="php"
@@ -8,9 +8,10 @@ short_desc="Dependency manager for PHP"
maintainer="Felipe Nogueira <contato.fnog@gmail.com>"
license="MIT"
homepage="https://getcomposer.org/"
+changelog="https://raw.githubusercontent.com/composer/composer/main/CHANGELOG.md"
distfiles="https://github.com/composer/composer/releases/download/${version}/composer.phar
- https://raw.githubusercontent.com/composer/composer/master/LICENSE"
-checksum="82ea8c1537cfaceb7e56f6004c7ccdf99ddafce7237c07374d920e635730a631
+ https://raw.githubusercontent.com/composer/composer/main/LICENSE"
+checksum="ba04e246960d193237d5ed6542bd78456898e7787fafb586f500c6807af7458d
7855ac293067aebe7e51afdd23b9dea54b8be24187dbecc9b9142581c37f596c"
do_install() {
next prev parent reply other threads:[~2022-01-20 13:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 17:22 [PR PATCH] " fnogcps
2022-01-20 1:15 ` [PR REVIEW] " paper42
2022-01-20 1:29 ` [PR PATCH] [Updated] " fnogcps
2022-01-20 9:45 ` paper42
2022-01-20 13:35 ` [PR PATCH] [Updated] " fnogcps
2022-01-20 13:49 ` fnogcps
2022-01-20 13:53 ` fnogcps [this message]
2022-01-20 17:27 ` [PR PATCH] [Merged]: " paper42
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=20220120135302.HGwe3GckIZcS_KxZGfEboQShjAf-q_zm20qeEzMFZtw@z \
--to=fnogcps@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).