[00:00] geser, ok thnx [00:00] Aloha, sorry to bother you, but could you initiate a pm? [00:00] joejaxx: around? [00:00] Aloha: and I doubt you need samba during the build, the samba library should be enough (more precisely libsmbclient-dev which you already list) [00:00] geser, ok i wasn't sure [00:01] RAOF, it worked! replaced (.*) with ([0-9.]*) and now the rc releases aren't listed anymore [00:01] geser, thnx for the info [00:02] vemon: If you'd like to pick up the rc releases, but ensure that they're not considered higher than the final you might want to check out the various "versionmangle" options. [00:02] LaserJock: hi [00:02] Aloha: if you are missing a build-depends either the package doesn't build in a pbuilder (error during configure or compilation) or an optional feature is missing [00:02] LaserJock: :D [00:03] geser, i'm pbuilding on hardy but im using gutsy. will apt-get -s install still help me? [00:04] RAOF, well it doesn't feel right to include the rc releases since they are... well.. release candidates :) [00:05] Aloha: no, as it will simulate the installation on your gutsy system [00:05] Aloha: but can you login into your hardy pbuilder (pbuiler login) if you need to check something in a hardy environment [00:06] geser, oh sweet, didn't know about pbuilder login feature [00:07] I have to go now. I'll be back tomorrow... bye! [00:10] blueyed: Congratulations. [00:11] jono, Jono! hihi ;) [00:11] ScottK: thanks :) [00:11] hey [00:12] hows it going? [00:12] blueyed, what happened? [00:12] jono, learning how to build packages for REVU [00:12] Aloha: :) [00:13] Aloha: I'm MOTU now. [00:13] blueyed, YAY! congratz! [00:14] Aloha: Thanks :) [00:15] Aloha: blueyed can now break packages on his own :) === doko_ is now known as doko [00:16] woohoo ;) [00:20] geser, i found the problem... hardy uses libgtk2.0-dev not 1.2 like gutsy. thnx for the info [00:20] Oh, have we finally killed libgtk1.2? [00:21] RAOF, apparently [00:21] !info libgtk1.2-dev hardy [00:21] libgtk1.2-dev (source: gtk+1.2): Development files for the GIMP Toolkit. In component universe, is optional. Version 1.2.10-18.1build2 (hardy), package size 1151 kB, installed size 3788 kB [00:21] Awww :( [00:21] hrm [00:21] Both hardy and gutsy have both 1.2 and 2 [00:21] it wouldn't let me install from pbuilder login [00:21] Although the quicker we get rid of 1.2 the better. :-) [00:22] Perhaps you don’t have universe enabled inside the chroot. [00:22] ion_, is 2.0 under universe? [00:23] No, but 1.2 is. [00:23] 1.2 being the ancient version of gtk+ that no one should use :) [00:23] RAOF, gotcha. howdo i enable universe under chroot? === Taggard is now known as Bunny [00:54] TheMuso: I'm now, in case I may be useful [01:00] I would like to get php-xdebug included in ubuntu. I have svn commit access for the Debian PHP maintenance team's SVN archive, so I can probably get it into Debian. Is that the best route to get it into Ubuntu? Or should I also submit it for REVU? [01:14] if i'm adding upstream package to REVU and its from tarball i do -0ubuntu1 for package version right? [01:16] The pacakge version should be $UPSTREAM_VERSION-$DEBIAN_REVISIONubuntu$UBUNTU_REVISION. [01:16] So, in the case where this version of the package isn't in Debian, you are correct. [01:18] RAOF, ok thnx [01:25] how long does it take for upload to show up on REVU site? [01:28] I uploaded and tried to login but it says No REVU account for tjgillies@gmail.com exists yet. [01:31] pochu: As I said, never mind. [01:33] Aloha: sadms? [01:33] ajmitch, yeah [01:34] * ajmitch would guess that you're not in the team, or the keyring hasn't been resynced for awhile [01:34] ajmitch, i'm in the team. can you resynch keyring? dput said it uploaded successfully [01:35] dput only knows as much as any ftp server will reply [01:35] it doesn't know about the key verification [01:36] ajmitch, gotcha. do i have to reupload after key sync? [01:38] no [01:38] the .changes file can just be moved back for reprocessing [01:39] ajmitch, whats that mean in english? ;) [01:41] 20:38 < ajmitch> no [01:41] ajmitch, i know but i mean what does moved back for reprocessing mean? [01:41] i don't understand that concept [01:42] Aloha: As in, no, you don't have to re-upload. [01:43] StevenK, i understand i don't have to reupload. but where does the file get moved back to? [01:43] Where it was before it got processed and rejected. [01:44] chiup chiup * [01:45] StevenK, gotcha. its that automatic or does someone have to manually do it? [01:47] if not can someone resync it please :) [01:50] RAOF, welcome back [01:52] Silly lock-happy mythtv :) [02:12] Heya gang [02:14] bddebian: thanks for the review [02:14] working on it now ... [02:15] Hi rjmyst3, np [02:18] thank whoever resynced the keyserver [02:18] s/thank/thanks/ [02:19] Mr. John Cronjob perhaps. ;-) [02:19] heh [02:21] maybe [02:21] * Aloha thanks Mr Cronjabbi [02:52] bddebian: you stated "Debian/copyright should list upstream authors and should have dates on the copyright. " [02:52] currently, the copyright file states "Copyright Holder: Jose Antonio Hurtado" [02:52] that is not sufficient? [02:53] That's OK but should have copyright dates if available [02:53] And the authors and copyright holders may or may not be the same so they are usually listed seperately === asac_ is now known as asac [02:57] bddebian: is this better? https://wxformbuilder.svn.sourceforge.net/svnroot/wxformbuilder/3.x/trunk/install/linux/debian/copyright [02:58] rjmyst3: Looks good to me. I suck at the copyright stuff overall though :-) [02:58] lol - me, too [02:59] http://revu.tauware.de/details.py?upid=1595 --- this is my once per day [03:00] bddebian: you pasted this lintian error "E: wxformbuilder: menu-item-creates-new-root-section Applications /usr/share/menu/wxformbuilder:1" [03:00] i can't get lintian to say that to me [03:00] I tried "lintian -I -i " on my .changes file [03:01] what am I missing? [03:01] That might be my fault. That machine is still running gutsy so it might be lintian [03:01] Anyone good with gtk2/perl/gladexml? :) === Bunny is now known as Taggard [03:23] if someone posts a packaging request and you upload to REVU but its not reviewed/advocated yet, should you change bug status to Fix Committed? or leave in progress? [03:35] joejaxx: ping [03:44] Laserjock hi [03:44] :( [03:59] LaserJock: hi :D [03:59] joejaxx: hi, still trying to figure out the memory thing [03:59] oh? [03:59] found it wasn't really so much Gnome [03:59] with openbox or other similarly minimal WM I still was runnin ~250MB RAM used [03:59] :\ [04:00] I swear it should be <100MB [04:00] yeah [04:00] now with Gnome+firefox is >300MB [04:00] yeah that is ridiculous [04:01] in top it looks like everything has a lot more memory usage than I'd expect [04:02] gnome-terminal and xchat are taking 20MB each [04:05] bddebian: I just uploaded a new version that fixes the issues you reported [04:05] If you could find the time to confirm that, I'd really appreciate it. [04:07] LaserJock: Is this hardy? [04:07] TheMuso: no, gutsy :/ [04:07] just firefox takes 90 MB [04:08] and this is not ubuntu specific [04:08] I have 2GB of RAM so it's not causing problem yet, but I'm not used to having that much used [04:08] LaserJock: Ouch. [04:08] effie_jayx: I used to usually have it use 20MB/tab [04:10] hmm, my wife's laptop is using 130MB of RAM [04:10] she has 512MB total but I wouldn't think that would matter so much for actual used RAM [04:10] LaserJock, well On my system it is not such a hungry beast === RAOF_ is now known as RAOF [07:12] Hi all [07:14] hello warp10 [07:14] dcmorton: :) [07:15] warp10: have you done anything with the MOTU team? [07:15] submitted packages, etc? [07:16] dcmorton: I had. I am a MOTU helpful, and I worked on a number of packages already. [07:17] thats interesting... i've been looking for somewhere to get started to help out, but i haven't been sure where [07:18] dcmorton: this channel and this page https://wiki.ubuntu.com/MOTU/GettingStarted are surely a good point to start [07:19] dcmorton: I recommend this page too, it gives a wide overview of the whole development process https://wiki.ubuntu.com/UbuntuDevelopment [07:20] thanks warp10, i'll check those out [07:20] dcmorton: :) [07:30] good morning [07:31] morning dholbach! [07:31] morning dholbach! [07:31] hey Hobbsee, hey warp10! [07:45] mornin dholbach [07:45] hey superm1 [07:51] learning cdbs is nuts [07:51] i think i'm over complicating it [07:52] Aloha, yeah it's supposed to be a minimalistic approach to packaging [07:52] superm1, i don't get what i'm supposed to do after i put in the *.mk lines.... [07:53] Aloha, well in some cases nothing [07:53] superm1, oh [07:53] for the kinds of apps your were describing earlier, you would only need something there if you had to say adjust permissions [07:53] did you get a chance to look over one of the packages i was describing to you earlier? [07:55] superm1, i forget if i did. what were they called again? [07:56] Aloha, i was saying you can look at any of the mythtv-theme-* source packages [07:56] they all use cdbs without Makefiles [07:56] and just install pieces into locations [07:56] superm1, ooh yeah... i knew it was mythtv* forgotthe -theme part [07:56] superm1, thnx [07:56] no prob [07:59] superm1, i hope your gmyth REVU gets advocated [07:59] Aloha, well there are a few more pieces that have to come with it too [07:59] i've had to talk to upstream about it [07:59] because they have a really bad .orig.tar.gz for the others [08:00] shipping a debian directory, .svn stuff all over, no licenses on source files [08:00] so i'm more worried about those pieces coming through [08:00] heh [08:00] and once all that is said and done, all 3 source packages need to have MIR's filed before totem is going to learn to talk mythtv [08:01] a *lot* to happen before a FF [08:03] yeah heh [08:11] how do i use debian/watch? [08:13] Try: https://wiki.ubuntu.com/PackagingGuide/Recipes/DebianWatch [08:21] dholbach, thnx [08:22] how do you do a literal character search on google i.e. "debian/file" [08:23] it wants to ignore the / [08:46] juliank, thanks for getting all that aufs together in lum === apache|mobile is now known as apachelogger [08:56] morning everyone [08:57] superm1: Re: gmyth - you're build-depending on libcurl3-openssl-dev, but I haven't seen an openssl exception in the copyright. [08:57] please review: [08:57] http://revu.tauware.de/details.py?package=whysynth [08:57] RAOF, what sort of exception is required for openssl? [08:58] http://revu.tauware.de/details.py?package=ghostess [08:58] i wasn't aware anything was necessary (never had built against it in the past) [08:58] the first is a DSSI synth and the latter a DSSI host for synths [08:58] superm1: Basically the licence headers have to also say "GPL, but you can link against OpenSSL" [08:59] RAOF, can you think of a package offhand that i can lift some verbatim wordage from on that to drop in place? [08:59] superm1: It needs to be upstream. [08:59] * superm1 shrugs [08:59] superm1: OpenSSL is *not* gpl-compatible; you can't redistribute it. [08:59] (At least, according to gnu.org) [08:59] that makes things a little more difficult here i suppose [09:00] superm1: There's probably a libcurl3-gnutls-dev, which should provide the same functionality? [09:00] While being GPL-compatible. [09:00] i'll see what i can do with upstream, i already had a few requests I had to send to fix a few more things [09:00] i'll give it a shot [09:00] Just before I go reviewing it too far :) [09:00] (Licensing sucks) [09:01] okay well assuming that can work out, let me know anything else you catch [09:01] Yup. [09:12] RAOF, yeah it appears to work perfectly with gnutls instead [09:22] nxvl: Thanks a lot for helping with support. Would you mind pushing these discussions to ubuntu-users@ or bugreports though? ubuntu-motu@ isn't really a support channel. [09:23] whats debian/compat for? kinda find it in debian policy anywhere [09:24] s/kinda/can't/ [09:24] Aloha: it is for specifying with which debhelper version your packaging is compatible. If debhelper in control file is 5.x then compat file should contain 5. [09:25] slytherin, so don't delete it? [09:25] trying to keep a clean debian [09:25] Aloha: no, don't delete it. [09:26] slytherin, ok [09:28] slytherin, what should debian/copyright look like if i _am_ the upstream? Can i delete? [09:29] Aloha: debian/copyright must *always* exist [09:29] and habe proper content too [09:29] Aloha: Nope. It is a must. [09:29] Aloha: Check my gnusim8085 package for example. [09:29] man-di, slytherin, ok thnx [09:36] slytherin, can you have it autogenerate the license or do you have to copy and paste everytime you make a package? [09:39] Aloha: What do you mean everytime you create a package. You can take copyright file from previous version of package can't you? [09:39] slytherin, yeah i guess i mean a package for a different project [09:40] Aloha: debian/copyright is typically hand-generated for each new packaging effort. [09:40] persia, ok thnx [09:41] Aloha: It actually depends on license. I think for some standard licenses which are installed by default on Debian systems it is enough to give reference to license. Someone please correct me if I am wrong [09:42] slytherin: You are correct, although I think you and I are answering different (and complementary) questions. [09:43] Well, mostly. For GPL/LGPL one is still expected to provide the 4-paragraph license header (although the full text of the license is not required in debian/copyright) [09:43] cdbs is really compact.... i like it [09:43] this is my first package using it [09:44] persia: Yes. But the reason i mentioned this is because I thought Aloha was specifically asking about copy/pasting of license text. [09:48] slytherin: Right. Like I said, we're answering complementary questions :) [09:49] how do i enable universe in pbuilder? [09:51] n/m found it [10:07] Can anyone think of a good reason to keep pine in multiverse? We've had alpine since feisty, and it's 1.0 in hardy. [10:07] (also, pine only apparently builds on sparc) [10:09] people still use pine? [10:09] Aloha: Not everyone likes mutt enough. [10:10] when running pbuilder i get the error: cp: cannot stat `./misc': No such file or directory anyone know what might be wrong? [10:10] its when its trying to copy source file [10:11] Aloha: does the file/dir exist? [10:11] Aloha: Pastebing your buildlog. I suspect it's trying to copy the ./misc file which doesn't exist. [10:11] why would it try to copy misc. thats not even a file i wrote anywhere [10:12] i have Section: misc in control maybe thats it [10:18] persia, http://pastebin.ca/884424 [10:20] * persia blames something odd with one of pbuilder, the manner in which pbuilder was called, or the environment from which pbuilder was called, and suggests asking someone who uses pbuilder about the issue. [10:21] Aloha: Actually, it might be something interesting in your .dsc file or your .changes file. Do either of them mention ./misc? [10:23] persia, in my files in.changes i have de055ded38b92bb4bc0101fb1b8e78fb 625 misc extra shakabuntu-surf_0.1-0ubuntu1.dsc [10:24] persia, you think it could be that misc? [10:25] Aloha: I suspect so. I don't use pbuilder, but I suggest passing it the .dsc rather than the .changes file. I suspect that will work better (and hope someone else will comment if I am mistaken). [10:26] persia, oh yeah i guess i should pass itthe dsc heh thats probably my problem [10:26] Could anyone point me to a get-orig-source for a .zip repack? I remember there being a recent REVU candidate that did this splendidly, but I cannot remember the affected package. [10:30] persia, what do you use to build packages? [10:32] Aloha: sbuild [10:32] persia, is it "better"? [10:33] Aloha: Yes, and no. Would you like a full opinion? [10:33] persia, sure [10:33] lol [10:34] * persia suspects Aloha has not previously read a "full opinion" in backscroll :) [10:34] persia: No, its because I know how detailed your full opinions can be. :) [10:34] nope [10:34] is there a wiki page for it? [10:35] OK. sbuild and pbuilder are the two most popular means of building Debian-format packages in a clean chroot environment. There are also a number of other tools that can do this, all of which currently have smaller userbases. [10:35] Aloha: I only put opinions on the wiki page when I get really tired of typing them. I don't think I've expressed this one before. [10:35] persia: Doesn't pine have a license problem? Or I have confused it with something else. [10:36] i mean a wiki page for sbuild. i can't find any docs on it [10:37] sbuild is a derivative of the build system used on the debian autobuilders, customised for ease of use by users, rather than the wanna-build system. As the Soyuz build system derives from the same source, sbuild tends to have greater bug-compatibility with the Soyuz buildds than pbuilder. [10:37] slytherin: Alpine fixed that. pine is in multiverse because of the licensing: I was thinking about removing it, rather than promoting to universe. [10:38] Aloha: I'm not sure. I usually point people at https://help.ubuntu.com/community/SbuildLVMHowto [10:38] persia, k thnx [10:39] On the other hand, sbuild has many limitations: it expects a fully deployed environment in which to work, and in currently common use, expects the user to have provided these environments as LVM volumes from which a snapshot may be taken. [10:40] One of the big plusses for sbuild/schroot/lvm for me, is the eas oe which one can use chroots for testing, and don't have to manually clean up afterwards. [10:40] As an alternate tool, pbuilder has the inherent advantage of a slightly different build process, which tends to help reduce the number of packages that would build under sbuild but fail under pbuilder. [10:40] TheMuso: pbuilder --login [10:40] persia: But thats as a root user. [10:40] persia: schroot leaves me as my user. [10:40] I'd rather that. [10:40] Easier access to home dir as well. [10:41] Additionally, pbuilder users tarballs for the chroots, which compress well, allowing many different build target environments. This comes at the expense of some performance, and a requirement for sufficient /tmp space to complete the builds. [10:42] TheMuso: I heard there were pbuilder hooks for bind-mounting /home, and su - $user can do it. Mind you, I've never been a pbuilder user, so I'm advocating something I neither use nor intend to use. [10:43] persia: I never see myself changing, so yeah. [10:43] persia: Do you think we should also preseed the debconf question for j2sdk1.4 package? It will fix at least batik and the other programs like fop depending on batik. [10:43] So, if you have the HD space to spare, and want something that mirrors the buildds, sbuild is closer (although the buildds run a different sbuild than is installed by aptitude install sbuild). On the other hand, if you have a reasonably large /tmp, want to maintain lots of different build targets, or want to participate in the greater QA effort provided by the alternate build, pbuilder is better. [10:44] Further, pbuilder is very slightly easier to set up for those who do not already use LVM or do not have available space in any volume groups. [10:44] Aloha: I hope that answers your question about which is "better". [10:44] persia, gotcha so the question is really "is it better for _me_?" [10:45] slytherin: I don't really understand why we have all of j2sdk1.4, sun-java5-jdk and sun-java6-sdk. Is there value in preserving three different non-free Java implementations, which could be considered three releases from a single upstream? [10:45] i have no clue how to setup LVM so i'll stick with pbuilder ;) [10:46] persia: I am in favour of dumping sun-java5. But there are some apps for which java5 or java6 are too new and hence won't build with either of them. [10:46] Aloha: Maybe. Also, your needs may change. I know of several users who switched from one to the other at various points, for various reasons. sbuild can also be used without LVM, but it's harder to set up that way (there's not a single script that does all the heavy lifting for you). [10:49] slytherin: If there's anything which cannot build with any of sun-java6-jdk, gcj, jikes, or iced-tea, I consider that source in need of porting work. We try to get rid of old versions of gcc, why not javac? [10:49] persia, got any docs on setting up LVM? [10:50] Aloha: repartition a disk to have some free space (I use 20GB for sbuild, but more is better), and run vgcreate. man vgcreate for details. [10:51] persia: true. but this needs discussion. But sun-java5 can go for sure since sun-java6 can cover up for that. [10:51] Aloha: After this, the mk-sbuild-lv script in ubuntu-dev-tools should take care of things. [10:52] slytherin: I'd suggest a mail to ubuntu-motu@ raising the discussion, referencing the FTBFS issues caused by the lack of the preseeding, and asking for opinions on preseeding vs. porting. [10:53] For sun-java5-jdk, if nothing really needs it, file a removal bug. Just be extra sure nothing really needs it. [10:54] persia: Don't have access to gmail now. Will do it on weekend in worst case. [10:55] slytherin: OK. As long as it gets in before FeatureFreeze, it should be OK. I don't suspect that sun-java5-* is considered buggy enough to drop thereafter. [10:55] whens FeatureFreeze? [10:55] Aloha: Feb 14th [10:55] 14th February [10:56] valentines day.. heh ironic [10:56] is that featurefreeze for hardy? [10:56] persia: I should just check if there are any hardcoded dependencies on sun-java5-* packages, right? [10:56] Aloha: yes, of course [10:56] slytherin: And hardcoded build-dependencies. [10:57] persia: How do I check that in an easy way? [10:57] slytherin, whats featurefreeze mean? no more items added to universe? [10:57] slytherin: with grep-dctrl on the Sources file [10:58] Aloha: no new features like new upstream versions [10:58] geser, soren: I just thought it might be better to wait for the MC election to end before I set up the motu-uvf poll to avoid confusion [10:59] (and also to rename the team to motu-ff beforehand) [10:59] slytherin: rep-dctrl -FBuild-Depends sun-java5-jdk -sPackage /var/lib/apt/lists/*hardy_universe_source_Sources is probably a good start [10:59] * dholbach will follow up to the thread again [10:59] geser, so only debian packages? [11:00] * persia would like to see the polls at least delayed until after the MOTU Meeting deciding the team name [11:00] anyone got a wiki page to featurefreeze? [11:00] dholbach: Sure. One day extra will not matter much :) [11:00] I'm guessing http://wiki.ubuntu.com/featurefreeze [11:00] persia: ok... good point [11:01] all the freeze pages are linked from http://wiki.ubuntu.com/HardyReleaseSchedule [11:01] soren, thnx [11:01] persia: I guess then we will also need some extra porting efforts. Make list of packages that have hard coded build dependency on sun-java5, check if package builds with GCJ/sun-java6/icedtea and then modify the package accordingly. [11:01] and in http://wiki.ubuntu.com/CategoryProcess AFAIK [11:02] persia: not s/universe/multiverse/? I doubt there are many package in universe build-depending on sun-java. [11:03] geser: Right. This is a case of failure to edit sufficiently when pasting from the grimoire. I expect soon to find myself trapped between a flood and a horde of brooms. [11:04] I have a knack for really long packages [11:04] grrrrrrrr [11:04] i didn't know hardy was LTS [11:08] :O [11:08] superm1: Sorry, I'm not going to finish the gmyth review tonight. Would you like some comments later, here & now, or on revu? :) [11:08] RAOF, on revu probably more appropriate [11:08] How regular are the MC meetings? Weekly or biweekly? [11:08] Err http://archive.ubuntu.com hardy/main man-db 2.5.0-4 404 Not Found [IP: 91.189.88.31 80] [11:08] LucidFox: weekly [11:08] i fixed the gnutls/openssl issue up there [11:08] superm1: Yeah. I'll paste my current notes there. [11:08] and also cleaned the dependencies a little bit [11:08] thanks [11:09] effie_jayx: You likely want 2.5.1 anyway. Lots of good improvements. [11:09] woohoo it built [11:11] superm1: There you go. Some rough notes/revu questions :) [11:11] RAOF, okay [11:12] some of that stuff was for debugging while building the package, so i'll pull it out [11:13] superm1: I'll check it again tomorrow (and, since it's a library package, work out whether you need a shlibs file/dh_makeshlibs options). Goodnight for now! [11:13] night [11:24] effie_jayx: you should really update your pbuilder every day [11:25] hi [11:25] i have problems when i create debdiff alway the first line is something like this: [11:25] diff -Nru /tmp/cPSsxVmdXJ/hubackup-0.0.7/debian/changelog /tmp/ZTVKssgSJB/hubackup-0.0.8/debian/changelog [11:26] that use /tmp/ ¿? [11:26] why? [11:26] i created it with debdiff previous.dsc new.dsc > new.debdiff [11:27] dcordero: Install patchutils [11:28] it's installed [11:29] dcordero: My apologies. reflex response. The issue is that you have a new upstream. You like would find https://wiki.ubuntu.com/UbuntuDevelopment/Interdiff interesting. [11:30] Note that this is (again) on the agenda for the MOTU Meeting for this Friday, so that page may become less interesting next week. [11:31] thanks [11:43] I seem to be able to use most of the standard tools (including sbuild) with an orig.tar.bz2. Are these permitted for upload yet? [11:45] hello hello [11:45] which favorite python packager could help us out with bug 187286? [11:45] Launchpad bug 187286 in ubuntu "Can't run pywings in ubuntu 7.10" [Undecided,New] https://launchpad.net/bugs/187286 [11:46] pywings isn't packaged at all, but it's referred to in print books [11:46] would be nice to have it packaged [11:48] kiko: Are you sure you wouldn't like to give it a shot? If it uses distutils, and is fairly well behaved, it can be incredibly easy. [11:51] persia, hmmm. I have never done it before, but maybe it would be fun. I have a weekend in brasilia.. [11:53] kiko: Give it a shot this weekend then. Take a look at the CDBS+distutils section of http://wiki.debian.org/DebianPython/NewPolicy as a hint for rules. use dch for changelog, borrow from http://lists.debian.org/debian-devel-announce/2006/03/msg00023.html for copyright, and review http://www.debian.org/doc/debian-policy/ch-controlfields.html for the control file. The rest ought nearly do itself. [11:54] okay then. [11:54] Of course, if it's not well behaved, doesn't use distutils, has an odd license, or something else, it might be a little harder :) [11:55] it depends on python2.4, that much I know. [11:55] python2.4 got rid of whrandom (thankfully as it was hideous) [11:55] err [11:55] python2.5 did [11:55] Not working with python2.5 is one of the things that can easily make it harder. [11:55] there is a great flow to that sentence [11:57] anyone would like to give http://revu.tauware.de/details.py?package=jodviewer a review? [12:01] hi folks [12:01] kiko: You can look at my crude hack to the gaphor package if you want an example of how to make something python2.4 only. There may be cleaner ways. http://patches.ubuntu.com/g/gaphor/gaphor_0.12.5-1ubuntu1.patch [12:02] thanks for the hints persia [12:03] gasp! kiko is in here? [12:03] * kiko threatens Hobbsee with a flower [12:04] Hobbsee: kiko is planning to join the list of hardy contributors this weekend, with a brand new python package :) [12:04] I wonder if that expression exists in english [12:04] kiko: not really [12:04] * Hobbsee attacks kiko with a carrot in return [12:04] crappy unromantic language [12:05] * mok0 wonders about the vegetarian warfare [12:05] mok0: There's a shortage of mammoth femurs about these days [12:06] persia: they became extinct for their handy femurs [12:06] whos' doing the mentoring stuff again? is that persia? [12:06] No. That's MOTU Mentoring Reception. [12:07] that's what i meant [12:07] i think, anyway [12:07] dcordero: It is not a problem. Debdiff always has that format [12:08] oops, checking old conversation [12:08] slytherin: It shouldn't include /tmp. Either it's something for which we don't typically want a debdiff, or the patchutils package isn't installed. [12:08] * persia dislikes running patch -p4 [12:08] slytherin, but with that format when you apply the debdiff always ask you about what file need to patch :/ [12:09] * Hobbsee still occasionally tries to run patch with reverse numbers. [12:09] persia: Ahh, right. patchutils is missing [12:09] but i have patchutils installed [12:09] * Hobbsee prefers the good old throwing back of a patch, with a "fix your patch please, so that it can actuallyb e applied, setting the bug to incomplete, then waiting till the person whines at me about it being fixed [12:10] * slytherin time for a gutsy -> hardy upgrade on office machine. :-) [12:10] dcordero: Yes, but you're running a debdiff against a new upstream. I don't want to look at the upstream patches when I'm looking at your work. [12:11] ok, so, always that a newstream is created is needed a interdiff isn't it? [12:14] dcordero: For now. We've been discussing changing that for a while, but will very likely continue to support interdiff at least until FeatureFreeze, at which time new upstreams will be harder to submit. [12:17] vemon: whysynth commented. Please update soonest and ping me: this enables a feature goal for me (and I'll start work on it based on the last candidate, expecting you can finish the packaging). [12:28] persia, should the misc:Depends be added to source or ibinary deps? [12:28] vemon: binary [12:32] Hi :) [12:32] Hi RainCT [12:32] * persia wonders why automatix is still around. What is left that can be absorbed to make it less appealing? [12:33] persia: the ability to kill -9 dpkg. [12:33] :) [12:34] Hobbsee: I know that was removed for gutsy. It is now just a medibuntu competitor? [12:34] i've no idea [12:34] persia: did we ever get the source, to check it out? [12:34] * persia wonders if anyone feels like finding out. [12:34] Hobbsee: It was scripts. The "binaries" weren't entirely. [12:35] right, true [12:35]