=== exocaesa1 is now known as exocaesar === exocaesar is now known as Guest82232 === Guest82232 is now known as exocaesar === Aaton_off is now known as Aaton === Aaton is now known as Aaton_off === RedBeard__ is now known as RedBeard_ === Gallomimia_ is now known as Gallomimia [05:14] hallyn: I don't remember you telling me that these are done, so I guess that's fine ;) but wait(state, timeout) doesn't quite work [05:15] hallyn: if passed (state, -1), it works as expected but when passed (state, 20) for example, it'll always wait for the timeout and will always return False [05:15] hallyn: even if state is reached before the timeout [05:37] hallyn: fixed some apparmor problems in quantal and uploaded a new version. I'm now rebasing our lxc-api-and-python branch on that, so you'll need to "bzr pull --overwrite" [05:42] hallyn: rebase done and pushed. I also pushed new packages to my PPA. === pehden is now known as pehden-net === pehden-net is now known as pehden === exocaesar is now known as Guest42896 [07:48] I want to use PHP to send a mail from a custom address (blah@example.com, for example). Do I install postfix or sendmail? And how do I configure them? === matsubara-afk is now known as matsubara === railsraider_ is now known as railsraider [08:13] mystblade9, forget sendmail, do postfix [08:14] sendmail is configurationhorror [08:16] I installed Postfix and got a bit further. But i'm having trouble configuring what it feeds as the MAIL FROM data. Here's the story: [08:16] I'm creating a small webapp for a few gaming friends of mine that maintains a list of contributions to an in-game toolkit, and sends mails every time something is accepted or rejected. I want this to be sent from a fake address ("info@LBPCreatorsToolkit.org") because I don't have a domain name yet. First: Is this legal? Second: How do I configure Postfix to do this? [08:17] thisismyname: ^ [08:20] if you're new in postfix... you could try webmin [08:20] Myrtti, http://www.google.com/url?sa=t&rct=j&q=download%20webmin&source=web&cd=1&ved=0CGEQFjAA&url=http%3A%2F%2Fwww.webmin.com%2Fdownload.html&ei=Sx_oT6yLMY3LswaGyInkAQ&usg=AFQjCNHxBp4sFUVRgYu_2yZk_KupwxBkpw&cad=rja [08:20] ah [08:20] http://www.google.com/url?sa=t&rct=j&q=download%20webmin&source=web&cd=1&ved=0CGEQFjAA&url=http%3A%2F%2Fwww.webmin.com%2Fdownload.html&ei=Sx_oT6yLMY3LswaGyInkAQ&usg=AFQjCNHxBp4sFUVRgYu_2yZk_KupwxBkpw&cad=rja [08:20] damn [08:21] www.webmin.com/download.html === almaisan-away is now known as al-maisan [08:34] 2 servers with same lucid install. tried do-release-upgrade on both [08:34] 1st detects precise en offers to upgrade [08:34] 2nd won't detect the new release. even not with do-releaese-upgrade -d [08:36] why is that [08:40] morning o/ [08:58] henkjan: New installs? [08:59] Jeeves_: installs from a few months old, but nothing extra installed/configured [09:00] /etc/update-manager/* (or something like that) identical? [09:02] yup [09:04] henkjan: silly question, but have you run apt-get update? [09:04] RoyK: yup [09:05] and /etc/apt/sources.list is the same on the two? [09:05] why doesn't precise show up in http://changelogs.ubuntu.com/meta-release-lts ? [09:05] editing /etc/apt/sources.list to precise [09:05] gives me [09:05] After this operation, 247MB of additional disk space will be used. [09:05] You are about to do something potentially harmful. [09:05] To continue type in the phrase 'Yes, do as I say!' [09:06] erm, you shouldn't need to edit that manually [09:06] that was in the old debian days [09:06] RoyK: i know. [09:41] ah, the 2nd node had only working ipv6 [09:42] and sadly, canonical still offers no v6 enabled servers/services [09:43] We will eventually, takes time to get everything lined up. [09:44] and tbh, running ipv6 only is -extremely- rare today [09:44] no, we've been running al our services on ipv6 for ages [09:45] ipv6, or ipv6 only? Quite different :> [09:45] and so does nl.archive.u.c [09:45] (which we run) [09:46] yes, there are lots of things running dual stacks today. [09:46] I was observing that running ipv6 ***only*** is extremely rare today. [09:46] that'll come soon enough [09:47] my 2nd internet connection is v4 behind CGN. Only v6 is 'native' (6RD) [09:47] hi [09:48] is it true that ubuntu-server 12. not have inittab ? [09:53] lifeless: I heard of some chinese ISP that was rolling out IPv6 *only*, because they couldn't get six million IPv4 addresses [09:54] lifeless: they were planning to gateway to IPv4, though, but still, IPv6 is coming, and canonical should know ;) [09:56] RoyK: we do:) [09:56] sacarde: correct. Ubuntu uses upstart. [09:56] !upstart | sacarde [09:56] sacarde: Upstart is meant to replace the old Sys V Init system with an event-driven init model. For more information please see: http://upstart.ubuntu.com/ [10:01] 10.04 too [10:10] is there a "rosetta stone" from sysv-sommands to upstart-commands ? [10:15] jamespage: can you give me a hola when you are here pls? [10:17] lifeless: ipv6 ubuntu is less secure than ipv4 :) [10:17] Daviey, here [10:17] Daviey: no, it isn't [10:18] RoyK: yeah it is :) [10:18] dave@frap:~$ dig +short AAAA security.ubuntu.com | wc -l [10:18] 0 [10:18] dave@frap:~$ dig +short A security.ubuntu.com | wc -l [10:18] 4 [10:18] Daviey: {{citation needed}} [10:19] jamespage: Okay cool.. I'm going to refactor, https://jenkins.qa.ubuntu.com/view/Openstack%20Testing/view/Openstack%20Quantal/view/Overview/job/quantal-openstack-folsom-nova-trunk/219/console [10:20] Daviey, how? [10:20] actually I think thats an old style job [10:20] one second - lemme check [10:20] jamespage: err, the patch just needs rebasing. no? [10:21] jamespage: Well, the fact it only has you as email recipient is concerning.. so it might be old. [10:21] Daviey, let me just do my first task which is to update the public views [10:22] ok, super === zyga_ is now known as zyga [10:23] Daviey, quantal views updated. === al-maisan is now known as almaisan-away [10:25] jamespage: j.qa.u.com ? [10:25] yep [10:25] precise now done as well [10:25] awesome.. it's all green :) [10:25] only one failure ATM [10:26] Daviey, I know that adam_g has been working on this stuff hard [10:26] he asked me to update the views last week [10:26] jamespage: neat-o [10:26] but I had not got round to it [10:26] jamespage: slack. :) === chu_ is now known as chu [10:44] Daviey: Full Overview Dash - https://jenkins.qa.ubuntu.com/view/Openstack Testing/view/Overview [10:46] jamespage: Status Code: 404 :)... Spaces in URL's make babies cry. [10:47] OK _ https://jenkins.qa.ubuntu.com/view/Openstack%20Testing/view/Overview/? [10:47] But after i deciphered your obfuscated url, it looks awesome :) [10:59] jamespage: where is the deploy job? https://jenkins.qa.ubuntu.com/view/Openstack%20Testing/view/Openstack%20Quantal/view/Folsom-Trunk/ ? [11:00] "quantal-openstack-folsom-deploy" [11:03] * jamespage faceplants [11:03] Daviey: missing from the view only [11:03] let me fix that [11:04] Daviey, actually no - I want to check with adam first [11:04] I can see them in the lab but quite a few are currently disabled [11:04] and I want to check why first [11:04] jamespage: ok [11:05] jamespage: What is the one command that jenkins now fires? [11:06] Daviey, "build-package -j" [11:07] "-j" being - lookup everything I ever needed to know in the Jenkins environment [11:07] jamespage: neato [11:07] yep, i just check :) [11:07] rather than pass as parameters (which you can still do of course) [11:08] jamespage: where does juju deploy happen then? [11:08] Daviey, in the deploy wrapper [11:08] I think thats part of the stuff in separate branches ATM [11:08] ah [11:09] That /was/ in jenkins itself i thought, and moved to lp:openstack-ubuntu-testing [11:12] adam_g: when you see this.. did you note that the bnx2 firmware issue is now fixed... are we still working around it? === matsubara is now known as matsubara-lunch [11:20] Daviey, http://pad.ubuntu.com/openstack-ci-sprint [11:21] adam_g, zul ^^ [11:22] morning zul :-) [11:23] hey zul [11:26] zul: morning [11:27] * koolhead11 says zul morning as well :P [11:27] * koolhead11 hellos lynxman Daviey jamespage as well [11:29] koolhead11: hola [11:29] hey koolhead11 [11:29] heylo [11:29] zul: stop causing a distraction. [11:41] New bug: #1003296 in samba (main) "lightdm crashed with SIGSEGV in _pam_winbind_change_pwd() when password is expiring" [Undecided,New] https://launchpad.net/bugs/1003296 [12:00] utlemming, https://jenkins.qa.ubuntu.com/view/ec2%20AMI%20Testing/view/Overview/job/quantal-server-ec2-daily/ [12:00] i386 images not looking so hot ATM === matsubara-lunch is now known as matsubara [12:07] Daviey: jamespage zul felt good on Saturday meetup when folks said everything works so simply/easily on Ubuntu/Essex :D === Skaag_ is now known as Skaag [12:22] jamespage, I think there may be a fix already in the rebase to 3.5-rc4 for that: thp: avoid atomic64_read in pmd_read_atomic for 32bit PAE [12:23] Though that is not uploaded, yet. [12:44] stgraber: looks good, thanks === jtv1 is now known as jtv [12:54] stgraber: in lxc-api-python tree, quilt patches became unapplied again [12:54] is SpamapS around? [12:57] nevermind, i'll just drop him a memoserv or something [13:02] stgraber: hrmph, it sounds like i must be using select wrong but i don't see why [13:02] btw i try 'python\nimport lxc' but it doesn't find it? [13:03] smb, ack - when will that land? [13:03] jamespage, Next time there is a quantal upload. Though I do not know the schedule for that [13:04] utlemming: I think we should disable the i386 test until that upload happens then [13:04] its just spinning instances we know won't start [13:05] ooooh i see === railsraider_ is now known as railsraider [13:07] stgraber: can you re-fetch and re-try? (remember to quilt push -a :) hopefully it was the simple obvious 'duh' i just fixed [13:24] LoT: I'm here now. [13:24] SpamapS: see the privmsg, unless you had +g on [13:24] SpamapS: when you're less busy, can yuo take a look at https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1014044 ? I think it needs syncing from Debian (this would fix the Ubuntu bug and also close my wishlist bug, in theory) [13:24] Launchpad bug 1014044 in php5 "PHP5-FPM not reporting errors to web server (nginx)" [Unknown,Fix released] [13:25] the fix released is in Debian [13:25] (and the bug reporting bot here is wrong) [13:25] LoT: there's a planned merge that will fix that in quantal. I was thinking we'd wait until July so that we catch any pre-freeze changes that the Debian php team makes [13:26] * LoT is getting nagged by questions about this on the nginx ppas, since his email is on everything [13:26] hence why i poked you to see what the status was [13:26] * LoT does not like getting 60 emails about this issue [13:26] LoT: 60 emails? [13:26] mhm [13:26] (so far, in hte past two days, on this issue, people thinking its an nginx problem( [13:27] AH [13:27] i keep saying "Its not an nginx issue, its a php5 issue, see this bug " [13:27] but people are... um... [13:27] how do i put it without being condescending to the world... [13:28] nope, cant put it any way that won't end up condescending. people are generally thick-headed when they automatically assume its an nginx problem [13:28] Is it a regression, or just people migrating to php5-fpm+nginx and not getting that its still new and different? [13:28] not sure, but in prior versions i've seen PHP-level errors get reported (last confirmed: natty) [13:28] so possible regression [13:29] * LoT hasnt stated as such because he completely skipped Oneiric [13:29] SpamapS: that's also why i havent been able to mark its importance (although i have the powers to do so) [13:29] because i'm not entirely certain if its a regression (if its a regression, well...) [13:30] wait, its medium [13:30] why the... [13:30] * LoT glares at LP [13:30] this thing's not sending me the right information [13:30] * LoT is not please [13:30] d [13:31] LoT: so its medium by the definition that it only affects a sub-set of users. [13:31] indeed [13:32] however, i'm mor eannoyed at launchpad not showing me the info [13:32] * LoT is not pleased with launchpad today [13:32] this is the third bug its not shown me information that already existed on the bug [13:32] not showing you *what* info? [13:32] importance or status [13:32] shows me [13:32] yeah, i blame this computer [13:32] (its not linux, its my work computer which is windows :/) [13:34] Can anyone recommend a site that pings a URL or checks source code on a site and notifies me when something changes? [13:34] LoT: its a web app, that shouldn't matter [13:34] SpamapS: IE6, its BUGGY [13:34] IE6, its *dangerous* [13:34] SpamapS: having said this, IE is evil in and of itself [13:35] * LoT doesnt have a choice in the matter [13:35] seriously [13:35] wtf? [13:35] * LoT has no admin, and FFox isnt approved [13:35] i know right? [13:35] but, ie6 has been out of support for a long time [13:35] i wrote up a white paper on it, sent it off to the CISO [13:35] you are basically walking around just asking for viruses [13:35] also wrote up a whitepaper on Java 5 :/ [13:35] (also installed by default, on these XP systems) [13:36] even met with the CISO last week about this :P [13:36] well, not directly about it, but... [13:36] lets just say i'm not too happy with this system :p [13:42] LoT: what place is this? [13:42] koolhead11: where i work, with the state [13:42] state == govenment agency? === zyga is now known as zyga-food [13:44] koolhead11: state = the government of the state of pennsylvania in the US [13:45] LoT: awesome, atleast our folks started using FF here and there website says only optimized for FF and Chrome [13:46] koolhead11: the site's optimized for that, but... :P [13:46] apps need ITSec approval before being usable [13:46] even then, it'd take at least 6 months for the process === LoT is now known as LordOfTime === zyga-food is now known as zyga [14:48] jamespage: did you manage to see which branch contains the juju magic? [14:50] Daviey: bzr+ssh://bazaar.launchpad.net/~gandelman-a/%2Bjunk/juju-deployer/ [14:53] doesn't every branch? [15:01] hallyn: hah! [15:01] jamespage: thanks [15:01] Daviey, np [15:01] * jamespage adds that to the list [15:08] * jamespage coffee [15:09] :> === ninjak__ is now known as ninjak === Ursinha` is now known as Ursinha === Ursinha is now known as Guest89684 === Guest89684 is now known as Ursula === Ursula is now known as Ursinha [15:24] hallyn: ok, I'll have a look now. As for quilt messing with patches on pull, I usually run something like "QUILT_PATCHES=debian/patches quilt push -a ; rm .pc/.quilt_patches .pc/.quilt_series .pc/*/.timestamp" that gives you the branch back to something readable (checking with bzr st for any remaining thing to fix) [15:27] hallyn: hmm, I see... something indeed unapplied all the patches from the branch... that's getting a bit annoying... [15:29] hallyn: I'll add a commit re-applying all the patches [15:38] hallyn: patches re-applied (quilt is really a pain...) [15:43] stgraber: did the new branch fix c->wait(c, 20)? [15:46] hallyn: just did a test build now, will know more in a minute [15:48] hallyn: yep, working fine now. thanks! [15:49] stgraber: phew :) [15:49] so i think my user namespaces patch for lxc is working [15:49] it's working in that it won't let me mount the rootfs :) [15:49] onward [15:57] zul, Daviey, adam_g: Pls can you comment on my PPA review in the Pad [15:58] jamespage: looks ok to me [15:59] jamespage: almost finish the piuparts stuff [16:00] zul, nice [16:02] zul: rocking [16:03] hallyn: :) well, that's a good start ;) [16:11] i wonder if find on a debootstrap rootfs would be a lot faster with a m1.medium than a m1.small [16:12] oh, no, i'd need a large before they claim improved i/o [16:16] jamespage: one thought on the bug triage process. I keep finding things that I feel should be templated, or standard instructions provided (eg. on for instructions on how to debug X, which I think is common). Is it possible to have a backlog somewhere so that we can list outstanding requests for templates or template improvements? Like filing bugs against the triage process, for example? [16:16] rbasak, yes [16:17] rbasak: why not just add a standard response, but prefix with [PROPOSED] ? [16:17] (directly to the wiki) [16:18] bikeshedding over exact wording, means it will take longer to get on the standard responses.. i'd suggest JFDI [16:18] Daviey: sure, but sometimes I don't have a response prepared because it needs work - eg. to follow through the debug process that comes up with the required results. I can write something that says "we need a template that results in us getting information Y in response" but don't know what instructions to provide straight away [16:19] rbasak: I'd add notes to the wiki page with the standard responses. [16:19] ScottK: Thanks. I'm more thinking about DebuggingProcedures here though [16:20] I don't recall all the pages, but I'd say pick one and do it. [16:20] It's easy enough to move if needed. [16:20] As Daviey said, JFDI. [16:20] http://paste.ubuntu.com/1059314/ is one that I've been using that I think we should have as a standard (or something simliar) [16:21] The point is that I can't JFDI. It takes work and a diversion that I'm not currently doing while triaging, as then I wouldn't get any triaging done [16:21] I do hate shelling out to non-ubuntu project urls :) [16:22] rbasak: I'm suggesting that the response you put into a bug, if it is a generalish one.. just put it on the wiki, warts and all. [16:22] It's no worse than what you are putting on the bug you are currently triaging.. and the next person to look at it can build upon it [16:22] Daviey: I end up not putting an appropriate response in the bug because I don't know the exact debugging procedure for problem Z off the top of my head [16:23] Usually I just leave it [16:23] ok [16:24] dont we have a whole list of pre-packaged canned answers to bugs? [16:25] This is about the ones that aren't on that list yet. === Lcawte|Away is now known as Lcawte [16:31] jamespage: Re: PPAs, should we just be stuffing both precise and quantal trunk builds into the same PPA (folsom-trunk-testing)? [16:32] adam_g, I think that was my plan - folsom trunk PPA for folsom trunk - irrespective of release [16:32] does that make sense? [16:33] jamespage: it does now that we're adding a ~$ubuntu_release tag to the version strings of the packages we build. there was .deb naming conflicts when precise and quantal builds triggered at the same time [16:33] adam_g, ah - that would make sense [16:34] jamespage: i fixed that in build_package script to solve the issue in the local repo, but i think it will allow us to consolidate trunk builds into one PPA [16:34] adam_g, lets do that then! [16:34] k, ill update the configs [16:35] smoser / jamespage: What is the status of iso testing posting the results back to base? [16:43] okies piuparts added [16:44] heh. stat vs. lstat. good one, serge [16:46] Daviey: re: firmware, i saw the bug marked fixed but haven't seen the new firmware show up in mini.iso. wasn't sure if it takes a while for it to hit the iso [16:49] adam_g: mini.iso is only rebuilt when d-i is. [16:49] zul: where did you push your piuparts addition ? [16:49] Daviey: in the main branch did you want to review it first? [16:49] Daviey: so yeah, the workaround is there and will be until mini.iso catches up. [16:50] zul: no, just wondered. [16:50] Daviey: ah ok [16:51] Daviey: im moving on to upgrade testing - i have an idea in my head to do it as well [16:53] zul: i think this commit to build_package is breaking things [16:53] adam_g: eh? [16:54] zul: no idea. http://10.189.74.7:8080/view/Openstack%20Precise/view/Overview/job/precise_folsom_python-keystoneclient_trunk/9/console [16:54] zul: fancy out-ling pre-imp what your plans are for upgrade testing? [16:54] Daviey: sure just a sec [16:56] adam_g: ah...ef....duh....pushed [16:56] Daviey: its using piuparts again, but the idea would be like this: [16:56] 1. Download the source [16:56] 2. build the soruce [16:57] 3. get the release source it was build for [16:57] 4. get the final upgrade release [16:57] 5. run piuparts [16:59] Daviey: ^^^ problems with that, complaints, am i on crack? [17:00] zul: http://10.189.74.7:8080/view/Openstack%20Precise/view/Overview/job/precise_folsom_python-keystoneclient_trunk/11/console <- still [17:02] adam_g: i suck [17:02] try it now [17:03] zul: for the work ive been doing on that branch, ive been committing to my own branch, pulling it to some other location on the jenkins master, and running it manually there to ensure it works before merging into the main branch and pulling down to the tree jenkins calls [17:03] for the less-trivial stuff, at least [17:03] adam_g: i ran it locally fine here but i dont think i merged from the right branch [17:04] adam_g: posting an url with 10.x.x.x won't work too well [17:04] zul: [ 'sudo', 'piuparts', '-d %s', % self.release, '--no-eatmydata', '%s' % source_changes ] [17:06] RoyK: Sadly, that machine is not a public facing box.. I agree it's a little frustrating to not be able to follow the conversation in completeness... But there are two options, people discuss publicly or in private (meaing all of it will be kept in private.).. What seems better to you? [17:08] Daviey: np [17:12] Daviey/adam_g/jamespage: melange is going away so i dont think we should be testing it [17:17] zul: np [17:17] Daviey, you're referring to jenkins ec2 -> iso tracker posting? [17:17] smoser: no, ISO images [17:18] RoyK: if you really wanna see https://jenkins.qa.ubuntu.com/view/Openstack%20Testing/view/Overview/job/precise_folsom_python-keystoneclient_trunk/11/console [17:19] zul: did you measure with and without eatmydata ? [17:19] Daviey: it would fail without eatmydata [17:20] zul: --no-eatmydata ? [17:20] yeah [17:21] why would it fail without? [17:22] Daviey: because it couldnt find eatmydata [17:22] jamespage: over the weekend, i began factoring the schroot wrapper stuff out of build_package into its own module . id like to make use of the same stuff for a juju test. any thoughts on where that type of stuff should live? [17:22] i was thinking ./lib/ or even packaging it properly and installing system-wide [17:22] but the latter would require we start properly versioning all of this stuff [17:23] zul: hmm, it shouldn't be using it. [17:23] Daviey: it is :) [17:28] Has anyone here tried orchestra on 12.04 server? I see articles about it being used on 11.x desktop, and other articles on using MAAS, but none of orchestra for 12.04. [17:33] zul, you will probably need to set the archive that piuparts to use universe - by default it does not [17:33] jamespage: doh! [17:33] zul: and also, piuparts needs to be exec'd in the schroot [17:34] right? [17:34] adam_g: right [17:34] zul: fixing now locally and pushing up [17:35] adam_g: ack [17:35] zul, adam_g: Am I good to get rid of the obsolete PPA's then? [17:35] jamespage: yep [17:36] jamespage: ya [17:39] adam_g, are we switched over from precise-trunk-testing -> folsom-trunk-testing yet? [17:39] jamespage: yes, not sure any packages have been pushed there yet. build script has issues atm with another change [17:39] adam_g, want me to copy the packaged over ? [17:40] jamespage: sure [17:40] Daviey, so did you get your answer? about test results to iso tracker? [17:42] Daviey: I'm not touching ISO tests ATM - the QA team are migrating everything to UTAH [17:42] so I don't really want to complicate things more [17:42] smoser, ^^ [17:48] jamespage: can you capture what PPA's are now what.. it will be confusing for users. [17:48] jamespage / smoser: right, but until they have done it.. we need to update the tracker [17:48] smoser: You last touched the script, right? [17:51] adam_g: precise chroot will need the same thing for piuparts [17:51] zul: need what? [17:52] adam_g: i thought you did piuparts/universe for quantal [17:52] zul: no, im just trying to fix the code you added. :) i dont even know what piuparts is. [17:53] adam_g: ok [17:53] zul: ive disabled build.run_piuparts_test() for the time being [17:53] k [17:54] zul: run_piuparts_test() itself looks okay, beyond that im not sure why its not working [17:56] adam_g: can you add the output of subprocess.check_call so we can capture the output? [17:57] zul: where? [17:58] adam_g: like you know in nova they have out, err = utils.execute [17:58] can we do soemthing like that? [17:59] zul: check_call() IIRC doesn't return stdout/err [17:59] adam_g: yeah nm [17:59] Daviey, its just re-aligning to https://wiki.ubuntu.com/ServerTeam/OpenStack [18:05] adam_g, while we are overlapping - does the no-change rebuild of openldap for bug 990742 still need to happen? [18:05] Launchpad bug 990742 in openldap "[SRU] slapd fails to upgrade: requires libsasl2-2 (>= 2.1.24) installed" [High,In progress] https://launchpad.net/bugs/990742 [18:06] halvors1: did you notice lxc-list in quantal listing every container tweice? [18:06] *twice [18:07] (well, running containers at least) [18:07] jamespage: im not sure TBH, i cant think of a way to test. it seems the original issue was fixed with the update to cyrs-sasl2, without a openldap rebuild [18:09] halvors1: sorry, was meant for hallyn [18:09] hallyn: ^ [18:10] hallyn: reason is that we lost a "| sort -u" in lxc-list with the Debian merge. We also lost the code checking for .conf files to mark them as auto, so the auto flag no longer works... [18:16] stgraber: sigh, those debian merges... [18:17] hallyn: I'm pushing a fix that'll make lxc-list work with both Debian and Ubuntu [18:17] hallyn: ideally we should move these upstream so the downstreams stop fighting ;) [18:18] stgraber: sending it to lxc-devel? (sadly i've not gotten my new not-yet-included-patches lxc git tree up yet) [18:19] hallyn: well, I'd really like us to get rid of all that bash non-sense (lxc-ls + lxc-list) and move to something cleaner (likely based on the python or C api), so it'll have to wait for now [18:20] but my mid-term goal is to get rid of debian/local ;) [18:21] adam_g, I'm quite tempted to mark the rebuild for openldap as invalid then [18:22] hallyn: gah... the branch importer messed up again and broke ubuntu:lxc... looks like I'll have to spend half an hour rebasing lxc-api-with-python again... [18:23] broke ubuntu:lxc? [18:23] jamespage: thats okay with me. i was following debian's lead on that one, wrt their fix for the same issue. apologies for forgetting about that one. [18:23] is that bc we had part of the changes committed? [18:23] adam_g, np [18:23] hallyn: well, reverted my commits and resynced from the uploaded package... [18:24] hallyn: so now lxc-api-with-python is no longer a branch of ubuntu:lxc ... hopefully rebase can fix that [18:24] SpamapS: still here? [18:24] or rather, are you alive. [18:26] stgraber: oh, i see. [18:26] stgraber: if before dputing the package, you get every bit of the package changes uploaded to ubuntu:lxc, will it still do that? or will it then just tag the new release? [18:26] just wondering [18:27] hallyn: it shouldn't but it apparently didn't agree with me that I got everything in that branch [18:27] hallyn: even though I made sure everything was commited, ran debcommit -r and built the source upload from it [18:29] stgraber: that sucks [18:32] hallyn: and not surprinsingly, rebase no longer works... or rather it does but you end up with a branch loosing all the changes... === Aaton_off is now known as Aaton [19:09] how to change the PS1 to show it like this bash-4.1.5$ ? [19:09] so just the bash version === henkjan_ is now known as henkjan [19:37] LordOfTime: I was at lunch, whats up? [19:38] SpamapS: check your emails, i updated a bug slightly with a poke, one you helped me with (getting that patch to Debian) [19:38] lemme find the bug again [19:38] SpamapS: this one https://bugs.launchpad.net/ubuntu/+source/php5/+bug/900620 [19:38] Launchpad bug 900620 in php5 "Possible Bug: php5-fpm does not listen on a socket by default" [Unknown,Fix released] [19:38] (its fix released in Debian, but not updated for ubuntu) [19:39] (and 5.4.4 is in Quantal) [19:42] whoops [19:42] LordOfTime: right.. hm [19:43] SpamapS: it *should* be fix released [19:43] since the patch (if you read the changelogs) was included [19:43] I was just verifying that [19:44] php5 (5.4.0~rc7-2) experimental; urgency=low [19:44] * php5-fpm now listen on socket instead of localhost by default [19:44] (Closes: #650204) [19:44] ^ except that only closed the Debian bug and not the LP bug [19:44] LordOfTime: Error: "except" is not a valid command. [19:44] silence you [19:46] New bug: #1017408 in clamav (main) "Viruses reported by clamav" [Undecided,New] https://launchpad.net/bugs/1017408 [19:46] SpamapS: i wanted the confirmation before this was Fix Released in Ubuntu (I have rights to change it, but didnt want to until this was confirmed) [19:48] LordOfTime: right. Thanks for taking a look at that. :) [19:48] anyone know how to create a apt mirror with just the packages you have installed. I want to just have a partial mirror so I can control what packages are at apt-get installable. [19:48] yep, i was scanning bugs, so... :P [19:49] Aaton: I don't know if there is a specific command for that, but you basically just need all the debs, then you can use apt-ftparchive to build a mirror. [19:49] I [19:50]