From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 702b59cd028018d0002d90f0ed9afbfa2248ed6a
Date: Thu, 02 Apr 2020 16:30:23 +0000 [thread overview]
Message-ID: <48tT7h0WsLz2y4j@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1680 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, next has been updated
via 702b59cd028018d0002d90f0ed9afbfa2248ed6a (commit)
from 0b0a3634cdb241335f629e3173b607c3f4c3f304 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 702b59cd028018d0002d90f0ed9afbfa2248ed6a
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Thu Apr 2 16:28:39 2020 +0000
paks: fix meta size entry
remove the doublequotes around the size because pakfire not
accept this.
fixes: #12348
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/Config | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/lfs/Config b/lfs/Config
index faf01ca1a..a278b0155 100644
--- a/lfs/Config
+++ b/lfs/Config
@@ -283,7 +283,7 @@ define PAK
-e "s/VER/$(VER)/g" \
-e "s/RELEASE/$(PAK_VER)/g" \
-e "s/DEPS/$(DEPS)/g" \
- -e "s/SIZE/$$(stat --format=\"%s\" /install/packages/$(PROG)-$(VER)-$(PAK_VER).ipfire)/g" \
+ -e "s/SIZE/$$(stat --format=%s /install/packages/$(PROG)-$(VER)-$(PAK_VER).ipfire)/g" \
< /usr/src/src/pakfire/meta > /install/packages/meta-$(PROG)
endef
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2020-04-02 16:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=48tT7h0WsLz2y4j@people01.haj.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@lists.ipfire.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