From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, core141, updated. 83165259b1db395e2bfecef0b584055583b7d99a
Date: Wed, 29 Jan 2020 12:55:02 +0000 [thread overview]
Message-ID: <4873Nl2FGtz30hP@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1633 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, core141 has been updated
via 83165259b1db395e2bfecef0b584055583b7d99a (commit)
from e2338aa7ef6936044b6782fdbdd6abc12738395c (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 83165259b1db395e2bfecef0b584055583b7d99a
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Wed Jan 29 12:54:00 2020 +0000
core141: run pakfire update after db cleanup
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/141/update.sh | 4 ++++
1 file changed, 4 insertions(+)
Difference in files:
diff --git a/config/rootfiles/core/141/update.sh b/config/rootfiles/core/141/update.sh
index d990b44b7..51fe6ad9c 100644
--- a/config/rootfiles/core/141/update.sh
+++ b/config/rootfiles/core/141/update.sh
@@ -92,6 +92,10 @@ rm -fv /opt/pakfire/db/*/meta-elinks
rm -fv /opt/pakfire/db/rootfiles/python3
rm -fv /opt/pakfire/db/*/meta-python3
+# run pakfire update twice (first sometimes fail)
+/usr/local/bin/pakfire update
+/usr/local/bin/pakfire update
+
# Finish
/etc/init.d/fireinfo start
sendprofile
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2020-01-29 12:55 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=4873Nl2FGtz30hP@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