[13:37] <scientes>  iinstalled the ubuntu-mobile package and it totally messed my desktop
[13:37] <scientes> xchat is stuck in full screen and is set so you cant resize it
[13:44] <ian_brasil_> scientes: what device are you using
[13:44] <scientes> a desktop
[13:44] <scientes> i though the changes would be autonomous and i could just load up another gdm and look at it, or nest a gdm
[13:45] <scientes> a restart after deinstalling what i could fixed the window manager
[13:45] <ian_brasil_> why don't you try it in kvm or qemu
[13:45] <scientes> but simply restarting the window manager didnt
[13:45] <scientes> yeah
[13:45] <ian_brasil_> there is also a gconf key you could change to exit the full screen
[13:46] <persia> No, it's not a gconf key : it's a config file value.
[13:46] <scientes> most thing you could jsut use ctrl-click (of course only in compiz), but for some reason xchat was stuck at full screen
[13:46] <ian_brasil_> gconf-editor in a termainl
[13:46] <scientes> i mean alt-click to move/resize
[14:17] <crevette> heya
[14:17] <crevette> someone from the bluetooth team here ?
[14:18] <crevette> I wanted to know what the state of bluetooth, because this is quite hectic now in intrepid, and we need to fix that.
[14:20] <persia> crevette, Well, how do you suggest we fix it?  It's certainly broken.  slytherin was testing some patches, but never found anything that both worked and seemed small enough to fit in an SRU.
[14:20] <persia> My memory is that the biggest issue was with gnome-user-share and it needing apache.
[14:21] <crevette> a lot of people complain about sending and reception issues
[14:21] <crevette> sending from computer
[14:21] <persia> Sending from the computer?  That worked last time I checked.
[14:21]  * persia tests again now
[14:21] <crevette> I think this is due to nautilus-sendto which is too restructive when checking the phone capabilities
[14:21] <crevette> persia, some phoen don't work
[14:22] <crevette> phones
[14:22] <crevette> (apparently), mine does
[14:22] <persia> Oh, so that it works for me isn't enough.  I very much dislike bugs I can't reproduce :(
[14:22] <crevette> I needed to hack the source but didn't find time
[14:23] <persia> I suspect others are in the same position.
[14:23] <crevette> https://bugs.edge.launchpad.net/nautilus-sendto/+bug/285283
[14:24] <crevette> people should try to execute dbus-send --system --print-reply --dest=org.bluez /org/bluez/hci0/dev_XX_XX_XX_XX_XX_XX org.bluez.Device.GetProperties
[14:24] <crevette> if in the properties there is no somethiong like 0x1106 in the UUID nautilus-sendto won't even go further
[14:25] <crevette> I wonder if bluetooth-sendto checks the capabilities or not
[14:25] <crevette> but most of the time it works fine
[14:25] <crevette> so if bluetooth-sendto work but not nautilus-sendto, you can bet this is the nautilus-sednto bug
[14:25] <persia> Yeah, it certainly sounds like one.
[14:26] <crevette> so I need to remove the capabilities check from nautilius-sendto
[14:26] <crevette> or someon with REAL coding capaibilities
[14:26] <crevette> I just know copy & pasting code
[14:26] <persia> Mind you, it might be a applet bug that it does allow send, but a bug that's left there to work around devices that don't describe themselves.
[14:27] <crevette> for the file reception problem, there is an issue with obex-data-server, our snapshot isnot working fine
[14:28] <crevette> jumping to 0.4.2 would be radical, but it proved to work for me at least, and some other persons
[14:28] <persia> Right.  slytherin thought that some gconf adjustments might help.
[14:28] <crevette> gconf ? for which problem ?
[14:29] <crevette> s/\ \?//
[14:29] <persia> jumping to 0.4.2 for jaunty would be a sensible step then.  That doesn't require any approvals.  I'm less sure what to do with intrepid.
[14:29] <persia> gconf for the obex-data-server issue.
[14:29] <crevette> okay, for changing which key, (I didn't know that obex-data-server uses gconf)
[14:31] <persia> I don't actually know.  Best ask slytherin (who is rarely in this channel : more often in #ubuntu-motu).
[14:31] <crevette> okay
[14:31] <ian_brasil_> crevette? there is also the password issue in bluetooth
[14:31] <crevette> the third problem is the reporter themself, who are a little confused and mix the problems
[14:32] <crevette> ian_brasil_, the one where the notification disappear quickly ?
[14:32] <persia> crevette, I think the reporter is seeing both bugs.
[14:32] <ian_brasil_> yes..for instance on a gps device there is no way to enert a password
[14:32] <ian_brasil_> enert == enter
[14:32] <persia> ian_brasil, Or the one where the filter for which devices get assigned a password, and which have defaults is mostly broken?
[14:32] <crevette> ian_brasil, rh has some patch, where they hard-code 000
[14:32] <crevette> 0000
[14:32] <persia> Well, that needs a better device DB.
[14:32] <ian_brasil_> i saw that...the main.c hack
[14:33] <crevette> yep
[14:33] <ian_brasil_> the proper solution is to modify the UI i think
[14:34] <ian_brasil_> but much more time involved ibviously
[14:34] <ian_brasil_> damn keyboard ..ibviously == obviously
[14:35] <crevette> ian_brasil, you suggest let the user enter the pair code ihimself ?
[14:37] <crevette> persia, perhaps I wasn't clear enough, I was stating that users are confused between various bluetooth package, and which one provide which functionnality, so people add a comment on nautilus-sendto stating about reception,
[14:37] <persia> For devices that can enter codes, I like the UI.  I'm somewhat annoyed that one of my devices on which I can enter a code defaults to 0000.  On the other hand, I know several people have devices on which they can't enter codes which default to random, which is even more annoying.
[14:37] <ian_brasil_> crevette: that was how it worked in hardy IIRC
[14:37] <ian_brasil_> and is the expected behaviour from a users POV
[14:40] <persia> Yeah, the hardy behaviour wasn't that bad either.
[14:42] <crevette> we need to see with uptream, perhaps
[14:42] <crevette> it would make sense
[14:42] <crevette> damn, if I wish I were rich to have time for that
[14:42] <crevette> :)à
[14:42] <crevette> unfortunately I'm at work now :)
[14:43] <persia> Well, the hardy implementation was a bit annoying, and very fragile.  The UI might be nice, but it would be better to do it differently.
[14:44] <crevette> persia, you're talking about bluez-properties ?
[14:44] <crevette> (I'm lost)
[14:44] <crevette> :)
[14:46] <crevette> persia, for nautilus-sendto http://svn.gnome.org/viewvc/nautilus-sendto/trunk/src/plugins/bluetooth.c?view=markup line 32 and after line 377
[14:47] <persia> crevette, Yeah.  That's the issue.
[14:47] <persia> No, I was talking about the pinentry hack, which isn't worth keeping.
[14:47] <crevette> ah I don't it
[14:48] <crevette> +know
[14:48]  * persia didn't really look at bluetooth that much between Breezy and Intrepid, so may have missed a step or two
[14:48]  * crevette didn't look at bluetooth until now
[14:48] <crevette> :)
[14:49] <persia> My memory was that there was a hook into the config file, which if it had a certain value would then call an external helper to ask the user for the PIN (or else use a default PIN in the config file).  This was more fragile than the current state, which is broken, but at least robust.
[14:50] <crevette> there was a bluez-pin yeah
[14:50] <crevette> with dbus activation eventually?
[14:51] <persia> That still sounds a little fragile to me, but it might work well, as various services could use a common tool.
[15:12] <rrittenhouse> When I try Ubuntu umpc on this new Aspire G1, is there a way to restore back to Windows in case the crap hits the fan?
[15:13] <persia> Well, first try the live image.  That lets you test the basics.
[15:13] <rrittenhouse> It is the windows model. The files look to be stored on a 5gb partition on the hd and I'm not sure how I would initiate a restore.
[15:13] <rrittenhouse> ooh ok :) Is there a Wiki entry for this?
[15:13] <persia> It's worth doing a defrag of your windows disk first, but the installer should be able to resize it so you can dual-boot.
[15:14] <persia> When you're satisfied, delete Windows.
[15:14] <rrittenhouse> Does it use that Wubi thing from windows?
[15:15] <persia> Oh, if you have a restore partition, you can probably just install over Windows, and "dual-boot" with the restore partiion.  Personally, I'd be careful, and maybe test with a triple-boot scenario first.
[15:15] <persia> No.  Ubuntu UMPC doesn't work with wubi yet.  Maybe for Jaunty.
[15:15] <rrittenhouse> hmm. Personally I don't like Windows at all but this model had better specs.
[15:15] <rrittenhouse> and it was available at Staples
[15:20] <rrittenhouse> Is the Ubuntu UMPC Edition a live-install ?
[15:21] <persia> Yep.
[15:21] <persia> dd it to USB.  Boot a live session.  If you like it, click "install".  If you don't, try a different flavour of Ubuntu :)
[15:27] <rrittenhouse> persia: I don't have a thumbdrive laying around. Would a spare usb hard drive work?
[15:27] <rrittenhouse> It seems like it would
[15:29] <persia> It might, although dd of 600MB to a hard drive is soemthing that calls for a near-future reformat :)  I'd recommend making sure your device can boot from external USB HD first : some machines balk at booting from real hard drives on USB.
[15:29] <rrittenhouse> Interesting :)
[18:31] <bizkut> os[Linux <IP_ADDRESS>-aao i686] distro[Ubuntu "intrepid" 8.10] cpu[2 x Intel(R) Atom(TM) CPU N270   @ 1.60GHz (GenuineIntel) @ 1.60GHz] mem[Physical: 0.9GB/1.5GB free] disk[Total: 22.1GB/27.9GB free] video[Intel Corporation Mobile 945GME Express Integrated Graphics Controller] sound[HDA-Intel - HDA Intel]
[18:37] <piju> os[Linux 2.6.24-21-generic i686] distro[Debian lenny/sid] cpu[2 x Intel(R) Core(TM)2 Duo CPU     T5450  @ 1.66GHz (GenuineIntel) @ 1.67GHz] mem[Physical: 2.5GB, 75.1% free] disk[Total: 110.0GB, 65.9% free] video[Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller] sound[HDA-Intel - HDA Intel]


[11:28] <CIA-117> debian-installer: cjwatson * r1530 ubuntu/ (5 files in 2 dirs): Move to 3.0.0-11 kernels.
[15:17] <CIA-117> debian-installer: cjwatson * r1531 ubuntu/debian/changelog: releasing version 20101020ubuntu63


[02:00] <oerheks> nor you have mint, tomreyn
[02:00] <oerheks> *hips*
[02:38] <lotuspsychje> good morning to all
[03:00] <hggdh> lotuspsychje: morn
[03:14] <lotuspsychje> heyy hggdh guiverc
[03:15] <guiverc> howdy lotuspsychje
[06:09] <ducasse> good morning
[11:28] <BluesKaj> Howdy all
[12:09] <pauljw> hi everyone
[12:10] <BluesKaj> 'Morning pauljw
[12:10] <pauljw> hey BluesKaj :)
[12:15] <BluesKaj> heatwave here, 90F/90% humidity
[12:41] <pauljw> same here, BluesKaj, thank goodness for a/c.
[12:45] <BluesKaj> yup, already turned it on, it's already 28C/83F /80% humidity
[12:45] <BluesKaj> outside
[12:47] <BluesKaj> we a near tornado yesterday over our little town, that was a scary experience...the clouds were dark green then the wind came up and rain was horizontal
[12:57] <pauljw> oooh, yeah, don't like tornadoes.
[12:58] <BluesKaj> heh, no kidding
[13:00] <BluesKaj> very rare around here
[15:23] <tomreyn> oerheks: have firefox upgrades been made available faster in the past?
[15:24] <tomreyn> (when they contained critical security patches, but i thinkt hat's almost the case, more or less)
[16:28] <oerheks> tomreyn,  i thought FF is on a 6 week cycle?
[16:29] <oerheks> something like that
[16:29] <tomreyn> oerheks: yu mean upstream releases are?
[16:30] <oerheks> yes? i see it in debian already
[16:30] <tomreyn> what i was asking about is time to patch, or how fast the upstream releases have hit ubuntu in the past.
[16:31] <oerheks> i don't remember exactly, normally firefox would appear 3-5 days afer release, chromium much later
[16:32] <tomreyn> i guess we could check mozilla security advisories vs USNs
[16:32] <tomreyn> ...comparing dates
[16:32] <tomreyn> Firefox https://www.mozilla.org/en-US/security/known-vulnerabilities/firefox/
[16:32] <oerheks> stable in debian https://packages.debian.org/search?keywords=firefox
[16:35] <tomreyn> paste firefox USNs https://www.google.com/search?q=host%3Ausn.ubuntu.com+firefox
[16:35] <tomreyn> *past
[16:36] <tomreyn> oerheks: not stable in debian, no. they use ESR
[16:38] <tomreyn> actualyl this link https://www.google.com/search?q=site%3Ausn.ubuntu.com+firefox
[16:38] <oerheks> oh indeed, sid gives 61 https://launchpad.net/debian/sid/+source/firefox
[16:39] <tomreyn> btw you got a private message if you dont ignore them
[16:39] <oerheks> so, maybe today or tomorrow, holding on on the 4-5 day cycle? but that cycle is just an observation
[16:39] <oerheks> yes i read it.
[16:40] <tomreyn> i dont know the usual time to patch, it's what i'm trying to determine now
[17:05] <tomreyn> oerheks: feel free to add to it in case you got some time: https://lite.framacalc.org/QdSF3zNebB
[17:11] <tomreyn> just pick some version from https://www.mozilla.org/en-US/security/known-vulnerabilities/firefox/ and look up the usn
[17:17] <oerheks> 6 week cycle indeed https://wiki.mozilla.org/Release_Management/Calendar
[17:17] <oerheks> maybe i should just contact the mozilla team
[17:17] <tomreyn> about what? asking them to patch firefox in ubuntu?
[17:18] <oerheks> not patching, just the whole new version?
[17:20] <tomreyn> right, that's what i meant. but why would mozilla provide ubuntu packages? for all we know they have some kind of contract with ubuntu to define who does what (not) and to protect each others brands.
[17:20] <tomreyn> s/ubuntu/canonical/
[17:20] <oerheks> oh, i thought we waited for the debian branch to build first?
[17:21] <tomreyn> i tzhionk packaging firefox in ubuntu is independant from debian
[17:21] <tomreyn> *think
[17:22] <tomreyn> since canonical decided to do rolling releases for firefox in ubuntu some years ago.
[17:23] <tomreyn> before this, there was a team involving people form both debian and ubuntu working on backporting patches.
[17:23] <tomreyn> actually that was the very old times, then both debian dn ubuntu switched to esr, then ubuntu switched to rolling releases
[17:24] <tomreyn> dn -> and
[17:24] <tomreyn> that's from my memory, may be incorrect
[17:24] <oerheks> hasn't that changed when firefox changed to 6 week cycle too?
[17:24] <oerheks> this happened a few years ago, iirc
[17:28] <tomreyn> what do you mean changed then?
[17:29] <EriC^^> evening all
[17:30] <tomreyn> mozilla was never happy with distros shipping old firefox releases with backports, which is why they prohibited using the firefox brand on those backports, which is why there was iceweasel.
[17:30] <tomreyn> hi eric
[17:30] <EriC^^> hi tomreyn
[17:31] <oerheks> oh so far does my knowledge not go ..
[17:31] <oerheks> hi EriC^^
[17:31] <EriC^^> hi oerheks
[17:31] <oerheks> at a certain point, i read about firefox releasing a fresh version any 6 weeks, and seems correct looking at their timetable
[17:32] <oerheks> EriC^^, i am wondering why FF 61 is not in the repos yet
[17:32] <EriC^^> aha
[17:32] <oerheks> and what the 'normal' timeline is, between release and build
[17:32] <tomreyn> yes, i agree that they seem to have a 6 week release schedule. but this doesn't tell us how long it takes for upstream releases to arrive in ubuntu
[17:33] <oerheks> i migh be wrong looking a debian, expecting that package to show up
[17:33] <oerheks> jups
[17:33] <tomreyn> debian stable wont have 61.0.0
[17:33] <tomreyn> unless 61.0.0 will be selected as an ESR by mozilla
[17:34] <tomreyn> ESR = "extended support release"
[17:34] <oerheks> nope, 60 will jump to 68
[17:34] <tomreyn> so debian stable wont have 61
[17:35] <tomreyn> debian testing aklso uses ESR exclusively, i think
[17:36] <tomreyn> so either ubuntu syncs firefox from debian unstable (but i dont think they do) or they build it themselves.
[17:38] <tomreyn> chances are that canonical is bound to some contractual terms to be able to deliver "firefox" branded packages. such as not removing / modifying some things (default search engine? start page still getting the google cookie?)
[17:40] <tomreyn> i'm just making this up, have no idea what is there and what isn't, but it would seem logical for how businesses would set terms.
[18:42] <oerheks> tomreyn, > chrisccoulson> it will be published when it's in a releasable state and we can build language packs that work
[18:43] <oerheks> so it is a 2-trap rocket
[18:47] <tomreyn> thanks for sharing
[18:47] <tomreyn> while going over the USNs i notice that there have been many regressions and upstream follow up releases.
[18:48] <tomreyn> probably not the greatest packages to work on.
[18:49] <tomreyn> btw. my table is growing steadily
[18:49] <oerheks> I have no idea how hard that would be, i would like to contribute, but understanding how this packaging works is also valuable to pass on
[18:51] <tomreyn> looking at the launchpad bazaar(s) will probably provide more info on how packaging is done.


[13:51] <CarlFK> netboot, preseed, maverick - works fine on a real box.  running under qemu, it prompts me to confirm creating / and swap.  that bit of syslog: http://dpaste.de/oe2k/
[13:52] <CarlFK> preseed has d-i partman/confirm boolean true
[14:22] <CarlFK> Jan  2 14:08:19 in-target: Failed to fetch http://us.archive.ubuntu.com/ubuntu/pool/main/k/keyutils/libkeyutils1_1.4-1_i386.deb  Hash Sum mismatch
[14:23] <CarlFK> another qemu only thing.  happened 2x now.  I am using squid to cache the .debs - how can I manually check the mismatch? (I am guessing md5sum libkeyutils1_1.4-1_i386.deb  and look it up somewhere


[20:24] <lifeless> morning
[20:58] <lifeless> I can has review?
[22:27]  * mwhudson stabs xchat's url-finding
[22:27] <mwhudson> lifeless: which is the most urgent of the reviews?
[22:27] <lifeless> they're all basically tiny; any of them would be great to have reviewed.
[22:27] <lifeless> test is trivial - bare except -> not bare except
[22:28] <mwhudson> ah, so the reviews are not related to the fire?
[22:28] <lifeless> no
[22:28] <lifeless> I'm just pouncing
[22:28] <mwhudson> heh
[22:29] <mwhudson> i need to persuade someone to fix the ath9k drivers, then my arrival in the morning will be less obvious
[22:30] <lifeless> mwhudson: actually, it was saying 'hi' that tipped me off
[22:49] <lifeless> thanks for test approval, to make ec2 land happy could you click on 'comment' change to 'approved', click in the text field, click on 'save commnt' ?
[22:50] <mwhudson> lifeless: i did, and it timed out :-)
[22:51] <lifeless> hah
[22:51] <lifeless> yes, waiting for a gsa/losa to appear
[22:51] <mwhudson> i think it took the second time
[22:51] <lifeless> elmo is trained
[22:51] <lifeless> by which I mean, a train is messing with his bandwidth
[22:51] <mwhudson> ah
[22:57] <mwhudson> lifeless: in https://code.edge.launchpad.net/~lifeless/launchpad/bug-631884/+merge/35219 i don't really understand the comment
[22:57] <mwhudson> "features have two homes" -> i don't see how the request home matters here?
[22:58] <lifeless> if you use LaunchpadTestRequest
[22:58] <lifeless> and create_initialized_view
[22:58] <lifeless> and the code you are calling calls into getFeatureFlag
[22:58] <lifeless> it all goes boom
[22:58] <lifeless> because nothing glues the two things together.
[23:01] <lifeless> what needs to happen is:
[23:02] <lifeless>  - the thread local should die
[23:02] <lifeless>  - it should be found via participations
[23:02] <lifeless>  - login() and scripts should set participations up
[23:02] <lifeless> its another case of building on mud.
[23:05] <mwhudson> i see
[23:05] <lifeless> the problem is that there are lots of tests that do stuff outside of publication
[23:06] <lifeless> or even outside of views
[23:06] <lifeless> so using that as the place to set/remove the thread local won't work well
[23:06] <mwhudson> lifeless: would it more appropriate to say something like "feature flags really should live on the request, but currently don't for reasons as stated in bug 623199" ?
[23:06] <lifeless> I don't konw.
[23:06] <mwhudson> s/request/participation/ i guess
[23:07] <lifeless> I think what I've written is correct without specifying /where/ etc : and its easier to change our mind in a bug than in the comments in the code
[23:07] <mwhudson> otoh, it's very likely that the next person to edit this code will be you and you can figure it out then :)
[23:07] <lifeless> thats true too
[23:07] <lifeless> I'm happy to change it, I don't see that it makes a lot of difference either way.
[23:08] <lifeless> I looked at zope.app.testing.functional.FunctionalTestSetup
[23:08] <lifeless> zomg
[23:08] <lifeless> its -terrible-
[23:11] <mwhudson> lifeless: for the pageid feature thing, i don't see how pageid is ever set to stuff like scoped:thing#type
[23:11] <lifeless> check out api publication
[23:11] <mwhudson> i am
[23:13] <lifeless> servers.py
[23:14] <lifeless> no, sec
[23:16] <lifeless> https://code.edge.launchpad.net/~matsubara/launchpad/bug-606184-pageid-for-collections/+merge/33801
[23:17] <lifeless> is what landed
[23:17] <lifeless> 'FakeContext:FakeCollectionResourceView:#milestone-page-resource'
[23:17] <lifeless> is an example
[23:17] <lifeless> so its :#
[23:18] <mwhudson> ah
[23:18] <lifeless> which my code will handle because it elides empty segments
[23:18] <lifeless> (but I knew there was a good reason)
[23:18] <lifeless> see also https://bugs.edge.launchpad.net/launchpad-foundations/+bug/627027
[23:19] <mwhudson> ah ok
[23:19] <mwhudson> there are no tests of the empty segment handling
[23:19] <lifeless> yes
[23:19] <lifeless> I shall add one for that example pageid
[23:20] <lifeless> actually there are tests of empty segment handling
[23:20] <lifeless> pageid:
[23:20] <lifeless> -> ['']
[23:20] <lifeless> without the empty segment code
[23:20] <lifeless> e.g. tests will fail if you remove the 'if name' clause
[23:20] <mwhudson> i guess
[23:20] <mwhudson> that's not very test as documentation though
[23:20] <lifeless> yes
[23:21] <lifeless> I shall add one
[23:21] <lifeless> just saying :)
[23:21] <mwhudson> ok
[23:23]  * mwhudson stares at an ajax spinner thing
[23:27] <mwhudson> third time lucky, sigh
[23:28] <lifeless> thanks!
[23:31] <mwhudson> huh, https://code.edge.launchpad.net/launchpad/+activereviews just got truncated on me
[23:32] <lifeless> yaup
[23:33] <mwhudson> huh, googling "truncated haproxy" finds some interesting stuff
[23:33] <mwhudson> i guess you're ahead of me on that game though :-)
[23:35] <lifeless> if there were specific ones that would be good
[23:35] <lifeless> however http/1.0 and truncation is a designed in 'feature' ><
[23:35] <mwhudson> lifeless: well<EMAIL_ADDRESS>[23:37] <lifeless> heh, thats a bug indeed


[11:10] <rajsagar> hello everyone
[11:13] <master__> hello
[13:29] <newbie|9> Hi guys...   I want to setup a local Launchpad server for production.. are there any instructions???..   I have found this: https://dev.launchpad.net/Running.. but it only seems to be for development....
[13:29] <newbie|9> When trying to set it up, I get a: /opt/test/stable/lib/lp/app/browser/../templates/root-index.pt
[13:29] <newbie|9> Line 72, Column 14
[13:29] <newbie|9> Expression: <PathExpr standard:u'view/apphomes'>
[13:29] <newbie|9>    - Names:
[13:29] <newbie|9>       {'args': (),
[13:29] <newbie|9>        'context': <lp.services.webapp.publisher.RootObject object at 0x7f1877d0b810>,
[13:29] <newbie|9>        'default': <object object at 0x7f187e0e8430>,
[13:29] <newbie|9>        'loop': {},
[13:29] <newbie|9>        'nothing': None,
[13:29] <newbie|9>        'options': {},
[13:29] <newbie|9>        'repeat': {},
[13:29] <newbie|9>        'request': <lp.services.webapp.servers.LaunchpadBrowserRequest instance URL=https://launchpad1.phaseone.com/index.html>,
[13:58] <newbie|9> Anyone here???
[14:16] <cjwatson> newbie|9: I can only really repeat what I said on launchpad-dev: https://lists.launchpad.net/launchpad-dev/msg09809.html
[14:16] <cjwatson> I'd need to see the full traceback to debug whatever you're currently seeing (in a pastebin or something, not just pasted into IRC)
[14:25] <newbie|9> Pastebin: https://pastebin.com/QH01TpjV
[14:26] <newbie|9> <-- traceback
[14:26] <newbie|9> Seems like it can be traced back to the canonical_url function..
[14:27] <newbie|9> I think I read something, someplace, that the "base" ubuntu branch has to be set in some way???
[14:30] <cjwatson> If you're running with a completely empty database then you're probably missing some of the "celebrities" that the Launchpad code relies on.
[14:30] <cjwatson> The "ubuntu" distribution is indeed one of those.
[14:31] <newbie|9> ahhh... ok.. and how do I generate these???
[14:35] <newbie|9> I have just run the "make schema"
[14:37] <cjwatson> make schema will give you sampledata, which is insecure for a new production instance.  I'm not aware of any documentation on setting up a new non-development instance entirely from scratch.
[14:37] <cjwatson> It would probably involve manual fiddling with psql ...
[14:37] <newbie|9> But "make schema" should provide the celebrities????
[14:37] <cjwatson> lib/lp/app/utilities/celebrities.py has the list of celebrities that exist.
[14:38] <cjwatson> It will, yes, but it will also provide other things that aren't suitable for an instance on the internet.
[14:38] <newbie|9> We'll sort that out, but apparently the celebrity is still not there...
[14:38] <cjwatson> Like a bunch of template accounts ...
[14:39] <cjwatson> I've never seen anyone sort that out successfully when starting from sampledata.
[14:39] <cjwatson> What are you actually trying to do?
[14:40] <newbie|9> for now, just setting up the development...
[14:40] <newbie|9> and then hardening...
[14:41] <cjwatson> Right, but what's your actual goal?
[14:41] <cjwatson> Having your own Launchpad instance is a pretty gigantic sledgehammer, and most nuts can be cracked with something a bit smaller.
[14:42] <newbie|9> For our Red Hat customers we are using COPR, for our SLES customers we are using OBS.. So we just want something similiar for our Ubuntu Customers
[14:43] <cjwatson> So, like I said on launchpad-dev, our practical purpose in open-sourcing Launchpad was mainly to make it easier for people to help with improving launchpad.net.  For setting up your own instance you're basically on your own.
[14:44] <cjwatson> It might be worth inserting 'import pdb; pdb.set_trace()' into the apphomes method in lib/lp/app/browser/root.py and seeing where it's going wrong exactly.
[14:45] <cjwatson> Then e.g. trying to evaluate getUtility(ILaunchpadCelebrities).ubuntu to see if it's that.
[14:46] <cjwatson> If it actually is something inside canonical_url then you can step into that and try to narrow it down a bit.
[14:46] <cjwatson> Given that you've started from sampledata it's probably something fairly simple, since that normally does work out of the box.
[14:46] <newbie|9> Ok.. so where did you what to enter getUtility(ILaunchpadCelebrities).ubuntu??
[14:47] <cjwatson> At the pdb prompt after you make a request
[14:47] <cjwatson> 'import pdb; pdb.set_trace()' is a breakpoint
[14:47] <newbie|9> And I would do that, just before using canonical_url?? or in the canonical_url method
[14:48] <cjwatson> Before.
[14:48] <cjwatson> The idea is to try to figure out which part of the apphomes method is raising an exception.
[14:48] <cjwatson> If you don't already know how to drive pdb, you are going to need to learn.
[14:51] <newbie|9> ok.. thanks...
[15:04] <newbie|9> I get a: "expected a string or other character buffer object" on getUtility(ILaunchpadCelebrities).ubuntu)... line 111 in lib/lp/app/browser/root.py...
[15:06] <cjwatson> p repr(getUtility(ILaunchpadCelebrities).ubuntu)
[15:07] <newbie|9> (Pdb) p repr(getUtility(ILaunchpadCelebrities).ubuntu)
[15:07] <newbie|9> *** TypeError: TypeError('expected a string or other character buffer object',)
[15:11] <cjwatson> uh
[15:12] <MrMEEE> ? a little weird?
[15:12] <cjwatson> from lp.registry.interfaces.pillar import IPillarNameSet
[15:12] <cjwatson> p getUtility(IPillarNameSet).getByName('ubuntu')
[15:13] <cjwatson> (should print "<Distribution 'Ubuntu' (ubuntu)>")
[15:13] <MrMEEE> (Pdb) from lp.registry.interfaces.pillar import IPillarNameSet
[15:13] <MrMEEE> (Pdb) p getUtility(IPillarNameSet).getByName('ubuntu')
[15:13] <MrMEEE> None
[15:13] <MrMEEE>
[15:13] <MrMEEE> nope
[15:14] <cjwatson> Then I don't believe that you're running against the database produced by make schema.
[15:15] <cjwatson> Have a look with psql (the default database name is launchpad_dev, but you should check with psql -l in case you're actually using something else): SELECT id FROM distribution WHERE name = 'ubuntu';
[15:15] <cjwatson> sampledata contains that with id 1
[15:16] <cjwatson> The database name is set in the [database] rw_main_master and rw_main_slave keys in launchpad-lazr.conf
[15:17] <MrMEEE> Haven't touched it after..... Ipostgres=# \c launchpad_dev
[15:17] <MrMEEE> You are now connected to database "launchpad_dev" as user "postgres".
[15:17] <MrMEEE> launchpad_dev=# SELECT id FROM distribution WHERE name = 'ubuntu';
[15:17] <MrMEEE>  id
[15:17] <MrMEEE> ----
[15:17] <MrMEEE> (0 rows)
[15:17] <MrMEEE>
[15:17] <cjwatson> Well, you'll need to work out why make schema didn't put sampledata in place then
[15:17] <cjwatson> Or else inject the right set of celebrities yourself
[15:18] <MrMEEE> I got this first...: https://pastebin.com/7eY17e3c
[15:18] <MrMEEE>
[15:18] <MrMEEE> and then I ran "sudo -u postgres make create"
[15:18] <MrMEEE> but ok... I'll look into the sampledata
[15:19] <cjwatson> Ah.  That would have been useful to know an hour ago.
[15:19] <cjwatson> You shouldn't run make schema as root.
[15:20] <cjwatson> In general you shouldn't run anything Launchpaddish as root.
[15:20] <MrMEEE> Ok.. sry.. It just said that I could run "sudo -u postgres make create"...
[15:21] <MrMEEE> so I presumed that it didn't matter
[15:21] <cjwatson> Yeah, but it shouldn't have failed in the first place.
[15:22] <cjwatson> And the message is a bit misleading.  It's only saying how to make that *particular* bit of the Makefile work, but there's more to it than 'make create'.
[15:22] <MrMEEE> Ok.. I'll try as a normal user... and see what happens
[15:22] <MrMEEE> Thanks
[15:23] <cjwatson> Anyway, utilities/launchpad-database-setup sets things up with a DB user corresponding to the mortal user you run it as.
[15:23] <cjwatson> You should run that (as non-root) if you haven't already.
[15:23] <cjwatson> And you'll probably need to chown all sorts of things now ...
[15:23] <cjwatson> I suspect your problem is in fact not having run launchpad-database-setup ...
[15:24] <MrMEEE> ok