From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. fe3a05da3a794e3025fde4b39775876835ad735a
Date: Fri, 26 Oct 2012 15:37:49 +0200 [thread overview]
Message-ID: <20121026133749.7FD3E200AE@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1792 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 fe3a05da3a794e3025fde4b39775876835ad735a (commit)
from 03207e65b1244bb4a82a55bc1e1f893e05695aa0 (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 fe3a05da3a794e3025fde4b39775876835ad735a
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Fri Oct 26 15:36:48 2012 +0200
pakfire: compression detection needs an extension.
-----------------------------------------------------------------------
Summary of changes:
src/pakfire/lib/functions.sh | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/src/pakfire/lib/functions.sh b/src/pakfire/lib/functions.sh
index 9c8bf53..3f7dbff 100644
--- a/src/pakfire/lib/functions.sh
+++ b/src/pakfire/lib/functions.sh
@@ -24,13 +24,13 @@
extract_files() {
echo "Extracting files..."
- tar xavf /opt/pakfire/tmp/files --no-overwrite-dir -p --numeric-owner -C /
+ tar xavf /opt/pakfire/tmp/files* --no-overwrite-dir -p --numeric-owner -C /
echo "...Finished."
}
extract_backup_includes() {
echo "Extracting backup includes..."
- tar xavf /opt/pakfire/tmp/files --no-overwrite-dir -p --numeric-owner -C / \
+ tar xavf /opt/pakfire/tmp/files* --no-overwrite-dir -p --numeric-owner -C / \
var/ipfire/backup/addons/includes
echo "...Finished."
}
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2012-10-26 13:37 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=20121026133749.7FD3E200AE@argus.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