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 

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

23
00:01:00,882 --> 00:01:02,605
Right? That's one of the things we ensure

24
00:01:02,605 --> 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
00:01:11,618 --> 00:01:14,282
in particular, like you can't
commit things

28
00:01:14,373 --> 00:01:15,506
and then revert them

29
00:01:15,518 --> 00:01:16,881
you can't make branches

30
00:01:17,407 --> 00:01:22,705
you can't manipulate the source
in all the ways you can with git.

31
00:01:23,150 --> 00:01:26,640
So, often what I think people will probably do

32
00:01:26,711 --> 00:01:29,656
is apt-get source and then just
commit everything to git.

33
00:01:30,499 --> 00:01:33,818
Now, dgit clone is kind of a
shortcut there

34
00:01:33,818 --> 00:01:37,838
so dgit clone will "apt-get source" and
commit it to git, roughly.

35
00:01:37,913 --> 00:01:39,277
(there's more stuff going on)

36
00:01:39,322 --> 00:01:41,542
But that's one way to understand it.

37
00:01:41,547 --> 00:01:45,327
And that's the git history you get,
if you type dgit clone

38
00:01:45,420 --> 00:01:48,990
when the maintainer just uploaded
the package with dput.

39
00:01:49,061 --> 00:01:52,575
So, it's kind of useful, it's in git now,
so you can type git clean

40
00:01:52,575 --> 00:01:54,325
and it's pretty convenient.

41
00:01:54,350 --> 00:01:56,960
But I think we could do a lot better for
our users.

42
00:01:56,989 --> 00:01:59,369
We could give them the whole packaging
history

43
00:01:59,425 --> 00:02:01,515
and eventually even the upstream history.

44
00:02:03,635 --> 00:02:06,755
Which is a lot powerful for debugging
problems on their system.

45
00:02:06,858 --> 00:02:11,568
So, that's what you get when you do dgit
clone, when it wasn't dgit-pushed.

46
00:02:11,583 --> 00:02:13,373
What happens when it was ?

47
00:02:13,675 --> 00:02:15,001
Well, that's what you get.

48
00:02:15,021 --> 00:02:18,821
If someone like I did, typed "dgit push",

49
00:02:18,850 --> 00:02:21,600
then, when the user types "dgit clone",

50
00:02:21,673 --> 00:02:25,423
they get this rich history, which is
useful information, for debugging,

51
00:02:25,491 --> 00:02:28,811
making reverts, and upstream changes
for example, and then trying build it.

52
00:02:29,126 --> 00:02:31,139
Or, you know, that kind of stuff.

53
00:02:31,537 --> 00:02:34,945
And as you see, the dgit push command
has gbp in it.

54
00:02:35,138 --> 00:02:41,374
Like this wasn't a fancy git-debrebase
workflow or anything like that.

55
00:02:41,496 --> 00:02:44,398
All I did was drop dgit --gbp push

56
00:02:44,461 --> 00:02:47,514
into my existing team gbp workflow.

57
00:02:47,514 --> 00:02:50,234
So if you're in a team that has
gbp-based workflow,

58
00:02:50,347 --> 00:02:54,687
consider incorporating dgit push
and give this extremely useful thing

59
00:02:54,751 --> 00:02:56,071
to our users.

60
00:02:56,094 --> 00:02:57,764
Thanks !

61
00:03:14,090 --> 00:03:16,979
Right, next up is Judit,

62
00:03:17,135 --> 00:03:20,445
telling us "debian lenny
worth every penny".

63
00:04:16,803 --> 00:04:19,156
OK. The main issue about -

64
00:04:19,236 --> 00:04:21,192
I'm gonna talk about Debian Lenny -

65
00:04:21,246 --> 00:04:25,356
(which) is "will you able to fill five minutes
with it ?"

66
00:04:25,442 --> 00:04:28,642
But I'm prepared and I have a backup !

67
00:04:31,897 --> 00:04:34,832
So, who of you is still using Lenny ?

68
00:04:36,359 --> 00:04:42,313
Who of you plans to use Lenny ?

69
00:04:42,553 --> 00:04:45,523
[laughs]

70
00:04:48,800 --> 00:04:49,822
So that's great !

71
00:04:49,822 --> 00:04:52,934
So. Lenny is not completely abandonned.

72
00:04:54,249 --> 00:04:58,401
(??) What it was back in 2009 when it
was released ?

73
00:04:59,691 --> 00:05:03,618
Everyone was using it, and now

74
00:05:06,123 --> 00:05:09,431
you feel somehow lonely about it.

75
00:05:09,434 --> 00:05:12,534
And of course there are reasons for it.

76
00:05:15,926 --> 00:05:23,774
For example, it got security support
discontinued and doesn't do well.

77
00:05:26,935 --> 00:05:31,890
And of course, a lot of fancy stuff is
missing, like html5.

78
00:05:33,362 --> 00:05:36,394
This might not be an issue if you don't
like videos.

79
00:05:37,737 --> 00:05:44,627
And even if you would have support for
html5, probably you wouldn't have support

80
00:05:44,627 --> 00:05:46,403
for most of the codecs.

81
00:05:48,972 --> 00:05:51,899
Of course, you don't have these emoji thingies

82
00:05:51,923 --> 00:05:54,288
which also could upset you

83
00:05:56,106 --> 00:05:58,144
The worst issue is that...

84
00:05:58,184 --> 00:06:04,866
about... I think,
65% of the web is not usable(?) for you

85
00:06:05,045 --> 00:06:09,324
because you do not have the (??)

86
00:06:10,417 --> 00:06:13,660
And, you're missing the recent CSS

87
00:06:14,134 --> 00:06:17,249
which means the DebConf page looks like this.

88
00:06:23,599 --> 00:06:26,269
And it's supposed to look like... this.

89
00:06:26,512 --> 00:06:27,490
[laughs]

90
00:06:29,431 --> 00:06:32,531
Of course it also has upsides (half-jokingly)

91
00:06:32,696 --> 00:06:34,305
[laughs again]