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:02.605
Right? That's one of the things we ensure

0:01:02.605,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.

0:01:11.618,0:01:14.282
in particular, like you can't[br]commit things

0:01:14.373,0:01:15.506
and then revert them

0:01:15.518,0:01:16.881
you can't make branches

0:01:17.407,0:01:22.705
you can't manipulate the source[br]in all the ways you can with git.

0:01:23.150,0:01:26.640
So, often what I think people will probably do

0:01:26.711,0:01:29.656
is apt-get source and then just[br]commit everything to git.

0:01:30.499,0:01:33.818
Now, dgit clone is kind of a[br]shortcut there

0:01:33.818,0:01:37.838
so dgit clone will "apt-get source" and[br]commit it to git, roughly.

0:01:37.913,0:01:39.277
(there's more stuff going on)

0:01:39.322,0:01:41.542
But that's one way to understand it.

0:01:41.547,0:01:45.327
And that's the git history you get,[br]if you type dgit clone

0:01:45.420,0:01:48.990
when the maintainer just uploaded[br]the package with dput.

0:01:49.061,0:01:52.575
So, it's kind of useful, it's in git now,[br]so you can type git clean

0:01:52.575,0:01:54.325
and it's pretty convenient.

0:01:54.350,0:01:56.960
But I think we could do a lot better for[br]our users.

0:01:56.989,0:01:59.369
We could give them the whole packaging[br]history

0:01:59.425,0:02:01.515
and eventually even the upstream history.

0:02:03.635,0:02:06.755
Which is a lot powerful for debugging[br]problems on their system.

0:02:06.858,0:02:11.568
So, that's what you get when you do dgit[br]clone, when it wasn't dgit-pushed.

0:02:11.583,0:02:13.373
What happens when it was ?

0:02:13.675,0:02:15.001
Well, that's what you get.

0:02:15.021,0:02:18.821
If someone like I did, typed "dgit push",

0:02:18.850,0:02:21.600
then, when the user types "dgit clone",

0:02:21.673,0:02:25.423
they get this rich history, which is[br]useful information, for debugging,

0:02:25.491,0:02:28.811
making reverts, and upstream changes[br]for example, and then trying build it.

0:02:29.126,0:02:31.139
Or, you know, that kind of stuff.

0:02:31.537,0:02:34.945
And as you see, the dgit push command[br]has gbp in it.

0:02:35.138,0:02:41.374
Like this wasn't a fancy git-debrebase[br]workflow or anything like that.

0:02:41.496,0:02:44.398
All I did was drop dgit --gbp push

0:02:44.461,0:02:47.514
into my existing team gbp workflow.

0:02:47.514,0:02:50.234
So if you're in a team that has[br]gbp-based workflow,

0:02:50.347,0:02:54.687
consider incorporating dgit push[br]and give this extremely useful thing

0:02:54.751,0:02:56.071
to our users.

0:02:56.094,0:02:57.764
Thanks !

0:03:14.090,0:03:16.979
Right, next up is Judit,

0:03:17.135,0:03:20.445
telling us "debian lenny[br]worth every penny".

0:04:16.803,0:04:19.156
OK. The main issue about -

0:04:19.236,0:04:21.192
I'm gonna talk about Debian Lenny -

0:04:21.246,0:04:25.356
(which) is "will you able to fill five minutes[br]with it ?"

0:04:25.442,0:04:28.642
But I'm prepared and I have a backup !

0:04:31.897,0:04:34.832
So, who of you is still using Lenny ?

0:04:36.359,0:04:42.313
Who of you plans to use Lenny ?

0:04:42.553,0:04:45.523
[laughs]

0:04:48.800,0:04:49.822
So that's great !

0:04:49.822,0:04:52.934
So. Lenny is not completely abandonned.

0:04:54.249,0:04:58.401
(??) What it was back in 2009 when it[br]was released ?

0:04:59.691,0:05:03.618
Everyone was using it, and now

0:05:06.123,0:05:09.431
you feel somehow lonely about it.

0:05:09.434,0:05:12.534
And of course there are reasons for it.

0:05:15.926,0:05:23.774
For example, it got security support[br]discontinued and doesn't do well.

0:05:26.935,0:05:31.890
And of course, a lot of fancy stuff is[br]missing, like html5.

0:05:33.362,0:05:36.394
This might not be an issue if you don't[br]like videos.

0:05:37.737,0:05:44.627
And even if you would have support for[br]html5, probably you wouldn't have support

0:05:44.627,0:05:46.403
for most of the codecs.