public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 031becc0e25503b7082675c7d30c00cdc2fa7a74
Date: Thu, 09 Jul 2015 21:02:30 +0200	[thread overview]
Message-ID: <20150709190230.83A482239D@argus.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1594 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  031becc0e25503b7082675c7d30c00cdc2fa7a74 (commit)
      from  5555c4b887ce05f24a05e3c95ed22f32abebeb52 (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 031becc0e25503b7082675c7d30c00cdc2fa7a74
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date:   Thu Jul 9 21:01:10 2015 +0200

    pakfire: Resolve dependencies for upgraded packages
    
    When updating more than one package, only new dependencies
    for the first one are resolved. The rest was ignored.
    
    This patch fixes that.
    
    Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>

-----------------------------------------------------------------------

Summary of changes:
 src/pakfire/lib/functions.pl | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Difference in files:
diff --git a/src/pakfire/lib/functions.pl b/src/pakfire/lib/functions.pl
index d2f77fa..96f8d14 100644
--- a/src/pakfire/lib/functions.pl
+++ b/src/pakfire/lib/functions.pl
@@ -591,7 +591,7 @@ sub resolvedeps {
 }
 
 sub resolvedeps_recursive {
-	my @packages = shift;
+	my @packages = @_;
 	my @result = ();
 
 	foreach my $pkg (@packages) {


hooks/post-receive
--
IPFire 2.x development tree

                 reply	other threads:[~2015-07-09 19:02 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=20150709190230.83A482239D@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