From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. 932cee06f17fd900f21582ff652ffc9ec89d06f0
Date: Mon, 27 Jan 2020 19:05:37 +0000 [thread overview]
Message-ID: <485zjF6H70z2yGt@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1888 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, master has been updated
via 932cee06f17fd900f21582ff652ffc9ec89d06f0 (commit)
from 3195d17490e041cca7196858c6c0823fc09c55b5 (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 932cee06f17fd900f21582ff652ffc9ec89d06f0
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Mon Jan 27 17:56:51 2020 +0000
core141: manually delete pakfire lists
pakfire update --force
fail sometimes fail and use the old version of the serverlist
and get the old addon list. With removed list it cannot
use the wrong addonlist after update to IPFire 2.25.
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/141/update.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/config/rootfiles/core/141/update.sh b/config/rootfiles/core/141/update.sh
index f249152f1..d990b44b7 100644
--- a/config/rootfiles/core/141/update.sh
+++ b/config/rootfiles/core/141/update.sh
@@ -83,8 +83,8 @@ telinit u
# This update needs a reboot...
touch /var/run/need_reboot
-# Force update the package lists
-/usr/local/bin/pakfire update --force
+# Force pakfire to redownload lists
+rm -f /opt/pakfire/db/lists/*.db
# Let pakfire forget the elinks and python3 package
rm -fv /opt/pakfire/db/rootfiles/elinks
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2020-01-27 19:05 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=485zjF6H70z2yGt@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