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 a lot of problems at once

11
00:00:31,422 --> 00:00:33,432
and the source package certainly is
(one of those)

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
incorporating 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 offer our 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 ensure

24
00:01:03,345 --> 00:01:04,255
and it's a nasty bug 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.

27
99:59:59,999 --> 99:59:59,999
in particular, like you can't
commit things

28
99:59:59,999 --> 99:59:59,999
and then revert them

29
99:59:59,999 --> 99:59:59,999
you can't make branches

30
99:59:59,999 --> 99:59:59,999
you can't manipulate the source
in all the ways you can with git.

31
99:59:59,999 --> 99:59:59,999
So, often what I think people will

32
99:59:59,999 --> 99:59:59,999
probably do

33
99:59:59,999 --> 99:59:59,999
is apt-get source and then just
commit everything to git.

34
99:59:59,999 --> 99:59:59,999
Now, dgit clone is kind of a
shortcut there

35
99:59:59,999 --> 99:59:59,999
dgit clone will "apt-get source" and
commit it to git, roughly.

36
99:59:59,999 --> 99:59:59,999
(there's more stuff going on)

37
99:59:59,999 --> 99:59:59,999
But that's one way to understand it.

38
99:59:59,999 --> 99:59:59,999
And that's the git history you get,
if you type dgit clone

39
99:59:59,999 --> 99:59:59,999
when the maintainer just uploaded
the package with dput.

40
99:59:59,999 --> 99:59:59,999
So, it's kind of useful, it's in git now,
so you can type git clean

41
99:59:59,999 --> 99:59:59,999
and it's pretty convenient.

42
99:59:59,999 --> 99:59:59,999
But I think we could do a lot better for
our users.

43
99:59:59,999 --> 99:59:59,999
We could give them the whole packaging
history

44
99:59:59,999 --> 99:59:59,999
and eventually even the upstream history.

45
99:59:59,999 --> 99:59:59,999
Which is a lot powerful for debugging
problems on their system.

46
99:59:59,999 --> 99:59:59,999
So, that's what you get when you do dgit
clone, when it wasn't dgit-pushed.

47
99:59:59,999 --> 99:59:59,999
What happens when it was ?

48
99:59:59,999 --> 99:59:59,999
Well, that's what you get.

49
99:59:59,999 --> 99:59:59,999
If someone like I did, typed "dgit push",

50
99:59:59,999 --> 99:59:59,999
then, when the user types "dgit clone",

51
99:59:59,999 --> 99:59:59,999
they get this rich history, which is
useful information, for debugging,

52
99:59:59,999 --> 99:59:59,999
making reverts, and upstream changes
for example, and then trying build it.

53
99:59:59,999 --> 99:59:59,999
Or, you know, that kind of stuff.

54
99:59:59,999 --> 99:59:59,999
And as you see, the dgit push command
has gbp in it.

55
99:59:59,999 --> 99:59:59,999
Like this wasn't a fancy git (??)ry-based
workflow or anything like that.

56
99:59:59,999 --> 99:59:59,999
All I did was drop dgit --gbp push

57
99:59:59,999 --> 99:59:59,999
in my existing team gbp workflow.

58
99:59:59,999 --> 99:59:59,999
So if you're in a team that has
gbp-based worflow,

59
99:59:59,999 --> 99:59:59,999
consider incorporating dgit push
and give this extremely useful thing

60
99:59:59,999 --> 99:59:59,999
to our users.

61
99:59:59,999 --> 99:59:59,999
Thanks !

62
99:59:59,999 --> 99:59:59,999
Right, next up is Judith,

63
99:59:59,999 --> 99:59:59,999
telling us "debian lenny
worth every penny".

64
99:59:59,999 --> 99:59:59,999
Ok

65
99:59:59,999 --> 99:59:59,999
The main issue about -

66
99:59:59,999 --> 99:59:59,999
I'm gonna talk about Debian Lenny -

67
99:59:59,999 --> 99:59:59,999
Is "will you able to fill five minutes
with it ?"

68
99:59:59,999 --> 99:59:59,999
But I'm prepared and I have a backup !

69
99:59:59,999 --> 99:59:59,999
So, who of you is still using Lenny ?

70
99:59:59,999 --> 99:59:59,999
Who of you plans to use Lenny ?

71
99:59:59,999 --> 99:59:59,999
(laughs)

72
99:59:59,999 --> 99:59:59,999
So that's great !

73
99:59:59,999 --> 99:59:59,999
Lenny is not completely abandonned.

74
99:59:59,999 --> 99:59:59,999
(??) What it was back in 2009 when it
was released ?

75
99:59:59,999 --> 99:59:59,999
Everyone was using it, and now

76
99:59:59,999 --> 99:59:59,999
you feel somehow lonely about it.

77
99:59:59,999 --> 99:59:59,999
And of course there are reasons for it.

78
99:59:59,999 --> 99:59:59,999
For example, it got security support
discontinued and doesn't does well.

79
99:59:59,999 --> 99:59:59,999
And of course, a lot of fancy stuff is
missing, like html5.

80
99:59:59,999 --> 99:59:59,999
This might not be an issue if you don't
like videos.

81
99:59:59,999 --> 99:59:59,999
And even if you would have support for
html5, probably you wouldn't have support

82
99:59:59,999 --> 99:59:59,999
for most of the codecs.

83
99:59:59,999 --> 99:59:59,999