public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: IPFire 2.29 - Core Update 185 released
Date: Thu, 18 Apr 2024 10:37:17 +0200	[thread overview]
Message-ID: <cc39c40e-650e-417d-8e22-0297ac025c89@ipfire.org> (raw)
In-Reply-To: <171337021525.937787.6467291314249093863.ipfire@ipfire.org>

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

Hi Michael,

I am sorry but the ovpn.cnf file was not updated with CU185 full release.

I don't understand this as I tested it with CU185 Testing and cleared the OpenVPN x509 certificate set and recreated it successfully. However now with CU185 full release it is not working because the ovpn.cnf was not changed.

I checked the exclude file in the config/rootfile/core/185 directory and it has the line

/var/ipfire/ovpn

Does this mean that everything under ovpn is excluded from being updated? If yes then that would explain why it is not working now with the full release but would not explain why it worked for me with CU185 Testing.

How do we deal with this now.

Sorry,

Adolf.

On 17/04/2024 18:10, IPFire Project wrote:
> I am happy to announce that we finally have a new release of IPFire: IPFire 2.29 - Core Update 185. It comes with a brand new IPFire IPS based on Suricata 7, a number of bug fixes across the distribution and a good amount of package updates.
> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌
> 
> 
>   IPFire_
> 
> 
>   IPFire 2.29 - Core Update 185 released
> 
> I am happy to announce that we finally have a new release of IPFire: IPFire 2.29 - Core Update 185. It comes with a brand new IPFire IPS based on Suricata 7, a number of bug fixes across the distribution and a good amount of package updates.
> 
> Read The Full Post On Our Blog <https://www.ipfire.org/blog/ipfire-2-29-core-update-185-released?utm_medium=email&utm_source=blog-announcement>
> 
> The IPFire Project, c/o Lightning Wire Labs GmbH, Gerhardstraße 8, 45711 Datteln, Germany
> 
> Unsubscribe <https://www.ipfire.org/unsubscribe>
> 

       reply	other threads:[~2024-04-18  8:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <171337021525.937787.6467291314249093863.ipfire@ipfire.org>
2024-04-18  8:37 ` Adolf Belka [this message]
2024-04-18 21:40   ` Michael Tremer
2024-04-22 10:25     ` Adolf Belka

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=cc39c40e-650e-417d-8e22-0297ac025c89@ipfire.org \
    --to=adolf.belka@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