Re: repo missing package

[Greg Troxel <gdt%lexort.com@localhost>]

George Georgalis <george%galis.org@localhost> writes:

> On Wed, Jan 8, 2020 at 5:17 PM Greg Troxel <gdt%lexort.com@localhost> wrote:
>>
>> As for gating the release announcement, that isn't really reasonable,
>
> okay, fine :) it's my first choice of package manager because it's
> separate form the OS anyway :)
>
> I think it was only (relatively) recently I started using
> NetBSD/amd64/8.1/All and I didn't think about the consequences at all,
> using 8.x_2019Q3 and/or pkgsrc is a better value for me.

You can also build your own packages and then use pkgin on them.

I would encourage you to build things from source, if you have the disk
space and a machine that can cope (say 100G of disk and 4G of RAM should
be ok).

You can mix your packages and the official builds in practice, if you
are careful to check out the pkgsrc-2019Q4 branch.  You can  also choose
pkgsrc-current but those don't mix with the branch builds.

> Clock management has had more issues in releases than any other
> device, in my vmware and virtualbox experience. I think it stems from
> RTC doesn't make sense in a VM, so it's hard to characterize expected
> behavior, let alone support it, and inherit NTP at the same time...
>
> thanks for the links. A patch for rust to test the monotonic clock vs
> RTC might be an easy win, but if that fails I'd consider removing the
> forward clock tests altogether, if that is actually a problem
> (comparing timestamps in tests vs in operation), maybe a different
> locking scheme could resolve the issue?

I really haven't looked into this.  If you can figure out what's going
on precisely that would be helpful.

> if xen vm clock counters are rolling backward, I'm sure there is a
> very good and likely very complicated reason for it, if xen is not
> using the monotonic api for vm timesource, I'm very curious why? If
> the monotonic time source is moving backward, then I'm sure this will
> be very interesting bug and would reconsider removing the rust clock
> tests. ;-)

I don't understand what you mean.  xen runs on the bare metal and the
dom0 and domUs run under xen.  This is different from
nvmm/kvm/virtualbox/vmware-desktop and similar.



>
>
>
>
>
>
>
> --
> George Georgalis, (415) 894-2710, http://www.galis.org/