From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. f7879935a58e1420f632c64b98b21b08d6f8b046
Date: Tue, 06 Aug 2024 14:18:11 +0000 [thread overview]
Message-ID: <4Wdb4h1CsRz2xs0@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2921 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 f7879935a58e1420f632c64b98b21b08d6f8b046 (commit)
via 07358a9fc5ef0cb9ae7e386158bac5d5a21340ec (commit)
from cf6ab4e56944fcc39f707d87af411270bccc9dae (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 f7879935a58e1420f632c64b98b21b08d6f8b046
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Tue Aug 6 14:17:39 2024 +0000
core-updates: Fix release number
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
commit 07358a9fc5ef0cb9ae7e386158bac5d5a21340ec
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Tue Aug 6 14:11:04 2024 +0000
make.sh: Grant network access when downloading packages
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/core-updates | 6 +++---
make.sh | 6 +++---
2 files changed, 6 insertions(+), 6 deletions(-)
Difference in files:
diff --git a/lfs/core-updates b/lfs/core-updates
index e56ada70c..a6478b5e0 100644
--- a/lfs/core-updates
+++ b/lfs/core-updates
@@ -27,11 +27,11 @@ include Config
THISAPP = core-updates
TARGET = $(DIR_INFO)/$(THISAPP)
-PROG = core-upgrade
+PROG = core-upgrade
VER = $(VERSION)
-RELEASE = $(CORE)
+PAK_VER = $(CORE)
-SUMMARY = IPFire Core Update $(CORE)
+SUMMARY = IPFire Core Update $(CORE)
###############################################################################
# Top-level Rules
diff --git a/make.sh b/make.sh
index 2f629d73d..3a3590305 100755
--- a/make.sh
+++ b/make.sh
@@ -915,7 +915,7 @@ lfsmake1() {
[ $? == 1 ] && return 0
# Download source outside of the toolchain
- if ! make_pkg "${pkg}" download "$@"; then
+ if ! make_pkg --network "${pkg}" download "$@"; then
exiterror "Downloading ${pkg}"
fi
@@ -937,7 +937,7 @@ lfsmake2() {
[ $? == 1 ] && return 0
# Download source outside of the toolchain
- if ! make_pkg "${pkg}" download "$@"; then
+ if ! make_pkg --network "${pkg}" download "$@"; then
exiterror "Downloading ${pkg}"
fi
@@ -1144,7 +1144,7 @@ download_sources() {
[ $? == 1 ] && continue
# Download and check the package
- if ! make_pkg "${pkg}" download b2; then
+ if ! make_pkg --network "${pkg}" download b2; then
failed_packages+=( "${pkg}" )
print_status FAIL
continue
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2024-08-06 14:18 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=4Wdb4h1CsRz2xs0@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