From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: [PATCH] Tor: update to 0.4.1.6 Date: Wed, 25 Sep 2019 16:18:50 +0100 Message-ID: <4B47CA32-38AA-4F98-85B6-F67A140C1B51@ipfire.org> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5150026503697360342==" List-Id: --===============5150026503697360342== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi, > On 25 Sep 2019, at 16:15, peter.mueller(a)ipfire.org wrote: >=20 > Please refer to https://blog.torproject.org/new-release-tor-0416 for > release notes. This patch has to be applied after applying 9fb607ef6 > (https://patchwork.ipfire.org/patch/2407/), which was not merged at > the time of writing. Referring to the commit by its hash does not make any sense here, because it = will change if the patch is being merged into master. Just FYI. Reviewed-by: Michael Tremer >=20 > Signed-off-by: Peter M=C3=BCller > --- > lfs/tor | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) >=20 > diff --git a/lfs/tor b/lfs/tor > index 9fb607ef6..ea07f6ce2 100644 > --- a/lfs/tor > +++ b/lfs/tor > @@ -24,7 +24,7 @@ >=20 > include Config >=20 > -VER =3D 0.4.1.5 > +VER =3D 0.4.1.6 >=20 > THISAPP =3D tor-$(VER) > DL_FILE =3D $(THISAPP).tar.gz > @@ -32,7 +32,7 @@ DL_FROM =3D $(URL_IPFIRE) > DIR_APP =3D $(DIR_SRC)/$(THISAPP) > TARGET =3D $(DIR_INFO)/$(THISAPP) > PROG =3D tor > -PAK_VER =3D 42 > +PAK_VER =3D 43 >=20 > DEPS =3D "libseccomp" >=20 > @@ -44,7 +44,7 @@ objects =3D $(DL_FILE) >=20 > $(DL_FILE) =3D $(DL_FROM)/$(DL_FILE) >=20 > -$(DL_FILE)_MD5 =3D 4a7ee49500d536d6c301a73bac0d0393 > +$(DL_FILE)_MD5 =3D d5e290d2a09d4225693cebc37a83097f >=20 > install : $(TARGET) >=20 > --=20 > 2.16.4 --===============5150026503697360342==--