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.

I just compared the '.../config/rootfiles/core'-directories of 'Core 120' and 'next'.

It seems "...that the build fails because Core Update 121 does not have any filelists" is still present(?):

Core 120:
***SNIP***
root(a)Devel: /home/matz/ipfire-2.x/config/rootfiles/core/120/filelists # ls -l
total 8
lrwxrwxrwx 1 root root   23 May  4 22:07 apache2 -> ../../../common/apache2
lrwxrwxrwx 1 root root   19 May  4 22:07 apr -> ../../../common/apr
lrwxrwxrwx 1 root root   23 May  4 22:07 aprutil -> ../../../common/aprutil
lrwxrwxrwx 1 root root   20 May  4 22:07 bind -> ../../../common/bind
lrwxrwxrwx 1 root root   20 May  4 22:07 curl -> ../../../common/curl
lrwxrwxrwx 1 root root   26 May  4 22:07 cyrus-sasl -> ../../../common/cyrus-sasl
lrwxrwxrwx 1 root root   19 May  4 22:07 dma -> ../../../common/dma
-rw-r--r-- 1 root root  591 May  4 22:07 files
lrwxrwxrwx 1 root root   21 May  4 22:07 gnupg -> ../../../common/gnupg
drwxr-xr-x 2 root root 4096 May  4 22:07 i586
lrwxrwxrwx 1 root root   25 May  4 22:07 libevent2 -> ../../../common/libevent2
lrwxrwxrwx 1 root root   25 May  4 22:07 logrotate -> ../../../common/logrotate
lrwxrwxrwx 1 root root   26 May  4 22:07 Net_SSLeay -> ../../../common/Net_SSLeay
lrwxrwxrwx 1 root root   19 May  4 22:07 ntp -> ../../../common/ntp
lrwxrwxrwx 1 root root   23 May  4 22:07 openssh -> ../../../common/openssh
lrwxrwxrwx 1 root root   23 May  4 22:07 openssl -> ../../../common/openssl
lrwxrwxrwx 1 root root   30 May  4 22:07 openssl-compat -> ../../../common/openssl-compat
lrwxrwxrwx 1 root root   23 May  4 22:07 openvpn -> ../../../common/openvpn
lrwxrwxrwx 1 root root   29 May  4 22:07 python-typing -> ../../../common/python-typing
lrwxrwxrwx 1 root root   21 May  4 22:07 snort -> ../../../common/snort
lrwxrwxrwx 1 root root   26 May  4 22:07 strongswan -> ../../../common/strongswan
lrwxrwxrwx 1 root root   23 May  4 22:07 unbound -> ../../../common/unbound
lrwxrwxrwx 1 root root   22 May  4 22:07 vnstat -> ../../../common/vnstat
lrwxrwxrwx 1 root root   20 May  4 22:07 wget -> ../../../common/wget
lrwxrwxrwx 1 root root   30 May  4 22:07 wpa_supplicant -> ../../../common/wpa_supplicant

'next':
***SNIP***
root(a)Devel: /home/matz/ipfire-2.x/config/rootfiles/core/121/fileslists # ls -l
total 4
-rw-r--r-- 1 root root 29 May  4 22:09 files
***SNAP***

Something is missing here?

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-----
> 
>