public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Planning out Core Update 117
Date: Tue, 21 Nov 2017 11:25:26 +0100	[thread overview]
Message-ID: <32E4E5F7-133B-4C8B-8300-7A4C4BC375F1@ipfire.org> (raw)
In-Reply-To: <00de01d360af$56d354b0$0479fe10$@gmx.com>

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

Hello Michael,
i think this happens causing the switch from http to https. Can you use instead of
curl -O http://people.ipfire.org/~ummeegge/OpenVPN-2.4/Core115/ovpn_244_64_v3_core115.tar.gz
please
curl -O https://people.ipfire.org/~ummeegge/OpenVPN-2.4/Core115/ovpn_244_64_v3_core115.tar.gz

? Thanks.

Will correct this in the README-install.txt.

Greetings,

Erik

> Good evening Erik,
> 
> The package OpenVPN package hash from folder Core115 does not match with the
> ones posted by you in the .png snapshot:
> 
> [root(a)ipfire-vm tmp]# curl -O
> http://people.ipfire.org/~ummeegge/OpenVPN-2.4/Core115/ovpn_244_64_v3_core11
> 5.tar.gz
>  % Total    % Received % Xferd  Average Speed   Time    Time     Time
> Current
>                                 Dload  Upload   Total   Spent    Left
> Speed
> 100   185  100   185    0     0    774      0 --:--:-- --:--:-- --:--:--
> 777
> [root(a)ipfire-vm tmp]# sha256sum ovpn_244_64_v3_core115.tar.gz
> b8a7ebde1eec9fbba3790e31136fdfe3c7ea5b8c27900df1942f28cbe7b9f9f7
> ovpn_244_64_v3_core115.tar.gz
> 
> Can you confirm the above hash for the ovpn_244_64_v3_core115.tar.gz
> 
> Thank you,
> Horace
> 


  reply	other threads:[~2017-11-21 10:25 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7EA8C1E7-14CC-4906-9688-504DA016795D@gmx.com>
2017-11-10 15:36 ` ummeegge
2017-11-18 20:53   ` Horace Michael
2017-11-21 10:25     ` ummeegge [this message]
2017-11-21 11:49       ` Michael Tremer
2017-11-21 12:30         ` Horace Michael
2017-11-22 10:30 ummeegge
  -- strict thread matches above, loose matches on Subject: below --
2017-11-06 18:32 Michael Tremer
2017-11-06 21:06 ` Matthias Fischer
2017-11-07 10:44   ` Michael Tremer
2017-11-17 12:59     ` Matthias Fischer
2017-11-17 19:37       ` Matthias Fischer
2017-11-17 21:25         ` Michael Tremer
2017-11-17 23:15           ` Matthias Fischer
2017-11-18  7:44         ` Marcel Lorenz
2017-11-06 21:09 ` Matthias Fischer
2017-11-07 10:46   ` Michael Tremer
2017-11-07 15:05     ` Michael Tremer
2017-11-07 18:41       ` Matthias Fischer
2017-11-07 22:47         ` Michael Tremer
2017-11-21 14:42           ` Michael Tremer
2017-11-21 17:35             ` Matthias Fischer
2017-11-22 16:37               ` Michael Tremer
2017-11-10 11:01 ` ummeegge
2017-11-10 12:18   ` Michael Tremer
2017-11-10 13:35     ` ummeegge

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=32E4E5F7-133B-4C8B-8300-7A4C4BC375F1@ipfire.org \
    --to=ummeegge@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