1
00:00:05,535 --> 00:00:08,295
Good afternoon. Can you hear me?

2
00:00:10,406 --> 00:00:12,456
Good afternoon. Sorry for the delay.

3
00:00:12,626 --> 00:00:14,596
Welcome to Lightning Talks!

4
00:00:14,786 --> 00:00:17,476
We have... 5 people doing 6 things,

5
00:00:17,476 --> 00:00:18,936
and first up is Sean.

6
00:00:23,343 --> 00:00:24,203
Hello!

7
00:00:24,203 --> 00:00:25,283
Uh, I'm Sean.

8
00:00:25,833 --> 00:00:26,813
Um, so,

9
00:00:26,893 --> 00:00:28,963
Dgit is a multifaceted project

10
00:00:29,083 --> 00:00:31,303
trying to solve (??) problems at once

11
00:00:31,422 --> 00:00:33,432
(??) the source package certainly (??)

12
00:00:35,255 --> 00:00:37,165
I wanted to briefly talk about

13
00:00:37,240 --> 00:00:40,090
one of the things that dgit makes better, that

14
00:00:40,318 --> 00:00:42,258
is the reason why you should consider

15
00:00:42,357 --> 00:00:44,127
in cooperating(??) dgit push

16
00:00:44,175 --> 00:00:46,235
into your existing workflows.

17
00:00:46,387 --> 00:00:49,257
So, one of the things that 
we overall users(??)

18
00:00:49,733 --> 00:00:51,313
in our stable releases

19
00:00:51,559 --> 00:00:54,519
is that(?) we say:
Look, we are going to make sure

20
00:00:54,519 --> 00:00:56,449
that you can do
apt-get source,

21
00:00:56,510 --> 00:00:59,100
apt-get build-dep <package name>

22
00:00:59,226 --> 00:01:00,806
and then, it will (be) built

23
00:01:00,882 --> 00:01:03,292
Right? That's one of the things we (??)

24
00:01:03,345 --> 00:01:04,255
(??) if that doesn't work.

25
00:01:05,587 --> 00:01:08,697
But, apt-get source is a
pretty old-fashioned way

26
00:01:08,739 --> 00:01:11,379
to get a source for something
running on your computer.