9:59:59.000,9:59:59.000 welcome everyone 9:59:59.000,9:59:59.000 so this is the git-buildpackage skillshare BOF 9:59:59.000,9:59:59.000 and im hoping to take some notes here 9:59:59.000,9:59:59.000 im here basically as a facilitator 9:59:59.000,9:59:59.000 i dont plan to tell you exactly what you should do 9:59:59.000,9:59:59.000 what im hoping to do is to learn from everyone here 9:59:59.000,9:59:59.000 and we can all mutually get some practices ?? 9:59:59.000,9:59:59.000 maybe to get a sense of the room initally 9:59:59.000,9:59:59.000 so we all know who we are talking to 9:59:59.000,9:59:59.000 who here is currently maintaining a debian package 9:59:59.000,9:59:59.000 ok, and who here is thinking he might want to maintain 9:59:59.000,9:59:59.000 a debian package in the future but is not currently 9:59:59.000,9:59:59.000 maintaining one now 9:59:59.000,9:59:59.000 alright, cool, awesome 9:59:59.000,9:59:59.000 i really glad to have folks who are starting packaging 9:59:59.000,9:59:59.000 one now and are starting thinking how this workflow goes 9:59:59.000,9:59:59.000 ?? this people were just only packaging 9:59:59.000,9:59:59.000 so, of the peopl who are here packaging 9:59:59.000,9:59:59.000 how many people currently use git-buildpackage 9:59:59.000,9:59:59.000 but thats not everyone that currently packages 9:59:59.000,9:59:59.000 so its great that people are thinking about this 9:59:59.000,9:59:59.000 so if people have other packaging schemas that use version control 9:59:59.000,9:59:59.000 that they are currently using and that they are thinking of 9:59:59.000,9:59:59.000 ?? 9:59:59.000,9:59:59.000 or that are here just to troll us because your system is better 9:59:59.000,9:59:59.000 that is great and i want to hear what works for you and 9:59:59.000,9:59:59.000 other systems and workflows that 9:59:59.000,9:59:59.000 ?? point out analogies of things that work without git-buildpackages 9:59:59.000,9:59:59.000 or other tools that we can share and ?? 9:59:59.000,9:59:59.000 so ?? remain me... how many minutes this session is? 9:59:59.000,9:59:59.000 is it a 45 minutes session? do i hear 30? 9:59:59.000,9:59:59.000 I wonder if somebody want to take a crack at explaining 9:59:59.000,9:59:59.000 to people in the room who maybe dont yet use git-buildpackage 9:59:59.000,9:59:59.000 just briefly, if you could just try to do it in 2 sentences 9:59:59.000,9:59:59.000 what git-buildpackage means to you as a packager 9:59:59.000,9:59:59.000 what does it do for you as a maintainer 9:59:59.000,9:59:59.000 what is the thing that... pick a highlight, a short highlight 9:59:59.000,9:59:59.000 anyone want to volunteer to do that? someone that is currently using git-buildpackage 9:59:59.000,9:59:59.000 what does it do for you 9:59:59.000,9:59:59.000 - it ties tags together where either sbuilder or cowbuilder in a logical sense 9:59:59.000,9:59:59.000 - ok, so you have either sbuilder or cowbuilder integration with git-buildpackage 9:59:59.000,9:59:59.000 by the way, this is a path, i dont know if you can see this URL up here 9:59:59.000,9:59:59.000 i dont know how to embigger this part of my screen 9:59:59.000,9:59:59.000 but it is pad.riseup.net/p/ oh... there you go 9:59:59.000,9:59:59.000 anyway, hopefully folks have seen that and you can get it from ?? 9:59:59.000,9:59:59.000 I welcome other people to take notes because im going to miss 9:59:59.000,9:59:59.000 so you use sbuilder or cowbuilder with git-tags integration, right? 9:59:59.000,9:59:59.000 yeah, the main value for me is that it utilize?? 9:59:59.000,9:59:59.000 not to keep track of files on my own, right? 9:59:59.000,9:59:59.000 I can point tags for upstream for the package i want to build 9:59:59.000,9:59:59.000 ok, so somebody else? 9:59:59.000,9:59:59.000 - it takes care that i dont build packages with uncommited changes 9:59:59.000,9:59:59.000 so take the wrong thing, for example, that can happen 9:59:59.000,9:59:59.000 and that i wanted explicetly 9:59:59.000,9:59:59.000 - ok, great 9:59:59.000,9:59:59.000 - it builds ?? of your original tarballs if you are generating for snapshots 9:59:59.000,9:59:59.000 a repository includes the git understandable trees within your version 9:59:59.000,9:59:59.000 and it just generates ?? for you 9:59:59.000,9:59:59.000 - it cares about the pristine tar handeling for me, it cares about running uscan for me 9:59:59.000,9:59:59.000 - can you explain what pristine tar is people who dont know what it is? 9:59:59.000,9:59:59.000 - well, pristine tar saves a minimal set of data that 9:59:59.000,9:59:59.000 with the content of the git repository plus the delta, you can 9:59:59.000,9:59:59.000 reproduce bitwise orig tarball 9:59:59.000,9:59:59.000 - ok, and the reason we care about that is becauase 9:59:59.000,9:59:59.000 debian, their whole infrastructure is framed around upstream tarballs 9:59:59.000,9:59:59.000 whether thats how upstream distributes their code or not, 9:59:59.000,9:59:59.000 thats the way we think about upstream source code 9:59:59.000,9:59:59.000 so pristine tar says, we get this tarball from somewhere 9:59:59.000,9:59:59.000 and thats exactly how to get that ?? 9:59:59.000,9:59:59.000 so how many use uscan integration? 9:59:59.000,9:59:59.000 do you want to expalin how you do uscan integration 9:59:59.000,9:59:59.000 - import-orig, the sub command, has this option --uscan 9:59:59.000,9:59:59.000 - yeah, its already there 9:59:59.000,9:59:59.000 so uscan looks at the debian's watch file and looks for new versions of the 9:59:59.000,9:59:59.000 upstream source code via https or http or whatever 9:59:59.000,9:59:59.000 ?? 9:59:59.000,9:59:59.000 so just for people that havent maybe look at gbp before 9:59:59.000,9:59:59.000 the way you invoke it these days, you use gbp, thats git build package 9:59:59.000,9:59:59.000 and then you have sub command, this is very similar to git 9:59:59.000,9:59:59.000 where you have a command and then a subcommand 9:59:59.000,9:59:59.000 so there is gbp import-orig that says get upstream tarball and bring it into the repository 9:59:59.000,9:59:59.000 and put it in the repository in the gbp way 9:59:59.000,9:59:59.000 and then we have this other option that says 9:59:59.000,9:59:59.000 it goes automatically and fetches from the network 9:59:59.000,9:59:59.000 and also does the import-orig 9:59:59.000,9:59:59.000 theres some other things that gbp can do besides import-orig 9:59:59.000,9:59:59.000 build packages is another big one, so you say gbp buildpackage 9:59:59.000,9:59:59.000 and it does some of the checks that people where talking about to make sure 9:59:59.000,9:59:59.000 no additional files get mixed in ?? or changes that you werent expecting and got mixed in 9:59:59.000,9:59:59.000 it requires of course than when you are using git for packaging, you are paying attention to 9:59:59.000,9:59:59.000 what you are commited, if you go ahead and blindnly commited everything ?? 9:59:59.000,9:59:59.000 - I like to mention the third important 9:59:59.000,9:59:59.000 - alright, this is the longes phrase i have ever heard 9:59:59.000,9:59:59.000 - where you can also import-dsc which import a complete debian source package 9:59:59.000,9:59:59.000 for example, if you take a package from someone else who hasnt use git before for packaging 9:59:59.000,9:59:59.000 you can import his source package and ?? your packaging with it 9:59:59.000,9:59:59.000 you can also import multiple with dscs and that one has a nice option to your snapsshot.d.o 9:59:59.000,9:59:59.000 --debsnap and you get push the package name and it pushes the whole history of that package 9:59:59.000,9:59:59.000 in your fresh to be created repository for packigng 9:59:59.000,9:59:59.000 if i have to take over some legacy package 9:59:59.000,9:59:59.000 - ok, this is exactly why i wanted to take this discussion 9:59:59.000,9:59:59.000 I had no idea ?? which is great 9:59:59.000,9:59:59.000 - they call it RTFM, right? 9:59:59.000,9:59:59.000 - so maybe that was only new to me and everybody already knew it 9:59:59.000,9:59:59.000 this whole sessions is teach dkg sesion. Anything else you want to teach me? 9:59:59.000,9:59:59.000 Anybody want to sum up how gbp works for them, what things does 9:59:59.000,9:59:59.000 Do you want to step in some workflows that maybe look at gbp ?? 9:59:59.000,9:59:59.000 ?? maybe some problems you have encountered 9:59:59.000,9:59:59.000 you are in your day to day work ?? 9:59:59.000,9:59:59.000 now and then we have a problem with[br]the import of the upstream tarballs 9:59:59.000,9:59:59.000 because git goes crazy and ?? 9:59:59.000,9:59:59.000 - its php[br]- it might be, but its only how import, so 9:59:59.000,9:59:59.000 you cant blame the language,[br]not this time at least 9:59:59.000,9:59:59.000 so what it is the problem with it?[br]you import the upstream tarball 9:59:59.000,9:59:59.000 - ?? for me 9:59:59.000,9:59:59.000 it just gives a problem and versions conflict 9:59:59.000,9:59:59.000 and it doesnt want to apply all the changes 9:59:59.000,9:59:59.000 maybe something we do wrong 9:59:59.000,9:59:59.000 ?? 9:59:59.000,9:59:59.000 dkg: Im embarrassed to say that[br]i dont know who is on the team 9:59:59.000,9:59:59.000 that is maintaining gbp. Are they here? 9:59:59.000,9:59:59.000 [laughs] 9:59:59.000,9:59:59.000 thank you very much. 9:59:59.000,9:59:59.000 Do you know about this issue[br]with the php team 9:59:59.000,9:59:59.000 - no, i dont but if you have a weird history 9:59:59.000,9:59:59.000 theres a new thing that is merge ??[br]that doesnt care about history 9:59:59.000,9:59:59.000 it just download the whole upstream tree[br]into the debian branch 9:59:59.000,9:59:59.000 but it will be keeping the debian ?? 9:59:59.000,9:59:59.000 so you cant have any merge issues[br]- okay 9:59:59.000,9:59:59.000 - I had this long standing problem with