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