[00:08] good night === gaurdro is now known as themuffinman === themuffinman is now known as gaurdro [00:16] is it possible to upload a new orig.tar.gz file to your launchpad ppa? [00:17] SolarWar: Only if you increment the version. [00:17] Same as any other repository with any sanity checks. [00:17] increment the ppa version you mean? [00:17] or the source version? [00:17] or the ubuntu version? [00:17] haha :) [00:20] SolarWar: The source version. [00:20] The bit before the final hyphen is the orig.tar.gz version. [00:29] ohh [01:29] how do learn what dev tool has a file called mkmf? [01:31] xmkmf? [01:31] d [01:31] d? [01:31] i will look [01:31] thanks [01:32] my synaptic couldn't find a package entitled xmkmf [01:33] I didn't say there was [01:33] might it be called anything else? [01:33] oh [01:33] i mis understood you [01:33] anteaya: packages.ubuntu.com has a search for that [01:33] anteaya: You can search for files on packages.ubuntu.com or use apt-file [01:33] okay thank you [01:33] thank you both [01:33] i will try that [02:04] i found the file i was looking for mkmf.rb. it is in the directory that i placed the compressed app prior to installing it. It does seem to have made it into the installation. How do I get it where it needs to go? [02:12] so if I'm running an apt-repo and people install debs from my repo, will they get an automatic updates popup when I update my debs to newer versions? [02:20] hi guys, i was reffered here by someone as a bug i made on launchpad hasnt been addressed, i wondered if someone could take a look for me -- https://bugs.launchpad.net/ubuntu/+bug/224424 [02:20] Launchpad bug 224424 in ubuntu "wifi/internet lags system" [Undecided,New] === cambridgecow is now known as ___cambridgecow_ === ___cambridgecow_ is now known as ___________cambr === ___________cambr is now known as loveUbuntuIsSorr === loveUbuntuIsSorr is now known as WhatIsLinux [02:37] Bodsda: I think it's much more likely that #ubuntu-bugs is the channel you want. [02:38] ScottK, apologies, thanks [02:39] No problem. === stdin_ is now known as stdin [03:06] siretart: Since you are our designated Launchpad rep, I guess I'll complain to you. [03:06] Reading the blog, http://news.launchpad.net/cool-new-stuff/simpler-interface - I'm supposed to just suck up the pain. [03:07] So that we can have things like "Link a related branch" (which I have never ever used once) smack in the middle of the U/I where most of the action happens. [03:08] Launchpad: Getting in user's way in 2004. === Bodsda is now known as Bodsda|AFK [04:01] morning === Bodsda|AFK is now known as Bodsda === asac_ is now known as asac [06:13] Who wants some simple packaging work? [06:13] persia : me :) [06:13] me, if you teach me how ;~) [06:14] Bodsda: Sure. First, visit http://qa.ubuntuwire.com/uehs/no_watch.html and pick a package. [06:14] persia : you dont have to teach me , i will try and revert to you if i need your help [06:14] persia, done [06:14] bliZZardz: Since I'll be explaining to Bosda anyway, you can follow along. [06:15] Just to make sure there are no conflicts, which packages did you select? [06:15] * persia encourages more people to play: lots of packages to choose from [06:15] 'spong' [06:15] persia : cool... do all those require erpackaging? [06:15] *repackaging? [06:15] bliZZardz: Nope, they all need a watch file. [06:15] bliZZardz: Which is your package? [06:15] persia : what is a watch file? [06:16] good question [06:16] A watch file is a specially formatted file that lets us check for new upstream versions automatically. [06:16] persia : gcal [06:16] This is a list of packages that are missing watch files and don't have maintainers in Debian, so it's our job to make sure they have watch files and get them up to date for Ubuntu. [06:17] persia, shouldnt the package maintainer be doing this? [06:17] The first step is to make sure we have the right environment to make changes. Do both of you have an intrepid build environment? [06:17] persia, ah, not for the next few hours [06:17] persia : i need to get it. [06:18] Bodsda: Where there is a maintainer, yes. For these packages, there is usually no maintainer (although there might be an Ubuntu maintainer who needs help). [06:18] can the Ibex build env be run from older versions? [06:18] older versions of U [06:18] sorry, i dont no much about this motu business persia, im downloading intrepid alternate iso atm [06:18] bliZZardz: Yes, you can run a build environment on hardy (or even Dapper). [06:19] oh, how? [06:19] Well, there are two commonly recommended ways to set up the build environment. pbuilder and sbuild. Do either of you use LVM? [06:19] * Bodsda wonders what LVM is [06:19] sorry, total n00b to this [06:20] i know pbuilder a lil. [06:20] need to try out LVM [06:20] Bodsda: It's the Logical Volume Manager. If you don't know, we won't do it now. [06:20] ok [06:20] where can i learn about all this? [06:20] OK. You'll both want to set up pbuilder then. [06:20] !pbuilder [06:20] bots on holiday [06:20] Right. [06:20] persia : does LVM always require a different /home? [06:21] No, just a /boot that's off LVM [06:21] bliZZardz: Nope. I only use LVM on about 20GB of my disks. [06:21] Flannel, a seperate /boot partition? or just the folder? [06:22] i hate grub so seperate /boot = trouble [06:22] Bodsda: well, it winds up being a separate boot partition [06:22] damn, ok [06:22] Bodsa : some basics : http://www.debuntu.org/how-to-install-ubuntu-over-lvm-filesystem [06:22] pbuilder information is available from https://wiki.ubuntu.com/PbuilderHowto [06:22] You may need to get the debootstrap from backports to be able to build an intrepid target. [06:22] cheers bliZZardz [06:23] persia : i would like to take up some more packages from there - based on my workload and the 'interestigness' of the package.. [06:23] Bodsa : guess we are sailing in the same boat..hence always there to help :) [06:24] persia, i have a wifi bug so im gonna lag to hell while i install these [06:24] persia : quick comment : the Xorg/nvidia driver seems to crash whenever i do an upgrade of teh restricted packages...it is so frustrating.. i have to reinstall it again and again [06:25] ty bliZZardz im new to this packaging thing, but am interested in helping so im here to learn (and teach what i learn) [06:25] bliZZardz: Works for me, so I can't help there. Did you file a bug? [06:25] bliZZardz, drop to shell just for the package install? [06:26] persia, ok, got pbuilder debootstrap and devscripts [06:26] persia : am trying to debug it , if dont succeed then will file a bug [06:26] Bodsda : https://wiki.ubuntu.com/PackagingGuide [06:27] major bookmarking going on here [06:28] :) [06:30] Bodsda: Did you set up pbuilder for intrepid based on the wiki yet? [06:31] bliZZardz: How is your effort to get an intrepid pbuilder going? [06:31] persia, err,,.,. no i was reading all the links on packaging [06:31] Bodsda: Once you start the pbuilder setup, it will take a while. May as well get it started, and read the wiki whilst you wait. [06:32] persia: i guess we can at best start tomorrow. So that Bodsda also gets a feel of it. [06:32] persia, ok, 1 question, the 'sudo pbuilder create --debootstrapopts --variant=buildd' command on the wiki, is that the full command or am i meant to substitute anything? [06:33] Bodsda : just try it out - nothing will bomb :) [06:33] bliZZardz, k, cool [06:33] That looks like the right command. I think you want to substitute --debootstrapopts, but I forget with what [06:33] * persia looks around hopefully for someone familiar with pbuilder to help Bodsda get set up [06:34] good morning [06:34] bliZZardz, persia it seems to be setting up a hardy build environment? -- bod@bodubuntustu:~$ sudo pbuilder create --debootstrapopts --variant=buildd [06:34] W: /home/bod/.pbuilderrc does not exist [06:34] Distribution is hardy. [06:34] Building the build environment [06:34] -> running debootstrap [06:35] persia : Bodsda will learn :) .. we have shown him the door.. let him/her open it [06:35] him, and do i need a key? [06:35] ;~) [06:36] Bodsda: nope. GPL keeps it unlocked [06:36] ;) [06:37] tarheelcoxn, good ;~) [06:37] Err. Keys are good, although we tend to use them more for signatures, than to lock anything away. [06:38] From memory, I think you want to copy /etc/pbuilder (possibly .rc?) to ~/.pbuilderrc, and then edit that (it'll include the series you want to target). [06:38] just a note, its downloading a load of packages so im lagged out for a bit [06:39] RAOF, should i have done that before 'sudo pbuilder create etc etc' ? [06:39] Bodsda: Understood: it takes a while the first time. [06:39] Bodsda: If it's creating a Hardy pbuilder, yes. [06:39] RAOF, oops, the wiki didnt mention that [06:40] Isn't there a nice 'pbuilder-dist' tool lying around somewhere? [06:40] Bodsda: Sorry, it's been a while since I used pbuilder; sbuild-on-lvm is nice :) [06:41] RAOF, n00b here -- will have to be a bit more vivid, sorry [06:41] Oh, that's just that I haven't used pbuilder for a while, because I like sbuild. [06:41] dholbach: hi! [06:42] ah, ok [06:42] There might be a handy tool in ubuntu-dev-tools, but if there is, the wiki ought be updated to instruct how to use it. [06:44] Bodsda : are you trying to create an env? [06:44] bliZZardz, i ran -- sudo pbuilder create --debootstrapopts --variant=buildd [06:44] its done now [06:44] * RAOF is down to only 5000 spam messages to find the ham in. [06:45] Bodsda: then what is the problem? :) [06:46] bliZZardz, what problem? [06:46] wow :) [06:47] * Bodsda is confused [06:47] brb [06:47] Bodsda : i would strongly suggest you to read the packaging guide and ask the forum any Qs -only if you have them. [06:48] This is a better place to ask questions: someone is likely to be able to answer in realtime. [06:48] persia : which is most suggested approach : pbuilder or SbuildLVM? [06:49] Pbuilder is much easier to set up. [06:49] Unless you happen to have some spare space on an lvm-VG anyway... [06:49] pbuilder is easier to set up, sbuild tends to be slightly faster. [06:49] hi nxvl [06:50] persia : you mean sbuild is faster in terms of the instructions/steps? [06:51] In terms of time to build a package. [06:51] bliZZardz: No, it doesn't take as long to run because snapshot is faster than untar and dropping a snapshot is faster than rm. [06:51] ROAF , ok . means the same [06:51] bliZZardz: No. It's faster in machine time, not in human time (they require about the same human time to run) [06:51] It also is slightly closer to the environment on the buildds, so you'll very occasionally pick up a problem there that you wouldn't in a pbuilder environment. [06:52] RAOF , means that sbuild is better :) - isnt it? [06:52] Yes. But not very much better, and if you don't already have some spare LVM space it's a _lot_ more work to set up. [06:53] bliZZardz: Well, there are other issues that pbuilder catches that sbuild misses, and ought be fixed. sbuild also requires more space on one's hard drive, and has more trouble building very large packages. [06:55] * bliZZardz pheeeewwww! [06:56] * bliZZardz wonders why god gave a choice! [06:57] back, needed a coffee ;~) [06:58] bliZZardz: Having multiple tools that implement policy helps to ensure that policy is clear and correct. Without multiple tools, we tend to conform to the tool, rather than the actual policy. [06:58] Bodsda: OK. So, the next step is to get the intrepid source for [06:58] persia : shouldnt the tool reflect the policy? [06:59] spong [06:59] bliZZardz: Yes, but nobody is a perfect developer, and if policy is unclear, different developers may interpret it differently. [07:00] persia, show me the source, how do i get spong? [07:01] Bodsda: apt-get source spong [07:01] persia : i dont essentially understand that. For i have seen that w.r.t development having a single policy and having the tools which carry the flavour of the policy helps a lot. [07:01] hi folks [07:02] bliZZardz: It presumes that the tool is a correct implementation of the policy. I question that assumption, for any tool and any policy. [07:02] persia, do i need to cd to somewhere first or anything? [07:02] Hi sistpoty|work [07:02] hi geser [07:03] Bodsda: You don't, but you might want to create a working directory. [07:03] persia, /home/bod/packaging_stuff be good enough? [07:03] sistpoty|work: hi! [07:03] hi nxvl [07:03] sistpoty|work: upstram already send me the man page missing [07:04] sistpoty|work: now i only need to take care of rpath [07:04] :D [07:04] nxvl: excellent! :) [07:06] persia, ok, i have the source for spong [07:06] Bodsda: Which version? [07:07] persia, 2.7.7 [07:07] Bodsda: OK. The next step is to look in debian/copyright to find the upstream homepage. [07:08] sistpoty|work: also i talked to them about it, and thay are going to take care for the next release (or maybe tomorrow) [07:08] nxvl: cool, great! [07:08] persia, debian/copyright? [07:09] Bodsda: When you downloaded the source, it created a directory, right? [07:09] You want to cd into that directory, and then look at the debian/copyright file. [07:10] persia, Spong was downloaded from http://spong.sourceforge.net [07:12] persia, was that what you were after? [07:13] Bodsda: That is what you seek :) [07:14] Now, go upsteam, and make sure that the download files are also hosted by sourceforge. [07:14] persia, ok -- how? just by checking sourceforge for 2.7.7 version? [07:15] Bodsda: Somewhere on the upstream homepage should be instructions on how to download it. You want to see if that is the internal sourceforge system, or external hosting. [07:16] persia, sorry, im a bit confused, i downloaded the source for 2.7.7, spong.sourceforge says 2.8-beta2 is released, and the download page only links to 2.7.6 [07:20] <\sh> moins [07:21] sistpoty|work: did you have a amd64 machine now? [07:22] Bodsda: OK. You've found a confusing one then. For the first time, let's try a different package. Once you've done a couple, you can go back to spong. [07:22] persia, haha, trust me,.,.lol, ok [07:22] Let me know when you find one with a good upstream page that has links to the newest versions, etc. [07:22] nxvl: yes [07:23] persia, will do [07:23] sistpoty|work: can you please confirme me if the last version fixes the rpath issue [07:23] nxvl: will, but only this evening once I'm home [07:25] sistpoty|work: ok, i will look if someone can test it, to try to fix it before going to sleep [07:25] :D [07:25] persia, found one, walpaper v0.1 (although theres a debian link to v0.1-1) [07:25] nxvl: heh :) [07:25] dholbach: you have and amd64, didn't you? [07:25] nxvl: yep [07:27] dholbach: can you please build augeas and run lintian on it [07:27] http://revu.ubuntuwire.com/details.py?package=augeas [07:27] in intrepid or hardy? [07:28] intrepid please [07:28] ok [07:28] persia, what now? [07:29] * nxvl HUGS dholbach [07:30] * nxvl has noticed that metallica makes his development more productive and quick === greeneggsnospam is now known as jsgotangco [07:34] dholbach: please run lintian on the augeas-tool deb [07:36] Bodsda: Sorry. Distracted. Next step is to construct a watch file. [07:36] In preparation, read the manual page for uscan. [07:36] persia, ok, will do [07:37] persia, ok, so it creates a watch file and updates the package when necessary? [07:37] dholbach: btw, nice posts! the ones about sponsoring [07:38] Bodsda: Almost. Someone (like yourself) creates the watch file, and uscan helps check to see if the current package is up-to-date. [07:38] nxvl: http://paste.ubuntu.com/24148 [07:38] persia, for what purpose, ive already discovered by checking the upstream page that i have the current version? [07:39] ugh! [07:39] still there [07:39] Bodsda: So that you don't have to do that for each of the 20,000 packages, and we can have a website that lists the ones that are out of date and need updating. [07:39] persia, ok, but if i dont need to do it, why did i? [07:40] Bodsda: Because this package doesn't have a working watch file yet. That's what you're going to fix today :) [07:40] dholbach: con you please run "sed -i -r 's/(hardcode_into_libs==).*$/\1no/' aclocal.m4" and build again [07:40] persia, ahh, got ya! so im making a watchfile so others dont have to? [07:41] Bodsda: Right. There's a few hundred packages left without either maintainers or watch files, and we have a hard time being sure they are updated for each release. [07:42] Once you create a watch file for this one, we won't have to worry about it until the next upstream release. [07:42] persia, is there not some super clever scripter out there who could write a script to do all this? [07:42] Bodsda: It typically takes a human to read debian/copyright and click the right links on the upstream website to find the download page. There is a script, but it's not perfect. [07:44] So, the first thing to do is to check to see if the script worked properly (because there is a script). From http://qa.ubuntuwire.com/uehs/no_watch.html, and the wallpaper line, there should be a link labeled "watch". [07:44] Try putting the contents of that into debian/watch in the downloaded wallpaper source. [07:44] 08:37 nxvl : dholbach: btw, nice posts! <-- what posts? [07:44] persia, version=3 [07:44] opts=uversionmangle=s/\.(tar.*|tgz|zip|gz|bz2)$//i,dversionmangle=s/[-.+~]?(cvs|svn|git|snapshot|pre|hg)(.*)$//i,pasv \ [07:44] http://www.cgarbs.de/stuff.en.html (?:.*/)?wallpaper-?_?([\d+\.]+|\d+)\.(tar.*|tgz|zip|gz|bz2|) debian uupdate [07:45] Bodsda: Right. Put that in debian/watch in the package you are editing. [07:45] persia, there is no watch file in the source [07:45] Exactly, which is the problem :) Create a new file. [07:46] mouz: http://daniel.holba.ch/blog/?p=129 and http://daniel.holba.ch/blog/?p=131 [07:48] dholbach: neverming, found the problem, configure and friends are full of --rpath instruccions [07:48] i will need to work harder on this one [07:49] nxvl: the output is the same after the sed-ding [07:49] dholbach: yes, thanks a lot [07:49] anytime [07:49] i have just found what the real problem is [07:49] persia, ok done. [07:50] it harder than i thought [07:50] Bodsda: Now, run `uscan --report-status` from the package directory to make sure it worked. [07:51] persia, uscan: No debian directories found [07:51] Really? In which directory are you? [07:52] i have a doubt [07:52] persia, the same dir as the watchfile [07:52] when a package is build [07:52] Bodsda: Ah. Go back up a level. [07:53] it send everything to debian/tmp [07:53] watch file should be called 'watchfile' or 'watch' ? [07:53] didn't it? [07:53] watch file should be called "watch". [07:53] oops [07:53] but in what point does it send things to debian/$BINARY_PACKAGE dir? [07:53] nxvl: It usually does debian/tmp or debian/$(srcpackage), depending on how you build it. [07:53] persia: i have it in both of them [07:54] persia, => Package is up to date [07:54] nxvl: Does your package build one or many binary packages? [07:54] many [07:54] Bodsda: Excellent, it worked. Next, check https://bugs.launchpad.net/ubuntu/+source/wallpaper/ to see if there are any other bugs you can fix at the same time. [07:54] nxvl: OK. Are you using dh_install? [07:54] yup [07:55] nxvl: In that case, it is dh_install that copies from debian/tmp to debian/$(BINARY_PACKAGE) [07:55] persia, no bugs [07:55] persia: thanks! [07:55] so i was right [07:55] :D [07:55] * nxvl HUGS persia [07:55] Bodsda: That makes it easy then. The package is up-to-date, and no bugs. Time to prepare the source for submission. [07:55] persia, cool, that was nice and simple [07:56] persia : what happens if there is a bug there? [07:56] Bodsda: In your shell call `export DEBEMAIL="Your Name " [07:56] bliZZardz: You add that fix to the candidate before you prepare for the upload. [07:56] persia, export DEBEMAIL=bodssocks@yahoo.co.uk ? [07:57] persia : you mean fix that bug? if yes, what happens if i dont know the fix? [07:57] Bodsda: Almost. You need your name as well. `export DEBEMAIL="Your Name " [07:57] ` [07:57] persia, export DEBEMAIL=Bod bodssocks@yahoo.co.uk ? [07:57] bliZZardz: Ask here for help, and if that doesn't work, check the next bug. [07:57] persia, export DEBEMAIL="Bod bodssocks@yahoo.co.uk" ? [07:58] i have DEBEMAIL and DEBFULLNAME separately [07:58] :D [07:58] Bodsda: Should be both GivenName and Surname. [07:58] nxvl: Then you have extra variables :) [07:58] persia, why? Bod isnt technically my real name but very (very very) few people know my real name [07:59] Bodsda: Because policy says to use real names. [07:59] persia, hhmmm,. ok [08:00] Bodsda : anonymity is not always good :) [08:00] Bodsda: Note that once you do this a lot, you'll end up needing to put your real name on your GPG key, and using your GPG key to sign the packages, so it won't hide it for long. [08:01] ScottK: morning [08:01] its just that ive never been called by my real name (ever since birth) but if its legally required... [08:01] It's not legally required, but it's expected. Maybe someone else has different advice. [08:02] You're welcome to add a nick to your name. [08:02] GPG key does not need to have real name [08:02] mouz: Hard to get cross-signed without it, no? [08:02] But should you ever want to get your GPG key signed, the name on it will want to match the name on (eg:) your driver's license. [08:02] ScottK: I've been using the new interface on edge.launchpad.net now for a few days when it was previously introduced [08:03] ok, il use real name, cheers guys [08:03] ScottK: and TBH, I like the new interface more than the one before. Of course you need to get a bit used to it, but the new interface makes several things instantly more visible, and higlights some previously underused features [08:03] persia, ok, the command didnt give any output so i assume everything went well...? [08:04] siretart: Note that there's currently no link from +queue to +builds, and a few others are missing (not that many use LP links for navigation). [08:04] ScottK: since you are making a more or less formal request, may I ask you to email me your request? (ideally with a bug reference, but I can also file a bug for you if necessary) [08:04] Bodsda: Yep. Now, call dch -i to launch your editor and update the changelog. [08:04] persia, ok, whats dch? [08:05] It should automatically set the right version, but you may need to adjust the target from your current release to "intrepid". After the *, add "Add watch file". [08:05] nevermind [08:05] Bodsda: It's the command to edit the debian changelog :) [08:05] siretart: did you know well the rpath issue? [08:05] persia: there was previously? Interesting [08:05] nxvl: I'm not sure what you mean [08:06] persia: do we already have a bug for that missing links? [08:06] siretart: http://wiki.debian.org/RpathIssue [08:06] persia, add watch file / added watch file ? [08:06] siretart: I'm not sure. I only noticed it today, but wasn't very concerned, as I don't tend to use the links. I'm not sure if it's a bug. [08:06] Bodsda: Either works. [08:06] persia, ok [08:07] Bodsda: Now save the file. [08:07] At this point, you're ready to build the package. Call `debuild -S -us -uc` to build an unsigned source package. [08:07] persia, bod@bodubuntustu:~/packaging_stuff/wallpaper-0.1$ sudo dch -i [08:07] parsechangelog/debian: warning: debian/changelog(l4): badly formatted heading line [08:07] LINE: Added watch file [08:07] persia : from here , can i guide Bodsda - can you correct me if i am wrong plz? [08:07] Bodsda: OK. Call `dch` again (no -i), and correct it. You need the text to follow the * [08:07] nxvl: I read about it [08:08] bliZZardz: If you like. [08:08] * Bodsda feels special with '2' mentors [08:08] Bodsda : me is no mentor ..lol... i just want to try so that persia can correct me :) [08:08] siretart: ok, thnks :D [08:08] bliZZardz, ok cool [08:09] bliZZardz, persia -- but first, should i do anything about the badly formatted heading line? [08:09] Bodsda : badly formatted - as in? [08:10] wallpaper (0.1-1ubuntu2) intrepid; urgency=low [08:10] sistpoty|work: in theory "chrpath -d $binary" should fix the problem, didn't it? [08:10] Bodsda , leave it - i dont see a problem. [08:10] nxvl: in theory rerunning autotools with a debian/ubuntu libtool should fix the problem ;) [08:10] bliZZardz, ok [08:10] Bodsda, next try : debuild -S -sa [08:11] this basically creates the source package [08:11] problems [08:11] sistpoty|work: rerunning it on my local repo and repackage it or in debian/rules? [08:11] ? [08:11] nxvl: whatever you prefer... I think the first one might be easier [08:12] bliZZardz, http://paste.ubuntu.com/24153/ [08:12] * nxvl is starting to hate autotools [08:12] :D [08:12] Um. No. [08:12] It's essential that the changelog parses cleanly. [08:13] nxvl: Miro uses chrpath to strip the rpath, if you wan an example. [08:13] nxvl: heh... so do I *g* [08:13] sistpoty|work: did you know a doc/recipe/howto on how to do it? [08:13] Bodsda: Please pastebin the first 10 lines or so of your changelog. [08:13] nxvl: aclocal; autoconf; libtoolize; automake [08:13] RAOF: thank! [08:13] persia, 'my' chanlog? how do i do that? [08:13] wheres the file? [08:13] debian/changelog [08:13] oh, got ya [08:14] bliZZardz, persia -- http://pastebin.com/f10984fa1 [08:15] Bodsda : move Added to the previous line - along with '*' [08:15] line 4 to line 3. [08:15] persia , am i right? [08:16] bliZZardz: Yes. [08:16] wooho \o/ i have just broke my package [08:16] * nxvl officialy hates atutools [08:16] bliZZardz, done [08:16] * bliZZardz feels elated :) [08:16] Bodsda : try the cmd again [08:17] nope, same error [08:17] Bodsda: You also want to update the -- root part to be your name & email (I'm not sure why the export didn't take: works for me) [08:17] oh..yea -there it goes [08:17] persia : bug in dch ;) [08:18] Looks like http://pastebin.com/m100d4f66 ? [08:18] bliZZardz, persia -- better? http://pastebin.com/f341a80e1 [08:19] Bodsda: Add an extra line between the changelog entry and the signature. Also, remove the -- root part: it only needs one name & email. [08:19] Bodsda : it should be similar to what persia pastebinn'ed [08:19] "root " is not reqd [08:20] http://pastebin.com/f4b507d27 [08:20] <> [08:20] email id within "< >" [08:20] * Bodsda bangs head on table [08:21] Bodsda : you want some nails on the table? ;) [08:21] http://pastebin.com/f2a53a266 [08:21] no, im good ta [08:22] bliZZardz, persia -- i still get the same error [08:24] persia : ?? [08:24] Bodsda: Do you maybe have a backup file or anything? That looks right. About which line does it complain? [08:25] Can't exec "fakeroot": No such file or directory at /usr/bin/dpkg-buildpackage line 477. [08:25] debuild: fatal error at line 1329: [08:25] ahh..this error is different [08:25]