[04:44] <alo21> hi
[04:48] <alo21> I made a patch and applied it. How can I buikd the package?
[04:49] <alo21> build*
[05:19] <alo21> I hava a problem applying patch. If I run edit-patch, it gives me: http://pastebin.ubuntu.com/1055443/
[05:54] <alo21> philipballew: can you help me, please?
[05:54] <philipballew> Im not very good at this stuff. but someone will halp eventually
[06:37] <alo21> kklimonda: could you help me, please?
[06:39] <alo21> kklimonda: sorry, I make a mistake
[06:39] <alo21> kancerman: could you help me, please?
[07:37] <astraljava> alo21: Could you pastebin the rejects file? should be something like hello.c.rej or similar.
[07:38] <alo21> astraljava: yes, herehttp://pastebin.ubuntu.com/1055443/
[07:38] <astraljava> That's the same output you pasted before.
[07:39] <alo21> astraljava: o yes.. sorry should I pastebin .patch?
[07:40] <alo21> astraljava: I also followed this guide (http://developer.ubuntu.com/packaging/html/fixing-a-bug.html)  the build succesfull ends, but seems patches were not applied
[07:48] <astraljava> Well if there are no reject files, then yes, the patch, please.
[07:49] <alo21> astraljava: wait... maybe I am making a mistake. Should I download from LP?
[08:03] <astraljava> alo21: I wouldn't know what you should be downloading from LP. :)
[08:04] <alo21> astraljava: the source code
[08:06] <astraljava> alo21: Well it depends. The patch could be against a certain version. Was that done by you, or someone else?
[08:06] <alo21> astraljava: the patch?
[08:08] <astraljava> alo21: Yes, the patch that fails to apply as per your pastebin entry just above.
[08:14] <alo21> astraljava: http://pastebin.ubuntu.com/1055581/
[08:23] <astraljava> alo21: Try adding a whitespace at the end of the patch.
[08:23] <astraljava> Sorry, newline of course.
[08:24] <alo21> astraljava: what do you mean: at the end of the patch  ?
[08:25] <astraljava> alo21: The patch has on the last line some text, it might need an additional newline so the last line is empty. Just go to the end and press enter, that should do it.
[08:27] <alo21> astraljava: I try to make the package.... just for informations: I am working with hello (quilt)
[08:27] <astraljava> alo21: Yeah, I figured. I tested against the precise version of hello.
[08:29] <alo21> astraljava: Should I run thi command to apply my patch:  patch -p1 < debian/patches/file.patch ?
[08:31] <astraljava> alo21: If you are using debuild to build the package, then it should detect a patch if it's in the same directory, and offer you to add it as a proper patch under debian/patches/
[08:32] <astraljava> alo21: But you can of course test the patch that way, but then you cannot use it as a debian/patches/ patch anymore, as it of course has been applied already.
[08:32] <alo21> astraljava: Should I see the patch applied in both cases?
[08:34] <astraljava> alo21: You will want to see the patch applied as the end result, yes. You have two choices in making it happen, apply it with patch manually, or let the debuild handle it.
[08:37] <alo21> astraljava: to build my package I used: debuild -us -uc
[08:37] <alo21> astraljava: hello packages succesfully, but I can not see any changes
[08:38] <alo21> hello was built succesfully*
[08:38] <astraljava> alo21: Look one directory up.
[08:39] <alo21> astraljava: I have just installed .deb package
[08:39] <alo21> astraljava: but if I run hello, I can not see any change
[08:44] <alo21> astraljava: when you sad: "add a newline ad the and", did you meant this: http://pastebin.ubuntu.com/1055616/  ?
[08:47] <astraljava> alo21: Yes.
[08:47] <alo21> ok
[08:48] <alo21> astraljava: it is so weird
[08:52] <alo21> astraljava: any suggestions?
[08:55] <astraljava> alo21: Hang on, I'll try something. (and on the phone, brb)
[09:25] <astraljava> alo21: My inexperience is showing, I'm afraid, but when I prepare a debdiff out of it, apply that to a pristine source, then build it, the change is effective. Perhaps someone else can guide you better in the other methods.
[09:26] <alo21> astraljava: how did you make a debdiff?
[09:29] <astraljava> alo21: I think I linked that page to you earlier already, but here it is again: https://wiki.ubuntu.com/PackagingGuide/Recipes/Debdiff
[09:30] <alo21> astraljava: does metter if I use nano instead of vi?
[09:31] <astraljava> alo21: Certainly not. :) Any editor will do.
[09:31] <alo21> astraljava: The link above, is how to propose a maerge
[09:31] <alo21> merge*
[09:33] <astraljava> alo21: It's how you work with debdiffs. Like I said, it works for me when I do it that way. Others can help you with some alternative routes.
[09:33] <alo21> astraljava: thanks
[09:33] <alo21> Can somebody else help me with patch?
[09:34] <astraljava> alo21: Sorry I couldn't be of further assistance.
[09:34] <alo21> astraljava: is ok.... thanls a lot for your assistance
[09:45] <astraljava> alo21: Actually, now it works. I don't know what I did wrong there earlier.
[09:45] <alo21> astraljava: debdiff?
[09:46] <astraljava> alo21: No need for debdiff.
[09:46] <alo21> astraljava: what did you use?
[09:47] <astraljava> The procedure is simple; apt-get source hello; cd hello<tab>; patch -p1 < <path/to/patch>; dpkg-source --commit; dch -i; debuild -S; dpkg-buildpackage
[09:47] <alo21> astraljava: why commit?
[09:49] <astraljava> alo21: Because otherwise debuild will refuse to continue building.
[09:52] <alo21> astraljava: I ha this "error running debsign failed" when I run debuild -S
[09:52] <alo21> astraljava: it seems that I have no an gpg key or something similar
[09:54] <alo21> astraljava: I cannot sing changes and any dsc files
[09:54] <astraljava> alo21: You didn't update the changelog with `dch -i`, or your gpg key doesn't have the same identifier that you put in changelog.
[09:54] <astraljava> alo21: But you can get around that with `debuild -S -us -uc`
[10:07] <alo21> astraljava: If I run dpkg-source, it tells: info: there are no local changes to record
[10:09] <astraljava> alo21: Then your patch didn't apply correctly.
[10:10] <alo21> astraljava: why?
[10:11] <astraljava> alo21: I wouldn't know. You need to pastebin the output of that command.
[10:15] <alo21> astraljava: http://pastebin.ubuntu.com/1055724/
[10:18] <astraljava> alo21: I don't know what is going wrong, for me it suggests a new patch name. Double-check that you have the new, untouched source tree, and the patch is correct.
[10:22] <alo21> astraljava: wait... when I create a patch, should I download the source again and apply that patch to the new sorce?
[10:24] <astraljava> alo21: Yes, the patch won't do anything on changed sources.
[10:37] <alo21> astraljava: I tried it... the patch and source rae ok.
[10:37] <alo21> astraljava: I built the package, but I cannot see any change
[10:40] <astraljava> alo21: Did you follow the work flow exactly like I posted above?
[10:41] <astraljava> alo21: Are you sure you're executing the correct binary after the change? Did you install the new .deb?
[10:41] <alo21> astraljava: yes... but I used debuild -S -us -uc
[10:42] <alo21> astraljava: sudo dpkg -u <package>.deb  ?
[10:42] <astraljava> Heh, that's why you won't see the change. :) `sudo dpkg -i <package>.deb`
[10:43] <alo21> astraljava: sorry I meand -i
[10:43] <alo21> meant*
[10:46] <alo21> astraljava: what could going wrong?
[10:54] <astraljava> alo21: I would need the output of the whole work flow. Prior to that, make sure the patch is secure, then start in a clean directory, and also remove the existing hello package to be sure you're running the right binary.
[10:56] <alo21> astraljava: even how I created the patch?
[10:57] <alo21> astraljava: I run: sudo apt-get remove hello to remove hello, but it is still installed on my system
[10:59] <astraljava> alo21: You can check which package provides the binary with: `dpkg -S `which hello``
[11:02] <astraljava> alo21: O
[11:02] <astraljava> alo21: Sorry, I'm going out for a while, I'll be back in an hour or so to see your progress.
[11:02] <alo21> astraljava: ok.. thanks again
[11:03] <astraljava> Actually, scratch that. It just started raining.
[11:05] <alo21> astraljava: it works
[11:06] <alo21> astraljava: I removed hello (programm) in usr/local/bin
[11:06] <astraljava> Right.
[13:22] <alo21> hi all
[13:22] <alo21> Can I upload patches on Launchpad?
[13:24] <penguin42> alo21: Yes
[13:24] <alo21> penguin42: thanks
[13:25] <penguin42> alo21: You can attach a patch to a bug as an attachment, you can also if you feel up for it, you can submit the patch to the bzr source code repository and ask for it to be reviewed
[13:25] <penguin42> alo21: Is it a patch you wrote?
[13:26] <alo21> penguin42: what do you mean with wrote?
[13:26] <penguin42> alo21: Is it a patch you got off the net somewhere, or did you figure out the problem and change the code
[13:26] <alo21> penguin42: second one
[13:27] <penguin42> ok; it's always good to say that so people can track it
[13:29] <alo21> penguin42: so... can I upload the patch as an attachment on Launchpad in tgis case?
[13:29] <penguin42> alo21: Yep
[13:30] <alo21> penguin42: and when should I upload it via bzr?
[13:30] <penguin42> alo21: What's the bug number?
[13:30] <alo21> 988775
[13:30] <alo21> penguin42: https://bugs.launchpad.net/ubuntu/+source/sessioninstaller/+bug/988775
[13:30] <ubot2> Ubuntu bug 988775 in sessioninstaller "typo in ../sessioninstaller/core.py:915 -- follwing" [Low,In progress]
[13:32] <alo21> penguin42: is a bitsize
[13:32] <alo21> penguin42: I am new in this group, but I know quite good C and Python
[13:32] <penguin42> alo21: nod; I'd attach the patch first
[13:37] <alo21> penguin42: should I set "Assigned to" as Nobody, once the patch will be approved?
[13:38] <penguin42> alo21: I'm not quite sure the right way to use the assigned-to; it's used more where people are handing out bugs for others to ix, or to make sure people know that you are looking at it
[13:38]  * penguin42 tries to find the page on howto submit stuff using bzr; it's moved from my bookmark
[13:39] <alo21> penguin42: ok
[13:40] <alo21> penguin42: you are very helpful and open
[13:40] <penguin42> alo21: Here we are https://wiki.ubuntu.com/Bugs/HowToFix
[13:40]  * alo21 feels very comfortable here at Ubuntu
[13:41] <alo21> penguin42: thanks again, I keep it in mind
[13:41] <penguin42> no problem
[13:42] <alo21> penguin42: have noticed that people who use Ubuntu, but not contribute to make Ubuntu everyday better are not very polite?
[13:43] <penguin42> alo21: Oh politeness varies a lot - this channel tends to be good
[13:43] <alo21> penguin42: yes... this is very good...
[13:44] <alo21> penguin42: I am sorry, but I have to go.. thanks for your assistance and have a nice day
[13:44] <penguin42> no problem - come back!
[16:24] <alo21> hi all
[17:14] <alo21> Hoq can I know wich source contains some functionalities?
[17:17] <TheLordOfTime> alo21:  what do you mean?
[17:17] <alo21> TheLordOfTime: If I would fix a bug, I should know where the bug is
[17:18] <TheLordOfTime> alo21:  if you are going to fix a bug, then the bug in question is bound to the specific source package
[17:18] <alo21> TheLordOfTime: for example, I would like to fix this bug: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/835018
[17:18] <ubot2> Ubuntu bug 835018 in software-center "Can't select description text in software item screen" [Low,Confirmed]
[17:18] <TheLordOfTime> and you should fix in Quantal
[17:18] <TheLordOfTime> alo21:  check in 12.04
[17:18] <TheLordOfTime> does this still exist in 12.04?
[17:18] <TheLordOfTime> Updated for Software Center version 5.1.14.1, Ubuntu Precise Beta 2, as the package title and subtitle are selectable in this version. Only the description field remains unselectable.  <--
[17:18] <alo21> TheLordOfTime: yes.
[17:19] <TheLordOfTime>   Version 5.2.1 (precise)  <--
[17:19] <alo21> TheLordOfTime: I downloaded the sources, but there are a lot of file .py
[17:20] <TheLordOfTime> well, the bug in its *original* form was fixed, you can select the title and version
[17:20] <TheLordOfTime> you can't select the description
[17:20] <alo21> TheLordOfTime: How do I know whichfile.py manages descriptions?
[17:20] <TheLordOfTime> how should i know
[17:20]  * TheLordOfTime isnt a dev in that package
[17:20] <TheLordOfTime> you'll have to dig around
[17:20] <TheLordOfTime> and find out
[17:21] <alo21> TheLordOfTime: are joking?
[17:21] <alo21> are you*
[17:21] <TheLordOfTime> nope
[17:21] <TheLordOfTime> i'm not a dev on that package, i cant help find where the stuff is that needs fixing
[17:22] <TheLordOfTime> right now, i'm working on an nginx package, so i am a tad busy
[17:22] <alo21> TheLordOfTime: ok, anyway... thanks
[17:24] <TheLordOfTime> sorry i couldnt be of more help, but the bug squad doesnt directly analyze each package
[17:25] <TheLordOfTime> well... that's not true, i know the internal workings of the nginx package, but i'm on that team, so...
[17:25] <TheLordOfTime> :P
[17:26] <TheLordOfTime> https://launchpad.net/software-center  <-- you might be able to ask one of the people who develops this
[17:26] <TheLordOfTime> alo21:  ^
[17:26] <TheLordOfTime> they'd know the internal workings
[17:26] <alo21> TheLordOfTime: thank you
[17:41] <alo21> this bugs (http://harvest.ubuntu.com/opportunities/) does not seem all bitsize
[17:42] <TheLordOfTime> its tied in to the 'bitesize' tag.  and bitesize bugs may still take a bit of work
[17:42] <TheLordOfTime> most of the bugs you'll see require people who have programming and dev skills
[17:43] <TheLordOfTime> 'tis why my name isnt on many patches xD
[17:43] <TheLordOfTime> most of my packages are minor fixes, or patches derived from upstream changes (especially with nginx)
[17:43] <TheLordOfTime> s/packages/patches/
[17:44] <TheLordOfTime> but yeah, it requires a tiny bit of development skills in the languages being used on programs
[17:44] <TheLordOfTime> s/tiny bit/bit/
[17:44]  * TheLordOfTime notices he has a build that's exploding
[17:44] <TheLordOfTime> oops
[17:44]  * TheLordOfTime shifts attention
[17:46] <alo21> TheLordOfTime: what do you mean with: "dev skills"?
[17:47] <TheLordOfTime> dev skills ina specific language
[17:47] <TheLordOfTime> i.e. development knowledge of python, dev knowledge of C, etc.
[17:47] <TheLordOfTime> depending on the langauge and package
[17:47] <TheLordOfTime> in your case, python
[17:48] <TheLordOfTime> s/your/this/
[17:48] <TheLordOfTime> but also a knowledge of what file works with what
[17:48]  * TheLordOfTime needs to divert his attention before pbuilder eats up all 6 cores in his CPU and all 16GB of memory on his packaging system
[17:50] <alo21> TheLordOfTime: how do the other developer know a lot of packages structure?
[17:50] <TheLordOfTime> first off the developers of a package helped to *build* the package (or at least the uploader did)
[17:51] <TheLordOfTime> and if they built the package they understand the source code
[17:52] <TheLordOfTime> bah!
[17:52]  * TheLordOfTime swears
[17:52] <TheLordOfTime> just what i didnt want to have happen...
[17:52]  * TheLordOfTime moves off to go fix a hard-crash on the computer that he does his packaging on
[18:20] <TheLordOfTime> anyone here agree with me this report looks more like a question than a bug?  https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/1016932
[18:20] <ubot2> Ubuntu bug 1016932 in gnome-system-tools "Setting user to Adminstrator does not allow software installation" [Undecided,Confirmed]
[18:20] <TheLordOfTime> (read the details)
[18:21] <knome> it's a bug. maybe a better description would be "Setting user as administrator doesn't give him sudoing rights"
[18:22] <knome> whether this is intentional or not, i don't know, but that's what the bug was filed against
[18:41] <pleia2> TheLordOfTime: "him"? really?
[18:41] <pleia2> knome: ^^
[18:41] <pleia2> :P
[18:42] <knome> pleia2, in the bug, the OP refers to "joey"
[18:42] <pleia2> yeah, I confirmed and both users are not him ;)
[18:42] <pleia2> but yeah, it's a bug
[18:42] <pleia2> exists in 12.10 too :(
[18:54] <knome> aha
[18:55] <knome> in that case, sorry. definitely no sexism intended :P
[19:46] <alo21> I have a problem building juju
[19:47] <alo21> this is what I see: http://pastebin.ubuntu.com/1056476/
[19:59] <LordOfTime> help2man: can't get `--help' info from bin/juju  <--
[19:59] <LordOfTime> although first off, packaging help in -packaging, but why're you building JuJu again
[20:08] <TheLordOfTime> alo21:  ^
[20:08] <alo21> TheLordOfTime: to test my patch
[20:09] <TheLordOfTime> looks like your patch broke something
[20:09] <TheLordOfTime> alo21:  is there a bug tied to this thing?
[20:09] <TheLordOfTime> (and did you upload your patch there)
[20:10] <alo21> TheLordOfTime: here the bug: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/956000
[20:10] <ubot2> Ubuntu bug 956000 in juju "'juju bootstrap' with no arguments gives confusing message" [Low,In progress]
[20:10] <alo21> TheLordOfTime: I haven't uploaded the patch yet
[20:10] <TheLordOfTime> can you pastebin the patch for me?
[20:10]  * TheLordOfTime will see if he can replicate your build issues
[20:11] <alo21> TheLordOfTime: here: http://pastebin.ubuntu.com/1056505/
[20:12] <alo21> TheLordOfTime: I have to sat that inside debian/patches I have a dirrefent type of file
[20:13] <alo21> TheLordOfTime: whene i run: patch -p1 < /home/alo21/hello/juju-0.5+bzr531/debian/patches/confusing-message.patch
[20:13] <TheLordOfTime> ewww
[20:13] <TheLordOfTime> dont do that
[20:13] <TheLordOfTime> use quilt
[20:13] <TheLordOfTime> (which the packaging guide says to use)
[20:14] <alo21> TheLordOfTime: the file inside debian/patches is: http://pastebin.ubuntu.com/1056509/
[20:15] <TheLordOfTime> that's DEP3
[20:15] <TheLordOfTime> for build testing, DEP3 isnt really neede
[20:15] <TheLordOfTime> d
[20:15] <TheLordOfTime> and since that's all I'm doing, build testing, its irrelevant
[20:15] <TheLordOfTime> (won't be when the package gets fixed, but that's a differents tory)
[20:16] <alo21> TheLordOfTime: but it should be a .patch
[20:18] <TheLordOfTime> so you save it as a .patch
[20:18] <TheLordOfTime> i'll help you with that later
[20:18]  * TheLordOfTime dgets the juju source
[20:19] <alo21> TheLordOfTime: is ok if I download the source with: aot-get source juju?
[20:19] <alo21> apt*
[20:20] <TheLordOfTime> if you're not running Quantal yourself, i wouldnt do that
[20:20] <TheLordOfTime> since if you're on Precise the default apt-get source will get you Precise's
[20:20]  * TheLordOfTime always relies on dget anyways
[20:20] <TheLordOfTime> its just a thing i do
[20:20] <TheLordOfTime> anyways, i got the source, i've applied your patch, running build tests
[20:21] <alo21> TheLordOfTime: i run this command: atch -p1 <  <path/to/patch>; dpkg-source --commit; dch -i; debuild -S -us -uc; dpkg-buildpackage
[20:22] <TheLordOfTime> for the record, i dont trust dpkg-buildpackage
[20:22] <TheLordOfTime> i dont trust one-liners eithier
[20:22] <TheLordOfTime> where'd you get that one-liner from
[20:22] <TheLordOfTime> or rather that string of commands
[20:23] <astraljava> Me, and for the record, it's not meant to be a one-liner. Just a list of commands. :)
[20:23] <astraljava> As you can obviously see it wouldn't work as such anyway.
[20:23] <alo21> TheLordOfTime: I did not run theme on one line
[20:23] <alo21> in*
[20:24] <TheLordOfTime> whatever
[20:24] <TheLordOfTime> i personally dget the source, then *manually* import the patch using Quilt (i take the patch in raw format and save it somewhere on my system), then dch -i, then debuild -S, and then i testbuild the package with pbuilder
[20:24] <alo21> does you building work?
[20:24] <TheLordOfTime> a little bit more stuff needed, but...
[20:24] <TheLordOfTime> i just started the build process
[20:25] <TheLordOfTime> and like the LP PPA builders..
[20:25] <TheLordOfTime> it has to generate a base chroot
[20:25] <alo21> TheLordOfTime: could you tell me all the command you run, please?
[20:25] <TheLordOfTime> ... ***REALLY***?
[20:25] <TheLordOfTime> ***SERIOUSLY***
[20:25] <TheLordOfTime> well fine then
[20:25]  * TheLordOfTime hates you too
[20:26]  * TheLordOfTime is annoyed at builder
[20:26] <alo21> TheLordOfTime: if you do not want
[20:26] <TheLordOfTime> nah its something unrelated
[20:26] <TheLordOfTime> give me a bit
[20:26] <alo21> TheLordOfTime: ok
[20:28] <TheLordOfTime> this problem with pbuilder always happens when i start on a new system
[20:28] <TheLordOfTime> either that or a dependency is broken (unlikely)
[20:31] <alo21> TheLordOfTime: did you complete packaging?
[20:32] <TheLordOfTime> alo21:  oyi, you need to learn patience
[20:32] <TheLordOfTime> patience is required with bugs and when having someone help you
[20:32] <TheLordOfTime> my *strong advice* is you wait until i tell you if it worked or not
[20:32] <alo21> TheLordOfTime: I tought you had another problem... so... sorry.
[20:33] <alo21> I wait here
[20:33] <TheLordOfTime> the problem i'm having is with pbuilder itself, unrelated to building your package
[20:33] <TheLordOfTime> so i'm rebuilding the pbuilder tarball that is based on everything
[20:34] <alo21> TheLordOfTime: wow... why are there so many differnt techniques to build a package?
[20:34] <TheLordOfTime> alo21:  there just are
[20:34] <TheLordOfTime> and personally i do ***NOT*** recommend dpkg-buildpackage
[20:35] <TheLordOfTime> under any circumstances
[20:35] <TheLordOfTime> astraljava:  ^
[20:35] <TheLordOfTime> i'm redoing my blog, once i do that, i'll write a blog about how i do things
[20:35] <TheLordOfTime> and just give a few reasons as to why i do things that way
[20:35] <TheLordOfTime> and what commands I write
[20:35] <astraljava> TheLordOfTime: Calm down, I wouldn't use it for devel cycle bugfixing either. :) It was just a simple patch check-up on same release that the user was running.
[20:36] <TheLordOfTime> indeed
[20:36] <TheLordOfTime> astraljava:  :P
[20:36] <TheLordOfTime> astraljava:  i'm writing the blog anyways, so i know the blog works on planet :P
[20:36] <astraljava> The package was GNU hello. *smirk*
[20:36] <TheLordOfTime> LOLOLOLOLOLOLOLOL
[20:36] <TheLordOfTime> with the hello package, well... :p
[20:36] <TheLordOfTime> i should write up a helpdoc...
[20:36] <alo21> TheLordOfTime: you use pbuilder to do not stain you system, right?
[20:36] <TheLordOfTime> post it on the wiki under my namespace or some crap
[20:37] <astraljava> TheLordOfTime: But I agree with you otherwise, just haven't used quilt before, but since it's the de-facto patching system nowadays, I will.
[20:37] <TheLordOfTime> alo21:  my packaging system is a desktop that I built that has 6 cores running at 3.2GHz each, with 16GB of memory available to it
[20:37] <TheLordOfTime> its ***sole purpose*** is a dev environment
[20:37] <TheLordOfTime> that includes ruby, GNU C, GNU C++, python, perl, and a few other languages
[20:37] <TheLordOfTime> as well as all the debian build stuffs
[20:38] <TheLordOfTime> so in this case it doesnt strain my system
[20:38] <alo21> TheLordOfTime: ahaha
[20:39] <astraljava> alo21: pbuilder is handy for two reasons (that I care about, anyway, there are probably others): 1) always clean, no left-over dependencies that might skew the results, and 2) you don't need to run the devel cycle release on your desktop, and still are able to test on it.
[20:39] <astraljava> TheLordOfTime: It was 'stain', not 'strain'.
[20:39] <penguin42> TheLordOfTime: Do you ever get even vaguely close to using the 16GB?  I rarely do on my quad core 8GB machine, even when doing a -j10 build
[20:40] <TheLordOfTime> penguin42:  only if/when i'm running 18 things at once :P
[20:41] <TheLordOfTime> (and most of that's python)
[20:41] <TheLordOfTime> ah
[20:41] <TheLordOfTime> astraljava:  meh, not really
[20:42] <penguin42> TheLordOfTime: It is nice to be able to run a large VM with say a different distro in to build on that and be able to give the VM a good chunk of resource
[20:42] <TheLordOfTime> indeed
[20:42] <TheLordOfTime> i do that for Debian
[20:42] <TheLordOfTime> :P
[20:42] <alo21> astraljava: do you create a new pbuilder environment every time you build a new package?
[20:43] <TheLordOfTime> alo21:  its a chroot environment, the base exists all the time, but each chroot gets the additional required packages as determined by the debian package
[20:43] <astraljava> TheLordOfTime: Not really what?
[20:43] <TheLordOfTime> i.e. if it requires iamtheevil, and iamtheevil is not in the base tarball, it'll get those
[20:43] <alo21> TheLordOfTime: it seems you are very proud of your spacecrafr
[20:43] <TheLordOfTime> astraljava:  its not really a stain on my system
[20:43] <alo21> spacecraft*
[20:43] <TheLordOfTime> s/those/it/
[20:45] <astraljava> TheLordOfTime: I mean the question was "you use pbuilder to [] not stain you[r] system", as in it won't leave cruft on your own system.
[20:45] <alo21> TheLordOfTime: you run pbuilder-dist <distro>  --save-after-login, all your installed deps stay there
[20:45] <TheLordOfTime> ah
[20:45] <TheLordOfTime> astraljava:  i purge my cache pretty often
[20:45] <TheLordOfTime> usually once a week
[20:45] <TheLordOfTime> (at least for pbuilder, minus the base tarball)
[20:45] <TheLordOfTime> alo21:   i dont do that intentionally
[20:45] <TheLordOfTime> ;P
[20:45] <TheLordOfTime> i know that's what happens, but all the extra cruft goes away
[20:46] <astraljava> I don't think that's the point. You want to be sure the dependencies are set correctly for a package. If you don't test on pbuilders, you won't know which dependencies have already been installed by something else.
[20:46] <alo21> TheLordOfTime: good
[20:47] <TheLordOfTime> regardless
[20:47] <TheLordOfTime> i dont *care* whether dependencies are saved
[20:47] <TheLordOfTime> the reason i dont save those dependencies is because the *point* of a pbuilder base tarball is to have the *absolute basics*
[20:47] <TheLordOfTime> and then get the rest including dependencies
[20:48] <TheLordOfTime> the same general thing happens in the ppa builders
[20:48] <TheLordOfTime> except that they rebuild the base environment for each build
[20:48] <TheLordOfTime> (from observations)
[20:48] <TheLordOfTime> as well as install the dependencies and the likes for the build process
[20:48] <TheLordOfTime> afterwards, the chroot gets erased
[20:49] <penguin42> yeh the danger is having a package installed that turns out to have been a dependency but wasn't listed
[20:49] <TheLordOfTime> then the package needs bugfixed :P
[20:50] <penguin42> nod
[20:51] <TheLordOfTime> penguin42:  if a dependency is needed, and not listed in debian/control, that package needs burninated with fire until a replacement comes out
[20:51] <penguin42> TheLordOfTime: Indeed - but that's what I mean about the danger that a clean pbuilder removes
[20:51] <TheLordOfTime> indeed.
[20:52] <TheLordOfTime> oh i see
[20:52]  * TheLordOfTime misunderstood your intent :)
[20:52]  * TheLordOfTime yawns
[20:52]  * penguin42 admits to not liking pbuilder, but I only do an occasional fix - if you're doing stuff all the time I can see it would be easier
[21:12] <TheLordOfTime> hmm
[21:12] <TheLordOfTime> i cant seem to get pbuilder to work
[21:12]  * TheLordOfTime checks his ppas
[21:13] <TheLordOfTime> ooh i have a 'randombuilds' ppa :P
[21:13]  * TheLordOfTime uses
[21:21] <TheLordOfTime> bug or no bug?  https://bugs.launchpad.net/bugs/1016972
[21:21] <ubot2> Ubuntu bug 1016972 in owncloud "Owncloud 4.0 release, will 12.04 update be available?" [Undecided,New]
[21:21] <TheLordOfTime> (for the other bug squad peoples)
[21:25] <jtaylor> it might make sense for backports
[21:25] <TheLordOfTime> should i repoint this to backports?
[21:25] <jtaylor> you should check if a newer version packaged
[21:26] <jtaylor> if yes point the reporter to the wiki page on backports
[21:26] <jtaylor> depending on the rdeps it might be simple
[21:26] <TheLordOfTime> alo21 https://launchpadlibrarian.net/108472904/buildlog_ubuntu-quantal-i386.juju_0.5%2Bbzr542-1.1_FAILEDTOBUILD.txt.gz
[21:26] <TheLordOfTime> same error you're getting
[21:27] <alo21> TheLordOfTime: could it be a bug?
[21:27] <TheLordOfTime> unlikley
[21:27] <TheLordOfTime> since the non-modified source builds perfectly
[21:27] <TheLordOfTime> a MOTU tested that
[21:27] <TheLordOfTime> jtaylor:  its already in Quantal as 4.0.2
[21:28] <TheLordOfTime> so i'll point them to the backports wiki page
[21:28] <jtaylor> TheLordOfTime: good, it has no rdeps so its a straightforward backport
[21:28] <jtaylor> though if its brand new it might make sense to wait a while to let it stabilze
[21:30] <TheLordOfTime> jtaylor:  it looks brand new-isn (2012-06-17), but should i still post about the backport process, and then close the bug i already referenced (assuming in the description i mention it should sit a while and be tested before filing a backport request)
[21:33] <jtaylor> you could leave the bug open
[21:33] <jtaylor> just reassign it to backports
[21:33] <jtaylor> also debian has a 4.0.3
[21:34] <jtaylor> so its probably not very stable yet if it throws out so many bugfix releases
[21:35] <TheLordOfTime> its the precise-backports project, right?
[21:35]  * TheLordOfTime wants to make sure he doesnt break it
[21:37] <jtaylor> yes
[21:37] <jtaylor> though it should be checked if it builds in precise unmodified
[21:37] <TheLordOfTime> well, given my system is fubar'd... :P
[21:37] <TheLordOfTime> (you've seen -MOTU with the issues i'm having)
[21:38] <TheLordOfTime> i'll dget it and use my buildtests ppa
[21:40] <TheLordOfTime> and for the record, i love whomever set up the -bugs-announce system :P
[21:41] <TheLordOfTime> its nice to be able to see new bugs come out :P
[21:41]  * TheLordOfTime has a highlighter to see if 'nginx', 'display-dhammapada', or 'php5' are mentioned
[21:43] <TheLordOfTime> good, the PPAs are fast today :)
[21:47] <TheLordOfTime> jtaylor:  https://launchpad.net/~trekcaptainusa-tw/+archive/build-tests/+build/3600637  <-- built without incident
[21:51] <TheLordOfTime> alo21:  hang on a minute
[21:52] <alo21> TheLordOfTime: ok
[21:56] <TheLordOfTime> arand:  (from -motu) i was trying to help confirm whether there was a build problem caused by a patch or caused by the original source for the bug that alo21 was working on
[21:56] <TheLordOfTime> that bug is https://bugs.launchpad.net/ubuntu/+source/juju/+bug/956000
[21:56] <ubot2> Ubuntu bug 956000 in juju "'juju bootstrap' with no arguments gives confusing message" [Low,In progress]
[21:56] <TheLordOfTime> their patch applies with quilt, afaict, but it does not build
[21:57] <TheLordOfTime> was trying to figure out whether it was failing to build because of the patch or because of the original package from Quantal
[21:59] <TheLordOfTime> arand:  but if you're saying the original package isnt building from that source, then that's a bigger problem=
[22:01] <arand> Yeah :/ I'm not sure if the failures in the test cases are serious, the fact that they fail are enough to abort the build though.
[22:20] <alo21> TheLordOfTime: should I comment this bug (https://bugs.launchpad.net/ubuntu/+source/juju/+bug/956000) and say that is no possible to fix the bug due to instability?
[22:20] <ubot2> Ubuntu bug 956000 in juju "'juju bootstrap' with no arguments gives confusing message" [Low,In progress]
[22:21] <TheLordOfTime> absolutely not
[22:21] <TheLordOfTime> arand and i are still debating what the problem is
[22:21] <alo21> TheLordOfTime: ohh.. I did not read it
[22:21] <TheLordOfTime> (what we do know is the version that exists in Quantal fails to build from source (FTBFS))
[22:22] <TheLordOfTime> well, we're debating in #ubuntu-motu, they were helping me with pbuilder, now we're on a diagnosis-of-problem issue
[22:24] <alo21> TheLordOfTime: I am so sorry, but I have to go. Could send me by email what did you decide, please. You can find my info here: https://launchpad.net/~alo21
[22:25] <alo21> TheLordOfTime: thanls again and have a nice day
[22:26] <alo21> thanks*