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] OpenVPN: Update to version 2.4.5
Date: Sat, 17 Mar 2018 14:32:02 +0000	[thread overview]
Message-ID: <1521297122.178881.19.camel@ipfire.org> (raw)
In-Reply-To: <c9349778-b67c-0731-2095-4ca4eb98a7fb@ipfire.org>

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

Hi,

so if you can manage to do this this week, please send the smaller bits in like
htop, nano, rsync, etc. Not sure if we should unbound in this release, too,
because I am not sure if more things have changed. squid is certainly too large
for this update.

I would say we close the Core Update next Thursday, build it over the weekend
and put it into testing on Monday at the latest.

Best,
-Michael

On Sat, 2018-03-17 at 09:18 +0100, Matthias Fischer wrote:
> Hi,
> 
> On 16.03.2018 19:16, Michael Tremer wrote:
> > Do you have anything left for this Core Update? I guess we are ready to
> > close
> > this soon.
> > ...
> 
> Having a tough time, I nevertheless prepared - and run:
> 
> htop		2.1.0
> nano		2.9.4
> rsync		3.1.3
> hdparm		9.54
> logrotate	3.14.0
> bind		9.11.3
> unbound		1.7.0
> squid		4.0.24	=>'--without-netfilter-conntrack', running
> 			without seen problems, TESTING!
> 
> But I'm not sure. Seems a bit too much. Answering your question: Yes, I
> have "anything left"... ;-)
> 
> Time to push?
> 
> Best,
> Matthias

  reply	other threads:[~2018-03-17 14:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-12 12:47 Erik Kapfer
2018-03-16 16:57 ` ummeegge
2018-03-16 18:16   ` Michael Tremer
2018-03-17  8:18     ` Matthias Fischer
2018-03-17 14:32       ` Michael Tremer [this message]
2018-03-17  8:25     ` ummeegge
2018-03-17 14:32       ` 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=1521297122.178881.19.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