WEBVTT 00:00:05.535 --> 00:00:08.295 Good afternoon. Can you hear me? 00:00:10.406 --> 00:00:12.456 Good afternoon. Sorry for the delay. 00:00:12.626 --> 00:00:14.596 Welcome to Lightning Talks! 00:00:14.786 --> 00:00:17.476 We have... 5 people doing 6 things, 00:00:17.476 --> 00:00:18.936 and first up is Sean. 00:00:23.343 --> 00:00:24.203 Hello! 00:00:24.203 --> 00:00:25.283 Uh, I'm Sean. 00:00:25.833 --> 00:00:26.813 Um, so, 00:00:26.893 --> 00:00:28.963 Dgit is a multifaceted project 00:00:29.083 --> 00:00:31.303 trying to solve a lot of problems at once 00:00:31.422 --> 00:00:33.432 and the source package certainly is (one of those) 00:00:35.255 --> 00:00:37.165 I wanted to briefly talk about 00:00:37.240 --> 00:00:40.090 one of the things that dgit makes better, that 00:00:40.318 --> 00:00:42.258 is the reason why you should consider 00:00:42.357 --> 00:00:44.127 incorporating dgit push 00:00:44.175 --> 00:00:46.235 into your existing workflows. 00:00:46.387 --> 00:00:49.257 So, one of the things that we offer our users 00:00:49.733 --> 00:00:51.313 in our stable releases 00:00:51.559 --> 00:00:54.519 is that(?) we say: Look, we are going to make sure 00:00:54.519 --> 00:00:56.449 that you can do apt-get source, 00:00:56.510 --> 00:00:59.100 apt-get build-dep <package name> 00:00:59.226 --> 00:01:00.806 and then, it will (be) built 00:01:00.882 --> 00:01:02.605 Right? That's one of the things we ensure 00:01:02.605 --> 00:01:04.255 and it's a nasty bug if that doesn't work. 00:01:05.587 --> 00:01:08.697 But, apt-get source is a pretty old-fashioned way 00:01:08.739 --> 00:01:11.379 to get a source for something running on your computer. 00:01:11.618 --> 00:01:14.282 in particular, like you can't commit things 00:01:14.373 --> 00:01:15.506 and then revert them 00:01:15.518 --> 00:01:16.881 you can't make branches 00:01:17.407 --> 00:01:22.705 you can't manipulate the source in all the ways you can with git. 00:01:23.150 --> 00:01:26.640 So, often what I think people will probably do 00:01:26.711 --> 00:01:29.346 is apt-get source and then just commit everything to git. 00:01:30.499 --> 00:01:33.818 Now, dgit clone is kind of a shortcut there 00:01:33.818 --> 00:01:37.838 so dgit clone will "apt-get source" and commit it to git, roughly. 00:01:37.913 --> 00:01:39.277 (there's more stuff going on) 00:01:39.322 --> 00:01:41.542 But that's one way to understand it. 00:01:41.547 --> 00:01:45.327 And that's the git history you get, if you type dgit clone 00:01:45.420 --> 00:01:48.990 when the maintainer just uploaded the package with dput. 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 00:01:52.575 --> 00:01:54.325 and it's pretty convenient. 00:01:54.350 --> 00:01:56.960 But I think we could do a lot better for our users. 00:01:56.989 --> 00:01:59.369 We could give them the whole packaging history 00:01:59.425 --> 00:02:01.515 and eventually even the upstream history. 00:02:03.635 --> 00:02:06.755 Which is a lot powerful for debugging problems on their system. 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. 00:02:11.583 --> 00:02:13.373 What happens when it was ? 00:02:13.675 --> 00:02:15.001 Well, that's what you get. 00:02:15.021 --> 00:02:18.821 If someone like I did, typed "dgit push", 00:02:18.850 --> 00:02:21.600 then, when the user types "dgit clone", 00:02:21.673 --> 00:02:25.423 they get this rich history, which is useful information, for debugging, 00:02:25.491 --> 00:02:28.811 making reverts, and upstream changes for example, and then trying build it. 99:59:59.999 --> 99:59:59.999 Or, you know, that kind of stuff. 99:59:59.999 --> 99:59:59.999 And as you see, the dgit push command has gbp in it. 99:59:59.999 --> 99:59:59.999 Like this wasn't a fancy git (??)ry-based workflow or anything like that. 99:59:59.999 --> 99:59:59.999 All I did was drop dgit --gbp push 99:59:59.999 --> 99:59:59.999 in my existing team gbp workflow. 99:59:59.999 --> 99:59:59.999 So if you're in a team that has gbp-based worflow, 99:59:59.999 --> 99:59:59.999 consider incorporating dgit push and give this extremely useful thing 99:59:59.999 --> 99:59:59.999 to our users. 99:59:59.999 --> 99:59:59.999 Thanks ! 99:59:59.999 --> 99:59:59.999 Right, next up is Judith, 99:59:59.999 --> 99:59:59.999 telling us "debian lenny worth every penny". 99:59:59.999 --> 99:59:59.999 Ok 99:59:59.999 --> 99:59:59.999 The main issue about - 99:59:59.999 --> 99:59:59.999 I'm gonna talk about Debian Lenny - 99:59:59.999 --> 99:59:59.999 Is "will you able to fill five minutes with it ?" 99:59:59.999 --> 99:59:59.999 But I'm prepared and I have a backup ! 99:59:59.999 --> 99:59:59.999 So, who of you is still using Lenny ? 99:59:59.999 --> 99:59:59.999 Who of you plans to use Lenny ? 99:59:59.999 --> 99:59:59.999 (laughs) 99:59:59.999 --> 99:59:59.999 So that's great ! 99:59:59.999 --> 99:59:59.999 Lenny is not completely abandonned. 99:59:59.999 --> 99:59:59.999 (??) What it was back in 2009 when it was released ? 99:59:59.999 --> 99:59:59.999 Everyone was using it, and now 99:59:59.999 --> 99:59:59.999 you feel somehow lonely about it. 99:59:59.999 --> 99:59:59.999 And of course there are reasons for it. 99:59:59.999 --> 99:59:59.999 For example, it got security support discontinued and doesn't does well. 99:59:59.999 --> 99:59:59.999 And of course, a lot of fancy stuff is missing, like html5. 99:59:59.999 --> 99:59:59.999 This might not be an issue if you don't like videos. 99:59:59.999 --> 99:59:59.999 And even if you would have support for html5, probably you wouldn't have support 99:59:59.999 --> 99:59:59.999 for most of the codecs.