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 3.x development tree branch, master, updated. d1f2440ebd596662437a91e6d41c32497fc500c6
Date: Thu, 21 Feb 2013 23:22:37 +0100	[thread overview]
Message-ID: <20130221222238.6BB29200C2@argus.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2921 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 3.x development tree".

The branch, master has been updated
       via  d1f2440ebd596662437a91e6d41c32497fc500c6 (commit)
       via  04128d8c4d72ef18665ffb3426b1d75e658dc24b (commit)
       via  fe9ae6765111d376d46889989dbab24352124339 (commit)
      from  f9c2b4ea5bdf38660598e5671fc24fed2ad159b3 (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 d1f2440ebd596662437a91e6d41c32497fc500c6
Merge: 04128d8 fe9ae67
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date:   Thu Feb 21 23:22:29 2013 +0100

    Merge remote-tracking branch 'stevee/krb5-update'

commit 04128d8c4d72ef18665ffb3426b1d75e658dc24b
Author: Stefan Schantl <stefan.schantl(a)ipfire.org>
Date:   Thu Feb 21 19:56:43 2013 +0100

    icu: libicu-devel also should provide icu-devel.

commit fe9ae6765111d376d46889989dbab24352124339
Author: Stefan Schantl <stefan.schantl(a)ipfire.org>
Date:   Thu Feb 14 19:50:47 2013 +0100

    krb5: Update to 1.10.3.
    
    Bugfix release of the 1.10 series.
    
    * Use devel packages of libcom_err and libss which have been seperated from e2fsprogs.

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

Summary of changes:
 icu/icu.nm   | 6 +++++-
 krb5/krb5.nm | 6 ++++--
 2 files changed, 9 insertions(+), 3 deletions(-)

Difference in files:
diff --git a/icu/icu.nm b/icu/icu.nm
index b40cbf0..116ed14 100644
--- a/icu/icu.nm
+++ b/icu/icu.nm
@@ -8,7 +8,7 @@ version    = %{ver_major}.%{ver_minor}.%{ver_plevel}
 ver_major  = 50
 ver_minor  = 1
 ver_plevel = 2
-release    = 2
+release    = 3
 
 groups     = Development/Tools
 url        = http://www.icu-project.org
@@ -59,6 +59,10 @@ packages
 	package lib%{name}-devel
 		template DEVEL
 
+		provides
+			icu-devel = %{thisver}
+		end
+
 		files += \
 			%{bindir}/*config* \
 			%{bindir}/icuinfo \
diff --git a/krb5/krb5.nm b/krb5/krb5.nm
index a80872d..6496ded 100644
--- a/krb5/krb5.nm
+++ b/krb5/krb5.nm
@@ -6,7 +6,7 @@
 name       = krb5
 version    = %{version_maj}.%{version_min}
 version_maj= 1.10
-version_min= 2
+version_min= 3
 release    = 1
 
 groups     = System/Libraries
@@ -57,10 +57,11 @@ build
 		automake
 		bison
 		dejagnu
-		e2fsprogs-devel
 		flex
 		gettext
+		libcom_err-devel
 		libselinux-devel
+		libss-devel
 		ncurses-devel
 		openldap-devel
 		openssl-devel
@@ -235,6 +236,7 @@ packages
 		template DEVEL
 
 		requires
+			libcom_err-devel
 			libselinux-devel
 		end
 	end


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

                 reply	other threads:[~2013-02-21 22:22 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=20130221222238.6BB29200C2@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