Re: A few updates - built under Core 120

[Matthias Fischer <matthias.fischer@ipfire.org>]

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

Hi,

On 03.05.2018 21:34, Michael Tremer wrote:
> -----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.

Just saw this.

Core 120:
root(a)Devel: /home/matz/ipfire-2.x/config/rootfiles/core/120/filelists

next:
root(a)Devel: /home/matz/ipfire-2.x/config/rootfiles/core/121/fileslists
                                                            ^^^^^^^^^^
Typo?

Best,
Matthias

> 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
>> 
>> 
> -----BEGIN PGP SIGNATURE-----
> 
> iQIzBAEBCgAdFiEE5/rW5l3GGe2ypktxgHnw/2+QCQcFAlrrZFkACgkQgHnw/2+Q
> CQc4UQ//RJExr7KDBXYWaMmaTaTA9+lSaSG4wJ5mm6NXaKc6sKpQ8/TCrYZ6dgaA
> EtEKENLv7fx+Ch9zcdwAgfEDqLFONhtsA3crwvlwoFdYI4XlXQ8uJIRCUkvx10MW
> OLmlFNmDfDm3LO+ZlpGqwKOkh1PBOo0iVnFV8gr4iIsH3Kpeq9FPw2Ls8yx4HXvr
> nJRefshrpLdF33ARn+BbZZvj7iv3b5KgeIHagNpOjyTKMx7ggcpv7YD84V5lrQYV
> bluDnlcQsq6UVj7PveuNx02FaOO8a7D+z4nUas01ofXH+dvFFumjKWxtwJ5yM7rr
> bcYiiKQj4IOlLxmvdvcvpjZpVsHEZcFZwB1SvBqzSGS/oOHhxtHGJXQDU/l7nVUn
> 7KFBEc78QXbSOv3DD/5UaU5HkwBuqo1HWA1bOvyHRywIQeGvcS/rgIu4c548Gjwd
> +XC9ywbY5yKQf6JKfTeaAkPfACOskV3+UVlyu7xc3feqcIBQnTPVnJe+cyz7FgYk
> R3NCLEZXN/tJqOU5mPXpOBBKKO0w/ivj3SMgivmU2bmDqeEBAR7RaSVlGYl3paU1
> HPRjxfyMDQKLJ0mITsTWkCvV/mI7bu5QwgH+n1kihgAo8Snx2Q69Ge9HptvF/IVq
> qIZ0gXgqBx/IF7c0W9cLN21qppfepsm2V+XPqOjLGZb0PZgJtUI=
> =YkXc
> -----END PGP SIGNATURE-----
> 
>