From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH 2/2] krb5: Update to 1.19
Date: Fri, 05 Feb 2021 16:57:22 +0000 [thread overview]
Message-ID: <8F1F11E0-6EA1-4AA1-BD99-192FDB234168@ipfire.org> (raw)
In-Reply-To: <20210204161707.28292-2-matthias.fischer@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2304 bytes --]
Does this need the tcl version from this patchset or is it safe to merge this patch on its own?
-Michael
> On 4 Feb 2021, at 16:17, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>
> For details (complete list) see:
> https://web.mit.edu/kerberos/krb5-1.19/krb5-1.19.html
>
> Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
> ---
> config/rootfiles/packages/krb5 | 2 ++
> lfs/krb5 | 8 ++++----
> 2 files changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/config/rootfiles/packages/krb5 b/config/rootfiles/packages/krb5
> index 9a68f1b87..2e6e0285e 100644
> --- a/config/rootfiles/packages/krb5
> +++ b/config/rootfiles/packages/krb5
> @@ -171,3 +171,5 @@ usr/lib/libverto.so.0.0
> #usr/share/man/man8/krb5kdc.8
> #usr/share/man/man8/sserver.8
> var/lib/krb5kdc
> +#var/lib/run
> +#var/lib/run/krb5kdc
> diff --git a/lfs/krb5 b/lfs/krb5
> index 766dc8d05..c77e4fdfd 100644
> --- a/lfs/krb5
> +++ b/lfs/krb5
> @@ -1,7 +1,7 @@
> ###############################################################################
> # #
> # IPFire.org - A linux based firewall #
> -# Copyright (C) 2007-2020 IPFire Team <info(a)ipfire.org> #
> +# Copyright (C) 2007-2021 IPFire Team <info(a)ipfire.org> #
> # #
> # This program is free software: you can redistribute it and/or modify #
> # it under the terms of the GNU General Public License as published by #
> @@ -24,7 +24,7 @@
>
> include Config
>
> -VER = 1.18.3
> +VER = 1.19
>
> THISAPP = krb5-$(VER)
> DL_FILE = $(THISAPP).tar.gz
> @@ -32,7 +32,7 @@ DL_FROM = $(URL_IPFIRE)
> DIR_APP = $(DIR_SRC)/$(THISAPP)/src
> TARGET = $(DIR_INFO)/$(THISAPP)
> PROG = krb5
> -PAK_VER = 4
> +PAK_VER = 5
>
> DEPS =
>
> @@ -44,7 +44,7 @@ objects = $(DL_FILE)
>
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>
> -$(DL_FILE)_MD5 = a64e8018a7572e0b4bd477c745129ffc
> +$(DL_FILE)_MD5 = aaf18447a5a014aa3b7e81814923f4c9
>
> install : $(TARGET)
>
> --
> 2.18.0
>
next prev parent reply other threads:[~2021-02-05 16:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 16:17 [PATCH 1/2] tcl: Update to 8.6.11 Matthias Fischer
2021-02-04 16:17 ` [PATCH 2/2] krb5: Update to 1.19 Matthias Fischer
2021-02-05 16:57 ` Michael Tremer [this message]
2021-02-05 18:09 ` Matthias Fischer
2021-02-05 18:10 ` Michael Tremer
2021-02-05 16:56 ` [PATCH 1/2] tcl: Update to 8.6.11 Michael Tremer
2021-02-05 18:17 ` Matthias Fischer
2021-02-05 22:55 ` Matthias Fischer
2021-02-08 13:39 ` Michael Tremer
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=8F1F11E0-6EA1-4AA1-BD99-192FDB234168@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@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