[00:23] <AdamDH> very close to a working package - dpkg-buildpackage: warning: Failed to sign .dsc and .changes file what does this mean?
[00:24] <AdamDH> do i need to have a gpg key?
[00:24] <james_w> you don't have to
[00:25] <Laney> AdamDH: You really should when you actually publish it, but for now you can pass -us -uc to not sign them
[00:25] <james_w> hey Laney
[00:25] <Laney> hi james_w
[00:25] <Laney> good holidays?
[00:25] <Laney> (lenny GR results out for the interested)
[00:25] <AdamDH> well for the time I just want to test my rules etc I will sign them when I put them up
[00:25] <james_w> ooh
[00:25] <james_w> Laney: it was ok thanks, yours?
[00:26] <Laney> yeah quite good
[00:26] <Laney> watching my new Spooks DVD atm
[00:27] <james_w> cool
[00:27] <AdamDH> well it finished dpkg-genchanges: including full source code in upload
[00:27] <AdamDH> dpkg-buildpackage: source only upload (original source is included), where did it put the .deb?
[00:27] <james_w> Laney: when's the global bug jam again?
[00:28] <AdamDH> or did I miss something
[00:28] <Laney> james_w: February I think
[00:29] <james_w> an 20-22
[00:29] <Laney> AdamDH: What command did you run
[00:29] <Laney> ?
[00:30] <james_w> Laney: I'd be well up for getting something going in the uk for that.
[00:30] <AdamDH> dpkg-buildpackage -S -rfakeroot
[00:31] <Laney> james_w: Definitely. Location is always the problem though
[00:31] <james_w> always
[00:31] <Laney> Do you think popey's house would work?
[00:31] <james_w> what area are you based?
[00:31] <Laney> I'm in Nottingham
[00:32] <Laney> I could maybe get a room at the uni, but would people come?
[00:32] <james_w> oh cool, I'm in Nottingham currently
[00:32] <Laney> oh!
[00:32] <Laney> I'll be back there on Monday
[00:33] <james_w> the centre of mass does seem to be in the South though
[00:33] <Laney> quite
[00:33] <james_w> ah, damn, just going to ask if you were around tomorrow :-)
[00:33] <Laney> gone back to cambs for christmas :(
[00:34] <james_w> we could always have a couple of locations and an online presence for those that can't make one of the venues
[00:36] <Laney> I think nailing one down in London would be the best way to go
[00:37] <Laney> u-uk hasn't really run anything like this before afaik
[00:37] <james_w> yeah
[00:37] <james_w> I think a few people met in a pub last time
[00:37] <james_w> I was away I believe
[00:38] <james_w> I think picking a venue and then looking at alternative arrangements for those that can't make it is the best thing to do, as we will never find a location to suit everyone
[00:38] <james_w> I'll post to the list about it.
[00:39] <AdamDH> seem to have some issues about: make: *** No rule to make target `dh_testdir', needed by `configure-time-stamp'.  Stop.
[00:39] <AdamDH> dpkg-buildpackage: failure: debian/rules build gave error exit status 2 dh_testdir? why that's an inbuilt function?
[00:41] <james_w> AdamDH: do you have a tab character before "dh_testdir" under "configure-time-stamp:"?
[00:41] <james_w> it needs to be a real tab character, and not some spaces
[00:43] <AdamDH> configure-time-stamp:	dh_testdir
[00:43] <AdamDH> its a tab
[00:43] <AdamDH> but not on a new line
[00:44] <james_w> it needs to be a new line
[00:44] <AdamDH> thanks
[00:44] <james_w> if it's on the same line then it is not a command to run but a "target" that must be built before the current one
[00:44] <AdamDH> i am getting a feel for how this all works now
[00:45] <AdamDH> took so reading and playing about
[00:45] <AdamDH> *some
[00:46] <james_w> cool :-)
[00:47] <AdamDH> really should be doing uni work instead of packaging a cross compiler!
[01:08] <AdamDH> looks like I got most of it working just getting compile errors now on the source
[01:24] <AdamDH> what does it mean when make: build: Command not found?
[01:24] <AdamDH> after running sudo pbuilder build ../*.dsc
[01:25] <james_w> AdamDH: I suspect another syntax error in your debian/rules
[01:25] <james_w> AdamDH: could you pastebin it and I will have a look?
[01:27] <AdamDH> yer sure give me a mo
[01:35] <AdamDH> james_w: http://www.pastebin.ca/1294753
[01:36] <james_w> ok
[01:36] <james_w> you have an "install" target, where you want to build the stuff before-hand
[01:36] <james_w> so you have "build" afterwards
[01:37] <james_w> as you have put it on the next line, starting with a tab make will interpret it as a command
[01:37] <james_w> to make it a dependency as you require then put it on the same line
[01:37] <james_w> "install: build"
[01:38] <james_w> same with "binary-arch: install"
[01:38] <james_w> and "configure: configure-time-stamp"
[01:39] <james_w> also, at the end of "build-time-stamp:" you do "touch configure-time-stamp" instead of "touch build-time-stamp", which would cause a problem in some cases
[01:40] <AdamDH> cheers I will add those changes
[01:41] <AdamDH> thanks for the help
[01:42] <james_w> no problem
[01:46] <bobbo> does DIF mean that sync requests require a freeze exception before they are sponsored?
[01:47] <vorian> they arent automagic anymore bobbo, you can still do sync requests
[01:49] <bobbo> vorian: ah ok, the Wiki page jsut semed like a lot of words, not making much sense :P
[01:49] <vorian> haha
[01:49] <vorian> i like that
[01:50] <vorian> "a lot of words" :)
[01:56] <AdamDH> wow even on my macbook pro compiling still takes some time, cant want till I get my dual quad core amd box
[01:56] <AdamDH> *wait
[02:07] <ra> Hi
[02:15] <AdamDH> hey
[03:58] <AdamDH> i am running sudo pbuilder build ../*.dsc  and I get ~/msp430/msp430-binutils-ubuntu-package
[03:58] <AdamDH> any ideas?
[04:19] <tmmoyer> If I am building a custom kernel, and building the debs for it, is there anyway to add extra version information such that I can install the same version of the kernel without my custom modifications?  For example, I have linux-image-2.6.24-22-server installed and I would like to patch it and rebuild it.  When I install the custom version, how can I make is so that I can have both the Ubuntu package installed and my custom package
[04:25] <tmmoyer> maybe how I can create a custom flavour maybe?
[04:25] <tmmoyer> something like server-custom ?
[06:47] <nellery> any revu admins around?
[11:03] <AdamDH> it says: dpkg-deb: building package `msp430-binutils' in `../msp430-binutils_2.18.msp430.cvs.0.0.20081228-1_amd64.deb'.
[11:03] <AdamDH>  dpkg-genchanges  >../msp430-binutils_2.18.msp430.cvs.0.0.20081228-1_amd64.changes
[11:03] <AdamDH> but i cant find msp430-binutils_2.18.msp430.cvs.0.0.20081228-1_amd64.changes
[11:04] <AdamDH> i mean .deb
[11:06] <Hobbsee> check /var/cache/pbuilder/result
[11:06] <Hobbsee> or wherever else you've set it
[11:08] <AdamDH> thankyou Hobbse! I just made my first debian package
[11:09] <AdamDH> it was in there
[11:10] <Hobbsee> :)
[11:11] <AdamDH> something went slightly wrong as when I check with the gui package installer there is no included files
[12:20] <Brucevdk> Question, I've created a Python distutils setup script which in combination with pysupport, debhelper.mk, python-distutils.mk is used to build our package. Lintian still throws a few warnings I need to fix, but I'm currently wondering how I should properly go about adding a postinst to do a notification (update-notifier). See package apt-file for an example.
[12:20] <Brucevdk> You can find the control files here btw: http://code.google.com/p/nautilussvn/source/browse/#svn/branches/v0.12/packages/ubuntu/debian
[12:22] <Brucevdk> I'm assuming there might be some debhelper available to do just this (I could obviously manually created a postinst file, but I'm looking for "The One True Way" (TM)
[12:22] <directhex> you could look at the apt-file source package...?
[12:23] <Brucevdk> directhex: I did
[12:24] <Brucevdk> See my reference to "The One True Way" (TM), also somebody else build a Debian package for us before and he was told "Please remove postinst and postrm.". http://revu.ubuntuwire.com/details.py?package=nautilussvn
[12:26] <Brucevdk> directhex: oh wait, you might mean.... look closer
[12:26]  * Brucevdk looks closer
[12:30] <Brucevdk> no luck, but I'll just manually created the postinst file for the time being. Somebody will just have to look at it whenever I might submit it for inclusion.
[12:30] <Brucevdk> create*
[12:31] <maxb> Why do you think following the way apt-file's postinst does it is not right?
[12:33] <Brucevdk> maxb: I don't think anything. But it's a package, it's not documentation (guideline, packaging guide, tutorial). I'm not familiar with all the intricacies of Debian packages, and obviously the source package doesn't explain "why" things are done the way they are
[12:33] <Brucevdk> maxb: also it's not using the same methods to build the package (we use pycentral)
[12:33] <Brucevdk> maxb: combined with the fact that some reviewer said to remove the postinst file, well that makes me wonder what "The Right Way" (TM) is
[12:36] <Brucevdk> For example, what does the #DEBHELPER# in the postinst file mean/do?
[12:36] <maxb> The reviewer was objecting to the inappropriate content of the file, not its existence
[12:37] <maxb> #DEBHELPER# identifieds the point in the file at which debhelper will insert automatically addend snippets
[12:37] <maxb> *added
[12:38] <Brucevdk> maxb: now we're talking, this is all I was asking for (a little help/pointers) ;-) Thanks.
[12:39] <Brucevdk> maxb: can you point me in the right direction where I should look what arguments are passed to postinst? apt-file also does a check for [ "$1" != configure ]; then
[12:40] <maxb> The reviewer was calling attention to two specific problems - (1) It's unequivocally wrong to be including debhelper snippets in the source package's postinst, since debhelper is going to add them during the package build, and (2) There's no obvious reason why that symlink wasn't simply shipped in the package
[12:41] <maxb> The authoratative manual for core packaging details is the Debian Policy Manual - including a (rather complex) description of the arguments a maintainer script can expect to be passed
[12:43] <maxb> and yes, the many ways maintainer scripts can be invoked *is* hideously complex
[12:43] <laga> there is a nice graph in the debian women wiki
[12:45] <Brucevdk> maxb: just browsing the manual is complex ;-P
[12:46] <Brucevdk> maxb: thanks for the help though, everything is just a little clearer than it was before
[12:49] <maxb> Most of the complexity comes from the fact that an installation process can fail, and be rolled back
[12:50] <maxb> e.g. if a prerm was run, but something went wrong and the package then isn't going to be removed after all, postinst gets used to roll back the result of running prerm
[12:52] <Brucevdk> maxb: are you allowed to include comments in postinst etc. to explain this to readers?
[12:55] <maxb> Of course. It's just a shell script like any other
[12:57] <maxb> Well, actually, it's possible to write the maintainer scripts in other languages too, but it's seldom done
[12:59] <Brucevdk> Oh, from now on I will write all maintainer scripts in LOLCODE
[12:59] <laga> kthx
[13:00] <Brucevdk> :-)
[13:00]  * StevenK kills Brucevdk 
[13:00] <StevenK> DO NOT WANT
[13:01] <Hobbsee> sure?
[14:49]  * hyperair grumbles at how long revu is taking to publish an uploaded package
[14:51] <hyperair> http://revu.ubuntuwire.com/details.py?package=codelite <-- revu, anyone?
[15:55]  * nhandler is having a fun morning re-reviewing packages on REVU
[15:57]  * RainCT hugs nhandler :)
[15:58] <nhandler> RainCT: If I don't, vorian will pass me up on the Hall of Fame. We can't have that, can we? ;)
[15:59] <RainCT> of course not!
[15:59]  * RainCT whispers to vorian: go, go, go!    :P
[16:00] <nhandler> lol
[16:25] <RainCT> jpds: in case that you can manage to come, we'll meet at 20:30 in Plaça Catalunya (BCN)
[17:12] <marnold> could anyone tell me how long sync requests usually take to get done, after they've been approved
[17:26] <iulian> marnold: It depends on how busy the archive admins are.
[17:27] <marnold> thought so just wanted to ask
[17:34] <hyperair> how do i set files to be excluded from a package.install file?
[17:39] <hyperair> ..is there nobody in this room?
[17:39] <laga> everyone is probably busy
[17:40] <maxb> hyperair: man dh_install suggests that this is only possible from the dh_install invocation command line, not in the controlling file
[17:41] <hyperair> maxb: yeah, i've read the man page over and over. i'm quite sure i've seen a package that uses a reverse of dh_install though
[17:41] <hyperair> somewhere
[17:46] <jpds> RainCT: Unmöglich.
[18:00] <RainCT> Btw, are two acks for new packages required or not? https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages says no ("but greatly encouraged"), but I think I saw some other wiki page which said it's mandatory
[18:05] <Laney> RainCT: I don't think the REVU process is actually required by policy
[18:06] <RainCT> Laney: I'm not talking about REVU (which isn't policy, but non-MOTUs getting acks from 2 MOTUs is), but about MOTUs requiring an ack from someone else
[18:06] <Laney> mm
[18:06] <RainCT> like one year ago it wasn't, but I don't know if this has changed or not
[18:14] <sebner> RainCT: it isn't a must have but a good advice
[18:15] <RainCT> sebner: alright, so it hasn't changed
[19:55] <terli> when an update is requested by apt/aptitude/synaptic/whatever, does ubuntu/debian have any kind of a mechanism to only download changed files or does it automatically download a complete package?
[20:00] <crimsun> terli: in Ubuntu, currently the latter
[20:02] <terli> crimsun : get me a cattle prod.
[20:02] <terli> I'm going into shuttleworth's house.
[20:02] <laga> is there a sane implementation of that other behaviour available somewhere?
[20:03] <terli> I don't think so.
[20:03] <laga> what?
[20:03] <crimsun> it's a nontrivial thing, really
[20:15] <CarlFK> df -m shows 1181 free.  aptitude install python-gtk2 ... "Need to get 3281kB of archives. After unpacking 12.0MB will be used."  after that, df -m shows 1199.  difference of 18.  I can understand the 3.281 got saved somewhere, but that only accounts for 15.2.
[20:15] <CarlFK> where did the other 3mb go?
[20:17] <CarlFK> laga: I read a description of 'that' - it would require the server extract the diffs real time.  which would load the cpu/ram and max out the server faster than the current way maxes out bandwidth.
[20:18] <CarlFK> at least thats what I got from it
[20:18] <CarlFK> if that's true or not is someone elses problem :)
[22:58] <marnold> would someone look over my merge please https://bugs.edge.launchpad.net/ubuntu/+source/azureus/+bug/311858
[22:59] <Laney> Can I suppress the update-maintainer warning when building a source package?
[23:04] <Laney> marnold: I've only looked quickly, but I see some strange changes in your debdiff from Debian, such as dropping azureus-gcj. Wasn't that done in the Debian upload?
[23:05] <marnold> hmm maybe i did the debdiff wrong
[23:05] <marnold> which diff
[23:05] <Laney> debdiff debian.dsc your_merge_candidate.dsc
[23:06] <Laney> the second one
[23:06] <marnold> ok
[23:06] <Laney> It's a good idea to run lsdiff on your debdiffs just before uploading to see if they look right
[23:06] <marnold> i'll do it again and reupload
[23:07] <marnold> i did but i was working to try to combat sleep problems so  i might not have done my best
[23:18] <marnold> Laney, corrected diff attached
[23:20] <Laney> marnold: Does azureus not use a patch system?
[23:21] <Laney> marnold: The changes to debian/rules aren't in the changelog
[23:21] <marnold> no
[23:22] <Laney> marnold: And the %f in the desktop file isn't explained afaics
[23:22] <marnold> thats because i took debian/rules from Debian
[23:22] <Laney> marnold: But the changes are showing up in your diff
[23:24] <marnold> previous uploader did the changes directly to the source directly without dpatch
[23:25] <marnold> so that is why the diff with debian looks the way it does
[23:27] <marnold> debian/rules was intended as a copy of Debian's as ours is cluttered with gcj changes
[23:27] <marnold> hang on
[23:31] <marnold> Laney, while I'm doing these corrections should i convert the multiuser patch to dpatch
[23:32] <marnold> or leave alone for now
[23:33] <marnold> imo we should get the thing building before we worry about that
[23:35] <marnold> i can always do a cleanup upload later
[23:41] <Laney> marnold: Right, it seems to have other changes directly on the source, so leave that there for now
[23:41] <Laney> marnold: But you need to explain the other things (rules, desktop) in the changelog or get them out of the diff
[23:42] <Laney> Note that these are just general comments - I know nothing about azureus specifically. ubuntu-java (I think) deals with java stuffs
[23:42] <marnold> rules adds a gconf scheme that we want to keep
[23:42] <marnold> almost forgot about that
[23:43] <Laney> marnold: There's the ant heap space change, and dh_gconf/link that were added
[23:43] <Laney> and %f in the desktop
[23:44] <Laney> azureus.template changes - are these covered by something you already mentioned?
[23:46] <marnold> * azureus.desktup: %U -> %f (otherwise file associations don't work)
[23:46] <marnold>     Thanks to Francisco Reverbel for pointing this out
[23:47] <Laney> marnold: You need to mention all the changes you keep in your new changelog entry
[23:47] <marnold> User interface auto selection patch
[23:47] <Adri2000> Laney: what update-maintainer warning were you talking about? did you mean the dpkg-source error rather?
[23:48] <Laney> Adri2000: Yes, but I bodged around it
[23:48] <Laney> I coudn't see anything in the manpage of dpkg-source
[23:48] <Laney> It'd be nice if submittodebian would filter that change out
[23:49] <marnold> are you using debuild or raw dpkg-buildpackage
[23:49] <Laney> debuild
[23:49] <Laney> -S
[23:49] <marnold> as i recall dpkg-bp only warns
[23:49] <Laney> hm, interesting
[23:50] <marnold> debuilld actually enforces it
[23:51] <Adri2000> dpkg-source errors if $DEBEMAIL contains @ubuntu.com, otherwise it just warns
[23:51] <Adri2000> so a workaround is to use DEBEMAIL='' debuild/whatever
[23:52] <Adri2000> UTSL http://patches.ubuntu.com/d/dpkg/dpkg_1.14.23ubuntu1.patch :)
[23:52] <Laney> \o/
[23:53] <Laney> thanks
[23:56] <Hobbsee> Adri2000: works fine for me?
[23:56] <Hobbsee> oh, never mind
[23:56] <Adri2000> Hobbsee: ?
[23:56] <Adri2000> :)
[23:57] <Hobbsee> i thought you were meaning in general