public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: A few updates - built under Core 120
Date: Thu, 03 May 2018 19:01:56 +0200	[thread overview]
Message-ID: <47c79f5e-ff16-d6cc-f77d-7e143a672fda@ipfire.org> (raw)

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

Hi,

as I wrote, current 'next' won't build for me - it still doesn't.

So I prepared the following updates under Core 119 / Core 120:

pcre	=>	8.4.2
libidn	=>	1.34
nano	=>	2.9.6
htop	=>	2.2.0
openssh	=>	7.7.p1
unbound	=>	1.7.1

All of these are running here, patches follow.

If anyone has any concerns about this, please let me know.

Best,
Matthias

             reply	other threads:[~2018-05-03 17:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-03 17:01 Matthias Fischer [this message]
2018-05-03 17:08 ` Michael Tremer
2018-05-03 18:19   ` Peter Müller
2018-05-03 19:34     ` Michael Tremer
2018-05-04 20:13       ` Matthias Fischer
2018-05-04 20:19       ` Matthias Fischer
2018-05-05 17:50         ` 'next' with new kernel 4.14.39 took a long time - (was: Re: A few updates - built under Core 120) Matthias Fischer
2018-05-06 22:55           ` 'next' with new kernel 4.14.39 took a long time - 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=47c79f5e-ff16-d6cc-f77d-7e143a672fda@ipfire.org \
    --to=matthias.fischer@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