Solved for me on build 1459134312. Thanks.
On Tue, Mar 22, 2016 at 11:18:21PM -0600, Theo de Raadt wrote:
> > Is there any verification of the contents of the tar balls being done?
>
> That is a bit snide, don't you think?
My sincere apologies if that was taken as a snide remark. I really did
not know if the contents of the tar files were
mail.com> writes:
> Same problem with build 1458662970.
> Anyone experiencing this same problem? I need to know if this is a
> hardware problem or if this have something to do with a build fail.
I tried basic installation inside virtual machine (qemu-kvm), when I found
that problem. Not a hardwa
> Is there any verification of the contents of the tar balls being done?
That is a bit snide, don't you think?
Yes, there is a check, after they start mirroring. Then the "sets"
files are fixed, and snapshots are rebuilt. Sometimes the files are
already moving along the mirror path...
That's a
Same problem with build 1458662970.
Anyone experiencing this same problem? I need to know if this is a
hardware problem or if this have something to do with a build fail.
On Mar 22, 2016, at 05:51, Mihai Popescu wrote:
>> Is there any verification of the contents of the tar balls being done?
>
> I don't know about you, but I don't feel like have balls verified.
You only have to worry if they're covered in tar.
> Is there any verification of the contents of the tar balls being done?
I don't know about you, but I don't feel like have balls verified.
On Tue, Mar 22, 2016 at 09:21:23AM +0100, arrowscr...@mail.com wrote:
> I did three installations, using install59.fs. In all of them I had problems
with libc.
> The two first I could not boot due to "can't load library libc.so.85.o".
> The other I could not install packages because "library c.84.2
8 matches
Mail list logo
