[00:03] cody-somerville, what's up? i'm in between airports, so leave me a message with what ya need [00:04] superm1, I suspect it was about a sound issue encountered with a particular device, now solved by an upgrade to karmic (unless my backscroll memory overflowed) [00:05] persia, ah okay [00:05] superm1: vostro 1520, already fixed in karmic. possible backport to jaunty-proposed (later) by apw. [00:06] (of course, he who actually pinged ought to have provided both bits of information :) ) [00:56] any one around who can add me to universe-sponsors? [00:58] asomething: Sure. Whats your LP username? [00:58] TheMuso: andrewsomething [00:58] asomething: Ok will add it, and congrats. [00:59] Thanks! [00:59] Done. [00:59] what's the benefit of being a team member? getting the extra pile of bugs to look at? [01:00] ajmitch_: being able to unsubscribe uus if need be for one. [01:01] hm, true [01:01] * ajmitch_ should probably join up there & u-m-s as well [01:02] ajmitch_: I can get you into the former if you'd like. [01:02] * persia goes to give ajmitch a gold star [01:02] alright [01:02] persia: but I want a pony! [01:02] ajmitch_, Then create a launchpad group with a pony icon [01:03] heh [01:03] if i ship an icon in different sizes in /usr/share/icons/hicolor/*/apps/, do I also need to continue to ship one in /usr/share/pixmaps? [01:04] fta, It depends on whether all the environments you wish to support include /usr/share/icons/ in their icon cache search path (most do). [01:04] looks like kees will be the most likely person to poke about u-m-s at this hour [01:05] persia, that's chromium, i asked upstream to provide several sizes, now i have 16 32 48 and 256 [01:05] 256? that's rather large [01:05] fta, Excellent. The part I can't tell you is if that will work in kubuntu. [01:05] 256 is for gnome do [01:08] persia, ok, so i'll keep my old 48x48 icon in /usr/share/pixmaps for now and ask the kde guys what they need [01:10] fta, My understanding was that the KDE cache was considerably more flexible than the GNOME cache. It's XFCE that makes me wonder. [01:11] (yet somehow I managed to type "kubuntu" instead of "xubuntu", for which I must apologise) [01:11] oh, ok. i'll find someone using xubuntu then [01:17] hicolor works in kde (since it's the xdg fallback icon theme) [01:18] JontheEchidna, Didn't hicolor come from KDE? [01:19] hmm, that's ringing a few bells so there's a good chance it did [01:19] especially since kde was a major contributor to xdg along with gnome [01:19] Certainly. .desktop files are basically .link files redone. === asac_ is now known as asac [01:27] what's the best way to go about sponsoring merges? unsubscribe u-u-s when it's uploaded? [01:33] assuming that this package builds properly & is flawless :) [01:42] hi all [01:42] persia: I just pushed out my update package to lp and revu... :D [01:43] ajmitch_, https://wiki.ubuntu.com/MOTU/Sponsorship/SponsorsQueue [01:43] freakabcd, Hi [01:43] ausimage, Cool. [01:43] of course, I only searched for 'Sponsoring' [01:43] I hope to really get some good feedback on how I can make my package better and to see it in Ubuntu [01:46] nellery: sorry about the bug spam, just juggling statuses ;) [02:04] ajmitch_: no problem, thanks for sponsoring that :) [04:12] hey guys, do i need to plan to have my package included in universe in conjunction with an ubuntu release or can it happen at any time [04:13] it needs to be ready, reviewed & uploaded before feature freeze [04:14] https://wiki.ubuntu.com/KarmicReleaseSchedule has the relevant dates for this release [04:14] August 27th [04:15] thanks ajmitch_ [04:16] I strongly suggets you have it uploaded way before that [04:16] because the first upload will probably generate a bunch of bug reports [04:17] i've had my own repo for years [04:17] what kinds of bug reports? [04:17] reviewing may take awhile as well, depending on how busy people are [04:17] have you looked at getting it into debian as well? [04:17] also, can i have a development snapshot of my project that i update semi frequently? [04:18] no i haven't [04:18] sometimes i get dependency conflicts but they are almost always because the user has some weird video card for which opengl is not working correctly [04:19] what other kinds of bug reports are you thinking of? related to the package itself? [04:21] here is my software btw http://grey.colorado.edu/emergent [04:22] prefrontal: your own debian repository with the software interacting with all 16K other packages? === bluesmoke_ is now known as Amaranth [04:22] yes [04:22] it has a huge whack of dependencies. our software is complicated [04:22] then thats where I would expect bug reports [04:22] its just a trend I see with new packages [04:23] but nothing else depends on our software [04:23] that'll make it fun to review [04:23] prefrontal: so, as I said, just get it uploaded early; if I'm wrong you got in early no harm done [04:24] k:) [04:24] if I'm right, you'll have time to fix things without needing SRU's [04:25] i can use SRU's to have the package included in previous versions of ubuntu? [04:25] do you have a source package around that you build the binary package from? [04:25] no, you can't include new packages that way - instead you use backports to get it into earlier versions [04:26] no, for my own repo i just use cpack's 'make deb' target. i built a package from hand once, it sucked [04:26] you may need to learn the sucky way of doing it to get a source package ready for review [04:27] yeah i know, thats why i'm here :) [04:27] about that frequent development snapshot package? [04:27] emergent-snapshot [04:28] can i do that, and how frequently? [04:28] sure [04:28] two ways [04:28] a PPA [04:28] with the regular package name in the PPA [04:28] or a dedicated snapshot package in karmic [04:28] I recommend a PPA [04:28] its much cleaner [04:29] i've used someone elses PPA before i think [04:29] they then have to modify sources.list? [04:29] which wouldn't present a benefit to me, since thats just like using my own repo [04:30] you're saying there is something unclean about the dedicated snapshot package [04:30] e.g., i wouldn't be able to do nightlies? [04:30] it does have the benefit of being built automatically on different architectures [04:30] oh that could be nice [04:31] nightly uploads wouldn't really work, and you couldn't do that with a snapshot package in a released version of ubuntu [04:31] but you can with a PPA [04:33] how frequent can i update my snapshot? weekly/monthly? [04:34] ok, i have a different idea.. [04:34] someone would probably need to review & upload the snapshot package each time, and this would just be for the development relerase unless you were then also getting the snapshot updated in backports [04:35] and I don't know how that would go :) [04:35] is Ubuntu ok with a snapshot package that svn checkouts the source code to my software and compiles it? [04:35] does your software change that rapidly? [04:35] prefrontal: its like, but not like using your own repo [04:35] using a PPA is probably the best option, I think [04:35] since you don't have to worry about ubuntu freezes, etc [04:35] prefrontal: firstly it builds with all the current karmic dependencies, and it builds in the same environment as karmic itself, so you'll find out about build issues [04:36] yeah it does change a lot, we are scientists and our nose and hence code follows the funding [04:36] secondly, it builds on all the karmic architectures, so you'll find out about portability to things like lpia that you were perhaps not doing yourself [04:37] yeah.. we haven't really thought about that [04:37] we can't target specific archs? [04:37] and lastly, you'll be building via the standard deb rule, rather than the cmake deb rule [04:37] you can, but the experience of getting it building in a PPA will make sure you have addressed those things [04:37] i see [04:38] so PPA's are great for upstream software authors to use as a staging area for updates to their software in Ubuntu itself [04:39] i think i'm going to create a PPA - thanks a lot guys [04:39] NB: PPAs only accept source package uploads, like ubuntu [04:42] NB? [04:43] short for nota bene, or colloquially 'take note of this' [04:43] kk [04:47] cool, so, after I upload a new source package to a PPA, does it get compiled straightaway, or is there a periodic cron? [04:47] reductio: can I submit a new snapshot package for each commit? [04:48] (to my PPA) [04:48] each upload would go into a queue to get built [04:48] prefrontal: yes you an [04:48] nice [04:48] prefrontal: various upstreams do this already [04:48] uploading on every commit may be a bit of overkill for something that large though [04:48] depending on how often you commit [04:48] prefrontal: I'd suggest establishing a baseline and uploading incrementals though [04:49] we don't do that now and wouldn't likely start, but i would like to do more frequent builds [04:49] step 1) get it working. step 2) tune :) [04:50] step N) automagic building based on pushes to bzr branches in launchpad? :) [04:50] ajmitch_: :) [04:50] if that comes about soon [04:53] what kind of compile farm you guys got? [04:53] just curious..:) [04:54] we just got a 26 node cluster with dual quad core nehalems and 24 gb ram per node [04:54] make -j8 takes less than a minute on a single node [04:54] takes like 30 minutes on my laptop [04:56] I don't remember the details [04:56] lots though [04:57] they get shared with other things - at release time I think most of the builders become mirrors for ubuntu; demand goes through the roof for a while there [04:57] lp has most of the details [04:59] https://edge.launchpad.net/builders/ [04:59] I coulnt 53 machines [05:00] with a lot of interesting names [05:01] there may be hidden ones for embargoed builds too; I dunno quite how that hangs together. [05:09] lifeless: There isn't, they just state 'Building private build' === txwikinger2 is now known as txwikinger [05:21] those are virtual machines? [05:21] some of them look to be [05:31] All Hai oh great ones :) [05:32] I have a question which should be easy , but no one has answered for me [05:33] Let us say I am building a package from source, applying a patch [05:33] call this package foo [05:33] so I get the ubuntu source (apt-get source foo) -> patch -> build it [05:34] how do I number the package so as not to confuse apt-get (dpkg) ? [05:34] ie I want to maintain satisfaction for dependencies [05:35] So bar depends of foo-ubuntu-1.0 [05:35] and I build foo-patched [05:35] how do I number it ? [05:36] prefrontal: we build on VM's for security. clean machine every time [05:37] bodhizazen: that will depend on how strict bar's dependencies are [05:37] bodhizazen: which is probably why noone has answered it, because there isn't a single answer, other than 'you should learn how version numbering in dpkg works' [05:39] would you have a link you would advise ? [05:40] http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Version [05:41] Thank you :) [05:42] Chapter 7 too: http://www.debian.org/doc/debian-policy/ch-relationships.html [05:43] lifeless, thats impressive:) [05:43] The problem is , sometimes bar can be very strict, in which case it seems like a can of worms :) [05:46] bodhizazen: it may be a bug in bar, or necessary for some reason. So if you think its going to occur you should check bar (or the reverse-depends of foo) and possibly change them too [05:50] Assuming I do not mind the breakage / building in a chroot ... [05:50] may I assume I can change / edit the dependencies as I wish ? [05:51] Sure. What you do in the privacy of your own computer is your own business :) :) [05:51] within sensible constraints yes [05:52] if you put it in a PPA you should be aiming for something that is in principle uploadable to ubuntu too [05:52] What I am working on is the php5 meta package [05:52] but I do not run apache [05:53] so I want to remove the apache dependencies [05:53] I am applying the php-fpm patch [05:53] http://php-fpm.anight.org/download.html [05:53] if you're planning on submitting that for Ubuntu, you should probably discuss it on the list first ;) [05:53] I have no problem building from source (ie php directly) [05:53] and I am trying to go to a ppa [05:54] which list ? [05:54] probably ubuntu-server [05:56] Good advice [05:57] for the moment I am wanting to learn what is involved (or at least a general idea) with going from source to a ppa ;) [05:58] not that I do not want to work with ubuntu-server, I am just at the beginning stage and as you can see need a little advice on actually packaging, lol [05:58] I'd love to help but I have to leave the computer for a bit - most of what you need to know will be covered on the wiki [05:58] !packagingguide [05:58] The packaging guide is at http://wiki.ubuntu.com/PackagingGuide - See https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages for information on getting a package integrated into Ubuntu - Other developer resources are at https://wiki.ubuntu.com/UbuntuDevelopment - See also !backports [05:59] bodhizazen: If you can build it in a pbuilder chroot locally, (and that chroot is "normal"), it will be fine in the PPA also. [06:00] So once you've read the Packaging Guide, check out https://wiki.ubuntu.com/PbuilderHowto and try building your packages that way; then try uploading them to a PPA. [06:12] bodhizazen: You don't have to have apache stuff to install the php5 metapackage. it's depends are satisfied by php5-cgi [06:12] jmarsden, I have nginx + php-fpm up and running in an OpenVZ container , which is essentially a chroot [06:13] Flannel, the fpm essentially replaces php5-cgi [06:13] bodhizazen: Well, it is a choroot but it contains a bunch of modules that are unlikely to be present by default in a PPA or a pbuidler... so it will not check build dependencies nearly as well as a real pbuilder [06:13] so it is php5-common with a patch, but otherwise is run as you would fastcgi [06:15] can pbuilder be run in a VM ? [06:15] I'm very imperfect... when I build stuff on a "real" machine or a VM and forget to also test in a pbuilder chroot, that's when I find my PPA builds fail with dependency problems... [06:15] such as KVM or Virtualbox ? [06:15] Yes, I run pbuilders inside virtualbox VMs here [06:15] Lets me test on Debian when I am running Ubuntu as my primary OS... [06:16] I will look at that over the next few days [06:17] The problem is I am patching php5-common [06:17] but that is part of php5 the meta package , lol [06:18] jmarsden, you don't need a vm for that: you can use a simple chroot to have a debian env in your machine [06:18] except if you are using windows as primary os [06:18] bodhizazen: php5 is a metapackage... just don't install it. [06:19] fabrice_sp_: True, but then if I want to test the resulting built modules under Debian, and the app concerned needs a GUI... I'm not sure I can do that in a chroot, can I? [06:24] hello, when was the last sync from Debian ? [06:27] jmarsden, you can use the x-windows server of Ubuntu to see the window [06:28] I actually do it with karmic (in a chroot) and even an i386 chroot for Firefox (because of flash on amd64) [06:29] fabrice_sp_: OK... thanks. I should try that (although virtualbox is so easy to use anyway). [06:30] Flannel, apt-get source php5-common pulls all of php5 (the meta package) with all it's dependencies [06:31] dpkg-buildpackage -rfakeroot -uc -b then builds all of php5 and all of it's dependencies, [06:31] AnAnt, you mean for Karmic? The last automatic sync will be end of June (https://wiki.ubuntu.com/KarmicReleaseSchedule). [06:31] so I am trying to figure out how to build just php5-common ? [06:32] jmarsden, the pb with VM is that you have to dedicate the memory, and some packages are so huge during compilation, that they 'eat' more than 1Gb... I also use virtualbox, but not for building ;-) [06:34] so before June I shouldn't ask that a package get sync'ed from debian ? [06:34] fabrice_sp_: OK. I do have pbuilder chroots under the main OS for building too; I tried it both ways. I put 8GB in this desktop so I can run several virtualboxes of 1GB each with no real worries... could probably try running a couple of 2GB Virtualboxes if I needed to :) [06:35] AnAnt: Unless the older package you are replacing in Ubuntu has a -XubuntuY Ubuntu-specific package earlier, autosync will do the job for you until then. BTW... it is already June :) [06:35] AnAnt, no, except if it has some Ubuntu changes that can be discarded [06:36] jmarsden, is quicker with his 8Gb of RAM :-) [06:36] if I run enough vboxes I will slow down :) [06:36] sure! :-) I only have 2, so I don't have much room to run a lot of VM ;-) [06:37] good morning [06:37] 2Gb, I mean [06:37] Hey dholbach ! Good morning ;-) [06:37] fabrice_sp_: Yes, that would be pretty limiting. [06:38] hiya fabrice_sp_ [06:39] jmarsden, my VM's don't have more than 400 Mb, so for building, it¡'s very short (the compiler sometimes eat all the ressources, and I have to kill the VM) [06:39] dholbach, how are you doing this morning? [06:39] very good very good - how 'bout you? [06:41] Good too :-) a bit hot lately here (more than 30ºC), so I don't sleep as much as I liked to :-) [06:44] ah, ok [06:44] dholbach: thanks [06:44] morning dholbach [06:48] hiya ajmitch_ [06:48] dholbach: I was inspired by you & sponsored an upload today ;) === ajmitch_ is now known as ajmitch [06:48] wooohoo! [06:49] more sponsoring! [06:49] and rejoined u-u-s so I can mangle the bugs [06:49] * ajmitch isn't in u-m-s though [06:50] dholbach: mind re-adding me there? [06:51] ajmitch: You're actually doing some sponsoring? [06:51] ajmitch: done [06:51] ajmitch: Who are you, and what have you done with the real ajmitch? [06:51] StevenK: shush, before you kill off my desire to do any more [06:52] * StevenK smiles sweetly [06:52] I even merged stuff! [06:53] Now let me revel in the fact that I've done more uploads to karmic already than the last 3 releases together [06:53] Haha [06:53] How many is that? [06:53] bugger all :) [06:53] Less than 9? [06:53] 6 or 7 so far, I think [06:53] * StevenK did 9 in a lump this morning for NBS-age [06:54] so I saw [06:54] they were mostly rebuilds though, they hardly count [06:54] But I did test build them! [06:54] ok, can you upload these: LP #359436 , LP #359444 , LP #359446 ? [06:54] I'd hope so! :) [06:54] Launchpad bug 359436 in ubuntume-gdm-themes "Rename package and update artwork " [Undecided,Confirmed] https://launchpad.net/bugs/359436 [06:54] Launchpad bug 359444 in usplash-theme-ubuntume "Rename package and update artwork " [Undecided,Confirmed] https://launchpad.net/bugs/359444 [06:54] Launchpad bug 359446 in ubuntume-themes "Rename package" [Undecided,Confirmed] https://launchpad.net/bugs/359446 [06:54] ajmitch: :-) [06:55] they are for karmic now [07:05] * StevenK uploads something to decrease the evilness present in the archive by a little. === fabrice_sp__ is now known as fabrice_sp [07:10] hmm, debootstrap karmic doesn't seem to be making use of both cores [07:14] brb [07:22] ajmitch: Does acidlab count? :-P [07:27] decreasing the evilness? I doubt it [07:28] it's a php package, that's pure evil right there [07:31] But it was using yada, and now it isn't! [07:33] oh, that's alright then [07:33] So before it was impure evil, and now it is pure evil? :) [07:34] I'm not sure whether uploading php5 made me evil or not [07:36] PHP + yada == evil^evil ; PHP == evil [07:50] Can anyone please tell me the meaning of this condition - ifneq ( ,$(filter-out $(DEB_HOST_ARCH), arm mipsel mips armel)) [07:55] If the arch isn't arm, mips, mipsel or armel do the following [07:58] StevenK: thanks. I was trying to figure out why armel build of libjogl-java fails. I thought the condition was problem. [08:04] StevenK: any idea if DEB_HOST_ARCH evaluates to armel on the armel buildd? Or should we rather use DEB_TARGET_ARCH? [08:05] steven@obliterated:~$ dpkg-architecture -qDEB_HOST_ARCH [08:05] armel [08:06] StevenK: then I am not able to understand why the build is failing [08:07] slytherin: Where's the build log? [08:07] StevenK: https://edge.launchpad.net/ubuntu/+source/libjogl-java/1.1.1+dak1-5/+build/983218/+files/buildlog_ubuntu-karmic-armel.libjogl-java_1.1.1+dak1-5_FAILEDTOBUILD.txt.gz [08:08] StevenK: the logic is supposed to be in such a way that if the arch is armel then 'javadoc' target should not be run. But the target is running anyway, it times out and fails. [08:08] StevenK: looks like the same problem is happening in Debian as well. [08:09] Build killed with signal 15 after 150 minutes of inactivity [08:09] Ahh [08:09] Perhaps javadoc should only run on the i386 builder and dump the docs into a arch all package? [08:10] StevenK: that is what supposed to happen according to the logic in debian/rules file. But the logic is not working. I will log a bug in Debian. [08:14] slytherin: With my logic, javadoc should only get run in the binary-indep target, so the !i386 builders would never call it [08:15] StevenK: how can that be handled in cdbs? [08:16] As a hack? [08:17] StevenK: No I am asking how to achieve what you are suggesting in a rules file which is using cdbs. [08:18] Yes, and my suggestion is a hack ;-) [08:20] H [08:20] *Hmm [08:21] I wonder if this is as simple as ifeq rather than ifneq [08:27] someone could please giveback ocaml-http [08:27] ? [08:27] (in my ppa builds fine) [08:28] and ocaml-lastfm as well, please. [08:33] hi. is karmic auto-import frozen yet? audacious2 just hit debian sid a few days ago. === nenolod_ is now known as nenolod [08:35] nenolod: https://wiki.ubuntu.com/KarmicReleaseSchedule - no [08:45] nenolod: It doesn't appear in the new source report I just ran on the archive master. [08:45] StevenK: it's there :P [08:46] StevenK: http://qa.debian.org/developer.php?login=nenolod@dereferenced.org [08:47] http://ftp.debian.org/debian/pool/main/a/audacious2/ is 404 [08:47] And? [08:47] Oh, I know. It's stuck in Debian NEW. [08:47] no. [08:47] Wait a few weeks, then [08:47] it's not in NEW [08:47] it is in SID. [08:48] StevenK: as the fucking maintainer of audacious, i damn well know where it is. [08:48] Ah, I was looking for the package name of audacious2 [08:49] yeah. sorry for the confusion. [08:49] we were originally going to run them side by side [08:49] Right. The version of audacious in Karmic has Ubuntu changes, so it needs a merge [08:49] since 2.0 series was originally meant more as a platform demo, than an actual finished product [08:49] yeah. i'll do it. [08:49] i need to up a fixed plugins though [08:49] i made an oops [08:49] :P [08:50] Looks like someone else has done it [08:51] well, plugins needs to be merged against pending 2.0.1-2 [08:51] otherwise audacious-plugins-dev convenience package becomes broken [08:51] as i said, i made an oops [08:52] But audacious-plugins is a seperate source? [08:52] StevenK: yep [08:53] That also needs a merge [08:53] yep [08:53] i've done it before in ubuntu [08:53] I don't trust the audacious merge in https://bugs.edge.launchpad.net/ubuntu/+source/audacious/+bug/383271 either [08:53] i need to go through and see what changes ubuntu has added on and if they are even relevant anymore, anyway. [08:53] Ubuntu bug 383271 in audacious "Please merge audacious 2.0.1-1 (universe) from Debian unstable (main)" [Undecided,Confirmed] [08:54] StevenK: yeah. it's done incorrectly. [08:54] SSE2 is safe to enable on x86_64, but... [08:54] that's a new patch introduced [08:54] I think it drops changes, but I haven't confirmed [08:55] i'll look into it [08:55] probably after audacious-plugins/2.0.1-2 goes up later today [09:00] StevenK: i commented on the merge === azeem_ is now known as azeem === ripps_ is now known as ripps [10:13] What's the bast way to ckeck what o put in build depends when packaging a new program? [10:13] I checked http://www.debian.org/doc/manuals/maint-guide/ch-dreq.en.html#s-control , all methods are a bit confusing [10:13] look in the README or COMPILATION file in the package? [10:14] loic-m: The source should have some docs saying what packages it needs in order to build the program. [10:14] siretart: there's no information there [10:15] loic-m: What about its homepage? [10:15] iulian: no information either :( [10:16] loic-m: it is very hard to guess what build dependencies a package needs. if it is not documented, I generally inspect the source to understand how it works [10:16] Well, in this case I usually build it with pbuilder to see what dependencies it needs. [10:16] loic-m: Well, I guess pbuilder it until it works I guess :/ [10:16] loic-m: Worst case, try building it in a base pbuilder chroot with no Depends: at all and see what fails, and go from there? [10:16] which is a good idea in any case in order to get an idea what the package is doing [10:18] So each time the pbuilder fails, I add the missing bit to control? That sound doable, easier than read the source for me ;) [10:18] welcome to the dark side... [10:18] loic-m: Yes. [10:19] ok, thanks [10:19] loic-m: Yes. if you have a compiled binary you can also try running ldd on it so see what libraries it links to, for some extra clues? [10:19] there are indeed some wrapper around the open syscall that observe what header files a subprocess is trying to open and guesses on that bases what development package might be relevant [10:19] jmarsden: I tried objdump -p /usr/bin/foo | grep NEEDED as the Debian maintainer guide suggest, but it gave me far to much dependencies [10:20] it still requires a bit of thinking [10:21] ldd list is eevn bigger [10:22] I'll try the pbuilder fail method first... [10:24] hi, when I use pbuilder to build package, but failed, and i want to dig it, and pbuilder remove the build environment, how can i keep it unremoved [10:24] When I used objdump -p /usr/bin/foo | grep NEEDED, I tried filtering the libs in build-essential, but i still had far to much libraries. I just want to make sure I don't add useless build-depends [10:26] rawang: Would https://wiki.ubuntu.com/PbuilderHowto#Running%20a%20Shell%20When%20Build%20Fails%20(Intro%20to%20Hook%20Scripts) help you out? [10:30] As a more general question, when reviewing on REVU, how do one check if the build-depends and depends in debian/control are correct (i.e. neither too much or too little)? [10:31] too little => package would not build in a pbuilder. too many is harder to detect, you have to know, or try removing the ones you think are unnecessary and rebuild, as far as I know. [10:33] Hi again, anyone feeling for a review of http://revu.ubuntuwire.com/p/task Would be appreciated. Really. [10:44] jmarsden, hey, big thanks, it helps [10:46] jmarsden, but it appears my problem is caused by fakeroot, since the build need to generate something with root privilege, but fakeroot can't do anything except get a root id [10:49] rawang: have you the exact error message? [10:57] geser, sure , http://paste2.org/p/244640 [10:58] geser, thanks a lot [10:58] geser, you will noticed at line 27, it said permission deny [11:01] When a package need intltool to build, what's the difference between using intltool and intltool-debian? Is it just that -debian depends on less stuff? [11:03] Or is the only difference that intltool-debian supports "Debconf template files" and intltool doesn't? [11:05] rawang: my guess would be to set $HOME to something which can be written to (like /tmp) but better ask someone who is more familiar with mono packaging (like directhex) [11:05] moo? [11:06] aha, rawang has encountered a rather... common... issue [11:06] directhex: see the paste http://paste2.org/p/244640 from rawang [11:06] export MONO_SHARED_DIR=$(CURDIR) [11:07] add the above to rules [11:07] geser, but this is not the first time I run into "permission deny" problem when I build package with "dpkg-buildpackage -rfakeroot", "sudo dpkg-buildpackage" resovle all [11:07] and add "rm -rf $(MONO_SHARED_DIR)/.wapi" to your clean rule [11:08] ok [11:08] directhex, in the debian/rules file? [11:08] although whatever the package is, should you be cooperating with pkg-cli-apps ? [11:08] oh... right, sorry [11:08] * directhex goes back to sleep [11:08] directhex, wow, thanks a lot! :) [11:09] rawang: the buildd run the build as a user (and only parts as root with fakeroot) so you need to take care that your package doesn't write outside it's packaging directory [11:09] yes, debian/rules is the makefile. you need to override MONO_SHARED_DIR because mono has a simple evaluation for where to put the .wapi folder for processes [11:11] geser, but you know, I even failed at "debuild -S" at "permission deny" error, I have to use "sudo debuild -S" to update my .dsc file :( [11:12] rawang, right, you have files now owned by root [11:12] time for a big ol' "chmod -R" [11:12] ahhhh... [11:13] directhex, maybe "chown -R" :) [11:13]