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

9:59:59.000,9:59:59.000