[00:49] <G> imbrandon: hey, let me know when you are around, spice 0.4 might be inthe impossible basket anyway
[01:11] <imbrandon> G: kk i'm here but about to jump in the car, i'll be arround to chat more in about ~1.5 hours
[01:16] <G> imbrandon: alright
[02:26] <effie_jayx> persia: the change had been done without adding a patch system to the package, I found by checking the debian versions and the ubuntu versions of modified files
[02:28] <effie_jayx> now I wonder what one does when a pacakge has been touched like this
[02:29] <ScottK> If the Debian maintainer didn't add a patch system, don't add one yourself.
[02:31] <effie_jayx> ScottK: ok, later the debian maintainer added the patch system with the changes from ubuntu. The changes in the source done by the ubuntu developer make the patch from the debian maintainer make the package FTBFS. then what do we do?
[02:32] <effie_jayx> change the source code and make the patch from the maintainer do it's thing and then request a sync?
[02:33] <ScottK> effie_jayx: In that case you need to revert the direct changes in the source and go with what Debian did.
[02:34] <ScottK> Other than direct change versus patch are there other Ubuntu changes?
[02:34] <effie_jayx> ScottK: no other changes
[02:34] <ScottK> Then test build the unmodified package from Debian and if it builds, request a sync.
[02:36] <effie_jayx> ScottK: you mean the dsc from debian? or you mean revert the changes in code and the build source pacakge and test build it
[02:36] <effie_jayx> ?
[02:37] <ScottK> effie_jayx: I mean the dsc from Debian.  If you are considering to ask for a sync, that's what you should be testing.
[02:37] <effie_jayx> ScottK: ok
[02:39] <effie_jayx> sorry for being so insisive and obnoxious with so many q's
[02:39] <effie_jayx> just wanna make sure I get it right this time
[02:39] <ScottK> effie_jayx: No problem.  It's how people learn.
[02:40] <ScottK> It's better to ask questions if you have doubt than get it wrong.
[02:41] <effie_jayx> ScottK: sure thing
[02:41] <effie_jayx> this is for tomorrows post and I wanted some sense of conclusion to this
[02:41] <effie_jayx> is it usual for changes to be in code, is that usual now
[02:42] <effie_jayx> a year back people would suggest to have changes in code through patch systems
[02:42] <ScottK> It depends.  It's not the norm, but generally we don't add patch systems where Debian doesn't have one.
[02:42] <ScottK> Also now that more packages are maintained in a VCS, code is often managed that was rather than through patch systems.
[02:43] <effie_jayx> right, and the debdiff would be enough patch for debian?
[02:43] <effie_jayx> ahhh ok
[04:11] <mase_wk> hi guys, i'm trying to create a debian package but i'm having a few issues. Lintian is reporting FSSTND-dir-in-usr usr/doc  , is anyone able to translate this into english for me please ?
[04:12] <persia> If you use lintian -i it will give you a bit more verbose description of each message.
[04:12] <mase_wk> awesome thank you persia
[04:18] <imbrandon> G: pong
[04:23] <mase_wk> persia: so in my /usr/share/<pkg>/changelog.gz i need to have package (version) , is this any different from what is in my DEBIAN/control file ? if not why does it need to be present, is that not creating the potential for the two to get out of sync ?
[04:25] <persia> Um, no.
[04:25] <persia> But for complex reasons.
[04:26] <persia> 1) You should never modify DEBIAN/control manually: this should be constructed at build-time based on other files, most notably debian/control (note the difference in capitalisation).  DEBIAN/control gets Version: set from debian/changelog and Version never exists in debian/control
[04:27] <persia> 2) /usr/share/<pkg>/changelog.gz should never exist
[04:28] <persia> 3) /usr/share/doc/<pkg>/changelog.gz may be one of debian/changelog or an upstream changelog.  In the latter case, debian/changelog will become /usr/share/doc/<pkg>/changelog.Debian.gz
[04:28] <persia> Does that answer your question?
[04:29] <mase_wk> hmm ok , well i'm obv doign something wrong. i have writen some software (GPL licensed of course =) which for some reason other people are finding useful and i'm tryign to make it easier for them to install and Ubuntu/Debian seems to be the most commonly requested format
[04:29] <mase_wk> and i'm following a packaging howto which said that i needed the DEBIAN/control file
[04:30] <mase_wk> so i just made it following the guidelines as best i could
[04:30] <persia> Ah.  The wonder of the internet is the lack of editors :)
[04:30] <mase_wk> and now i'm trying to make it pass lintian
[04:30] <persia> Could you post the URL of the guide you used?
[04:31] <mase_wk> i have printed copy infront of me, url is somewher at home. i read the official ubuntu one but to be honest the hello demo app didn't really help me understand what i was doing
[04:31] <mase_wk> maybe i'm just a bit thick
[04:31] <mase_wk> but constructing it from scratch at least made sense.
[04:32] <persia> I doubt that.  Many of the guides on the internet are flat out wrong.  The official Ubuntu guide is designed to teach folks to deal with packages done in all sorts of ways, and isn't useful at all to create a new package, unless one is prepared for significant study first.
[04:32] <mase_wk> well yeh i spent about 6 hours trying to actually make a package with the ubuntu guide =)
[04:33] <mase_wk> this took me 1/2 and hour but i could actually install it.
[04:33] <persia> So, there's lots of ways to package.  I'd be happy to share mine (which I believe  to be easy), if you're willing to start over.
[04:33] <mase_wk> sure
[04:33] <persia> OK.  First step, get a release tarball of your source, and unpack it.
[04:33] <persia> Second, create a debian/ directory
[04:34] <persia> Third, install the debhelper package, and copy /usr/share/doc/examples/debhelper/rules.tiny to debian/rules
[04:34] <persia> Fourth, run `echo 7 > debian/compat`
[04:34] <mase_wk> what does that do ?
[04:35] <mase_wk> the echo 7 bit
[04:35] <persia> Creates a file called debian/compat containing the the character '7', a carriage return, and an end-of-file marker
[04:35] <persia> This file is used by debhelper to indicate which debhelper compatibility level you are using for the package.
[04:37] <mase_wk> sorry, quick question, the tarball, i've just exported from git, does the tarball need to have the contents at the root ?
[04:37] <persia> It's more automatic that way, but it's not required.
[04:38] <mase_wk> ok, may as well do it correctly first time
[04:40] <persia> Fifth, create debian/copyright.  I like the format described at http://dep.debian.net/deps/dep5/
[04:41] <persia> Sixth, run `dch --create` to create an initial changelog entry.  Set the package name, and version here.
[04:42] <persia> Seventh, create debian/control.  The fields are defined at: http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-sourcecontrolfiles
[04:43] <persia> Eighth: create debian/watch  The format is described in the uscan manpage.  This is optional, but nice.
[04:43] <persia> Ninth, Install devscripts and `debuild -S -us -uc` to create a source package
[04:44] <persia> Tenth, using sbuild, pbuilder, or a PPA, build the package to make the .deb files.
[04:44] <persia> That ought do it.  The result may need some tweaking, but as the upstream author you can do most of that better upstream rather than mangling the packaging.
[04:44] <persia> If you don't have the soruce in the top-level directory, you can add --sourcedir=... in debian/rules (man dh for an example).
[04:45] <persia> If you need to install extra files (manpages, etc.), it's best to do this by adjusting your build system upstream.  Often the build logs will contain useful information about what went right, or what went wrong.
[04:45] <mase_wk> ok cool, thanks for your help, i'm up to doing the copyright section, but i'll let you know how i get on.
[04:46] <persia> Good luck!  Feel free to ask here as you get closer to getting it ready, and want to get it into the distribution.  If you decide not to be part of the distribution, #ubuntu-packaging is also a good reasource for packaging questions.
[04:46] <mase_wk> does it make a difference if the buildsystem is not GNU Make? i'm currently using phing which is very similar to Apache Ant ?
[05:08] <G> imbrandon: sorry, still here?
[05:46] <imbrandon> G: yup wasup ?
[05:48] <G> imbrandon: this is proving to be a nightmare
[05:49] <G> imbrandon: I was okay with the forks of qpixman/qcairo, but vdesktop is really a fork of qemu
[05:49] <G> imbrandon: not only is it going to be a maintenance nightmare, it's going to be a security nightmare if every there are problems in qemu etc
[05:49] <imbrandon> :) most new packages do, thus personaly i dont recomend them for new packagers, but its good to see what "could" go wrong technicly and policticly
[05:50] <imbrandon> yup
[05:50] <imbrandon> we might be better watching it as a project and see how much becomes unforked
[05:50] <G> imbrandon: plus, the devs don't publically say where their forked copy is hosted, they put to the upstream git repos which I've checked and are spice less
[05:55] <imbrandon> ouch
[05:55] <G> imbrandon: however I'm currently knee deep in an interesting libvirt bug
[05:55] <imbrandon> maybe even doing some PPA packages in the meantime etc
[05:55] <imbrandon> G: cool, anything i can help with lemme know
[05:56] <imbrandon> i'll do what i can/time permits :)
[05:56] <G> I could do with a SAN? :P
[05:58] <G> in actual fact, going to tackle this bug
[06:04] <imbrandon> kk
[06:14] <eagles0513875> imbrandon: ping
[06:23] <eagles0513875> imbrandon: never got a response from upstream about mysql workbench :( via mailling list
[06:58] <imbrandon> hum
[07:13] <eagles0513875> imbrandon: how should i proceed with getting workbench into maverick since upstream never got back to me
[09:11] <tarzeau> good morning
[10:16] <AnAnt> Hello, is notify-osd going to be dropped in meerkat ?
[10:19] <arand> AnAnt: I wouldn't think so, why should it?
[10:28] <AnAnt> arand: https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue193#Advanced Configuration pop-up messages (notify-osd)
[10:41] <arand> AnAnt: That's news to me... I'm not sure I trust it without further reference..
[12:10] <AnAnt> arand: yeah, that's why I came asking too
[13:18] <micahg> \sh: ping/poke re zend-framework :)
[13:36] <persia> micahg: My recommendation would be to just fix it, rather than waiting.  it's been long enough.
[13:37] <persia> As with everything else, the idea is to use Debian names (adjusting anything in Ubuntu as required), etc.
[13:40] <ajmitch_> is that with the zend-framework vs zendframework?
[13:43] <micahg> persia: no, that's been taken care of, \sh just has to upload the new version to maverick :)
[13:44]  * persia still believes in not blocking on folks if they are apparently busy with other things
[14:02]  * sebner waves at persia 
[14:03] <persia> sebner?
[14:03] <sebner> persia: I'm a nice person
[14:04] <sebner> nah, I have a question indeed :)
[14:04] <sebner> persia: my u-u-s membership is expiring but I don't need/can do anything as ubuntu-sponsors membership keeps running, right?
[14:04] <persia> ...
[14:06] <persia> According to https://launchpad.net/~sebner/+participation you're only an indirect member of ubuntu-sponsors.  Would you like to be a direct member?
[14:07] <persia> As an indirect member, your membership will run out when your ubuntu-universe-sponsors membership terminates.
[14:07] <sebner> persia: I thought the teams got merged and there is/will only be the ubuntu-sponsors team. I was wrong then :\
[14:08] <nigelb> packages.ubuntu.com is not updated with maverick packages?
[14:08] <persia> No, you had the idea right.  The implementation we chose was to have people join the new team if they wanted when their membership in the old team expired.  Launchpad doesn't allow us to force-merge teams.
[14:08] <persia> nigelb: You want rmadison anyway, but I know the necessary bits made it into git (although they may not have yet been deployed)
[14:09] <sebner> persia: ah Ic. So what's the difference between renewing my u-u-s sponsoring and officially joining u-s ?
[14:09] <persia> That I'm not going to do the first unless you can demonstrate that it's a critical requirement to continuing the effort to merge everyone into ubuntu-sponsors.
[14:10] <persia> s/ment to/ment for/
[14:10] <geser> nigelb: it's half-broken currently as it lists maverick, but maverick doesn't work currently
[14:10] <geser> nigelb: I don't know if Frank Lichtenfels is the right contact about it or not
[14:10] <persia> He is, but he's been very busy lately.
[14:11] <nigelb> geser: I wanted rmadison (which I forgot about) anyway, just checkign up version number
[14:11] <persia> The code is prepared, but the current model requires him to pull it from the shared repo, and put it in a special place, and file an RT and wait...
[14:11] <sebner> persia: heh, I'm now willing to cause extra work for you so ... :)
[14:11] <sebner> *now = not
[14:12] <persia> sebner: at this point the extra work is clicking the "accept" button.  I'm just not going to add anyone to the new team except if they want.  Do you want?
[14:12] <persia> (hint: everyone else is doing it)
[14:13] <sebner> persia: haha, /me swims with the crowd then ;D
[14:14] <persia> Thanks for joining the team.  We will continue to measure your sponsoring activity and carefully log it :)
[14:14]  * sebner hides
[14:14] <nigelb> I forget how to query rmadison for debian. Sigh.
[14:14] <persia> nigelb: -u debian
[14:14] <sebner> persia: thx for the add
[14:14] <nigelb> persia: Thanks :)
[14:15] <persia> sebner: No no.  You joined the team.  There's lots of stuff to sponsor :)  LP does all the tracking of everything internally anyway ( and the output gets used for stuff like MoM), so don't think it's sinister.
[14:22] <nigelb> If a bug is fixed in the new release of an app, do we allow backports for earlier releases or do I have to look for the particular fix?
[14:25] <nigelb> Also, anyone has any clue how to dissect cvs like we do for git?
[14:29] <geser> ScottK: as you merged boost1.42: boost1.42 drops libboost-graph-parallel1.42-dev and libboost-mpi1.42-dev on purpose, but libvtk5-dev depends libboost-all-dev which depends in the end on those which makes it uninstallable. Any idea how to resolve this?
[14:30] <ScottK> geser: Does is actually need any of those or is it just a question of making libboost-all-dev installable?
[14:31] <jetienne> *.dsc ... what dsc stands for ?
[14:33] <geser> ScottK: don't know yet, I just looked at a FTBFS and why libvtk5-dev isn't installable
[14:33] <arand> jetienne: description
[14:34] <ScottK> geser: The two possible solutions are drop the non-existing packages from libboost-all-dev or figure out how to build the MPI stuff in Universe.
[14:34] <ScottK> One of those is way easier than the other, so it'd be good to know.
[14:34] <arand> jetienne: Or, debian source control ...I'm not exactly sure in fact.
[14:35] <jetienne> arand: ok :)
[14:36] <nigelb> jetienne: isn't it signature or something? I dont remember
[14:37] <jetienne> nigelb: i was guessing "description" too. but wanted to be sure so i asked... apparently im not the only one to be sure :)
[14:37] <nigelb> Debian Source Control :D
[14:38] <geser> ScottK: I'll try to test the first solution in my PPA over the weekend
[14:38] <ScottK> geser: Great.  If that solves it there's s patch in the sponsorship queue already.
[14:39] <arand> jetienne nigelb: http://www.debian.org/doc/debian-policy/ap-pkg-sourcepkg.html :  "Debian source control file - .dsc"
[14:39] <jetienne> arand: thanks
[14:39] <nigelb> arand: beat you to it ;)
[14:40] <arand> nigelb: I did note that as a possibility up there ↑ :) But I wasn't sure though.
[14:41] <nigelb> arand: ;)
[14:42] <jetienne> in "control", most packages priority is "optional", correct ?
[14:43] <geser> yes
[14:43] <jetienne> geser: thanks
[14:43]  * arand is annoyed by all those .d* endings, whomever designed that must not use tab-comletion..
[14:46] <nickbnf_> Could someone have a look (and possibly advocate) my glogg package? It's lintian free and has already been reviewed by jcfp. bug #575764 or http://revu.ubuntuwire.com/p/glogg. Thanks a lot!
[14:50] <nigelb> nickbnf_: have you thought of getting that into debian?
[14:51] <nickbnf_> nigelb: yes, I've uploaded a debian version to mentors.d.net, but haven't had any news yet (http://mentors.debian.net/cgi-bin/sponsor-pkglist?action=details;package=glogg)
[15:03] <ScottK> Did you also submit a request for sponsorship (RFS) in Debian?
[15:04] <nickbnf_> ScottK: yes (http://www.mail-archive.com/debian-mentors@lists.debian.org/msg68322.html), but since I got good inputs from here to improve the package, I tried here as well!
[15:05] <ScottK> OK
[15:27] <nigelb> nickbnf_: there are several DD's around.  Hopefully you can catch one of them ;)
[16:07] <nigelb> siretart: you're part of the ubuntu burning team right? Is it possible to import the cdrdao package for me?
[16:07] <nigelb> I'd like the cvs branches improted to LP.  There is a bug fix I'm trying to get in
[16:08] <nigelb> Can't find it on the sourceforge cvs
[16:42] <bilalakhtar> Hello, can anyone over here sponsor package python-tweepy?
[16:45] <bilalakhtar> hyperair: Hi there! Thank you a lot! You taught be how to debianize packages, and now my first package is in! You were right "This all is part of the learning process"
[16:46]  * hyperair doesn't recall the context of that quote any more
[16:47] <bilalakhtar> hyperair: Should I get packages into Debian or Ubuntu? What did you do to become motu?
[16:47] <hyperair> bilalakhtar: debian first. then sync into ubuntu.
[16:47] <bilalakhtar> hyperair: You did that only?
[16:47] <siretart> nigelb: I can make you a member of the burning team so you can do so yourself ;-)
[16:48] <hyperair> bilalakhtar: as for becoming MOTU, i just contributed to packages randomly, fixed random bugs, until the MOTUs who sponsored me got sick of sponsoring me. =D
[16:49] <bilalakhtar> hyperair: oh. Contributed to packages means?
[16:49] <hyperair> bilalakhtar: fix bugs, sync, merge, fix more bugs...
[16:50] <bilalakhtar> hyperair: Unfortunately DDs are not accepting gnome-media-player. They say it has a misleading title.
[16:50] <bilalakhtar> Doesn't matter, a car can never cross the river without any modifications.
[16:56]  * siretart also thinks that gnome-media-player is unfortunate. that term makes me immediatly think of totem.
[16:56]  * hyperair agrees with siretart 
[16:56] <hyperair> a rename would be good.
[17:38] <mcl0vin> arand: am here
[17:38] <arand> mcl0vin: yep?
[17:40] <mcl0vin> so i got the .deb
[17:41] <arand> mcl0vin: (if you have karmic), just double-click it and install.
[17:41] <mcl0vin> arand: am ssh'd
[17:42] <arand> mcl0vin: Ah, right "sudo dpkg -i pastebinit*.deb"
[17:43] <mcl0vin> cool it works
[17:44] <mcl0vin> arand: now where are the docs so i can read how to get started in this business
[17:45] <arand> mcl0vin: https://wiki.ubuntu.com/PackagingGuide/Complete
[17:46] <arand> mcl0vin: Martin Owens did a very good overview drawing of the different steps in packaing: http://doctormo.org/wp-content/uploads/2010/04/02-what-are.png
[17:47] <nigelb> siretart: that would be great!
[17:48] <nigelb> siretart: I've already requested a code import, once you accept me in, I'll make the team the owner
[17:49] <siretart> nigelb: what's your lp id?
[17:49] <nigelb> nigelbabu
[17:50] <arand> mcl0vin: And Daniel Holbach did a nice video series of som basic packaging: http://www.youtube.com/view_play_list?p=2AB3B94B228B6FE1
[17:50] <siretart> nigelb: welcome!
[17:51] <nigelb> siretart: thank you! :)
[19:15] <fabrice_sp_> geser, I'm working on vtk merge/sync from Debian
[19:17] <fabrice_sp_> and also uploaded a 'fixed' boost-defaults and new vtk version in my ppa
[19:18] <fabrice_sp_> but new vtk FTBFS because of boost 1.42 and python, so Im in contact with Debian maintainer to fix it so that it can be a sync
[19:35] <carstenh> fabrice_sp_, Rhonda: uploaded
[19:36] <fabrice_sp_> cool! Thanks a lot to both of you!