[00:08] How would you typically invoke get-orig-source? Directly with debian/rules? [00:10] Is ${DEB_SOURCE_PACKAGE} set anywhere? [00:19] Could someone explain the difference between Build-Depends and Build-Depends-Indep? [00:39] joh: I think './debian/rules get-orig-source' is ok [00:39] cheatr: -Indep are only used for building arch:all packages (they are only built once, usually on i386 for Ubuntu, whereas arch:any packages are built once for each architecture) [00:40] cheatr: -indep are also used to run the clean target [00:40] pochu: Ok [00:41] mok0: I thought packages used in clean should be in Build-Depends and not -Indep [00:41] mok0: as you want to clean it in every architecture ;) [00:42] pochu: You always want to be able to clean the package though, arch dependent or not :-) [00:42] pochu: you may be right [00:43] s/package/source tree/ [00:43] you have to be very careful with debian/rules to design it so it can build arch and indep targets independently of each other [00:44] for example, if the indep package is doxygen generated documentation, you can put doxygen in Build-Depends-Indep [00:46] pochu: I think the clean target is only called when you build the source package [00:51] mok0: right, but if you build some arch:any packages in say hppa you will call the clean target, so you need things called in clean to be installed [00:51] so they need to be in Build-Depends and not in -Indep [00:51] * jdong thinks the new update-manager security update notification icon is evil and nice :) [00:52] that bold red exclamation mark really gets the point across [00:52] only thing that'd do it better is if in 7 days it turns into a glowing pair of red eyes... [00:52] pochu: afaik the indep targets are only built on the i386 platform, all others are binary package only [00:53] mok0: yes, but they will call clean anyway [00:53] that's http://lintian.debian.org/reports/tags/clean-should-be-satisfied-by-build-depends.html [00:53] "The specified package is required to run the clean target of debian/rules and therefore must be listed in Build-Depends, not Build-Depends-Indep, even if no architecture-dependent packages are built. " [00:54] pochu: I stand corrected [00:54] I should be misunderstanding you then [00:54] 01:40 < mok0> cheatr: -indep are also used to run the clean target [00:55] Of course the easiest is to avoid using Build-Depends-Indep altogether :-P [00:55] jdavies, got a few min? [00:55] oops [00:55] jdong, [00:55] that is [00:56] there is a big problem in pulseaudio [00:56] now my laptop sound dont work [00:56] superm1: reviewing for a test, but shoot if it's fast [00:57] last ubuntu updates? [00:57] good night [00:57] jdong, no i am just trying to get you for more than 3 min to discuss this handbrake build system [00:57] to see where you got on things [00:57] superm1: I havent' given it much of a look [00:58] o [00:58] superm1: if the archive admins are okay with it carrying embedded versions of the libs it wants, I think we should just prefetch the versions it wants for it, then build statically against it [00:58] superm1: i.e. do the fetching step while building the src pkg [00:58] jdong, could you shoot an e-mail to ubuntu-devel about it ? [00:58] superm1: I think this is not a bad idea either because we are talking about encoding against iPods and other sensitive-to-format devices and upstream often has good reason for picking said versions [00:59] well not often, sometimes it 's just for convenience [00:59] eg look at the date that they picked the version and the latest version available on that date [01:00] superm1: I recall there being a big differential the last time I looked [01:00] superm1: esp. for things like ffmpeg that change on a daily basis, it felt to me like they made particular choices [01:00] jdong, well if ubuntu-devel says no, then i say we go to devs [01:01] and talk to them about the choices they made [01:01] and how hard coded they are on those versions [01:03] superm1: agreed [01:03] but we do have precedence for bundling encoders with volatile APIs [01:03] VLC, mplayer (at some points), gstreamer, etc [01:03] * superm1 shoves mythtv aside === fta_ is now known as fta === effie is now known as effie_jayx === evalles_ is now known as keffie_jayx [02:21] Heya [02:32] ScottK: uploaded an adjusted php5-clamav package to the ppa [02:32] sommer: Cool. How did it go? [02:33] ScottK: built and tested fine on my machine... basically the same issue as python-clamav [02:33] Cool. [02:34] the url in the debian/copyright file is no longer active however [02:35] sommer: I'm asking the Debian clamav maintainer how he'd like to proceed now. [02:36] ScottK: cool, which channel? (I need to get more involved with debian :) [02:36] It's a PM at the moment. [02:37] ah [02:37] I also took a look at dansguardian, and there's a new up up stream release that covers 0.93 [02:37] is it better to backport or do an NMU, and sync? [02:37] I'll ask. [02:38] ScottK: cool thanks [02:39] According to him dansguardian was just uploaded. Would you check if it needs a merge or is we can just wait for it to sync. [02:40] ScottK: sure, where do you chack for merges? :) [02:41] sommer: Look in Launchpad and see if there's an Ubuntu diff. [02:41] ScottK: nm, reading https://wiki.ubuntu.com/UbuntuDevelopment/Merging [02:41] K [02:42] ScottK: ah thanks, I'll do that too [02:57] ScottK: from what I can tell after reading the merge page and the package page: http://packages.ubuntu.com/intrepid/dansguardian... a sync will be fine [02:57] ScottK: is the package page the one you meant when refering to LP? [03:01] That's the one. [03:02] great, I'll move on down the list [03:04] sommer: I tend to look on LP becuase it's more up to date. We have it already: https://launchpad.net/ubuntu/intrepid/+source/dansguardian/2.9.9.4-1 [03:05] ah, I always forget the /ubuntu/codename part of the url [03:06] ScottK: that's the latest version on the dansguardian website, so we should be good [03:06] Would you please upload that to the PPA. [03:06] sure [03:06] With an appropriate version number. === boomer` is now known as boomer [03:58] no0tic, have you created a pbuilder already= [03:58] ? [03:58] not for intrepid [03:58] no0tic, im building it without problems [03:58] I'm waiting the new disc! :) [03:59] i thought you already got it [04:01] no0tic, anyways, i guess they fixed libc6 issue, but i did this and it is going good so far: sudo pbuilder create --distribution intrepid --othermirror "deb http://it.archive.ubuntu.com/ubuntu intrepid universe multiverse" [04:03] !seen mario_limonciell [04:03] CTho: Error: I am only a bot, please don't think I'm intelligent :) === Igorot_ is now known as Igorot [04:11] ScottK: dansguarding == success, uploading to the ppa [04:11] sommer: Great. [04:12] Anyone very familiar with doxygen? [04:12] sommer: Would you please file a bug against php-clamavlib with a debdiff for your change and I'll upload it to Intrepid and then send it to Debian. [04:12] sure will do [04:20] ScottK: Bug #227588, in case it doesn't email you :) [04:20] Launchpad bug 227588 in php-clamavlib "Patch for clamav-0.93" [Undecided,New] https://launchpad.net/bugs/227588 [04:20] sommer: Thanks [04:20] np, think I'm going to call it a night... I'll update the wiki tomorrow [05:49] anderson58ken: hi [05:49] hey, could we get tesseract into repositories? [05:49] or is there some other OCR software already there? [05:50] ethana2, tesseract-ocr [05:50] oh [05:51] is there any way to make add/remove show things without gui frontends? [05:51] anderson58ken: sudo apt-get install tesseract-ocr [05:52] ethana2, you mean in the comand line? [05:52] y [05:52] nevermind ;) [05:52] back in 10 === Scientus_ is now known as Scientus [06:27] anderson58ken: you got it installed? [06:28] good morning [06:47] anyone here that can help me? [06:47] possibly [06:47] ethana2, packaging stuff ? [06:47] involving a package needing modification in or addition to ubuntu repos? [06:47] oh [06:47] yeah, this is the place [06:47] ...i think [06:47] (I'm not talking about /me/ though) [06:48] ethana2, yeah i know, but i ment you lol... [06:48] sorry ;( [06:48] ok np ;) [06:48] seems everyone is sleeping [06:50] !ask | RoAkSoAx [06:50] RoAkSoAx: Please don't ask to ask a question, ask the question (all on ONE line, so others can read and follow it easily). If anyone knows the answer they will most likely answer. :-) [06:51] RAOF i know that.. but at this time of the day everyone is sleeping so i was just wondering is someone was alive that could helo me [06:51] RAOF, you expert in packaging? [06:52] RoAkSoAx: I'm a MOTU. I can _probably_ help. [06:52] RoAkSoAx: The nice thing about worldwide collaboration is that someone's _always_ awake. It's mid afternoon here :) [06:53] late evening here :) [06:53] RAOF, here is almost 1 hour after midnight xD [06:53] I mean, it's 9:53, but since we're so far north, still very bright out [06:53] RAOF, ok 'll explaing my prob... i did a merge and after doing the necessary changes i tried to build the binary and i got this error: http://pastebin.ubuntu.com/10679/ [06:54] RAOF, since it shows problem with patch 99_... i supposed i had to drop the patch and i did it... so after dropping, i built another source package and then tried to build the binary again and i got this error: http://pastebin.ubuntu.com/10680/ [06:55] Good morning [06:55] any ideas what could be wrong? [06:55] good morning warp10 [06:55] hi RoAkSoAx [06:56] RoAkSoAx: Right; so, this is one of autotools less endearing features. [06:57] RAOF, so what should i do? [06:57] What's happened is that someone has made some changes to the build system, presumably to make it look for mozilla-xpcom in teh right place or something. [06:58] Changing the build system requires re-running autoconf, which shouldn't be done at package build time because it makes things non-deterministic (or less obviously deterministic). [06:58] So, you re-run autoconf and then work out the diff between the new buildsystem files and the old files; this is what 99_... was. [06:59] ok, the Build-Depends in debian/control are: http://pastebin.ubuntu.com/10681/ and i think mozilla-com is this package: xulrunner-1.9-dev (something to note, MoM only showed me that there were conflics on the Build-Depends) [07:00] This indicates that the packaging is non-trivial; you'll need to understand what's being patched and why before you can actually perform the merge. === doko_ is now known as doko [07:01] (Moreso than usual; you should have at least a basic understanding of the packaging for any merge, and checking for that is part of the sponsorship duties) [07:01] RAOF, that patch was for: * rerun autotools [07:01] - debian/patches/99_autotools_rerun.patch [07:02] RoAkSoAx: Yeah; I know. What you need to work out is what part of the buildsystem was patched, why it was patched, and probably end up re-running autotools and creating a new 99_autotools_rerun.patch. [07:02] One of the previous patches probably touches a Makefile.am or configure.ac; that's the buildsystem change you're interested in. [07:04] RAOF, do you have any documentation that i can see to do it (i'm just learning packaging =) [07:08] RoAkSoAx: I'd suggest trying a different merge if you're just learning; build system changes are always ugly and autotools is the work of Satan. [07:09] RAOF, what if i've already reported it and suscribed to u-u-s ? https://bugs.launchpad.net/ubuntu/+source/blam/+bug/226670 [07:09] Launchpad bug 226670 in blam "[wishlist]Please merge blam 1.8.5-1 from Debian unstable (main)" [Undecided,Confirmed] [07:10] RoAkSoAx: You shouldn't have subscribed u-u-s until you'd finished the merge. u-u-s subscription should be once you've finished and have uploaded the debdiff. [07:11] RoAkSoAx: I'm a member of u-u-s, so I can unsubscribe; you'll want to unassign yourself from the bug with a comment that it's free. [07:12] DANGIT [07:12] Satan on irc.freenode.net is already registered [07:12] RAOF, yep now i know i shouldn't have, but i did what i was told there... and i just realized of this problem when redoing the merge (because i wanted to redoit to get more familiarized) [07:12] RoAkSoAx: Did you upload that debdiff without testing that it built? [07:12] I was going to have him show up and denounce it ;) [07:12] Heh. [07:13] * RAOF stops trying to chase the null pointer through nv40 gallium. [07:13] oh? [07:13] RAOF: is it close to being usable? [07:14] RAOF: the FOSS nVidia drivers? [07:14] ethana2: Depends on what you mean by "usable". ~ [07:14] Yes, the foss nvidia drivers. [07:14] Human Being playing tremulous [07:14] ...usable? [07:15] Dunno. Never tried tremulous. [07:15] nexuiz? [07:15] any 3d thing [07:15] It works for neverput & neverball. [07:15] And PPracer [07:15] sweeeet! [07:15] compiz? [07:15] And OpenArena [07:15] does OpenArena work well with it? [07:15] No, not compiz. It doesn't yet support a bunch of necessary hooks. [07:15] Yes. [07:15] but it probably will soon, right? [07:16] RAOF, in my learning process i didn't realized that it haven't built the first time... and as i said... i just realized that it didn't when redoing it :( [07:16] within 6 months? [07:16] ethana2: Dunno. If Canonical hired a full time dev, my answer would be 'almost certainly, and we'd be shipping nouveau by default for nv40'. [07:17] ok then [07:17] my Ubuntu dell will be an nVidia card [07:17] But it depends. [07:17] is nv40 what's in the 8400gs? [07:17] Noooooo. [07:17] oh [07:17] what's the 8400gs? [07:17] nv4x == 6xxx/7xxx, nv5x = 8xxx/9xxx [07:18] ah [07:18] are there any exceptions to that? [07:18] nv5x is currently undersupported. I'm not sure if there's _any_ 3d for it yet, and 2d is very much unfinished. [07:18] ethana2: No, I don't think so. Not like that stupid Geforce 4 MX business. [07:18] I think I heard about that card today.... [07:19] when i mentioned my radeon 9200se [07:19] something about sucking horribly, i may be mistaken [07:19] Yeah; the GF4MX was _actually_ a GF2 chip. [07:19] RAOF, so... you going to unsuscribe it from u-u-s and i should do that too and add a comment that it is free to be merged?? [07:19] RoAkSoAx: Yes. [07:19] RoAkSoAx: Unsubscribed. [07:20] RAOF: well it sounds like you wouldn't consider nv5x support to be a /problem/ in the future [07:20] just the present [07:20] that's good enough for me to buy one I guess [07:20] That's true; I'd be buying ATI at this point though. [07:20] my other option on the Dell Inspiron is the X3100 [07:20] 1/2.8x the power of the 8400gs [07:21] RAOF, ok thanks, and sorry for the inconvenience... but i would still like to have documentation to work on it and just learn by myself... got any? [07:21] and I'm going to be watchin peach and playing apricot, so I need all the power I can get ;) [07:21] Yeah. If it wasn't blown out of the water by ATI or nvidia cards, I'd be totally there. [07:21] * ethana2 goes to leave you fine gentlemen alone now [07:21] RoAkSoAx: I'm not sure if I've seen any 'patch the buildsystem' documentation. I certainly can't remember any. [07:21] thanks for all the info, RAOF [07:22] RAOF, ok thanks, and sorry for the inconvenience =( [07:22] No inconvenience at all! [07:23] Feel free to ask as many questions as you like; much easier to learn from other peoples experience than from your own mistakes :) [07:24] yeah thanks very much for your help RAOF :D === tb1 is now known as tbf === ogra_ is now known as ogra [09:50] could someone pleas look at possibly sponsor Bug #224241 [09:50] Launchpad bug 224241 in smstools "smstools stop working after upgrade" [Undecided,Confirmed] https://launchpad.net/bugs/224241 [09:58] where can I see how many packages are there in u-u-s queue? Just curious. [09:58] bugs.lp.net/~ubuntu-universe-sponsors [10:01] Hobbsee: guess what, your link does not go to launchpad. :-P === asac_ is now known as asac [10:01] slytherin: expand it :) [10:02] * Hobbsee typed it from memory, rather than visiting [10:02] Hobbsee: still you should check it. There is actually a site called lp.net. :-) [10:02] * Hobbsee thought you would be skilled enough to automatically expand it. [10:03] apologies for not typing every single character. === luisbg_ is now known as luisbg [10:04] Hobbsee: are you being serious? It is not your fault. I overlooked it. No offense meant. [10:05] slytherin: oh ;) [10:05] slytherin: sorry, i'm still kinda stunned at the stuff that has come out in -meeting today. [10:06] so i'm trying to be careful, and not break rules that i don't know about [10:08] <\sh> Hobbsee, one solution: just swear at me..I'm used to it ;) [10:08] * norsetto swears at \sh [10:08] \sh: i can't. even if i apologise to you, i'm still a leader in stuff related to ubuntu, and so it gets held against me forever. [10:09] \sh: i'm unsure if it makes a difference if the apology is publically logged or not, but i do hope not to need to try it. [10:09] * \sh doesn't file complains for every little crap said in any channel here [10:09] yes, you don't. but others might, on behalf of you, and it still gets me lynched. [10:09] see the -meeting earlier :) [10:10] (this is the kind of stuff as to why i'm still stunned) [10:10] <\sh> Hobbsee, oh hell yes...the moses problem and the hundreds of thousands laws around them [10:11] <\sh> no crime without a law [10:39] * slytherin searches meeting log [10:39] slomo__: URL? ;) [10:39] err, slytherin. sorry. [10:41] laga: I am not sure I have found the right one, I just started reading it. - http://irclogs.ubuntu.com/2008/05/06/%23ubuntu-meeting.txt [10:46] ugh. interesting drama. [10:47] good morning!! [10:48] hugs for everybody!.. [11:02] laga: unfortunately, yes ;) [11:08] did I miss something interesting? [11:11] <\sh> ajmitch, you miss all the funny things ;) /me too ;) [11:40] all bow to huats (so that he will give you an ubuntu t-shirt) [12:10] Please remind me: how can I list all packages that provide a certain meta-package? [12:12] mok0: do you mean that provide a virtual package? [12:12] pochu: yes, I need to know what packages provide libgl-dev [12:13] If so, 'aptitude show $package' will do the trick [12:14] pochu: THANKS! [12:14] pochu: AFAIK some of the proprietary Nvidia packages also include a version of GL [12:15] pochu: I hope they provide that virtual package as well... [12:17] mok0: IIRC they divert something. [12:17] wgrant: ok, great [12:17] So they probably won't provide them. [12:19] what's the right place to explain the renaming of a source package? debian/README.Debian-source? [12:19] hmm, README.source [12:20] Isn't it README.source? [12:20] * wgrant checks. [12:20] There's a standard now. [12:20] pochu: copyright I think [12:20] mok0: No. [12:20] README.source has been discussed on the DD list [12:21] As I understand it, it's for explaining how to build a source package that can not be done using the standard tools [12:21] http://lists.debian.org/debian-devel-announce/2008/04/msg00016.html [12:21] but I'm not sure this can be included here [12:21] "a [12:21] package where one one cannot unpack the source package with dpkg-source -x [12:22] and immediately get the source that would be built" [12:22] pochu: right [12:22] pochu: Are you renaming binaries as well? [12:22] here if you can do 'dpkg-source -x' I assume you already have it packaged, so the renaming of the upstream tarball has already been done... [12:23] anyone with a intrepid system/chroot can you please try gpg --edit-key adduid or ? im trying to add an address to my key and its not working [12:23] pochu: in what way are you renaming a source package? [12:23] wgrant: this is because there's too 'alarm-clock' packages been packaged, one in Debian and one in REVU, so I'm suggesting the REVU packager to rename it (or to talk to the Debian owner of the ITP) [12:23] and it prints gpg info (version, ect...) than back to command propmt [12:24] pochu: Is it already in Ubuntu? [12:24] pochu: Hi, could you please see my comment on revu regarding alarm-clock? [12:24] so he has proposed to rename it to alarm-clock-applet, but that would need to be done to the source package too, which should then be documented [12:24] oh joh, you're here :) [12:24] wgrant: nope [12:24] gnomefreak: shouldn't keyid be immediately after --edit-key? [12:24] Hah, you're talking about my app :P [12:24] pochu: Why would you document it, then? [12:24] slytherin: i thought adduid was but maybe that is after getting into gpg :) thanks ill try [12:25] pochu: I would think changelog, then, that's what I am doing with mesa-glw [12:25] pochu: No point documenting it if it's only on REVU. [12:25] pochu: Why would the source package need to be renamed btw? The binary itself is named 'alarm-clock-applet' for what it's worth... [12:26] slytherin: thanks that was it [12:26] joh: because (I think) there can't be two source packages with the same name [12:26] wgrant: well, it will some day hit the archive and if I go and update it I would like to know what changes have been done to it [12:26] pochu: Ah you meant that source package. I thought you were talking about the original tarballs. Sure :-) [12:26] wgrant: although I think i see your point, that it's obvious to what it has been renamed looking at the actual name [12:27] What's the difference between the two alarm clocks? [12:27] pochu: It hasn't been renamed if it was only known by the old name on REVU. [12:27] mok0: the one in debian is a stand-alone python app, mine's a gnome applet. [12:27] wgrant: ah, sorry, with renaming I mean renaming from the upstream tarball, not from an old package [12:28] pochu: No need for a comment. [12:28] I mean, this is not a transition [12:28] joh: then I think the package should be called alarm-clock-gnome-applet [12:28] mok0: Really? Cause other gnome-applets have names ending only in -applet, like sensors-applet. [12:28] pochu: I would think it is sufficient to document in the changelog [12:28] alarm-clock-applet [12:28] It's not a change! [12:28] ah well [12:28] wgrant: *nod* [12:28] it doesn't need documentation. [12:29] ok [12:29] As someone running kubuntu, it is nice to be able to see from the package name that the applet is for gnome [12:30] But that's only my 2 cents [12:30] mok0: Other GNOME applets are -applet. [12:30] Aren't KDE applets plasmoids? [12:30] wgrant: yeah [12:30] wgrant: plasmoids? :-) [12:31] It does seem odd to just call them -applet, but it's also odd to not follow convention. [12:31] well, the description is "Description: Alarm Clock applet for the GNOME panel" [12:31] wgrant: it's probably wise to follow convention [12:31] mok0: Plasma has plasmoids. [12:31] whats wrong with gnome-alarmclock-applet? [12:31] I like the sound of that [12:32] So what changes are needed to change the name? Other than editing control and changelog? [12:32] joh: that's it [12:32] norsetto: Well, it's not officially part of gnome so I'm a bit reluctant about branding it that way... [12:32] mok0: Nothing in rules needed? [12:32] joh: is the applet already in hh? [12:33] mok0: hh? [12:33] hardy heron [12:33] mok0: no [12:33] joh: it doesn't need to be officially in gnome for that [12:33] joh: that's for the binary package. for the source package, rename the orig.tar.gz and move the alarm-clock-*/ directory to the new name [12:33] joh: see gnome-mplayer as an example [12:33] pochu: ok, thanks. [12:34] <\sh> grmpf [12:34] norsetto: That's true. [12:34] <\sh> damnit [12:34] joh: btw, it fails compilation in intrepid, did you check if it compiles with gcc-4.3? [12:34] <\sh> who the hell packaged this tool [12:34] norsetto: Haven't tested against intrepid yet now... [12:34] norsetto: *no [12:34] <\sh> fireflier-client-kde doesn't depend on fireflier-server neither recommends it [12:35] joh: I'm getting few warnings (unused variables, implicit declarations) and a couple of fatal errors [12:35] \sh: Why should a client need a server? [12:35] joh: alarm.c:1858: error: expected ')' before ';' token [12:36] norsetto: I'll look into it. Probably a missing header. [12:36] <\sh> wgrant, it should recommend it actually :) [12:36] <\sh> or suggests [12:36] norsetto: Could you pastebin the whole output please? [12:36] joh: yes [12:36] <\sh> wgrant, I just thought it's a stupid frontend for iptables ;) [12:37] \sh: If it is client-server one might conceivably want the client without the server. [12:37] joh: for the fatal error is just that and alarm.c:1858: error: too few arguments to function 'g_timeout_add_seconds' [12:37] <\sh> wgrant, yes..but it should actually point someone to "hey, there is actually a server, and this tool does not use iptables only" ;) [12:38] \sh: .*client.* matches. [12:38] norsetto: That's wierd, which version of glib? [12:40] Alright, alarm-clock-applet source package uploaded to revu [12:41] joh: the one currently in intrepid, in my build log is libglib2.0-0 2.16.3-1 [12:42] norsetto: They wouldn't change API from 2.14 to 2.16 though. How can I test this out myself without upgrading my entire system? pbuilder? [12:42] <\sh> ah damnit..I'll hack manually my iptables...so I know it works out of the box ;) [12:42] joh: yes [12:43] \sh: If you're looking for a frontend to iptables, shorewall is pretty nice. [12:44] * norsetto -> lunch [12:44] norsetto: bon appetit [12:45] stgraber: Is there any great reason why pastebinit isn't in Debian? [12:47] broonie: the debian packager not having uploaded it yet :) [12:48] broonie: David Paleino is supposed to do it (last I spoke with him) [12:48] stgraber: Ah. I've got someone else (Rolf Leggewie) wanting me to sponsor an upload of it just now. [12:48] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=425226 [12:48] Debian bug 425226 in wnpp "ITP: pastebinit -- command-line pastebin client" [Wishlist,Open] [12:49] that bug is almost one year old :) [12:49] And no activity. [12:50] Plus the initial ITP is malformed. [12:50] OK, thanks. [12:51] np [12:52] How exactly do I create an intrepid chroot with pbuilder? I tried upgrading my hardy build with DIST=intrepid sudo pbuilder update --override-config --othermirror "deb http://no.archive.ubuntu.com/ubuntu/ intrepid main" but there are package conflicts... [12:53] joh: sudo pbuilder --distribution intrepid create [12:53] stgraber: Ok, thanks [12:54] sudo pbuilder --create --distribution intrepid: E: No such script: /usr/share/debootstrap/scripts/intrepid [13:02] joh: do you have hardy-backports enabled> [13:03] jw2328_: no? === jw2328_ is now known as james_w [13:04] you need it so that the updated debootstrap that knows how to create intrepid can be installed. [13:05] Ok, I'll try that then [13:10] joh: upgrade is not working due to a bug. And create is not working due to another bug. :-P [13:11] slytherin: Seems to be working now though :P [13:11] Or not... [13:11] joh: What is working? create or upgrade? [13:11] until libc6 fails to install... [13:12] slytherin: create, but: W: http://archive.ubuntu.com/ubuntu/dists/intrepid/main/binary-amd64/Packages.bz2 was corrupt [13:13] W: Failure trying to run: chroot /var/cache/pbuilder/build/13869/. mount -t proc proc /proc [13:13] joh: please tell me once you are finished with the create process. Last time Itried it didn't work. [13:13] slytherin: It didn't work here either. pbuilder: debootstrap failed [13:14] ls [13:14] focus error, sorry [13:14] Could someone please review http://revu.ubuntuwire.com/details.py?package=alarm-clock-applet ? [13:17] joh: collapse your changelog entry into just one [13:18] mok0: Ok [13:19] joh: in rules, remove the sample comment at the top [13:20] mok0: The entire comment? [13:20] joh: and remove the debhelper calls that have been commented out and that you're not using [13:20] joh: yes [13:20] joh: that's the custom [13:20] joh: get rid of all not needed fluff [13:21] :) [13:21] Done :-) [13:22] joh: also, the #ifeq ... stuff, it seems you always want to compile w/o optimization [13:22] mok0: Yeah, for debugging purposes actually... [13:23] mok0: Is that a bad idea? [13:23]