Look, this is rather simple. If you don't understand that snapshots get built, that libraries crank, that there are PEOPLE building this, that the data takes time to get to the mirrors, and that this is a non-static situation, that small catch-up syncronization errors are made, that they get fixed by real people, then PLEASE DON'T RUN SNAPSHOTS.
Hours later, another snapshot neaks out for each architecture, which has managed to pick up the shared library crank. Please learn what the snapshot processes are. It's in the FAQ! If you don't learn and understand the strong tech-innovation promise but much weaker delivery promise of snapshots, you are denegrating the effort by chattering into people's mailboxes. We do what we can, based on what we have. It is very nearly an auto-build platform with catchup corrections for these details. AND furthermore, snapshots sometimes contain surprise eggs for future coming test code; where it is easier to build it for all architectures and get it dogfooded in subsets of the test community, than wait and wait and wait for them to build it themselves. Those are our prorities showing through. Alternatively we could create a [email protected] mailing list, which I will not participate in. > On 10 December 2014, Stan Gammons <[email protected]> wrote: > > When will new packages be built for AMD64? I'm getting library errors > > with the latest snapshot and the current packages. > > There are bigger problems with the latest snapshot: > > $ ldd /usr/sbin/unbound > > /usr/sbin/unbound: > /usr/sbin/unbound: can't load library 'libssl.so.30.0' > /usr/sbin/unbound: exit status 4 > > $ ls -l /usr/lib/libssl* > > -r--r--r-- 1 root bin 1518902 Oct 29 03:25 /usr/lib/libssl.so.27.2 > -r--r--r-- 1 root bin 1512855 Nov 16 09:49 /usr/lib/libssl.so.28.0 > -r--r--r-- 1 root bin 1518550 Dec 8 07:54 /usr/lib/libssl.so.29.0 > > $ dmesg | head -1 > OpenBSD 5.6-current (GENERIC.MP) #668: Wed Dec 10 12:43:55 MST 2014 > > > Regards, > > Liviu Daia > <
