-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Ah, sorry I forget to check this out.
I just started my build and it will need a while now to go to the point where it crashes. Probably has something to do with the core update folder. Just delete that and the build should complete without creating any core updates.
Best, - -Michael
On Thu, 2018-05-03 at 20:19 +0200, Peter Müller wrote:
Hi,
just curios: Does anyone have an idea why the next-tree won't build? I poked a little bit, but without satisfying results.
Like Matthias, I am also interested in updating packages for IPFire 2.x, and experiencing the same problem (testing). Usually, I do that in a VM, but some network stuff is hard to port into that environment. Maybe we could specify some criteria here, but that is nothing with a high priority...
Best regards, Peter Müller
Perfect. Keep them coming. It is good to bundle them together and align the patches a little with the release schedule of the Core Updates though.
Also, please try to encourage people to review and *test*. We need to have more eyeballs on the patches that we merge than just mine.
Best, -Michael
On Thu, 2018-05-03 at 19:01 +0200, Matthias Fischer wrote:
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