►
From YouTube: NixOS Office Hours, 2019-09-20
Description
Today, office hours are in a question-and-answer format. We will take questions on Zoom and on IRC.
A
B
A
As
you
are
aware,
I've
just
got
back
from
vacation
and
I
also
have
a
little
bit
of
a
cold
I'm,
really
happy
to
be
back
with
all
of
you
doing
this
again.
These
are
a
lot
of
fun
for
me,
even
if
they're
a
little
bit
of
stretching
since
our
last
call
was
a
bit
flaky
and
we
weren't
able
to
have
Elko
do
his
presentation
about
Nick's
flakes.
We
were
gonna
have
him
back
this
week,
but
because
of
a
scheduling
conflict
we
weren't
able
to
do
that
today.
A
A
A
B
B
B
So
there's
a
precedent
currently
for
like
P
name
and
version
I've
accidentally
been
encouraging
people
to
put
unstable
inversion
instead
of
P
name
like
the
manual
you've,
actually
been
trying
to
undo
that
so
just
other
contributors
to
realize
that
you
need
to
put
if
you're,
using
p
name
to
put
unstable
when
you're
using
that
version
format
in
that
attribute,
I
can't
remember
the
exact
issue
so
to
find
it.
So
let
me
request
that.
B
B
Sorry
I
had
a
message
on
right,
so
the
usual
things
I
look
at
on
a
PR.
This
is
a
simple
packaging.
One
is
the
version
and
the
name
and
I'm
seeing
that
they're,
correct
I
could
check
the
revision,
but
typically
the
too
lazy.
To
do
that.
To
be
honest
and
I'm
saying
it
only
depends
on
pigeons,
so
I
usually
look
at
the
upstream
URL
and
look
for
the
build
dependencies.
B
B
A
B
A
B
A
B
A
A
B
I
just
used
hub
PR
checkout
in
the
number,
which
is
really
convenient
to
me
to
check
PRS
cuz
I
can
just
check
it
out.
Half
deal
a
lot
of
magic,
it's
just
nice
tool,
so
that's
what
I
did
other
than
that
definitely
build
it.
This
is
a
library
for
what
I
don't
think.
I
was
paying
attention
to
that
detail.
I.
B
B
A
All
right,
I
will
see
about
screen
sharing.
We
have
a
question
on
the
Zune
group
chat
from
Tobias
fluke.
He
wants
to
talk
about
poor
request.
Number
is
69
thousand
and
eight
I'm
gonna
paste
that
in
to
IRC,
okay,
which
is
about
removing
an
odious
version
that
reached
end
of
maintenance.
This
is
a
general
thing,
he'd
like
to
get
feedback
on
from
others,
so
I
think
specifically
he's
asking
about
how
how
do
we
decide
to
drop
versions?
I'm
going
to
open
up
the
issue
in
the
screen
share?
Okay,.
C
B
D
C
A
So
and
that's
exactly
right:
keeping
in
end-of-life
software
in
NYX
packages
sort
of
gives
the
impression
that
we
are
maintaining
it,
but
and
we
are
definitely
not
maintaining
nodejs
11,
so
in
that
case
yeah.
So
the
typical
thing
we
would
want
to
do
is
remove
it
from
NYX
NYX
packages
before
the
next
table
release
and
then
provide.
If
people
have
trouble
or
need
to
get
this
older
version
say:
okay,
you
have
you,
can
you
can
get
that,
but
you
have
to
fetch
this
old
version
of
NYX
packages.
We.
C
Right
I
mean
you
know
the
only
and
maybe
I
mean
that
that
makes
complete
perfect
sense
to
me.
I'm
I'm
completely
perfectly
happy
with
that.
Be
the
only
the
only
question
that
pops
up
in
my
mind
and
maybe
I'm
just
thinking
too
much
about
that-
is
that
in
a
way
like
I
said,
there
is
plenty
of
software
which
is
like
end-of-line
in
this
sense
that
nobody's
nobody's
you
know
kind
of
change
it
anymore
right,
so
yeah,
okay,
but
I
mean
that's,
probably
not
not
a
good
argument
to
keep
it
anyway.
So
I
think.
B
D
D
C
A
B
A
That
is
because
a
lot
of
a
lot
of
tools
packaged
in
the
expected
just
depend
upon
it.
So
if
I
think
I
think
there
is
an
edge
case
here,
which
is
that,
if
there's
a
bunch
of
if
there's
important
software
index
packages
that
depends
on
mu
J
as
11
definitely
want
to
keep
it.
If
all
of
the
software
that
we
have
that
depended
on
nodejs
11
is
easily
upgraded
to
one
that
is
not
end-of-life.
That's
that
would
be
a
preferred
route.
Does
that
sum
it
up.
Yeah.
B
B
A
A
A
E
Reduce
it
if
you
prefer
Oh
excellent
I,
just
had
to
make
things
put
work,
so
the
audio
was
on
the
output
and
okay.
This
PR
is
basically
adding
a
new
SD
image
builder,
but
specialized
for
the
Raspberry
Pi.
For
the
reason
we
need
this
and
we
can't
rely
on
the
current
generic.
A
are
64
builder
is
because
currently
upstream,
you
boot
and
in
the
upstream
kernel,
are
of
streaming
themselves
the
Raspberry
Pi
for
stuff
and
mic.
E
E
This
brings
in
a
new
builder
and
a
couple
of
new
kernel
configurations
for
this
other
specific,
raspberry
PI's.
It
should
make
I'm
not
sure
how
to
introduce
this
bit,
but
during
between
1903
in
1909,
I
changed
something
about
the
ah-64
generic
image
before
19-point
o3n
before
it
was
a
building
at
the
image
with
the
kernels
and
in
authorities
in
a
fat32
partition.
E
E
So
the
chance
now
is
that
the
files
are
on
the
main
partition
and
the
factor
due
to
partition
for
s
berry
pies
is.
We
are
now
treating
it
like
an
app
like
an
opaque
blood.
That's
the
u-boot
for
s,
berry
pie!
Only
this
in
turn
makes
the
image
order
to
use.
If
you
don't
want
to
use
your
boot
on
raspberry
pies.
For
some
reason,
oh
and
since
you
would
currently
doesn't
work
for
the
raspberry
pie
for
and
total
upstream,
you
there's
already
work
for
a
streaming.
E
A
E
Right
now,
there's
no
breaking
changes.
It's
only
new
stuff,
the
main
issue,
and
that
is
that
we
will
get
a
specific
kernel
built
for
the
Raspberry
Pi.
Is
this
disk
image
built
for
the
Raspberry
Pi,
so
this
may
lead
to
other
board
other
people
wanting
to
introduce
other
boards
specific
derivation
for
other
boards
on
in
the
NYX
mix,
a
wesen
mix
packages
instead
of
relying
on
the
main
mainline
kernel
like
we
used
to
do.
A
E
X
packages
for
this
I,
like
just
other
people,
to
look
at
it,
see
if
they
smell
anything
bad
in
it
in
it,
but
I
think
everything
is
fine
and
maybe
other
people
with
Sarah's
berry
pie
could
taste
it
see
that
verify
it
works
for
them
too,
but
it
I
checked
it
on
the
to
dig
about
today.
The
two
gigs
and
4
gigs
variants,
I
think
there's
an
issue
with
the
four
gig
variant:
that's
not
relevant
to
the
PR.
E
E
B
B
E
E
E
Almost
thinking
this
is
more
something
that
could
go
into
a
repo
like
mixes
hardware,
that
the
Cornell
tangents
could
go
into
domain
expectations,
but
the
image
building
stuff
could
be
go
somewhere
else,
but
man
maybe
something
to
talk
about
later.
When
there's
another
board
that
wants
to
get
included
and
we'll
see
it.
Maybe
we
just
remove
the
Raspberry
Pi
specific,
build
once
William
once
it
gets.
Mainlined.
A
That's
so
I
wonder
almost
about
setting
up
like
a
hardware
lab
what
I
don't
know
what
that
actually
means,
but
like
Hardware,
where
we
can
easily
test
stuff
on
different
pieces
of
like
embedded
boards
and
whatnot
I.
Don't
know
what
that
would
look
like
for
Hydra,
but
it
would
be
pretty
interesting
to
be
able
to
verify
that
things
keep
working
on
these
different
boards,
yeah
sure.
A
B
B
Currently
I
commented
something
like
I'm
fixes
now
and
then
marketers
was
over
each
conversation
and
I'm
pretty
sure.
That's
like
a
de
facto
practiced.
Please
do
that
because
it
does
help
me
to
see
that
the
changes
I
requested
were
resolved
by
you
and
to
always
push
the
changes
and
then
mark
them
resolved.
So
don't
resolve
as
you're
writing
acts.
I
can't
actually
be
sure.
That's
done
it
send
us
want
to
mention
that.
A
Cool
well
so
I
don't
actually
know
if
we
have
any
of
the
release
managers
right
now.
But
let's,
let's
talk
a
little
bit
about
1909
and
actually
I
see
read
on
IRC
has
asked
a
question
about
Minecraft.
Let's
do
that.
First,
we
could
always
get
back
to
the
release.
Read
has
asked
about
four
requests.
Number
is
sixty
eight
thousand
one
hundred
and
seventy
five
I.
B
B
A
B
A
A
B
B
B
B
B
A
B
B
B
Until
the
channel
advances
in
the
PR
is
merged.
It
is
unfortunate
for
users
that
certain
situations
you
get
into
it.
We
have
to
wait,
and
the
program
is
just
broken.
I
know
for
other
programs
like
discourse,
it
breaks
all
the
time.
This
is
updates
and
you
know
it's
not
backwards
compatible.
So
it's
quite
a
pain
for
certain
users
who
use
it.
I
cannot
it's
a
pain
in
general
for
users
who
use
it.
That
is
the
procedure
to
do
that.
A
B
C
B
C
B
B
B
C
D
B
C
C
C
B
C
Keep
on
scrolling
down
down
down
down
down
it's
like
way
too
much
stuff
going
on
yeah,
okay,
that
was
slightly
too
far
up
and
yeah,
yes
top
here
there
we
go.
He
basically
says
like
like
these
could
be
the
remaining
things,
but
even
even
then,
afterwards,
some
worth
pointing
out
that
the
date
stuff
or
time
stuff
in
GCC
is
superseded
by
some
other
change,
and
so
it's
quite
possible
that
there
is
nothing
left
in
there
which
is
relevant,
but
I'm,
not
really
not
even
closely
an
expert
on
these
topic,
so
I'm
not
sure
so.
C
C
I
might
I
guess
the
idea
was
that
that
if
anything,
then
these
few
things
could
still
be
of
relevance,
but
then,
even
even
then,
afterwards,
someone,
if
you
scroll
down
someone's
pointing
out
that
even
even
parts
of
that
or
now
also
irrelevant
here
we
go
like
the
GCC
stuff
has
been
superseded
by
then,
and
so
it's
quite
possible.
There
there's
absolutely
nothing
left
in
this
in
this
PR,
which
is
I,
don't
know,
I
mean
how
many
years
old
now
is.
A
B
A
A
All
right-
and
that
concludes
the
next
office
hours
for
this
week.
Next,
con
2019,
just
a
reminder-
is
coming
up
on
October
25th
through
October
27th
in
Brno,
Czech
Republic,
you
can
go
to
2019
Nick's
conduct.
Work.
I
will
paste
a
link
to
that
in
chat.
Oops,
no
I
won't,
maybe
the
world.
If
these
can
do
that,
so
you
can
go
to
2019
that
next
comes
out.
Work
for
tickets
and
I'll,
be
there
and
I
hope
to
see
a
lot
of
you
out
there.
A
Alright
next
office
hours
are
going
to
be
on
October
4th
and
if
you
would
like
to
be
a
guest
in
a
future
call-
or
you
have
something
interesting-
that
you've
been
working
on
we'd
love
to
have
you
on
and
world
of
peace,
we'll
also
share
a
link
to
a
survey
where
you
can
put
in
some
information
and
we'll
that'll
go
into
our
system
and
we'll
reach
out
to
you.
Thank
you
all
so
much
for
coming
and
I
hope
this
has
been
good
and
I'll.
See
you
all
in
a
couple
weeks:
Thanks.
Okay,
thanks
bye.
Everyone.