0:00:05.535,0:00:08.295
Good afternoon. Can you hear me?

0:00:10.406,0:00:12.456
Good afternoon. Sorry for the delay.

0:00:12.626,0:00:14.596
Welcome to Lightning Talks!

0:00:14.786,0:00:17.476
We have... 5 people doing 6 things,

0:00:17.476,0:00:18.936
and first up is Sean.

0:00:23.343,0:00:24.203
Hello!

0:00:24.203,0:00:25.283
Uh, I'm Sean.

0:00:25.833,0:00:26.813
Um, so,

0:00:26.893,0:00:28.963
Dgit is a multifaceted project

0:00:29.083,0:00:31.303
trying to solve a lot of problems at once

0:00:31.422,0:00:33.432
and the source package certainly is[br](one of those)

0:00:35.255,0:00:37.165
I wanted to briefly talk about

0:00:37.240,0:00:40.090
one of the things that dgit makes better, that

0:00:40.318,0:00:42.258
is the reason why you should consider

0:00:42.357,0:00:44.127
incorporating dgit push

0:00:44.175,0:00:46.235
into your existing workflows.

0:00:46.387,0:00:49.257
So, one of the things that [br]we offer our users

0:00:49.733,0:00:51.313
in our stable releases

0:00:51.559,0:00:54.519
is that(?) we say:[br]Look, we are going to make sure

0:00:54.519,0:00:56.449
that you can do[br]apt-get source,

0:00:56.510,0:00:59.100
apt-get build-dep <package name>

0:00:59.226,0:01:00.806
and then, it will (be) built

0:01:00.882,0:01:03.292
Right? That's one of the things we ensure

0:01:03.345,0:01:04.255
and it's a nasty bug if that doesn't work.

0:01:05.587,0:01:08.697
But, apt-get source is a[br]pretty old-fashioned way

0:01:08.739,0:01:11.379
to get a source for something[br]running on your computer.

9:59:59.000,9:59:59.000
in particular, like you can't[br]commit things

9:59:59.000,9:59:59.000
and then revert them

9:59:59.000,9:59:59.000
you can't make branches

9:59:59.000,9:59:59.000
you can't manipulate the source[br]in all the ways you can with git.

9:59:59.000,9:59:59.000
So, often what I think people will

9:59:59.000,9:59:59.000
probably do

9:59:59.000,9:59:59.000
is apt-get source and then just[br]commit everything to git.

9:59:59.000,9:59:59.000
Now, dgit clone is kind of a[br]shortcut there

9:59:59.000,9:59:59.000
dgit clone will "apt-get source" and[br]commit it to git, roughly.

9:59:59.000,9:59:59.000
(there's more stuff going on)

9:59:59.000,9:59:59.000
But that's one way to understand it.

9:59:59.000,9:59:59.000
And that's the git history you get,[br]if you type dgit clone

9:59:59.000,9:59:59.000
when the maintainer just uploaded[br]the package with dput.

9:59:59.000,9:59:59.000
So, it's kind of useful, it's in git now,[br]so you can type git clean

9:59:59.000,9:59:59.000
and it's pretty convenient.

9:59:59.000,9:59:59.000
But I think we could do a lot better for[br]our users.

9:59:59.000,9:59:59.000
We could give them the whole packaging[br]history

9:59:59.000,9:59:59.000
and eventually even the upstream history.

9:59:59.000,9:59:59.000
Which is a lot powerful for debugging[br]problems on their system.

9:59:59.000,9:59:59.000
So, that's what you get when you do dgit[br]clone, when it wasn't dgit-pushed.

9:59:59.000,9:59:59.000
What happens when it was ?

9:59:59.000,9:59:59.000
Well, that's what you get.

9:59:59.000,9:59:59.000
If someone like I did, typed "dgit push",

9:59:59.000,9:59:59.000
then, when the user types "dgit clone",

9:59:59.000,9:59:59.000
they get this rich history, which is[br]useful information, for debugging,

9:59:59.000,9:59:59.000
making reverts, and upstream changes[br]for example, and then trying build it.

9:59:59.000,9:59:59.000
Or, you know, that kind of stuff.

9:59:59.000,9:59:59.000
And as you see, the dgit push command[br]has gbp in it.

9:59:59.000,9:59:59.000
Like this wasn't a fancy git (??)ry-based[br]workflow or anything like that.

9:59:59.000,9:59:59.000
All I did was drop dgit --gbp push

9:59:59.000,9:59:59.000
in my existing team gbp workflow.

9:59:59.000,9:59:59.000
So if you're in a team that has[br]gbp-based worflow,

9:59:59.000,9:59:59.000
consider incorporating dgit push[br]and give this extremely useful thing

9:59:59.000,9:59:59.000
to our users.

9:59:59.000,9:59:59.000
Thanks !