< Return to Video

gitbuildpackage_skillshare.webm

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

English subtitles

Incomplete

Revisions Compare revisions