bzr builddeb --in-15-minutes with james_w

   1 [12:59] <james_w> hi everyone
   2 [12:59] <Tumie> hi
   3 [13:00] <darkwise> hi
   4 [13:00] <RainCT> hi
   5 [13:00] <james_w> who's here for the packaging training session?
   6 [13:00] <deto> me
   7 [13:00] <Plague> hi, me i quess
   8 [13:00] <jimjeeves> I am
   9 [13:00] <JanTar> ye, me too
  10 [13:00] <piti> is that now ?
  11 [13:00] <blfgomes> I am
  12 [13:00] <Tumie> me too
  13 [13:00] <dave_sn> here
  14 [13:01] <james_w> wow, large crowd :-)
  15 [13:01] <james_w> so, I'm down to do a 15 minute session on bzr-builddeb
  16 [13:01] <lfelipe> hey
  17 [13:02] <james_w> this is a tool that I wrote to help with building packages from bzr branches
  18 [13:02] <james_w> is everyone interested in that?
  19 [13:02] <jimjeeves> yes
  20 [13:02] <Rafik> sure
  21 [13:02] <Rail> yes :)
  22 [13:02] <psicus78> yes
  23 [13:02] <darkwise> sure
  24 [13:02] <james_w> we can use the rest of the time after for general questiong
  25 [13:02] <deto> yep
  26 [13:02] <james_w> excellent
  27 [13:02] <dave_sn> yes
  28 [13:03] <james_w> so, first things first, why don't you all install the "bzr-builddeb" package while I talk a little about it
  29 [13:03] <james_w> is there anyone that doesn't know what bzr is?
  30 [13:03] <k-s> sure
  31 [13:03] <Tumie> i don't know bzr
  32 [13:03] <james_w> ok, let's start there
  33 [13:03] <james_w> bzr (http://bazaar-vcs.org/) is a version control system
  34 [13:04] <james_w> this allows you to keep snapshots of your work, and then to look back over them
  35 [13:04] <james_w> bzr is a very good one :-)
  36 [13:04] <james_w> in particular it is a "distributed" version control system
  37 [13:05] <james_w> what this means is that all of us are collaborating on a project, then we each get a "branch" of the project
  38 [13:05] <james_w> in that branch we work on the things that we are interested in
  39 [13:05] <james_w> so you can implement one feature, while I am working on another, and someone else is fixing bugs
  40 [13:06] <james_w> then we can all "merge" from each other, and bzr will use the historical information that we store to integrate all our work
  41 [13:06] <james_w> it isn't always possible to do this without human intervention, so it will sometimes ask us to help out
  42 [13:06] <james_w> so using this for developing Ubuntu can be very useful
  43 [13:07] <james_w> you can grab a branch of the package that you want to work on, and make your changes. You can then ask for a review, and if the reviewer asks you to change a few things then you can do so and ask again for review
  44 [13:07] <james_w> you can keep doing it until the reviewer is happy
  45 [13:07] <james_w> they can then take your branch and merge it to the main branch for the package
  46 [13:08] <james_w> so, lets have a look at what this might look like
  47 [13:08] <james_w> I maintain a site called "package-import.ubuntu.com" currently
  48 [13:08] <james_w> http://package-import.ubuntu.com/
  49 [13:08] <james_w> on there is a branch of every source package in Ubuntu
  50 [13:09] <james_w> we are working to make these available on launchpad
  51 [13:09] <james_w> you should all have "bzr" installed now if you installed "bzr-builddeb"
  52 [13:10] <james_w> you can check that by running "bzr help" at the command line
  53 [13:10] <james_w> so, to get ourselves a branch of a package we use the "bzr branch" command
  54 [13:10] <james_w> so everyone try:
  55 [13:10] <james_w> bzr branch http://package-import.canonical.com/s/ssss/jaunty
  56 [13:11] <james_w> that gets us a branch that corresponds to what is in the "ssss" package in Jaunty
  57 [13:11] <james_w> once that completes you should have a "jaunty" directory in your current directory
  58 [13:11] <james_w> everyone got that?
  59 [13:11] <HerbY_NL> yes
  60 [13:12] <Tumie> jes
  61 [13:12] <burun0> yes
  62 [13:12] <Tumie> *yes
  63 [13:12] <shankhs> ya
  64 [13:12] <jimjeeves> yes
  65 [13:12] <darkwise> yes
  66 [13:12] <Rafik> yes
  67 [13:12] <james_w> excellent :-)
  68 [13:12] <jimjeeves>     *
  70 [13:12] <james_w> so, lets check we can build it
  71 [13:12] <james_w> if you "cd jaunty" and then run "bzr builddeb"
  72 [13:12] <james_w> it should build the package for you
  73 [13:13] <psicus78> i didn't got it
  74 [13:13] <james_w> psicus78: did you run the "bzr branch" command? Did it give you an error?
  75 [13:13] <shankhs> me too its giving error
  76 [13:13] <psicus78> (14:09:55) james_w: you should all have "bzr" installed now if you installed "bzr-builddeb" nothing more after this
  77 [13:13] <HerbY_NL> here also error
  78 [13:13] <RainCT> dpkg-buildpackage: warning: Build dependencies/conflicts unsatisfied; aborting.    - this one?
  79 [13:13] <shankhs> bzr: ERROR: unknown command "builddeb"
  80 [13:13] <jimjeeves> yes
  81 [13:14] <james_w> shankhs: it seems you don't have the "bzr-builddeb" package installed
  82 [13:14] <dave_sn> what if we're on hardy
  83 [13:14] <shankhs> james_w: ok
  84 [13:14] <james_w> psicus78: I will PM you the text in between
  85 [13:14] <plars> dpkg-checkbuilddeps: Unmet build dependencies: libgmp3-dev xmltoman quilt (>= 0.40)
  86 [13:14] <jimjeeves> I also get "dpkg-buildpackage: warning: Build dependencies/conflicts unsatisfied; aborting."
  87 [13:14] <psicus78> james_w: i didn't receive the message where you say what to branch
  88 [13:14] <psicus78> james_w: ok
  89 [13:14] <Tumie> bzr: ERROR: The build failed.
  90 [13:15] <james_w> ok
  91 [13:15] <blfgomes> sudo apt-get install libgmp3-dev xmltoman quilt
  92 [13:15] <james_w> so we don't have the "Build-Depends" installed
  93 [13:15] <HerbY_NL> to correct error: sudo apt-get install debhelper
  94 [13:15] <james_w> you can either do what blfgomes has suggested
  95 [13:15] <james_w> or use "apt-get build-dep ssss"
  96 [13:15] <HerbY_NL> package build ok after rest install
  97 [13:15] <blfgomes> cool, didn't know that one :)
  98 [13:16] <james_w> or you could just build a source package with "bzr builddeb -S"
  99 [13:16] <james_w> that will show the mechanism, but won't involve the extra packages
 100 [13:16] <james_w> ok, so that's 15 minutes
 101 [13:16] <posingaspopular>  bzr branch
 102 [13:16] <posingaspopular> bzr: ERROR: command 'branch' requires argument FROM_LOCATION
 103 [13:17] <james_w> I can show you a bit more of this, or we can move on to Q+A
 104 [13:17] <james_w> posingaspopular: you need "bzr branch http://package-import.ubuntu.com/s/ssss/jaunty"
 105 [13:17] <posingaspopular> thanks
 106 [13:18] <jimjeeves> Ok, "bzr builddeb" has worked for me now.
 107 [13:18] <james_w> excellent
 108 [13:18] <jimjeeves> it would be quite good for me to see more of this, pleas
 109 [13:18] <darkwise> james_w: " I can show you a bit more of this"  => +1
 110 [13:18] <james_w> ok, another 15 minutes of bzr-builddeb?
 111 [13:18] <shankhs> darkwise: +1
 112 [13:18] <jimjeeves> yes please
 113 [13:19] <james_w> I'm here to serve you people :-)
 114 [13:19] <blfgomes> it didn't work for me
 115 === _Purple_ is now known as _Purple_away
 116 [13:19] <shankhs> james_w: ya
 117 [13:19] <james_w> blfgomes: did you get an error?
 118 [13:19] <blfgomes> gpg: skipped "James Westby <jw+debian@jameswestby.net>": secret key not available
 119 [13:19] <blfgomes> gpg: [stdin]: clearsign failed: secret key not available
 120 [13:19] <james_w> ah
 121 [13:19] <Rail> it worked actually :)
 122 [13:19] <james_w> so
 123 [13:19] <james_w> this is a common issue, not just with bzr-builddeb
 124 [13:20] <blfgomes> Rail: it actually said "bzr: ERROR: The build failed." at the end
 125 [13:20] <james_w> "debian/changelog" says that I changed the package, so it wants me to sign it, but you aren't me, and you don't have my secret key, so you can't
 126 === Pollywog_ is now known as pollywog
 127 [13:20] <james_w> so really at this point you want to build it without signing it
 128 [13:21] <james_w> you can do that with "bzr bd -S -- -uc -us" on Jaunty
 129 [13:21] <james_w> err, "bzr bd -- -uc -us" to build the binary package as you were doing, sorry
 130 [13:21] <Rail> ...or ignore thas message
 131 [13:21] <blfgomes> james_w, I can see why that happened... I just don't get why I'm the only one that got this error
 132 [13:21] <james_w> those on Intrepid or earlier won't have seen that
 133 [13:21] <blfgomes> oh, alright
 134 [13:21] <j1mc> i got an error, debuild: fatal error at line 1329:
 135 [13:21] <j1mc> dpkg-buildpackage -rfakeroot -D -us -uc failed
 136 [13:21] <james_w> blfgomes: it seems you are the only one running Jaunty :-)
 137 [13:21] <blfgomes> that explains it
 138 [13:21] <Tumie> i only have errors..
 139 [13:22] <james_w> j1mc: is there another error in the output?
 140 [13:22] <james_w> I haven't seen "-D" before
 141 [13:22] <fabiodmt> quit
 142 [13:22] <james_w> I'm not sure where that came from
 143 [13:22] <psicus78> I'm running jaunty and it ran fine with uc and us options
 144 [13:22] <shankhs> how to install bzr-builddeb?( i tried sudo apt-get install bzr-builddeb it didnt work)
 145 [13:22] <j1mc> ah, there are some unmet build dependencies.  i'll grab them
 146 [13:22] <Tumie> input: bzr builddeb output: bzr: ERROR: The build failed.
 147 [13:22] <james_w> Tumie: can you pastebin the whole output of the command please?
 148 [13:23] <Tumie> http://paste.ubuntu.com/147630/
 149 [13:23] <james_w> shankhs: it should do, it is in the repositories, did it say it didn't exist, or that it couldn't be installed?
 150 [13:23] <Rail> james_w: what's the magic of upstream tarball retrieving? debian/watch?
 151 [13:24] <james_w> Rail: in this case it uses "apt-get", it can also use debian/watch, yes
 152 [13:24] <shankhs> james_w: Couldn't find package bzr-buliddeb
 153 [13:24] <RainCT> shankhs: typo in there :)
 154 [13:24] <james_w> shankhs: ah, make sure you typed "sudo apt-get install bzr-builddeb"
 155 [13:24] <james_w> I realise it's not the easiest thing to type :-)
 156 [13:24] <j1mc> i'm good now.  :)
 157 [13:25] <posingaspopular> error: http://paste.ubuntu.com/147631/
 158 [13:25] <shankhs> james_w: thankhs
 159 [13:25] <shankhs> james_w: :)
 160 [13:25] <james_w> Tumie: ah, you need to install the "quilt" package, sorry. That is one of the build-dependencies, but you also need it to build the source package
 161 [13:25] <james_w> posingaspopular: you too
 162 [13:26] <posingaspopular> thanks :P
 163 [13:26] <Tumie> how to build the source package ?
 164 [13:26] <james_w> ok, anyone not managed to get it to build yet?
 165 [13:27]  * j1mc is ok
 166 [13:27] <james_w> Tumie: you did it :-) it was "bzr builddeb -S"
 167 [13:27] <Tumie> ok
 168 [13:27] <Rail> james_w: what's the preferred method of versioning packages: keeping the whole sources + debian dir or just debian and use --merge?
 169 [13:27] <shankhs> james_w: Where can I find the log of "bzr builddeb"?
 170 [13:27] <Rail> (for non-native packages of course)
 171 [13:28] <posingaspopular> k it build properly
 172 [13:28] <james_w> Rail: my preferred method is the whole source, some people prefer the latter. I prefer the former as it is not working against the version control system. With the latter you sometimes have to do things by hand that bzr could automate for you
 173 [13:28] <james_w> Rail: good question though
 174 [13:28] <james_w> shankhs: it doesn't save a log of its own operation
 175 [13:29] <james_w> ok, those who have built it, you can look at the history
 176 [13:29] <darkwise> james_w : can we install  builddeb if we're not on a debian like Linux ?
 177 [13:29] <shankhs> james_w: OK
 178 [13:29] <james_w> try "bzr log", or install "bzr-gtk" and look at "bzr viz", or if you prefer Qt then install "qbzr" and look at "bzr qlog"
 179 [13:30] <james_w> you can see there a summary of changes made to the package, and you can get diffs between versions easily
 180 [13:30] <posingaspopular> win 12
 181 [13:30] <james_w> darkwise: you can, though it's not packaged anywhere else. It also depends on various tools that will only normally exist on a Debian like distro, so you would have to install them too
 182 [13:31] <darkwise> james_w : thanks
 183 [13:31] <sky_walkie> I've got this:
 184 [13:31] <sky_walkie> dpkg-checkbuilddeps: Unmet build dependencies: debhelper (>= 5.0) libgmp3-dev xmltoman quilt (>= 0.40)
 185 [13:31] <sky_walkie> dpkg-buildpackage: warning: Build dependencies/conflicts unsatisfied; aborting.
 186 [13:31] <sky_walkie> dpkg-buildpackage: warning: (Use -d flag to override.)
 187 [13:31] <sky_walkie> debuild: fatal error at line 1329:
 188 [13:31] <sky_walkie> dpkg-buildpackage -rfakeroot -D -us -uc failed
 189 [13:31] <sky_walkie> bzr: ERROR: The build failed.
 190 [13:32] <sky_walkie> which probably means install that stuff to get things working ?
 191 [13:32] <posingaspopular> sky_walkie: sudo apt-get install libgmp3-dev xmltoman quilt
 192 [13:32] <Rafik> yes
 193 [13:32] <sky_walkie> thanks
 194 [13:32] <Rail> james_w: you mentioned "bzr could automate". What kind of automation you mean?
 195 [13:33] <pollywog> is there a metapackage that will install everything we need?
 196 [13:33] <james_w> Rail: say when you package a new upstream release. If you have patches to the upstream software then it can be tedious to go through each, check if it has been fully applied upstream, and resolve conflicts where necessary. bzr was built to do that sort of thing, so it's a lot easier.
 197 [13:34] <blfgomes> pollywog: apt-get build-dep ssss
 198 [13:34] <pollywog> ty
 199 [13:34] <Rail> james_w: you mean when upstream uses bzr?
 200 [13:34] <sky_walkie> well now I've got this error:
 201 [13:34] <sky_walkie> dpkg-buildpackage: warning: (Use -d flag to override.)
 202 [13:34] <sky_walkie> debuild: fatal error at line 1329:
 203 [13:34] <sky_walkie> dpkg-buildpackage -rfakeroot -D -us -uc failed
 204 [13:34] <sky_walkie> bzr: ERROR: The build failed.
 205 [13:35] <sky_walkie> so I've used -d option
 206 [13:35] <sky_walkie> and got this:
 207 [13:35] <sky_walkie> make: dh_testdir: Command not found
 208 [13:35] <sky_walkie> make: *** [clean-patched] Error 127
 209 [13:35] <sky_walkie> dpkg-buildpackage: failure: fakeroot debian/rules clean gave error exit status 2
 210 [13:35] <sky_walkie> debuild: fatal error at line 1329:
 211 [13:35] <sky_walkie> dpkg-buildpackage -rfakeroot -d -us -uc failed
 212 [13:35] <sky_walkie> bzr: ERROR: The build failed.
 213 [13:35] <Rail> sky_walkie: pastebin is great ;)
 214 [13:35] <james_w> Rail: it doesn't really matter. bzr-builddeb also allows you to package a new upstream from a tarball almost as if it was a branch.
 215 [13:35] <james_w> sky_walkie: ah, you also need to install "debhelper"
 216 [13:36] <sky_walkie> ok
 217 [13:36] <Rail> james_w: ah, ok, I need to refresh my bzr-builddeb knowledge :)
 218 [13:37] <james_w> Rail: yeah, that sort of stuff is just coming together. I need to iron out the kinks and document it better
 219 [13:37] <james_w> ok, does anyone have any questions?
 220 [13:37] <blfgomes> james_w: you said you planned to make every source package available on launchpad. How will that work?
 221 [13:37] <james_w> I'm happy to answer general packaging questions
 222 [13:37] <psicus78> james_w: I have one
 223 [13:37] <james_w> so if you are stuck on something then speak up
 224 [13:37] <j1mc> james_w: so bzr builddeb just grabs the tarball via the url of the upstream source package, and builds it for you?  is this done primarily for testing purposes?  you then need to update the changelog and stuff, right?
 225 [13:37] <frogfoot> How do I make the debian/rules file?
 226 [13:38] <frogfoot> the default one does not always work
 227 [13:38] <james_w> blfgomes: launchpad has a code hosting service for bzr, and one of the launchpad developers is currently working on making it support package branches well (not in terms of storage as such, but in terms of UI)
 228 [13:38] <james_w> blfgomes: once that is done we will migrate the branches to being stored on launchpad
 229 [13:39] <sky_walkie> <james_w> thanks no I've deb package
 230 [13:39] <sky_walkie> now
 231 [13:39] <james_w> sky_walkie: excellent
 232 === _Purple_away is now known as _Purple_
 233 [13:40] <blfgomes> james_w: oh, I thought you were trying to persuade developers to use bzr :)
 234 [13:40] <james_w> j1mc: it builds whatever is in the branch, but we also require a tarball to get the source package correct, so we automate fetching that where possible. The normal packaging tasks of updating changelog etc. are still pretty much the same
 235 [13:40] <RachedTN> james_w: when I try this command :  sudo bzr branch http://package-import.canonical.com/s/ssss/jaunty   I get this error : bzr: ERROR: Unknown branch format: 'Bazaar Branch Format 7 (needs bzr 1.6)\n'
 236 [13:40] <sky_walkie> so if I understand well, this is related to packages localted in bazaar only
 237 [13:40] <james_w> psicus78: shoot
 238 [13:41] <psicus78> james_w: j1mc asked the question I wanted to ask :)
 239 [13:41] <james_w> RachedTN: ah, you don't have a new enough bzr installed. I forgot about that requirement, sorry. There is a PPA with backports available if you like.
 240 [13:41] <pollywog> is bzr better than the traditional tools such as pbuilder or are they used for different things?
 241 [13:41] <james_w> blfgomes: I am :-)
 242 [13:41] <menesis> I have more than a hundred packages of zope modules. If I were to turn them into bzr-builddeb debian/-only branches and put into Launchpad, do I have to create a project for each of them?
 243 [13:42] <james_w> sky_walkie: bzr-builddeb is for use with bzr branches, yes, (though it works on SVN as well if you have bzr-svn installed)
 244 [13:42] <RachedTN> james_w: yes, I like to add it, could you please tell me :)
 245 [13:42] <james_w> pollywog: these are used for different things. You can make bzr-builddeb run pbuilder if you like
 246 [13:42] <james_w> RachedTN: there are links from "https://launchpad.net/bzr"
 247 [13:42] <sky_walkie> so if I've my onw bazaar configured with some source code than this bzr appz will do the rest to build ubuntu package
 248 [13:43] <james_w> menesis: not necessarily, you could put them all under one project
 249 [13:43] <RachedTN> thanks james_w and keep the good work man, it's reallly helpful and beautiful too :)
 250 [13:44] <james_w> frogfoot: hi, the debian/rules file is hard to create automatically. The default one from dh-make is primarily designed for packages that have a ./configure script and Makefile. If you don't have those then you need to tweak those lines to what is equivalent for your package.
 251 [13:44] <james_w> frogfoot: if you have an example package then I can give some more direct suggestions
 252 [13:45] <Rail> james_w: another one: I use quilt and debian/patches for "true" packaging :). Is there any way to automate preparation of patches?
 253 [13:45] <Rail> quilt add file file file; quilt refresh is boring :)
 254 [13:45] <james_w> sky_walkie: if you already have the packaging done, then yes it can build you the packages. It doesn't make writing the packaging any easier though, sorry :-)
 255 [13:45] <james_w> Rail: I agree :-). There is nothing like that yet, I would like to add it, but I'm not too sure what it should look like.
 256 [13:46] <james_w> Rail: you might be interested in http://vcs-pkg.org/ which aims to discuss that sort of thing
 257 [13:47] <Rail> james_w: thanks a lot
 258 [13:47] <psicus78> james_w: why do I get output files both in build-area and in the directory on top of jaunty?
 259 [13:48] <james_w> psicus78: it's a bit unfortunate, but necessary. It needs a temporary directory to do the work so that it doesn't mangle any of your precious files, so it uses build-area for that
 260 [13:48] <james_w> you should be able to delete it with no ill-effects
 261 [13:49] <james_w> it could use a real tempdir that it deletes before finishing, but it is sometimes useful to be able to look inside that directory, so it uses build-area to make that easy
 262 [13:49] <psicus78> ah ok, no problems, just asking...I thought the good files were those in build area... :)
 263 [13:49] <psicus78> are they always the same?
 264 [13:50] <james_w> as a last step it tries to copy them from build-area to .., so they should be
 265 [13:50] <james_w> it doesn't always work as we would like though :-)
 266 [13:50] <psicus78> james_w: ok, last question
 267 [13:51] <psicus78> just to understand if I figured out correctly. When I branch I get only debian dir and some other files
 268 [13:51] <psicus78> are those the ones that I patched to build the package?
 269 [13:51] <psicus78> namely, the files that differs from upstream?
 270 [13:51] <james_w> nope, with "ssss" you should have got all the files from the upstream as well
 271 [13:51] <james_w> it's just a small package :-)
 272 [13:52] <psicus78> ah, ok...so why does it get the orig.tar.gz?
 273 [13:52] <psicus78> I mean when you run bzr-builddeb
 274 [13:52] <james_w> because if you are building a source package as well it needs the actual .orig.tar.gz to produce a correct package
 275 [13:53] <james_w> due to the way that debian source packages work, just having the files isn't quite enough
 276 [13:53] <psicus78> fine
 277 [13:53] <james_w> it doesn't always need it though, so it could optimise by only fetching it when necessary
 278 [13:53] <psicus78> do you get any warning if the orig has changed? or just can't happen?
 279 [13:54] <psicus78> this lead to another question, when is the package updated on the site you maintain?
 280 [13:54] <psicus78> is it linked to upstream automatically?
 281 [13:55] <blfgomes> james_w: so the only reason we need the .orig.tar.gz is to build a source package as well? Could we tell bzr-builddeb to only build the .deb?
 282 [13:56] <jimjeeves> All: I have to go (lunchbreak's over).   james_w: Thanks, very informative.
 283 [13:56] <james_w> blfgomes: that's not currently possible
 284 [13:56] <james_w> psicus78: the orig.tar.gz isn't supposed to ever change unless the upstream version number changed
 285 [13:57] <pollywog> could checkinstall be used to build just a deb ?
 286 [13:57] <james_w> psicus78: if you were to edit the .orig.tar.gz on disk then I don't think you would get an error, but you would if you tried to upload to the archive
 287 [13:57] <pollywog> I am not sure whether checkinstall is still maintained
 288 [13:57] <james_w> psicus78: the branches on that site aren't linked to upstream. They are linked to the packages in the archive. So when a developer uploads a new version it appears there.
 289 [13:58] <james_w> psicus78: I however do plan to link it to upstream, and then provide reports when there is a new upstream and whether there are any conflicts, and then perhaps whether it builds, installs etc.
 290 [13:58] <psicus78> james_w: ok, I think I understood
 291 [13:58] <james_w> psicus78: that's a little way off though :-)
 292 [13:58] <psicus78> james_w: that would be cool
 293 [13:59] <james_w> pollywog: checkinstall can be used to build a .deb, yes. However, a .deb does not an Ubuntu package make.
 294 [13:59] <RachedTN> So, for people running hardy heron, you 'll notice that when you try this command :  sudo bzr branch http://package-import.canonical.com/s/ssss/jaunty   I get this error : bzr: ERROR: Unknown branch format: 'Bazaar Branch Format 7 (needs bzr 1.6)\n'   , the solution is to remove bzr just installed using this command : apt-get remove --purge bzr builddeb  , than download bzr 1.6 from : https://edge.launchpad.net/ubuntu/+source/bzr/1.6.1-1 
 295 [13:59] <james_w> it will give you something that you can install, but there is a bit more to the process than that, so I would be distrustful of the things that it produces
 296 [13:59] <psicus78> james_w: so, when a new upstream is released, which is the workflow to update the package?
 297 [14:00] <james_w> pollywog: it would also never be accepted in to Ubuntu proper, as we require proper source packages for that
 298 [14:00] <james_w> psicus78: take a look at "bzr help merge-upstream", that aims to automate some parts of it
 299 [14:00] <pollywog> james_w: yes I understand it would not be a proper package
 300 [14:00] <Rail> james_w: where (and when) bzr-builddeb stores the "pristine-tar" information?
 301 [14:00] <psicus78> RachedTN: It is easier to add this repo https://edge.launchpad.net/~bzr/+archive/ppa
 302 [14:01] <psicus78> james_w: thanks!
 303 [14:01] <james_w> Rail: during the "merge-upstream" command ahtat I just mentioned. It stores it in a "revision property". It will then use it when building the package. That's also something new to Jaunty
 304 [14:02] <RachedTN> hanks psicus78, I am a little bit addicted to the " coomand line" :P
 305 [14:02] <menesis> james_w: the ssss package does not have Vcs-Bzr: field in debian/control. But if it had, what does the field mean? Does it help package a new upstream snapshot, or it is the url of a packaging branch?
 306 [14:02] <james_w> menesis: it's the URL of the packaging branch
 307 [14:02] <psicus78> RachedTN: that's fine! :)
 308 [14:03] <james_w> menesis: the "debcheckout" tool from the "devscripts" package can grab you the branch from Vcs-Bzr for any package that has that info
 309 [14:03] <james_w> ok, that's all for today people. Thanks for all the great questions
 310 [14:03] <james_w> if you have more there are always lots of helpful people in #ubuntu-motu
 311 [14:03] <psicus78> james_w: thank!
 312 [14:04] <Rail> james_w: thank you very much, bzr-builddeb rocks ;)
 313 [14:04] <pollywog> james_w:  thanks
 314 [14:04] <blfgomes> james_w: thank you for the class!
 315 [14:04] <menesis> ok
 316 [14:04] <james_w> in one week + 6 hours we will have the incredible didrocks presenting "How to update a package", I hope to see you all there
 317 [14:04] <Ryback_> james_w: Thanks for the class, it was good to know bzr-builddeb.
 318 [14:04] <RachedTN> certainly, I will not miss it ;)
 319 [14:05] <Ryback_> james_w: I'll see that one too :-)
 320 [14:05] <james_w> excellent
 321 [14:05] <bdilly> yeah, really nice
 322 [14:05] <james_w> thank you all
 323 [14:05] <k-s> yeah!
 324 [14:05] <james_w> time to find some lunch
 325 [14:05] <lfelipe> cheers
 326 [14:05] <RachedTN> thank you james_w, see you soon  :)
 327 [14:05] <dave_sn> Thanks!
 328 === santiago-pgsql is now known as santiago-ve
 329 [14:33] <sky_walkie> thanks james_w for your time today, how we hear from you soon on another session
 330 [14:33] <sky_walkie> hope

Packaging/Training/Logs/2009-04-09 (last edited 2009-04-09 15:42:06 by cpe-67-243-165-104)