From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 5555c4b887ce05f24a05e3c95ed22f32abebeb52
Date: Thu, 09 Jul 2015 20:54:32 +0200 [thread overview]
Message-ID: <20150709185433.0320E2239D@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1774 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 5555c4b887ce05f24a05e3c95ed22f32abebeb52 (commit)
from c972b1c467ee3babf60fab4e1b23f72cc7eade74 (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 5555c4b887ce05f24a05e3c95ed22f32abebeb52
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Thu Jul 9 20:53:33 2015 +0200
pakfire: Fix installing dependencies when updating packages
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
src/pakfire/pakfire | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
Difference in files:
diff --git a/src/pakfire/pakfire b/src/pakfire/pakfire
index 8bca061..da68454 100644
--- a/src/pakfire/pakfire
+++ b/src/pakfire/pakfire
@@ -255,10 +255,11 @@
} elsif ("$ARGV[0]" eq "upgrade") {
&Pakfire::upgradecore();
my @upgradepaks = &Pakfire::dblist("upgrade", "noweb");
+ my @deps = ();
if (@upgradepaks) {
# Resolve the dependencies of the to be upgraded packages
- my @deps = &Pakfire::resolvedeps_recursive(@upgradepaks);
+ @deps = &Pakfire::resolvedeps_recursive(@upgradepaks);
&Pakfire::message("");
&Pakfire::message("PAKFIRE UPGR: We are going to install all packages listed above.");
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2015-07-09 18:54 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=20150709185433.0320E2239D@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