►
From YouTube: Package Community Office Hours: Debian MVC
Description
The Package Group meets with Mathieu who has been working on a contribution to add support for Debian to the GitLab Package Registry.
A
Hi
everyone
I
scheduled
a
synchronous
meeting
to
meet
with
matthew
who's,
been
working
on
a
new
community
contribution
for
adding
support
for
dbm
packages
to
the
gitlab
package
registry,
and
I
feel,
like
the
team,
has
all
the
people
in
this
room
have
been,
or
this
virtual
room
have
been
working
together
for
the
past
several
months.
So
I
thought
it
would
be
nice
to
kind
of
have
a
chance
for
everyone
to
get
together
and
ask
any
questions
synchronously
that
they
have
and
also
start
to
get
the
community
excited
about.
A
A
B
A
B
A
C
C
Usually
how
we
do
things
at
gitlab
is
really
we
go
for
the
simple
version
first,
so
it
can
be,
it's
not
dangerous,
but
you
could
invest
a
lot
of
time
in
trying
to
solve
a
future
problem.
That
might
not
happen,
and
usually
what
we
do
is
that
we
just
focus
on
on
the
problem
at
hand
and
just
iterate
on
it
in
if
we
have
a
more
complex
thing
to
handle.
Well,
we
just
iterate
on
it,
so
I
would
say
that
it's
it's
a
balance
about
yeah.
C
I
know
that
this
is
something
we
will
need,
so
I
can
start
working
on
it.
That's
that's
correct,
but
I
guess
it's
a
warning:
don't
fall
in
the
trap
of
yeah.
I
need
to
handle
this
and
this
and
we
will
need
this
and
actually,
after
releasing
the
feature,
this
abcd
problem
do
not
happen
at
all,
and
actually
we
didn't
need
to
handle
them
at
all
and
those
situations
already
occurred.
Sometimes
so
that's
why
I'm
I'm
putting
this
warning
of
not
going
too
far
in
solving
future
problems,
because
it's
it's
not
worth
it.
C
C
We
need
the
group
level
okay,
so
we
will
need
to
implement
the
group
level
and
then
you
wait
for
us
people
needing
the
instance
level,
and
then
you
implement
the
instance
level.
But
this
is
a
really
long
time
frame
and
in
that
time
frame
we
could
have
other
features.
So
other
features
such
as
the
virtual
registries
that
we
have
in
mind
that
could
replace
a
complete
whole
set
of
features
which
in
this
case
would
be
the
group
and
instance
level.
They
could
be
a
good
replacement
for
that.
C
A
A
A
C
E
Cool,
well,
I
wanted
to
say:
hey,
I
mean
we've
been
chatting
for
a
while
on
reviews,
so
it's
good
to
finally
meet
you
and
I
just
wanted
to
say
thank
you
again
for
all
of
your
expertise
that
you've
brought.
I
mean
I've.
I
come
from
the
world
of
npm
and
rubygems,
where
debbie
or
deviant
seems
very
different.
E
So
it's
been
really
nice
to
have
your
expertise
and
and
help
and
understanding
as
we've
been
working
through
these.
I
had
a
couple
questions
that
I
had
thought
of
one.
It
was
actually
something
that
I
was
trying
to
recall
for
for
david
as
well
was
the
group
distributions
are
not
associated
to
packages
in
any
way
right
now,
and
I
don't
recall
why
that
is.
Was
there
a
reason
or
is
that
planned.
B
B
E
B
B
B
B
E
The
other
curiosity
I
had
just
not
being
super
familiar
with
debian
is
I
see
that
you
know
in
in
the
draft
of
the
docs
and
through
working
through
these.
Mrs,
the
the
distributions
are
all
handled
through
an
api
where
we
make
curl
requests.
How
do
other
registries
work
with
distributions?
Are
those
also
just
usually
using
simple
tools
like
curl,
or
do
they
ever
have
specialized
client
tools
or
cli
tools.
B
B
E
B
B
B
Yeah
it's!
It
came
from
all
time,
so
it's
in
debian
the
generation
is
done
four
times
a
day
which
is
very
slow.
When
I
upload
package
to
debian
I
I
may
need
to
wait
six
hours
before
it
enters
seed
before
it
is
processed.
So
I
don't
want
to
create
the
same
behavior
in
the
github.
I
want
something
very
instantaneous,
but
the
problem
is
the
way
those
files
are
created.
B
B
B
The
the
word
thing
is
signed,
transitively
sign
this.
This
is
done
from
packages
to
release
to
package
file
to
a
release
file,
but
when
the
client
requests
the
data,
it
goes
the
other
way,
so
it
first
asks
for
the
release
files,
but
this
file
can't
be
known
until
all
the
other
files
are
already
processed.
B
B
The
package
packages
only
when
a
package
for
the
corresponding
component
and
architecture
would
change,
but
I
think
it's
it's
complicated
to
to
to
manage
events
and
to
to
know
when
when
each
file
is
outdated,
so
I
change
I
change
it
between
the
start
and
the
current
implementation.
I
change
it
things
a
bit
so
now,
when
one
package
is
uploaded
or
removed
or
something
the
world
distribution
is,
is
marked,
outdated
and
should
be
completely
regenerated.
E
Okay,
yeah
and
that's,
I
believe,
that's
one
of
the
mrs
that
we're
looking
at
or
recently
looked
at
the
regeneration.
That's
interesting,
yeah!
It's
it's
very
interesting
how
that
works
and
how
it's
I've
made
it
dynamic.
Thank
you
for
explaining
do
anyone
else.
Have
any
questions
follow
up
with
that?
E
Merge
requests
anymore
and
I
believe
david
will
be
probably
the
primary
maintainer
moving
forward
unless
something
else
changes,
but
just
so
you're
aware,
I
think
that's
kind
of
all
that
I
was
curious
about
and,
of
course
just
to
to
note.
You
know
if,
if
there's
anything
else
that
I
can
do
to
help
with
the
mrs
and
reviews,
because
I
know
sometimes
I'm
the
slowdown
point
of
there's
a
few
days
where
I
get
busy
and
can't
can't
get
back
to
them.
E
D
Of
course,
called
in
the
second,
I
was
taking
a
sip.
Yes,
we
are
actually
at
time,
though
so
I'll
just
verbalize
it
for
the
sake.
What
do
you
envision
will
be
valuable
to
see
in
the
ui
on
the
front
end,
both
in
the
list
and
the
details
page
which
data
is
do
you
think,
is
the
most
useful
when
you
are
looking
at
a
debian
package
to
see
and
if
there
is
any
special
action
that
will
need
to
support.
D
B
B
B
D
B
B
B
C
A
A
A
I
heard
from
a
customer
recently
that
they
that's
that
that's
not
the
preferred
way
and
they
still
want
to
use
killer
and
older
versions
of
helm.
So
I
think
there's
some
open
questions
on
how
we
pursue
pursue
that,
but
generally,
that
is
something
that
we'd
like
to
add,
and
we
are
thinking
about
probably
the
the
latter
half
of
this
year.