public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] gnupg: Update to 1.4.21
Date: Sun, 21 Aug 2016 21:49:21 -0400	[thread overview]
Message-ID: <1471830561.14571.9.camel@ipfire.org> (raw)
In-Reply-To: <20160820104410.25366-1-matthias.fischer@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 2386 bytes --]

Hi,

this won't apply since we have only 1.4.18 in next.

Why are our trees out of sync?

Best,
-Michael

On Sat, 2016-08-20 at 12:44 +0200, Matthias Fischer wrote:
> Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
> ---
>  config/rootfiles/common/gnupg | 2 --
>  lfs/gnupg                     | 6 +++---
>  2 files changed, 3 insertions(+), 5 deletions(-)
> 
> diff --git a/config/rootfiles/common/gnupg
> b/config/rootfiles/common/gnupg
> index 9aecc41..edd2bec 100644
> --- a/config/rootfiles/common/gnupg
> +++ b/config/rootfiles/common/gnupg
> @@ -13,6 +13,4 @@ usr/lib/gnupg/gpgkeys_ldap
>  #usr/share/info/gnupg1.info
>  #usr/share/man/man1/gpg-zip.1
>  #usr/share/man/man1/gpg.1
> -#usr/share/man/man1/gpg.ru.1
>  #usr/share/man/man1/gpgv.1
> -#usr/share/man/man7/gnupg.7
> diff --git a/lfs/gnupg b/lfs/gnupg
> index e5e34c1..aa76042 100644
> --- a/lfs/gnupg
> +++ b/lfs/gnupg
> @@ -1,7 +1,7 @@
>  ####################################################################
> ###########
>  #                                                                   
>           #
>  # IPFire.org - A linux based
> firewall                                         #
> -# Copyright (C) 2015  Michael Tremer & Christian
> Schmidt                      #
> +# Copyright (C) 2007-2016  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.4.19
> +VER        = 1.4.21
>  
>  THISAPP    = gnupg-$(VER)
>  DL_FILE    = $(THISAPP).tar.bz2
> @@ -40,7 +40,7 @@ objects = $(DL_FILE)
>  
>  $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>  
> -$(DL_FILE)_MD5 = 3af4ab5b3113b3e28d3551ecf9600785
> +$(DL_FILE)_MD5 = 9bdeabf3c0f87ff21cb3f9216efdd01d
>  
>  install : $(TARGET)
>  

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-08-22  1:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-20 10:44 Matthias Fischer
2016-08-22  1:49 ` Michael Tremer [this message]
2016-08-22 16:39   ` Matthias Fischer
2016-08-22 18:25     ` Michael Tremer
2016-08-23 16:30 Matthias Fischer

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=1471830561.14571.9.camel@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