►
From YouTube: NixOS 20.03 Markhor Go / No-Go
Description
Blocker review meeting.
C
B
F
B
B
B
B
H
A
D
D
F
D
F
H
B
D
H
G
D
H
H
I
think
you
already
put
the
notes
in
there
right.
Oh
no,
a
couple
notes,
so
that
was
just
the
notes
that
we
have
prepared
and
I
guess
we
can
begin
I,
guess
without
sound
or
since
he's
not
responsive,
currently
kind
of
hard
to
reach
him
on
rst.
Maybe
something
no
other
way
to
chat,
and
they
could
do
that.
H
Okay,
so,
but
we've
meet
it
today,
because
I've
noticed
it's
pretty
difficult
to
figure
out
if
Nick's
of
us
is
ready
without
a
sort
of
important
communication
point
so
sort
of
like
a
fine
defined
moment
of
when
we
decide
that
actually
right,
let
me
get
everyone
together,
just
figure
out
that
out
and
evaluate
that
I
do
plan
to
sort
of
put
it
in
the
documentation.
So
we
could
continue
to
do
this.
H
Pretty
sure
we
already
know
if
I
Jenna
says,
do
a
roll
call
of
who's
very
know.
Everyone
subsystem
everyone's
representing
right
sounds
good
I'm,
not
sure
it
might
be
much
like
announce
that
so
we
have
that
for
recordings
and
what
everyone
is
present
for
so
I
guess
I
can
go
down
online,
so
Aaron.
What
are
you
representing
in
this
meeting
currently.
B
D
H
H
Thanks
Owen
I
thought
he
was
cooking,
okay,
anyways,
so
the
first
thing
we're
going
to
look
at
it's.
If
you
look
in
the
notes,
there's
a
section
that
says
it's
blocker
bugs
and.
F
H
Prs
and
the
ones
that
I
found
in
the
discourse
thread
have
already
sort
of
labeled
with
a
blocker
bug,
so
we
can
sort
of
unlabeled
them
to
the
side
if
a
knocker
or
something
like
that
in
the
same
with
the
pr's
and
if
you
have
any
proposals,
just
drop
them
in
the
proposal
section
right
here.
So
we
can
look
at
those
two
for
not
already
and
they
hold
so
I
guess.
I.
H
A
H
Okay,
I'll
leave
that
whoever
it's
been
following
that
bug
to
close
it,
but
pretty
sure
we
already
think
that's
already
done
so
I
believe
the
next
bug
we
can
I.
Let
me
get
to
showing
my
screen,
so
you
can
all
see
what
I'm
looking
at
sorry,
let's
see
if
it
works.
H
H
E
So
the
thing
is
this:
only
of
course,
when
you
are
using
Nyx's
1909
and
you
are
try
to
use
packages
from
unstable
or
2003,
this
is
because
you
use
the
system-wide
ldd
to
resolve
libraries,
but
if
you
do,
for
instance,
nix
shell
beyond
a
reasonable
shake
out,
this
is
M.
This
issue
disappear,
so
I'm
yeah,
not
Auto,
fix
it
actually.
I.
H
F
H
So
it
says
this
seems
to
be
depending
on
the
environment:
I
just
built
a
nexus
99,
VM
and
I
could
reproduce
this
issue
and
you'd
say
what
revision
you
checked
out
built,
and
you
said
it
was
reproducible.
But
when
you
change
the
environment,
the
VAR
crowd
disappears,
and
then
you
said
race
these
following
questions.
I.
I
H
I
H
H
I
I
H
E
H
E
Yes,
that's
right,
so
the
thing
is,
we
still
have
a
fairly
outdated
MongoDB
version
on
2003,
which
depends
on
an
in
sexual
version
of
OpenSSL.
Last
week,
I
emerged
put
requests
which
basically
did
an
upgrade,
and
so
we
have
a
recent
3.4
by
default
and
also
3.6
and
4.0.
The
problem
is
that
MongoDB
has
its
own
license
now,
which
is
just
based
on
GPL,
but
it's
not
a
proof
by
the
open
source
initiative
for
several
reasons,
which
is
white,
smartness,
unfree
and
now
I
have
the
problem.
E
That's
everyone
who
wants
to
use
MongoDB
basically
needs
to
compile
it
locally,
and
I
basically
wanted
to
ask
if
this
is
fine
or
if
we
should
or
yeah
what
you
think
about
it,
because
I
think
infamously
made
the
suggestion
to
modify
the
licensing
logic
in
expected.
Just
to
add
a
third
category
like
distributed
about
unfreedom
to
make
sure
that
either
actually
lose
the
package.
H
Right,
let's
see
if
I
can
find
out
exact
issue
right
is
this
one,
and
this
is
the
content
of
it.
It
was
not
sorry
proved
so,
but
a
lot
of
distribution,
innovation,
but
we're
still
marking
is
on
great.
So
you
need
to
add
a
type.
That's
redistributed
off.
Another
category.
I
did
see
even
on
some
sort
of
me
that
people
were
all
a
little
annoyed
with
it
having
to
be
rebuilt
like
that.
H
So
it's
definitely
a
problem
for
users,
in
that
sense,
I'd,
say
or
PR
definitely
can
be
merged,
but
I'm
not
completely
certain
about
the
issue
with
it
being
on.
Cherie
has
to
be
built
locally,
I.
H
I
I
H
I
B
H
D
There
was
also
I'm
gonna
link
it
in
the
IRC.
There
was
an
issue
or
a
PR
that
would
refactor
the
license
stuff,
so
we
can
probably
distinguish
between
unfree,
redistributable
and
unfree
non
redistributable,
but
didn't
seem
like
the
work
was
finished,
but
that's
probably
something
we
should
do
in
the
future.
All.
H
C
C
This
feature
is
broken
for
some
reason.
The
thing
that
plugs
into
Pam
crashes
and
the
symptom
of
this
is
the
first
time
you
you
do
something
that
needs
the
wallet
to
be
opened.
It
will
prompt
you
for
your
password
a
second
time
essentially
at
which
time
it
succeeds
in
opening
the
wallet
and
everything
works.
So
while
this
is
pretty
annoying
I,
don't
think
that
this
is
a
blocker.
The
core
feature
of
Kay
wallet
seems
to
work.
From
my
perspective,
exactly.
H
H
F
B
F
H
H
H
Okay,
so
it
sees
that
it's
like
here
in
this
meeting.
Currently
don't
think
so
so
it
did
say
it
could
reproduce
this
issue
in
VN,
which
is
pretty
reliable,
let's
scrum
fit
your
five
fails
on
latest
next
boss
and
say
well,
I
think
it's
one
of
those
issues
that
gets
hijacked
repeatedly.
Yes,.
A
H
Right
I
think
I
believe
I've
heard
you
say
that
before
and
next
was
stuff
repeatedly
actually,
but
it
did
say,
lioness
did
say
that
there
was
a
reproducible
case
right
here
with
this
configuration
which
it
said
installing
ninety
nine
booting
it
and
then
upgrading
to
tonio
3
beta
rebooting
and
going
back,
wait,
Celia
I've
been
able
to
I,
don't
think
I
actually
how
to
read.
Sorry.
H
D
D
A
H
D
H
Exactly
okay,
I
guess
that's
been
agreed
and
I
guess
we
have
some
a
at
least
an
IPR.
It
has
conflicts.
So
I
guess
this
is
part
of
the
review
documentation.
The
phase,
let
me
check
with
and
I,
don't
have
any
other
PRS
sitting
around
that
are
booking,
since
it
looks
sort
of
like
they're
kind
of
separated.
H
The
highlight
section
sort
of
thingy
that
I
was
supposed
to
do,
but
I
just
have
kind
of
not
a
lot
of
patience.
Right
doc
looks
to
be
honest:
it's
not
finished
a
PR
to
add
explanation
for
how
the
Python
driver
is
being
deprecated
stuff,
like
that.
That's
not
done
I,
couldn't
finish
that
and
I'm
pretty
sure.
If
I
don't
want
this
note,
so
I've
been
decided,
sort
of.
H
H
H
D
H
H
H
H
H
H
A
F
H
H
A
H
A
Yeah
they
are
says,
there's
a
fix,
I
just
haven't
had
the
time
to
actually
look
into
it,
but
the
fix
is
probably
probably
working.
It's
my
cell.
It's
just
that.
We
need
to
look
into
it
which
I'll
be
able
to
do
after.
This
is
a
meeting
so
I.
Don't
think
this
is
a
blocker
for
the
future.
I
think
it's
just.
We
probably
want
to
do
it
before
we
ready.
A
H
I
think
I
understand
you,
I've
actually
approved
on
this
Peter
I
thought
because
it
doesn't
seem
to
be
very
well
verified,
since
the
other
little
rushed
excited
here
to
figure
out
that
nothing
actually
changed.
Yeah.
A
A
Regression
with
stun
setups
I,
don't
know
about
it,
should
be
plus
since
I
don't
have
a
tree
plus
to
test
with
so
I'll
be
pinging
that
the
IRC
user
that
had
the
issue
with
the
non
plus
to
verify
weapons
on
their
stops
and
I'm,
hoping
someone
with
Raspberry
Pi
3
plus,
will
be
able
to
light
it.
What,
if
that
is
they
made
I
specifically
linked
to
works?.
A
H
D
D
A
A
A
B
G
G
H
H
H
So
I
think
for
what
we've
gotten
feedback
on
we
looked
at
as
that
we
need
a
little
bit
of
work,
but
not
much
you
could
probably
realistically
like.
So
today
we
couldn't
reconvene
right,
I,
just.
B
Want
to
call
out
a
couple
of
things
about
after
CONUS,
as
managed
as
they
gave
you
wallet
at
a
true,
seem
to
have
been
fixed
on
2009
and
maybe
a
fix
to
be
backward
and
then
a
second
thing
from
Aaron
and
just
saying
there
seems
to
be
a
bigger
Ruby
problem.
That's
broken
the
Red
Vine
test
on
2003,
no
he's
not
in
a
position
to
fix
them.
H
H
H
J
Yeah,
this
is
Minoru
in
the
117
3
2
1
4.
J
J
J
J
J
H
H
And
then
it
just
has
to
be
merged.
Its
tool
fix
pretty
sure.
I
said
that
he
would
watch
that
and
do
that.