[00:01] <[reed]> Linux people will always hate huge packages
[00:01] <[reed]> except the kernel
[00:12] <asac> hmm
[00:12] <asac> right he is in launchpad-dev team
[00:22] <asac> commented
[00:22] <asac> fta: ^ ;)
[00:37] <fta> yep
[02:04] <dtchen> asac: xulrunner-1.9.1 <IP_ADDRESS>+nobinonly-0ubuntu<IP_ADDRESS> and firefox-3.5 3.5.5+nobinonly-0ubuntu<IP_ADDRESS> from the security ppa work fine from my testing (new 3.5.5 profile, existing 3.5.4 profile, existing 3.0.15 profile)
[02:05] <micahg> ugh, 3.5.5 is a update release, not a security release...
[02:06]  * micahg needs to add something to Lucid Ideas wiki page
[02:07] <asac> dtchen: thx a bunch
[02:07] <asac> micahg: yes. its a stability only release
[02:07] <micahg> asac: it gave me another topic for the wiki
[02:08] <asac> :)
[02:08] <asac> great
[02:08] <micahg> asac: when do we get to discuss the topics?
[02:09] <asac> micahg: right. thats what we talk about for ages now
[02:09] <asac> i started a wiki on PPA reorg
[02:09]  * asac searches wiki
[02:09] <asac> https://wiki.ubuntu.com/MozillaTeam/PPAs
[02:09] <asac> the pinning examples are a bit messed up
[02:10] <asac> still have the feeling that the pinning will be a red herring for the transitional package use-case ... which is the only reason not to also split per-branch
[02:11] <micahg> asac: I don't use it like that
[02:11] <asac> what do you mean?
[02:12] <micahg> I pin all PPAs at 450, if you install a version from a ppa, you get updates from the ppa until an archive version supercedes it
[02:13] <micahg> I pinned my moz-beta ppa at 475, so it's ahead of the dailies
[02:14] <asac> so assume you have firefox-backports and firefox-daily ppas enabled
[02:14] <asac> and want
[02:14] <asac> a) firefox-3.5 from archive
[02:14] <asac> b) firefox-3.6 from -backports
[02:14] <asac> c) firefox-3.7 from -daily
[02:14] <asac> how would you pin that?
[02:14] <asac> and maybe
[02:15] <asac> a) firefox-3.5 from archive
[02:15] <micahg> sounds like me :)
[02:15] <asac> b) firefox-3.6 from -backports
[02:15] <asac> c) firefox-3.7 from -backports (in theory)
[02:15] <asac> micahg: can you post your pin files?
[02:15] <micahg> no
[02:15] <micahg> would be no ff3.5
[02:16] <micahg> I would pin -backports higher than -dailies
[02:17] <asac> so how do your current pins look like?
[02:17]  * micahg has too many
[02:17] <asac> e.g. how do you do the per-version pinning
[02:17] <asac> do you list all package names explicitly?
[02:17] <micahg> I'll pastebin the relavent ones
[02:17] <asac> thx
[02:18] <micahg> http://pastebin.ubuntu.com/314734/
[02:18] <asac> ok
[02:18] <micahg> I have 3.7 from dailies, 3.6 from micahg-mozilla-beta, and FF35 from -security
[02:18] <asac> thats just seleting based on PPAs
[02:18] <asac> not by version
[02:19] <asac> so if you want to run 3.5 from dailies but 3.6 from archive ... will not work
[02:19] <micahg> sure it will
[02:19] <asac> how?
[02:19] <micahg> ppa is on demand if higher version
[02:19] <micahg> you install it, you get updates
[02:19] <micahg> you don't, you don't get it
[02:19] <micahg> http://pastebin.com/f5a3bcbb8
[02:21] <asac> well. that depends on a specific layout of what is where, right?
[02:21] <micahg> not really
[02:21] <asac> if you assume that all packages are everywhere, etc. ... this wouldnt work, right?
[02:21] <micahg> as long as the ppa is higher than the archive, you can choose which one you want
[02:21] <asac> like you have a firefox-3.7 in the archive, beta and daily ppa
[02:21] <asac> how?
[02:21] <asac> how do you choose that?
[02:22] <asac> the user-experience i want is that user says:
[02:22] <asac> "i want firefox-3.5 as dailies"
[02:22] <micahg> pin beta at 475
[02:22] <micahg> daily will always be higher
[02:22] <asac> "i want firefox-3.6 as backports/milestones"
[02:22] <micahg> apt will not make you install a lower version
[02:23] <asac> then user runs apt-get dist-upgrade ... and all should be as he opted-in
[02:23] <micahg> dist-upgrade disables all ppas :)
[02:23] <asac> no
[02:23] <asac> not here ;)
[02:23] <micahg> did for me
[02:23] <asac> well.. you know what i mean
[02:23] <micahg> :)
[02:23] <asac> apt-get dist-upgrade?
[02:23] <asac> that works for me
[02:23] <asac> i always run that
[02:24] <asac> you probably mean update-manager -d
[02:24] <micahg> oh, I guess I'm remembering from debian :)
[02:24] <micahg> you want it totally automatic
[02:25] <micahg> ugh, yeah, you'll probably have to pin individual packages then
[02:25] <asac> what i want is to build a UI that allows users to just select what they want from where ...
[02:25] <micahg> which is a mess
[02:25] <asac> that UI does not interfaces with apt/update-manager etc. to reduce complexity
[02:25] <asac> just adds the PPAs and the pinning
[02:25] <micahg> once you install a version higher than the archives, you'll get updates
[02:25] <asac> that would be the perfect user experience i would hope for :;)
[02:25] <micahg> mozilla-configurator?
[02:25] <asac> micahg: right. but then in case archive gets a higher version for a minute you bounce back to archive
[02:25] <asac> right
[02:25] <asac> or daily-tester-tools
[02:25] <asac> or something like that
[02:26] <micahg> well, if we're going to do that, then we can certainly pin higher and the individual pacakges
[02:27] <micahg> like you have on the wiki
[02:27] <asac> yes. but we need working examples
[02:27] <asac> for the two cases i mentioned (not sure what the UI would use, but probably the second):
[02:27] <asac> 1. For users that want to run dailies or backports for just a specific version, we suggest lowering the priority of the repository using apt pinning and then increasing the score for the app that is wanted.
[02:27] <asac> 2. To opt-in only for specific application versions we provide a wizard script puts the proper pinning in place.
[02:28] <asac> sorry for the confusion ;)
[02:28] <asac> thats just one approach. i think i removed the second way of approaching this ;)
[02:28] <asac> from the wiki
[02:28] <Out_Cold> i'm confused... can someone please direct me towards the firegpg team?
[02:28] <micahg> I think all ppas should be < 500 by default
[02:29] <micahg> maybe that should go in lucid...
[02:29] <asac> but does that matter for the mozilla configurator thing?
[02:29] <asac> i would think thats independent.
[02:29] <micahg> no, we can handle it independently
[02:30] <asac> right
[02:30] <asac> something that might be worth looking into for the whole distro
[02:30] <micahg> Out_Cold: in Ubuntu or in general?
[02:30] <asac> we should discuss with mvo
[02:30] <micahg> asac: yeah, that's what I'm thinking
[02:30] <asac> micahg: also i hoped by using a low prio like 10 that packages might even get downgraded if user opt-out later on
[02:31] <micahg> Out_Cold: http://getfiregpg.org/s/help
[02:31] <Out_Cold> well i'm using ubuntu so it may be related to that
[02:31] <asac> the main problem is that we seem to need to add explicit entry for _all_ binary packages for a source
[02:31] <micahg> Out_Cold: we don't package it yet, so I suggest following the link I posted
[02:31] <asac> like user says: "firefox-3.5 from beta" -> we need to somehow get all package names and put a pin with prio like in the wiki or something
[02:31] <Out_Cold> thanks
[02:31] <asac> micahg: gnomefreak made a package
[02:32] <asac> it should get uploaded for lucid finally
[02:32] <asac> it had license issues in the past
[02:32] <asac> i /think/ those are now fixed
[02:33] <asac> micahg: what i mean is that "Package: firefox-3.6* abrowser-3.6* xulrunner-1.9.2*
[02:33] <asac> "
[02:33] <asac> does not work i found out
[02:33] <micahg> asac: well, we can code the package names into the app
[02:33] <asac> we need one entry for each binary package
[02:33] <asac> micahg: yeah. but thats also maintenance pain ;) ... would prefer if it was automatic somewhat ...
[02:33] <asac> that leads to another question: how to keep track in case more packages pop up etc.
[02:34] <micahg> don't one of the files in the bzr archive have the package names?
[02:34] <asac> control
[02:34] <asac> debian/control
[02:34] <micahg> can we parse that?
[02:35] <asac> we probably could. but when? when user enables/disables it, that might be simple ... but what if suddenly there is one more package avail.
[02:35] <asac> we can also check the package DB ...
[02:35] <asac> thats not that hard
[02:35] <micahg> asac: that would be after they enabled though
[02:36] <asac> yeah. so probably needs to be just implemented and then tested
[02:36] <micahg> we'd have to add the source, pin, update again
[02:36] <asac> micahg: not necessarily
[02:36] <micahg> sorry, add source, update, pin, update
[02:36] <asac> micahg: in ubufox i use python apt lib to do our own package db tempdir
[02:36] <micahg> asac: a regular user wouldn't have any package info on  3.7 without a daily
[02:37] <asac> you can do that for arbitrary sources.list snippets that would be shipped in the configurator app
[02:37] <asac> bzr branch lp:ubufox
[02:37] <asac> cd ubufox/pfsdb/
[02:37] <micahg> ah, we could build a temporary apt db, pin, update
[02:37] <micahg> ok
[02:37] <asac> pfs/db/
[02:38] <asac> nppapt.py  plugindb.py  recreatedb.sh  sources.list  sources.list.7.10  sources.list.8.04  sources.list.8.10  sources.list.9.04  sources.list.9.10
[02:38] <asac> micahg: yes. still we would need to react on when new package appear
[02:39] <asac> point is that if we start to have our own apt db ...
[02:39] <asac> we will be out of sync of what the real apt db knows
[02:39] <asac> so we could do our own db in mozilla configurator ... and also add a trigger maybe
[02:39] <asac> apt trigger
[02:39] <asac> not sure how ;)
[02:39] <micahg> yeah
[02:40] <asac> have to check with mvo ...
[02:40] <micahg> asac: etckeeper has an apt trigger
[02:40] <micahg> http://pastebin.com/f211b5517
[02:41] <asac> in anycase ... before we start putting work into something like that we should be sure that we have the right generic pinning approaches
[02:41] <asac> strategies
[02:41] <asac> and that they work as expected
[02:41] <asac> otherwise we do lots of work and then find that the pinning is a mess ;)
[02:42] <asac> and that we need to split ppa per version too
[02:42] <micahg> asac: PPA per version seems crazy
[02:42] <asac> but in that case cant do transitional packages etc again ... but here again i am not sure about how the transition would behave
[02:43] <asac> micahg: the only technica reason (besides the guts feeling of bloet) to not have ppa per version is that we need to do transitions like i described
[02:43] <asac> in wiki
[02:43] <asac> for technical reasons we don't have per-version daily repositories as this would cause problems when shipping partial transitions such as moving the firefox meta package from 3.5 to 3.6 package
[02:43] <asac> https://wiki.ubuntu.com/MozillaTeam/PPAs#Using%20PPAs%20for%20just%20specific%20application%20versions
[02:44] <asac> maybe it would be easier to just implement the package* syntax in apt for pinning
[02:44] <micahg> oh, I wanted to ask, why are we taking over default browser in 8.04 - 9.04 dailies?
[02:44] <asac> in lucid
[02:44] <asac> (doesnt help for all the older releases though)
[02:45] <asac> micahg: you mean: why we transitioned to 3.5?
[02:45] <asac> thats because dailies are double dailies for us
[02:45] <micahg> in the dailies for hardy - jaunty
[02:45] <asac> otherwise things would become realy complex
[02:45] <asac> we would need -daily-stable ... -daily-backports ;)
[02:45] <asac> so antoher ppa set
[02:46] <asac> like daily, but using the release branches
[02:46] <asac> firefox-3.5.karmic ... firefox-3.0.hardy etc.
[02:46] <asac> and daily, but using .head branch
[02:46] <asac> the latter is what we define as dailies atm
[02:47] <asac> which automatically comes with the take over you asked for
[02:47] <asac> and also with the semi transition that is the technical blocker for splitting ppas per version
[02:47] <asac> 03:43 < asac> for technical reasons we don't have per-version daily repositories as this would cause problems when shipping partial transitions such as moving the  firefox meta package from 3.5 to 3.6 package
[02:48] <micahg> asac: you're up late :)
[02:48] <asac> yes
[02:48] <asac> too much holiday -> too much stuff to do this week
[02:48] <asac> next week is UDS etc.
[02:48] <micahg> well, it would seem like a lot of work to maintain per version ppas
[02:49] <asac> thats the same work imo ... fta would just upload them to the right repo
[02:49] <asac> we can also automate the milestone spinnings i hope in the same way
[02:49] <asac> just a manual push i guess rather than something that riuns fully automated
[02:51] <micahg> asac: is ff3.5.5 going through -proposed?
[02:51] <asac> no
[02:51] <asac> its a regression release
[02:51] <asac> for the previous security update
[02:52] <asac> and just has a hand ful of changes
[02:52] <asac> like a minibranch
[02:52] <micahg> -updates?
[02:52] <asac> it goes to -security ... and we always copy that to -updates too to help mirroring security updates
[02:52] <asac> same procedure as security updates basically
[02:52] <asac> just a regression fix for a security udpate
[02:53] <asac> (thats why i uploaded to the security ppa)
[02:54] <micahg> asac: you don't seem to make new snapshot commits, am I supposed to do that?
[02:54] <asac> i dont?
[02:54] <asac> oh
[02:54] <asac> i forgot ... my bad then
[02:54] <micahg> sometimes
[02:54] <asac> i usually do
[02:54] <asac> i try to do
[02:54] <micahg> like today
[02:55] <asac> so i should at least have bumped the changelog version
[02:55] <micahg> ugh, TB3 cairo bumped to 1.8.8
[02:55] <asac> and include that its a new snapshot in the same commite message
[02:55] <asac> did i do that at least?
[02:56] <asac> i think i ended up doing that in one commit if its just one change for that snapshot ... but splitting up in pure snapshot bump and multiple commits
[02:56] <micahg> yes
[02:56] <asac> if there is more than one thing required
[02:56] <asac> i think both is ok
[02:57] <asac> ok i failed here
[02:57] <asac> let me uncommit :/
[02:57] <micahg> ugh
[02:58] <asac> oh shit. i think that was really a bad idea because fta already did a new run :/
[02:58]  * asac feels dirty
[02:58]  * asac hides
[02:59] <micahg> I didn't see a new run since you fixed that
[02:59] <asac> good
[02:59] <micahg> asac: you're safe
[02:59] <asac> then i might be lucky :-P
[02:59] <micahg> he reran after I committed ff3.7
[03:00] <micahg> did you do overwrite?
[03:00] <asac> yes.
[03:00] <asac> i have a bound branch
[03:00] <asac> that automatically applies it
[03:00] <asac> thats why i couldnt stop it after bzr uncommit ;)
[03:00] <asac> it just did it
[03:00] <micahg> oops
[03:00] <micahg> wrong version :)
[03:01] <micahg> New upstream snapshot: <IP_ADDRESS> HG 20091109r26560
[03:01] <asac> help me ;)
[03:01] <micahg> I think only sleep can help at this point ;)
[03:01] <asac> ok i think its now ok ;)
[03:02] <asac> and yes. i should not touch branches after 4am ;)
[03:02] <asac> thats usually a bad idea
[03:02] <asac> ok i nthat sense out ... hope i didnt bust something else in that last commit ;)
[03:02] <micahg> ok, I'll bump libcairo for TB3 later otnight
[03:03] <asac> yeah go ahead
[03:03] <asac> ttyt
[03:03] <micahg> ok
[14:25] <asac> bdrung: also: http://www.asoftsite.org/s9y/archives/152-ubuntu-mozillateam-minutes-14th-sep-08-....html#c748
[14:27] <bdrung> k
[14:28] <asac> bdrung: so the other problem is that we cannot really share anything with debian because of trademark implications. so the only practical way would be for debian folks to join ubuntu mozillateam (e.g. flip it upside down)
[14:29] <asac> which would make much more sense
[14:29] <asac> especially because we have all the users and get real feedback on QA etc.
[14:30] <bdrung> asac: the feadback depends on the package. some packages get more feedback in debian.
[14:33] <asac> yes. but for mozillas
[14:33] <asac> i am only speeking on mozilla stuff ;)
[14:34] <bdrung> yeah, that true. simply compare the popcon stats
[15:00] <asac> kenvandine: not online with jabber?
[15:00] <kenvandine> asac, i am
[15:00] <asac> hmmm ... do you still have<EMAIL_ADDRESS>in there?
[16:39] <snorp> hello, my lizard friends
[16:40] <snorp> I am attempting to use xulrunner 1.9.1 from here: https://launchpad.net/~ubuntu-mozilla-daily/+archive/ppa
[16:40] <snorp> it looks like it needs a newer nspr, which is not in that ppa
[16:40] <snorp> a little help? :)
[16:40] <micahg> snorp: which package?
[16:41] <snorp> micahg: it's not a package dep issue (more of a missing dep)
[16:41] <micahg> or rather which releasE?
[16:41] <snorp> but libxulrunner-unstable pkg-config require mozilla-nspr
[16:41] <snorp> which I can't fine
[16:41] <micahg> are you trying to build it?
[16:42] <snorp> no
[16:42] <snorp> trying to build against it
[16:42] <micahg> which release are you on?
[16:42] <snorp> err, libxul-unstable.pc I mean
[16:42] <snorp> hardy
[16:42] <micahg> ah
[16:42] <snorp> s/fine/find/ :)
[16:43] <micahg> snorp: xulrunner-1.9.1 is not meant to be built against in hardy
[16:43] <snorp> oh :(
[16:43] <snorp> that makes me immeasurably sad
[16:43] <micahg> we don't officially support it at this time
[16:43] <micahg> we're working on backports for mozilla software right now
[16:43] <snorp> right, I understand
[16:45] <micahg> snorp: is there a reason you're using 1.9.1 instead of 1.9.0?
[16:45] <micahg> or rather 1.9
[16:45] <snorp> micahg: just want to move to 1.9.1 for some things
[16:45] <snorp> I work for a partner of canonical
[16:45] <snorp> they are going to get us "official" packages
[16:45] <micahg> asac: ^^^
[16:45] <snorp> but just trying to get something going in the mean time
[16:45] <snorp> yeah, if asac could help that would be good :)
[16:45] <micahg> pbuilder?
[16:45] <yoasif> micahg: any news on that nvidia/firefox issue?
[16:46] <micahg> yoasif: I've seen more bugs :)
[16:46] <micahg> no, unfortunately not
[16:46] <micahg> is 3.5.5 out yet?
[16:46] <asac> snorp: afaik we should have nspr 4.7.5 in all ubuntu releases ... isnt that the case?
[16:46] <yoasif> no master bug?
[16:46] <asac> !info nspr
[16:46] <yoasif> i just got 3.5.4 from lucid repos
[16:46] <asac> !info libnspr1
[16:46] <asac> !info libnspr1d
[16:47] <micahg> asac: yeah, 4.7.5 is
[16:47] <asac> https://edge.launchpad.net/ubuntu/+source/nspr
[16:47] <asac> snorp: ^^
[16:47] <asac> so maybe you just need to enable -security -updates
[16:47] <asac> to get 4.7.5
[16:47] <asac> that should be recent enough for 1.9.1
[16:47] <snorp> asac: win.
[16:48] <snorp> asac: it is requiring 4.8.2
[16:48] <micahg> ugh, we don't have 4.8.2 in anything
[16:48] <snorp> crap
[16:48] <asac> err
[16:48] <asac> no
[16:48] <micahg> snorp: are you sure it's xulrunner that requires that
[16:48] <asac> i dont think that 1.9.1 really needs 4.8.2 ... maybe latest dailies
[16:48] <asac> but i havent seen that
[16:48] <micahg> asac: the latest in karmic is 4.8
[16:48] <snorp> Requires: mozilla-nspr >= 4.8.2
[16:49] <snorp> from libxul-unstable.pc
[16:49] <snorp> yeah, this is dailies
[16:49] <snorp> is there another source for 1.9.1 I could use?
[16:49] <micahg> debian has 4.8.2
[16:51] <asac> i am in meeting ... will check with you ater that
[16:51] <snorp> cool
[16:56] <micahg> snorp: I don't see anything that would require that
[16:56] <snorp> so maybe I can just hack it to use a lower version
[16:56] <micahg> do you have nspr 4.8.2?
[16:56] <snorp> nope
[17:49] <armin76> asac: fta: sparc workaround latest comment at mozilla bug 448658
[17:50] <eagles0513875> can i ask a random question guys as im seeing armin76 mention sparc. how does one test stuff for other processor architectures if they dont ahve the hardware
[17:51] <av`__> eagles0513875, they use a qemubuilder for building purposes
[17:51] <av`__> but for testing is har
[17:51] <av`__> * hard
[17:51] <eagles0513875> gotcha
[17:52] <av`__> also setting up a qemubuilder is not that easy
[17:52] <eagles0513875> there is no emulated environment or anything of the sort?
[17:52] <av`__> qemubuilder is an emulated environment
[17:52] <av`__> it uses particular kernel images to build the chroot
[17:52] <av`__> and then you can run some archs like sparc or amd64
[17:52] <av`__> if you are on i386
[17:53] <eagles0513875> ahhhh
[17:53] <av`__> or i386 if you are into amd64, sparc whatever
[17:53] <av`__> but sometimes it's broken
[17:53] <eagles0513875> ahhh ok
[17:53] <av`__> so ...
[17:53] <eagles0513875> im gonna update my laptop to lucid and begin helping u guys out
[17:54] <av`__> cool
[17:55] <micahg> eagles0513875: you don't have to be on lucid to package for lucid
[17:55] <eagles0513875> micahg: working on extensions for ff
[17:55] <micahg> right
[17:55] <micahg> as long as you have the latest m-devscripts, you should be ok
[17:55] <eagles0513875> are you talking about working in a chroot environment?
[17:56] <micahg> well, pbuilder can build the lucid package for you
[17:56] <micahg> pbuilder-dist in ubuntu-dev-tolls
[17:56] <micahg> *ubuntu-dev-tools
[17:56] <eagles0513875> ahhh ok
[17:56] <eagles0513875> im a novice to all this
[17:56] <micahg> that's why I don't think you should move to lucid
[17:57] <micahg> unless you are willing to do full system recovery if something breaks
[17:57] <eagles0513875> if need be i am willing to reinstall
[17:57] <eagles0513875> or recover
[17:58] <micahg> latest mozilla-devscripts are in the daily PPA
[17:58] <eagles0513875> nice thing for me since im duel booting on boot camp partition on my mac is all i need to do is boot onto the live cd and reinstall grub doesnt complain about it and osx boots just fine
[17:58] <micahg1> eagles0513875: you could run virtualbox also
[17:59] <micahg> if it's an intel mac
[17:59] <micahg> which it has to be  I guess
[17:59] <eagles0513875> micahg: i have noticed though that bugs might not surface in a vm like they would in a physical machine
[17:59] <micahg> well, hw bugs wouldn't
[17:59] <micahg> ok, gtg
[18:00] <micahg> bbiab
[18:09]  * eagles0513875 waves to asac
[18:45] <asac> hi eagles0513875
[18:45] <asac> snorp: so what are you working on? karmic?
[18:46] <snorp> asac: hardy
[18:48] <asac> snorp: ok. for that you definitly need to pull in a nspr on your own if you want to build using system-nspr
[18:48] <asac> i would think that the karmic package should be enough
[18:49] <snorp> ok, I'll give that a shot
[18:50] <asac> snorp: so basically to build the karmic packages for xulrunner-1.9.1 firefox-3.5 and nspr and nss
[18:50] <asac> s/to //
[18:50] <snorp> nod
[18:51] <micahg> asac: membership meeting is Wed Nov 18 at 2100 UTC
[18:52] <asac> ok ... what time is that in dallas?
[18:54] <micahg> 3PM :)
[18:54] <micahg> I'll be several hundred miles north of you ;)
[19:04] <micahg> asac: should I comment on the blueprint?
[21:01] <fta> anyone using ff3.7 here?
[21:02] <fta> Error: uncaught exception: [Exception... "Component returned failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIXPCComponents_Utils.import]"  nsresult: "0x80520012 (NS_ERROR_FILE_NOT_FOUND)"  location: "JS frame :: chrome://browser/content/browser.js :: delayedStartup :: line 3590"  data: no]
[21:03] <fta> asac, [reed]: ^^
[21:03] <[reed]> on startup or what?
[21:03] <fta> yes
[21:04] <[reed]> guess it can't find the new components.list file?
[21:04] <fta> i'm trying to find why my session is no longer restored
[21:04] <fta> that's the only error in the console
[21:05] <[reed]> do you have components/components.list
[21:05] <[reed]> in your firefox directory?
[21:05] <[reed]> should be in the same directory compreg.dat is
[21:07] <[reed]> fta: ^
[21:08] <fta> nope
[21:10] <fta> [reed], but it doesn't seem to look for this either: http://paste.ubuntu.com/315396/
[21:11] <[reed]> some apparmor thing stopping it from creating it?
[21:13] <fta> no, no profile for 3.7 yet
[21:13] <fta> could it be the gio/gvfs switch?
[21:14] <[reed]> doubt it... when did this start?
[21:14] <[reed]> what is line 3590 of browser.js?
[21:15] <fta> last week
[21:16] <[reed]>   Cu.import("resource://gre/modules/NetworkPrioritizer.jsm", NP);
[21:16] <fta> 3590     if (!gPrefService.getBoolPref("browser.fullscreen.autohide"))
[21:16] <[reed]> that's line 3590 in my browser.js
[21:16] <fta> hm
[21:17] <[reed]> if you go to that url
[21:17] <[reed]> resource://gre/modules/NetworkPrioritizer.jsm
[21:17] <[reed]> in firefox
[21:17] <[reed]> what do you see?
[21:17] <[reed]> the file should be present in the modules/ directory
[21:18] <fta> not found
[21:18] <[reed]> so, that's your problem
[21:18] <[reed]> need to figure out why that file isn't found
[21:18] <fta> but root@ix:~ # find /usr/lib/firefox* -name NetworkPrioritizer.jsm
[21:18] <fta> /usr/lib/firefox-3.7a1pre/modules/NetworkPrioritizer.jsm
[21:18] <[reed]> hmm
[21:19] <fta> Error: uncaught exception: [Exception... "Cannot modify properties of a WrappedNative"  nsresult: "0x80570034 (NS_ERROR_XPC_CANT_MODIFY_PROP_ON_WN)"  location: "JS frame :: chrome://global/content/bindings/autocomplete.xml :: onxblpopuphiding :: line 825"  data: no]
[21:19] <fta> probably unrelated
[21:19] <[reed]> yeah, sounds unrelated
[21:20] <[reed]> can you do resource://gre/modules/PluralForm.jsm
[21:20] <[reed]> ?
[21:20] <[reed]> do you get that file?
[21:20] <fta> yes
[21:20] <[reed]> huh
[21:21] <fta> but it's provided by xul, not ff
[21:21] <fta>  /usr/lib/xulrunner-1.9.3a1pre/modules/PluralForm.jsm
[21:21] <[reed]> ah
[21:21] <[reed]> what about:
[21:22] <[reed]> resource://gre/modules/openLocationLastURL.jsm
[21:22] <[reed]> that is in ff
[21:22] <fta> nope, nada
[21:22] <fta>  /usr/lib/firefox-3.7a1pre/modules/openLocationLastURL.jsm
[21:23] <[reed]> could be one of ubuntu's gre patches is messing stuff up
[21:23] <[reed]> I know you all play with that
[21:23] <fta> asac, ^^
[21:27] <[reed]> mconnor: sound right, or could it be something on our end?
[21:30] <mconnor> in a meeting
[21:39] <Mook_sb> shouldn't it be resource://app/modules/NetworkPrioritizer.jsm ?
[21:45] <[reed]> fta: does that work for you? ^
[21:58] <fta> it does
[21:59] <fta> [reed], you know you can also install our debs, they will not destroy your profile
[21:59] <mconnor> just his soul
[21:59] <fta> i can reproduce on 3 boxes
[21:59] <[reed]> fta: `ls /usr/lib/firefox-3.7a1pre/modules/`
[22:00] <[reed]> what is in that directory?
[22:00] <[reed]> I'll work up a patch
[22:00] <fta> 3 files
[22:00] <fta> -rw-r--r-- 1 root root 13752 2009-11-10 02:49 distribution.js
[22:00] <fta> -rw-r--r-- 1 root root  7067 2009-11-10 02:49 NetworkPrioritizer.jsm
[22:00] <fta> -rw-r--r-- 1 root root  3661 2009-11-10 02:49 openLocationLastURL.jsm
[22:00] <[reed]> ok, cool
[22:01] <[reed]> resource://gre/modules/distribution.js I assume is file not found, too?
[22:02] <fta> right
[22:03] <[reed]> ok
[22:21] <fta> ok, cheated by making symlinks of those 3 files for ff to xul dir, it worked, my session is properly restored
[22:21] <fta> -for+from
[22:22] <fta> [reed], ^^
[22:22] <micahg> fta: maybe we need to ship them in ff instead of xul?
[22:23] <[reed]> no, it's a bug on the browser side
[22:23] <fta> upstream should fix that
[22:23] <[reed]> I'm filing a bug with a patch now
[22:23] <fta> yeah, good
[22:24] <fta> how come no one noticed it?
[22:25] <[reed]> dunno
[22:25] <[reed]> filed mozilla bug 527784
[22:27] <micahg> [reed]: what does dogfood mean?
[22:28] <[reed]> dogfood means it blocks developers from actually working
[22:28] <[reed]> and session restore being broken means developers unhappy
[22:28] <micahg> H
[22:28] <micahg> ah
[22:31] <fta> micahg, do have/know a bug # for the unicode bug?
[22:31] <micahg> no, not yet
[22:31] <micahg> are you seeing it too?
[22:33] <fta> yes, at work
[22:33] <fta> both in tab names, and inside pages
[22:35] <micahg> fta: 3.6 or trunk?
[22:36] <fta> trunk
[22:36] <fta> i only use trunk
[22:36] <micahg> ok, so it's something that landed between beta 1 and beta 2 on 3.6 and not fixed in trunk
[22:44] <[reed]> fixed mozilla bug 527784
[22:44] <[reed]> :)
[23:01] <fta> thx
[23:02] <[reed]> however, I will say that actually running the test suite would have caught this bug
[23:02] <[reed]> so, that's something you all should really _truly_ look into doing on a regular basis
[23:02] <[reed]> or at least once before every release
[23:04] <fta> i'm running the test suite at build time
[23:04] <fta> but it fails very early
[23:04] <fta> ..and no one cared until now
[23:06] <[reed]> fails with what message?
[23:07] <[reed]> and we most assuredly have cared before -- I remember several times where Mozilla has asked Ubuntu to run the test suite on a regular basis
[23:15] <fta> [reed], i've been running make check for nearly a year, but it's not clear what kind of tests you want us to run, and if it's possible to run that in our restricted env
[23:16] <fta> http://launchpadlibrarian.net/35496517/buildlog_ubuntu-karmic-i386.xulrunner-1.9.3_1.9.3~a1~hg20091110r34734%2Bnobinonly-0ubuntu1~umd1_FULLYBUILT.txt.gz
[23:16] <fta> search for "[check] Error"
[23:17] <micahg> [reed]: BTW, there's breakage with gcc4.4 and lpia on trunk
[23:19] <[reed]> fta: looks like a patch on your end is modifying system-wrappers
[23:19] <[reed]> micahg: file a bug
[23:19] <micahg> [reed]: :) when I get a chance
[23:38] <[reed]> fta: http://bazaar.launchpad.net/~ubuntu-mozilla-daily/firefox/firefox-3.7.head.daily/annotate/head%3A/debian/patches/dont_depend_on_nspr_sources.patch
[23:38] <[reed]> that patch is causing the problem
[23:44] <fta> wrong branch
[23:44] <fta> xul, not ff


[00:21] <dtchen_> greg-g: sorry, that ETA was optimistic. i lost three hours due to a incorrect wiki entry.
[00:21] <dtchen_> an incorrect*
[00:21] <dtchen_> (now fixed, of course)
[00:34] <greg-g> dtchen_: no worries
[00:35] <greg-g> dtchen_: so, after last night, I have no sound, is there a way to make apt reinstall the sound modules?
[00:37] <Hobbsee> greg-g: my favorite solution to that is to delete ~/.pulse-cookie, and restart X.
[00:38] <Hobbsee> and then see if you have sound
[00:39] <greg-g> Hobbsee: I can try that, but I'm not hopeful considering everything I did last night
[00:39] <Hobbsee> greg-g: ahhh
[00:39]  * Hobbsee is unaware of what happened last night
[00:40] <dtchen_> greg-g: aptitude reinstall linux-image-$(uname -r)
[00:40] <dtchen_> or apt-get --reinstall install linux-image-$(uname -r)
[00:40] <greg-g> testing new sound modules built by dtchen_, involved rm -rf sound/ under lib/modules/2.6.28-11-generic
[00:40] <dtchen_> correction: /lib/modules/2.6.28-11-generic/kernel/
[00:41] <greg-g> right :)
[00:43] <Hobbsee> ahhh
[02:36] <dtchen> greg-g: ETA 7 mins
[02:39] <greg-g> dtchen: /me nods.
[02:44] <dtchen> greg-g: http://kernel.ubuntu.com/~dtchen/
[02:47] <greg-g> one sec, phone
[02:49] <greg-g> dtchen: just gotta dpkg it? no depmods or anything?
[02:50] <dtchen> correct
[02:50] <greg-g> cool.
[02:51] <dtchen> if you're curious, you're running http://kernel.ubuntu.com/git?p=dtchen/ubuntu-jaunty.git;a=shortlog;h=refs/heads/pcm
[02:55] <greg-g> wow, bleeding edge, 4 hours ago
[02:55] <greg-g> correction, 3.
[03:02] <greg-g> installed, restarting, testing.
[03:11] <greg-g> dtchen: dude, you're a rockstar, it isn't crashing under the same test circumstances I used before
[03:12] <dtchen> greg-g: ok, and this is with the shipped /etc/pulse/default.pa ?
[03:12] <dtchen> i.e., with glitch-free disabled (you'll see load-module module-hal-detect tsched=0)
[03:13] <greg-g> dtchen: correct.
[03:13] <dtchen> excellent.
[03:13] <dtchen> thanks very much for testing; i'll dent for more testers now
[03:13] <greg-g> yay!
[03:14] <greg-g> thank you very much for being on top of it.
[03:14] <tranceenergyUSA> how long it takes to configure it and how does the interface compare to windows xp
[03:15] <greg-g> not long, and better.
[03:16] <tranceenergyUSA> what about the hassle of not having standard tools
[03:19] <greg-g> tranceenergyUSA: that depends on the situation.
[03:20] <greg-g> tranceenergyUSA: also, a better channel for this discussion would be #ubuntu-us or your Local Community team's channel, but #ubuntu-us is fine for now.
[03:22] <tranceenergyUSA> cool
[03:22] <tranceenergyUSA> thanks
[03:22] <tranceenergyUSA> folks
[05:05] <CarlFK> python-twisted is already the newest version.
[05:05] <CarlFK> >>> import twisted
[05:05] <CarlFK> ImportError: No module named twisted
[05:06] <CarlFK> that happened after apt-get upgrade
[05:08] <jmarsden> CarlFK: Check the output of    dpkg -s python-twisted   # and also    dpkg -L python-twisted  # maybe?  Do they look sane?
[05:12] <CarlFK> jmarsden: http://dpaste.com/16801/
[05:12] <CarlFK> juser@cp333:~$ python -c "import sys;print sys.path"
[05:12] <CarlFK> ['', '/usr/lib/python26.zip', '/usr/lib/python2.6', '/usr/lib/python2.6/plat-linux2', '/usr/lib/python2.6/lib-tk', '/usr/lib/python2.6/lib-old', '/usr/lib/python2.6/lib-dynload', '/usr/lib/python2.6/dist-packages', '/var/lib/python-support/python2.6', '/usr/local/lib/python2.6/dist-packages']
[05:13] <jmarsden> Hmmm.... you've got a Python that only looks in explicitly "2.6" places for libraries?
[05:13] <CarlFK> seems that way
[05:15] <jmarsden> I wonder if you need some special python-twisted for 2.6??  I'm not expert enough on the recent/current python transition to 2.6 to help with that.
[05:17] <CarlFK> juser@cp333:/usr/lib/python2.6$ sudo ln -s /usr/lib/python2.5/site-packages/twisted
[05:18] <CarlFK> lets see how well that works out...
[05:18] <CarlFK> ImportError: No module named zope.interface
[05:18] <CarlFK> swell.
[05:22] <jmarsden> Sounds like the whole python transition think just "got" you somehow...
[05:23] <jmarsden> You could try asking in #ubuntu-motu in case there is someone there who really knows all about the python 2.6 transition and what state it is in...?
[05:23] <jmarsden> But it's not really a support channel...
[06:07] <dholbach> good morning
[06:15] <mrooney> dholbach: morning again :)
[06:15] <mrooney> about bed time for me
[06:15] <dholbach> hi mrooney
[06:21] <YoBoY> yo
[08:17] <dominiks> hey, im reading https://wiki.ubuntu.com/BugSquad/KnowledgeBase/Classes/Triaging right now.. and there is "Assigning bugs to the proper package." as one of the tasks for bug triaging
[08:21] <dominiks> how can I assign correct package to bug.. when I'm not member of Bug Control team please?
[08:26] <rww> dominiks: click the down arrow to the left of the entry in the "Affects" column in the table at the top of the report, then type the package name under "Package", or click "(Choose...)" for a search box. Fill out any other changes, then click "Save Changes". That works for me, and I'm not in the bugcontrol team.
[08:28] <dominiks> thanks :)
[08:29] <dominiks> i wasn't logged in Launchpad.. what a shame :p
[10:55] <Tuxist> hi
[10:56] <Tuxist> i have a problem with nfs and heimdal https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/343897
[10:56] <Tuxist> have anybody a solution for my problem ?
[10:58] <BUGabundo> Tuxist: from what I've read
[10:58] <BUGabundo> nfs is broken in many places
[10:59] <Tuxist> i can't mount keberos crypted volumes
[10:59] <sbeattie> Tuxist: with nfsv4 on linux, don't you have to set fsid in /etc/exports?
[10:59] <Tuxist> no
[10:59] <Tuxist> it's is recomment ?
[11:04] <Tuxist> i have set fsid=0 whis no change of my problem
[11:06] <sbeattie> are you able to get nfsv4 working without heimdal?
[11:07] <sbeattie> what mount command did you issue?
[11:07] <Tuxist> http://pastebin.com/m420e815c
[11:09] <sbeattie> if you do 'mount -t nfs4 -o rw,sec=krb5p nfs.wehrwolf.local: /home' manually, does that work?
[11:10] <Tuxist> http://pastebin.com/m519e05ac
[11:11] <Tuxist> same error
[11:12] <Tuxist> pam ldap runs perfect only problems with nfs
[11:12] <sbeattie> and you had set fsid=0 in /etc/exports for /export/users on the server side and restarted the nfs daemons?
[11:13] <sbeattie> does it work without encryption? i.e. does 'mount -t nfs4 -o rw nfs.wehrwolf.local: /home' work?
[11:13] <Tuxist> it runs now thanks
[11:14] <Tuxist> i have forgotten to restart nfs-common
[11:17] <sbeattie> well, bah, I was going to (a) congratulate Tuxist and (b) ask him/her to close the bug, since it's working.
[11:29] <Tuxist> same issue after restart
[11:33] <Tuxist> nfs and heimdal
[12:42] <sectech> Crap... an update broke my sound.
[12:43] <sectech> Have we been getting any pulseaudio issues within the last 24 hours?
[12:47] <BUGabundo> sectech: yes
[12:47] <BUGabundo> know prob
[12:47] <BUGabundo> I gets fixed and the next update breaks it
[12:47] <BUGabundo> dan has a kernel patch for 64bits on his kernel repo
[12:48] <sectech> Ahhh... ok...  <cancels report>
[12:48] <sectech> do you have a link?
[12:48] <sectech> I know quite a few Dans
[12:55] <sectech> was it an actual pulseaudio regression? I could always revert back to the previous version
[12:55] <BUGabundo> sectech: try https://bugs.launchpad.net/bugs/330814
[12:55] <BUGabundo> remember that not all audio bugs are dupes!
[12:56] <BUGabundo> sectech: I tried it after yesterday update
[12:56] <BUGabundo> without much luck!
[12:56] <sectech> I guess we can expect a lot of these report within the next little bit then
[12:57] <sectech> This is actually an intrepid system too
[12:58] <sectech> Lets see if this test kernel works
[13:03] <sectech> nopee...
[14:22] <sectech> Okay someone stating that a bug has been fixed in a future release is not really sufficient when the issue is in the current release.
[14:22] <sectech> It's great that the audio problem is fixed in Jaunty but intrepid is our current release and even if it wasn't it still is supported
[14:37] <Ampelbein> sectech: When something is fixed in jaunty and the fix is important: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure . If the bug is minor and a backport is possible: https://help.ubuntu.com/community/UbuntuBackports#request-new-packages
[14:47] <sectech> Ampelbein, I don't actually have the patch though, the triager just set it to fix released with just the explanation that it was fixed in jaunty.
[14:50] <Ampelbein> sectech: bug 330814?
[14:52] <sectech> Ahh there we go...that's the original one.
[15:44] <bddebian> Boo
[15:44] <BUGabundo> foo
[15:44] <dominiks> moo
[15:44] <thekorn_> bar
[15:46] <bddebian> :)
[15:52] <dominiks> BugSquad noob question: How to triag bug, which was resolved by his reporter himself please?
[15:53] <bdmurray> dominiks: was it a configuration issue or something else?
[15:53] <dominiks> bdmurray: yes
[15:54] <BUGabundo> oii
[15:54] <BUGabundo> bddebian: 4x ?
[15:54] <bdmurray> dominiks: in that case Invalid may be the best choice
[15:54] <bdmurray> You can check http://wiki.ubuntu.com/Bugs/Status for guidance
[15:54] <dominiks> bdmurray: ok, thanks a lot for help
[15:58] <dominiks> one more question.. after "invalidating" such bug.. it won't be googleable anymore right? in such case.. maybe it should go to FAQ's of some kind of knowledge base.. for other user's reference..
[15:59] <bddebian> BUGabundo: ?
[16:03] <greg-g> dominiks: what is the bug number?
[16:04] <dug_> could anyone mark this as high priority, was hoping it would be corrected before jaunty release, thanks: https://bugs.launchpad.net/ubuntu/+source/sun-java6/+bug/291135
[16:04] <dominiks> greg-g: https://bugs.launchpad.net/ubuntu/+bug/292805
[16:07] <greg-g> bdmurray: would something like that bug (misdetected keyboard by kernel) be something to report against the kernel? It seems that since there is that config option they know the issue fairly well and might not be able to work around it.
[16:08]  * greg-g goes to get lunch
[16:09] <dominiks> bdmurray: yes, you are right
[16:12] <BUGabundo> bddebian: you now have 3 echos!
[16:20] <bddebian> BUGabundo: Ah nice :)
[16:20] <BUGabundo> Pici: you are lucky that "newnick" is not taken eheh
[16:21] <Pici> BUGabundo: I was surprised
[16:27] <BUGabundo> Pici: actually freenode and other networks should have some nicks reserved for that very purpose
[17:19] <dominiks> Could somebody please set importance level to Wishlist for bug 345857? I wasn't able to do it myself... thanks.  https://bugs.launchpad.net/ubuntu/+bug/345857
[17:20] <BUGabundo> who can I nag for bug 268727?
[17:20] <BUGabundo> need it to fix bug 335507
[17:21] <sbeattie> dominiks: done, thanks.
[17:23] <dominiks> sbeattie: thank you
[18:02] <greg-g> BUG... grrr
[19:06] <bdmurray> mrooney: if you made a ppa of the patch for bug 310551 can you add a debdiff for sponsoring too?
[19:23] <mrooney> bdmurray: I can if you think it has value, although the commenter said he was going to patch debian and sync
[19:25] <bdmurray> mrooney: its up to you, he is the upstream developer so will probably get it done
[19:48] <dominiks> Could somebody please set importance level to Wishlist for bug 345175? I wasn't able to do it myself... thanks.
[19:49] <charlie-tca> done
[19:49] <charlie-tca> Thanks for helping, dominiks
[19:50] <dominiks> charlie-tca: thank you
[19:50] <charlie-tca> You are welcome
[19:59] <bdmurray> charlie-tca: it would have happened automatically
[20:00] <charlie-tca> yeah? I didn't know that was set up now.
[20:00] <bdmurray> charlie-tca: yes, if something is tagged needs-packaging it'll get wishlisted automatically
[20:00] <dominiks> oh.. i didn't know it either.. thanks for info
[20:01] <charlie-tca> Thanks for that info. Things just get better and better.
[21:26] <amishgandhi> hi
[21:26] <amishgandhi> I installed ubuntu 8.10 and am having a problem with internet download speed
[21:26] <amishgandhi> it is very slow
[21:29] <BUGabundo> amishgandhi: check ipv6 bug
[21:29] <BUGabundo> on launchpad
[21:29] <BUGabundo> for more help, please go to #ubuntu channel
[21:29] <BUGabundo> that is more oriented for user help
[21:29] <BUGabundo> thanks
[22:11] <paul_> anybody here with some c (and possibly lesstif) knowledge. I can prevent bug 124573 from happening (in nedit) but only by reversing an upstream patch of 4.5 years ago.
[22:13] <paul_> The issue is also upstream at https://sourceforge.net/tracker/index.php?func=detail&aid=1578451&group_id=8596&atid=108596 but upstream is nearly dead
[22:13] <dtchen> paul_: if you'll generate a patch, we can get it into jaunty.
[22:13] <paul_> the patch is rather small
[22:13] <paul_> it is in sourceforge
[22:13] <paul_> ^^
[22:13] <dtchen> sf is blocked here
[22:13] <paul_> but I am not sure it is really clean
[22:14] <paul_> wait a moment
[22:16] <dtchen> ok, i see it
[22:16] <dtchen> yay for horkarounds
[22:16] <dtchen> go ahead and submit it, please
[22:17] <paul_> I attached it to the bug report (bug 124573)
[22:18] <paul_> dtchen: can you have a look at it? Would appreciate some feedback.
[22:18] <dtchen> i will later tonight
[22:18] <paul_> ok, please comment in the bug tracker than, I am nearly going to bed.
[22:19] <dtchen> ok, ping me tomorrow if i haven't.
[22:19] <paul_> ok
[22:21] <paul_> just for your knowledge, I am also preparing a NMU for lesstif for Debian, solving some other issues as well
[22:21] <paul_> basically giving some love to lesstif
[22:22] <dtchen> great, syncs are good
[22:36] <barberio> Hi. Anyone else want to confirm that the latest builds of python2.6-minimal have been built without zlib?
[22:36] <barberio> At least, on Jaunty they have.
[22:38] <bdmurray> barberio: How could someone test that?
[22:39] <barberio> Check to see if something that runs against python2.6 fails because of lack of zlib support?
[22:42] <sbeattie> barberio: do you have a specific example? That would help.
[22:42] <barberio> https://bugs.launchpad.net/ubuntu/+source/python2.6/+bug/346123
[22:43] <barberio> deluge fails on start complaining about missing zlib. Poking around the python2.6 installed, it seems like there is no zlib support there.
[22:52] <bdmurray> sbeattie: are you testing it?
[22:57] <barberio> I *think* 2.6.1-1ubuntu3 was working fine, and had the expected zlib functions. Any way to compare the files that were in that package, with the ones in the current package, to see if there's obviously a missing ext or mod?
[22:57] <bdmurray> http://launchpadlibrarian.net/24106595/python2.6_2.6.1-1ubuntu3_2.6.1-1ubuntu4.diff.gz
[22:58] <bdmurray> from https://edge.launchpad.net/ubuntu/+source/python2.6
[23:00] <barberio> That's changes in the source, not changes in the product binary packages.
[23:01] <barberio> Ah. Luckily, I still have the apt cache file.
[23:04] <barberio> Nope. ubuntu3 lacks a zlib extention too.
[23:06] <thekorn> really? I've a fresh install from today here, deluged is working and python -c "import zlib" too
[23:07] <barberio> Which binary platform?
[23:08] <thekorn> barberio, i386
[23:09] <barberio> That's very odd.
[23:09]  * barberio checks around some more.
[23:09] <barberio> Okay, -c "import zlib" works out fine here too.
[23:10] <barberio> There must be something damaged in deluged.
[23:10] <thekorn> ok, python -c "import zlib; zlib.compress('boo')" is a better testcase
[23:17] <barberio> Let's try downgrading deluge...
[23:18] <barberio> And now it works
[23:19] <barberio> Now to work out why deluge was throwing errors that made it look like python didn't have zlib support.


[12:17] <rtg_> kylem: I have 3 that all load i2c_ec, but nonoe of them oops.
[12:17] <mjg59> On the vast majority of machines, i2c_ec will never bind
[12:17] <mjg59> So loading it is uninteresting
[12:21] <maks_> BenC we can easily write a blacklist dir in /dev/.initramfs
[12:22] <maks_> some m-i-t would need to pick that up
[12:28] <BenC> is i2c_ec autoloaded somehow?
[12:28] <rtg_> Yep.
[12:28] <rtg_> Well, maybe. I'm not sure.
[12:28] <rtg_> I think its a result of sms
[12:30] <rtg_> sms --> sbs
[01:08] <mjg59_> rtg_: Uh. http://git.kernel.org/?p=linux/kernel/git/bcollins/ubuntu-feisty.git;a=commitdiff;h=82580efcd0224a29a9bef1b4ce53f7a4d4611b09 is really, really not a good idea.
[01:09] <mjg59_> Oh, wait, hang on.
[01:09] <mjg59_> Sorry, I see what you were doing there.
[01:11] <maks_> BenC qemu test complain about not beeing able to write to ${rootmnt}/etc/modprobe.d/initramfs as ro mounted
[01:12] <maks_> can post the patch if you want
[01:12] <BenC> maks_: Ah, right, it's mounted ro until after the init scripts run fsck and such
[01:13] <BenC> so maybe there should be a dangling symlink for /etc/modprobe.d/initramfs-blacklist -> /some/tmpfs/initramfs-blacklist
[01:13] <BenC> initramfs could create /some/tmpfs/initramfs-blacklist
[01:14] <mjg59_> BenC: It looks astonishingly likely that db2f0f088a056c4ccf9054747169802db2f9ae9a is what broke the i2c_ec stuff
[01:14] <mjg59_> Any idea what dragged that in?
[01:15] <maks_> BenC currently we like to write usplash stuff into /dev/.initramfs so there could be the modprobe.d blacklist there
[01:15] <BenC> mjg59_: right, rtg found that out too...that got dragged in either by devres stuff, or to fix some other bug, but I can't recall which now
[01:16] <BenC> I should really edit cherry-picks as to why they got picked, especially ones like that
[01:16] <mjg59_> Well, just lose that line
[01:17] <BenC> we are still seeing a bug with HPA patch, even reverted back to original ABI breaking code
[01:17] <BenC> reverting it just covered up the ata_dev_same_device() failure
[01:17] <mjg59_> BenC: Well, that's not the fix that he committed
[01:18] <pkl_> BenC: is there a reason why c25cfc3ad3cb8cac3474febfe66cff8ee0bfba18a was applied reverting the tifm driver from 0.8 to 0.7?
[01:18] <BenC> mjg59_: I'll look at that in a second...if it works with the i2c change reverted, I can maybe get it in
[01:18] <BenC> I need to get HPA working
[01:18] <mjg59_> BenC: I can't guarantee that it works, and I recommend not reverting the entire thing
[01:18] <BenC> [   67.208231]  ata1.00: ata_hpa_resize 1: sectors = 234441648, hpa_sectors = -1342616656
[01:19] <mjg59_> Just change that one line
[01:19] <mjg59_> It certainly can't make anything worse
[01:19] <BenC> mjg59_: which line?
[01:19] <mjg59_> +       smbus->adapter.dev.parent = &device->dev;
[01:19] <mjg59_> Delete it
[01:19] <BenC> for i2c_ec?
[01:19] <mjg59_> Yes
[01:19] <BenC> Ok
[01:19] <mjg59_> You can't legally do that with the acpi in 2.6.20
[01:20] <BenC> mjg59_: back to HPA, there seems to be some 64-bit issue with the lba to sectors code
[01:20] <BenC> I can see it on my xeon now
[01:20] <BenC> I need to check the values in that function
[01:21] <mjg59_> Ok
[01:21] <mjg59_> I'm unlikely to have a 64-bit install done in time to help you
[01:23] <BenC> mjg59_: be around for general poking if I find anything?
[01:24] <BenC> now that I can reproduce it, I can at least find out where it's coming from, but if I get any ata questions, I'm at a loss for quick answers
[01:29] <mjg59_> Yup
[01:36] <BenC>         printk("%02x %02x %02x %02x %02x %02x: %016llx \n",
[01:36] <BenC>                tf->hob_lbah, tf->hob_lbam, tf->hob_lbal,
[01:36] <BenC>                tf->lbah, tf->lbam, tf->lbal, sectors);
[01:37] <BenC> [   67.124009]  f9 4b af f9 4b af: ffffffffaff94baf
[01:37] <BenC> prints that
[01:37] <BenC> that can't be right
[01:37] <BenC> this is what gets printed for another drive
[01:37] <BenC> [   67.112044]  00 00 00 f9 4b af:<PHONE_NUMBER>f94baf
[01:37] <BenC> the f94baf looks awful familiar :/
[01:46] <BenC> the first read is from ata_read_native_max_address_ext()
[01:46] <BenC> the second is from the return value of ata_set_native_max_address_ext()
[01:47] <BenC> I think I see the problem with this
[02:15] <cjwatson> BenC: what's the status? I see scrollback ...
[02:30] <BenC> cjwatson: things are working, I just have a slight problem of 64-bit ness it seems
[02:31] <BenC> cjwatson: it's a problem I can reproduce so just a matter of figuring out the thinko that is hiding in here somewhere
[02:32] <cjwatson> ok, I'm going to doze here,
[02:32] <cjwatson> if you phone my landline it stands some chance of waking me up
[02:32] <BenC> cjwatson: Ok, elmo said he'd be around to process an upload, unless you prefer I contact you
[02:34] <cjwatson> use me as a first resort and elmo as a backup, please
[02:44] <BenC> cjwatson: will do
[04:07] <jml> t.
[04:07] <jml> (sorry, ultra-tappy touchpad)
[06:19] <defendguin> hey how do i mount the mmc device?
[06:35] <defendguin> now my mmc card wont work in -12 and it used to and my camera doesn't connect as a mass storage device
[06:38] <Mithrandir> defendguin: please try the absolute latest kernel, it should fix it.
[06:38] <defendguin> Mithrandir: what is the latest? -14?
[06:38] <defendguin> or did they release something else with the mmc fix?
[06:40] <fabbione> defendguin: yes. about 8 hours ago and should be in the archive.ubuntu.com as we speak
[06:40] <fabbione> probably the mirrors didn't catch it up yet
[06:40] <Mithrandir> <IP_ADDRESS>.12
[06:40] <defendguin> ahh i see it in update
[06:40] <defendguin> 2.6.20-14.23
[06:41] <defendguin> i hope that fixes the issue with the camera too
[06:50] <defendguin> doesn't look like it is working
[06:51] <defendguin> how can i tell that im in .23?   it just says generic
[06:51] <Mithrandir> make sure uname -a says 2.6.20-14-generic
[06:52] <defendguin> Linux houston 2.6.20-14-generic #2 SMP Thu Apr 12 22:53:19 UTC 2007 i686 GNU/Linux
[06:52] <Mithrandir> and neither your camera (which I presume is mass-storage) nor your mmc reader works correctly?
[06:53] <defendguin> correct
[06:55] <defendguin> it is most probably mass storage but i can't guarantee that
[06:57] <defendguin> i wish i had gotten a chance to test this fix out a few days ago
[06:58] <Mithrandir> I think it's too late to fix this now, we might be able to do it in a post-release update
[07:02] <defendguin> Mithrandir: i really need to mount this disk
[07:03] <defendguin> i used to remember my fstab stuff but its been so long since i needed to
[07:08] <defendguin> what sucks is that it used to work in -12 but now that doesn't even work
[07:12] <cjwatson> BenC: this isn't sounding good. What's up?
[07:21] <Mithrandir> what breaks if we just blacklist that i2c-ec driver?
[07:23] <Mithrandir> hm, the smart battery module breaks then..
[07:27] <Mithrandir> ugh, it's 1:30 for Ben, a bit on the late side to call him.
[07:45] <fabbione> i don't think he will mind too much if you call him
[07:45] <fabbione> probably the wife will mind more
[08:09] <Mithrandir> I've sent him an SMS and will send him an email too, hopefully he'll see either if he's up
[12:07] <mc44> the new kernel seems to be broken for me
[12:07] <mc44> should I file a bug?
[12:07] <Mithrandir> no
[12:08] <Mithrandir> there are about five hundred zillion dupes filed already
[12:08] <mc44> haha
[12:08] <mc44> ok sorry
[01:38] <Mithrandir> the SD/MMC reader on my x40 seems to work again, at least.
[01:53] <Keybuk> I've yet to find a use for the SD/MMC reader
[01:54] <Keybuk> since every single device I own has a different profile card
[01:54] <Mithrandir> I wish I had a CF reader instead.  SD is one of the few I actually don't have.
[01:55] <zdzichuBG> so I must be lucky. card reader in my z61t is compatibile with my sistet's Minolta camera
[01:55] <Keybuk> the 770 takes a little card that's half the size of the cards the N800 takes
[01:55] <Mithrandir> zdzichuBG: my camera uses CF cards, since it's a tad more expensive than the cheap ones you can get.
[01:56] <Mithrandir> at least I don't know of any prosumer DSLRs which use !CF.
[01:56] <Keybuk> successive sony phones have left me with a small pile of Memory Stick Duo, Memory Stick Pro Duo and now Scandisk M2 cards
[01:56] <Keybuk> none of which fit in any other device
[01:56] <Mithrandir> yes, I have MS Pro Duo as well, for my old camera.
[01:57] <Mithrandir> it's easier just to chuck a 250-thousand-different-kinds-of-cards reader in the bag and use that
[01:57] <Keybuk> I just use bluetooth
[01:57] <Keybuk> or USB
[03:01] <JanC> Mithrandir: 1000-in-1 usb card readers are cheap  :)
[03:01] <Mithrandir> they cost about 2.5 cents, so yes.
[03:05] <JanC> I don't understand why they don't just cram one of these in laptops instead of all those things that need special drivers
[03:06] <JanC> would probably be easier to support for manufacturers too
[03:35] <mjg59_> Keybuk: The ones in the N70 (RSMMC) are electrically compatible with MMC and SD
[03:35] <mjg59_> There's a little adapter that clips on
[03:36] <Keybuk> N70?
[03:36] <Keybuk> don't have one of those
[03:36] <Keybuk> I have a 770 and N800
[03:36] <mjg59_> 770, rather
[03:36] <Keybuk> the ones in the N800 are bigger versions of the ones in the 770, right?
[03:39] <mjg59_> The N800 comes with SD, not MMC
[03:39] <mjg59_> SD readers can read MMC, but not vice-versa
[03:44] <BenC> zul: ping
[03:44] <zul> BenC: pong
[03:44] <zul> whats up
[03:44] <BenC> zul: are you able to do anything with openvz? I sort of need to give Malc a heads up on what may or may not happen
[03:45] <zul> yeah I have x86 kind of working kind of broken on amd64
[03:45] <zul> I keep timing out when Im trying to upload it with dput
[03:45] <BenC> IMO, just apply the patches and getting it building if you can
[03:45] <BenC> let them worry about whether it works or not
[03:45] <zul> sure..
[03:46] <BenC> zul: could you reply to the email they sent?
[03:46] <zul> sure
[03:47] <BenC> zul: great thanks. I know you got a lot of other things going on more important, I'm just trying to follow up and make sure the communication doesn't go stale
[03:47] <zul> not a problem, thanks
[03:48] <zul> done
[03:49] <zul> Ill try to upload the kernel to the archive again
[03:50] <zul> and get the userland stuff uploaded at lunch
[04:19] <Keybuk> mjg59_: all I remember is that I tried to put the 770 card into my laptop
[04:19] <Keybuk> and couldn't get it out for weeks
[04:21] <mjg59_> Yes. You need the clip-on adapter.
[04:22] <kylem> wtf, could not resolve us.archive.ubuntu.com
[04:24] <Keybuk> I don't think I got an adapter
[04:24] <Keybuk> the M2 thing in the W880i is damned nifty though
[04:24] <Keybuk> it's 1GB and smaller than a thumb-nail
[04:28] <mjg59_> Keybuk: The 770 ships with the card in an adapter
[04:28] <mjg59_> You have to unclip it before you can put it in the machine
[04:28] <Keybuk> oh
[04:28] <Keybuk> wonder where I put that then
[04:29] <Keybuk> probably threw it away :)
[04:37] <gnomefreak> Keybuk: thank you for the n-m fix it worked great :)
[04:41] <EtienneG> hey guys ... I'm getting 403 Forbidden when trying to install linux-image-2.6.20-14-generic
[04:42] <EtienneG> before I look for someone to bug, am I th eonly one that noticed this ?
[04:42] <stgraber> EtienneG: this kernel is buggy, so the access is currently blocked
[04:43] <EtienneG> ha, ok then
[04:43] <stgraber> EtienneG: some people have crash with it another one is being built at the moment
[04:43] <EtienneG> thanks for the info, I'll be waiting for the next upload
[05:06] <zul> BenC: ping bu
[05:06] <zul> er... openvz-kernel-2.6.20_2.6.20-1_source.changes is NEW
[05:51] <BenC> mjg59, kylem: We need to figure out the correct fix for this
[05:51] <mjg59> Yes.
[05:51] <BenC> I'm leaning toward just not doing hpa if the driver is sata_nv...if it's even possible to do that check
[05:52] <mjg59> Not trivially.
[05:52] <mjg59> What other code paths are there that execute ata_exec_internal?
[05:53] <mjg59> Ah, hang on. Alan at one point suggested doing the resizing after the drive/controller timing had been set up.
[05:53] <mjg59> Can you move the call to...
[05:53] <mjg59> (Let me find this)
[05:53] <BenC> let me check...
[05:54] <BenC> we should do this for ATAPI, right?
[05:54] <mjg59> Ok, after the call to ata_set_mode() in ata_eh_recover()
[05:54] <mjg59> No, ATAPI isn't a problem
[05:54] <kylem> no.
[05:55] <mjg59> Or, rather, I don't think ATAPI devices can implement HPAs
[05:55] <kylem> doing HPA on ATAPI devices is illegal.
[05:55] <BenC> they should report no hpa support though right?
[05:55] <kylem> it won't claim ata_id_hpa_enabled
[05:55] <kylem> right
[05:55] <BenC> right
[05:55] <kylem> - Mandatory when the Host Protected Area feature set and the 48-bit Address feature set are
[05:55] <kylem>   implemented.
[05:55] <kylem> - Use prohibited when the Removable Media feature set is implemented.
[05:55] <kylem> - Use prohibited when PACKET Command feature set is implemented.
[05:55] <mjg59> kylem: Can you give that a go?
[05:56] <BenC> let me try mjg59's suggestion
[05:56] <mjg59> There's two codepaths where ata_set_mode() gets called, depending on whether the eh code is in use or not
[05:56] <mjg59> It may need adding to both
[05:57] <mjg59> Actually, yeah, it needs adding to both (if it works)
[05:57] <mjg59> But I guess we'll find out
[05:57] <kylem> mjg59, i've moved it somewhere myself trying.
[05:57] <BenC> mjg59: maybe put it in ata_set_mode?
[05:57] <mjg59> BenC: Could do, but no real need
[05:58] <mjg59> It's trivial to add to both
[05:58] <kylem> trying.
[06:00] <BenC> recompiling
[06:00] <kylem> worked.
[06:00] <kylem> mjg59, didn't fail that time.
[06:01] <kylem> ah. didn't fail because it didn't execute, fun.
[06:02] <kylem> ohhhh. hmm. maybe because hpa_id_enabled wasn't true there.
[06:02] <mjg59> kylem: Where did you add it?
[06:02] <kylem> mjg59, after ata_set_mode in bus_probe.
[06:03] <mjg59> kylem: That won't be executed if there's an error handler
[06:03] <mjg59> Put it in ata_eh_recover()
[06:03] <BenC> I've put it in both places, rebooting
[06:05] <BenC> boots
[06:05] <kylem> i still think we should add an avoid_all_hpa_code flag.
[06:05] <mjg59> Does it execute?
[06:05] <BenC> but I want to put a printk back in there to make sure it is getting called
[06:05] <BenC> kylem: I changed the ignore_hpa=0 to actually do that
[06:05] <kylem> at least that way, we don't brownpaperbag the pressed cds completley and utterly.
[06:06] <kylem> ok.
[06:06] <mjg59> I can sort of understand sata_nv getting upset if you're executing ata commands before actually making sure the disk and controller timings agree
[06:09] <BenC> it's not getting called
[06:09] <BenC> let me post my diff
[06:11] <BenC> people.ubuntu.com/~bcollins/libata.diff
[06:12] <BenC> I'm thinking about moving the checks for (ata_ignore_hpa && ata_id_hpa_enabled(dev->id) to the top of ata_hpa_resize to clean things up a bit
[06:13] <mjg59> Would also work
[06:13] <kylem> ok.
[06:13] <mjg59> BenC: It's not obvious why it's not getting called. You rebuilt the initramfs as well, right?
[06:13] <kylem> i have an idea.
[06:13] <kylem> we buy everyone scsi disks.
[06:13] <kylem> and pretend ATA doesn't exist. :)
[06:13] <BenC> yes
[06:18] <kylem> ergh.
[06:19] <kylem> ok.
[06:19] <kylem> i think ata_dev_revalidate is the right place to put it.
[06:19] <kylem> since it's called from both the _eh and bus_probe paths.
[06:20] <mjg59> After set_mode?
[06:21] <cjwatson> BenC: (is that another ABI bump, BTW?)
[06:21] <BenC> ok, it's getting called now
[06:21] <BenC> cjwatson: No
[06:21] <cjwatson> ok, just checkin'
[06:21] <cjwatson> I'm not going to say no if that's what it takes
[06:22] <mjg59> BenC: Getting called and breaking?
[06:22] <BenC> mjg59: I need to check that it is actually going down the code path
[06:23] <mjg59> Ok
[06:23] <BenC> but the function got called
[06:25] <notts> sorry to jump in, but there a major bug with the new updated kernel this morning
[06:26] <notts> got error message: error loading os"
[06:26] <mjg59> notts: Yes, it's broken for various people
[06:26] <mjg59> It's being worked on
[06:28] <kylem> hey hey.
[06:28] <kylem> garzik to the rescue.
[06:28] <notts> major thanks, any word on when
[06:30] <mjg59> When it works
[06:32] <kylem> WOOOOOO
[06:32] <kylem> I WIN
[06:32] <rpereira> hi everybody.
[06:33] <BenC> mjg59: neither of my drives says they support hpa when ata_resize_hpa() is called
[06:33] <kylem> BenC, boot with sata_nv.adma=0
[06:33] <BenC> kylem: with old patch?
[06:33] <kylem> ata4.00: ata_hpa_resize 1: sectors = 390721968, hpa_sectors = 390721968
[06:33] <mjg59> BenC: Hm. Odd.
[06:33] <kylem> BenC, yeah
[06:34] <kylem> want my defconfig'd kernel instead of rebuilding?
[06:34] <mjg59> kylem: Figures.
[06:34] <kylem> yes.
[06:34] <kylem> fuck nvidia.
[06:34] <kylem> right in the skull.
[06:34] <BenC> it doesn't take me long to rebuild libata.ko
[06:34] <kylem> ok.
[06:34] <BenC> kylem: so should we disable adma by default?
[06:34] <kylem> i think so.
[06:34] <mjg59> Fine. Dropping adma just costs us ncq
[06:34] <mjg59> But it's clearly broken in some respect
[06:35] <BenC> kylem: can you do a patch for that, and I'll include a patch so that ignore_hpa steers clear of all hpa code?
[06:36] <BenC> email it to me and I'll test it and prepare a -15.25
[06:36] <kylem> 1sec, trying to figure out if we can shortcircuit adma mode so we can leave it on.
[06:36] <BenC> kylem: just default the module param to 0 :)
[06:36] <BenC> if people want it they can enable it manually
[06:36] <kylem> NCQ is fairly hit or miss too.
[06:37] <BenC> do you think making module parm adma=0 by default is enough?
[06:37] <kylem> yes.
[06:37] <BenC> if that's all that's needed I can do that locally
[06:37] <kylem> ok.
[06:38] <kylem> it's static int adma_enabled
[06:38] <BenC> ok, I'll rebuild a kernel and see if danielk is still around to test
[06:38] <cjwatson> any idea when sata_nv.adma was turned on?
[06:38] <kylem> cjwatson, recently.
[06:38] <cjwatson> nod
[06:39] <kylem> commit 382a6652e91b34d5480cfc0ed840c196650493d4
[06:39] <kylem> Author: Robert Hancock<EMAIL_ADDRESS>[06:39] <kylem> Date:   Mon Feb 5 16:26:02 2007 -0800
[06:39] <kylem>     sata_nv: use ADMA for NODATA commands
[06:39] <kylem> turning it off wholesale is fine for now. i'll look into a real fix when we have some idle cycles.
[06:39] <cjwatson> hmm, git-blame says 2006-10-27
[06:39] <cjwatson> oh, it's only one bit of adma?
[06:40] <kylem> yeah.
[06:40] <kylem> basically instead of transitioning from adma mode to normal mode, they decided to submit NODATA with ADMA.
[06:41] <cjwatson> git log drivers/ata/sata_nv.c doesn't show the commit above?
[06:41] <cjwatson> (just trying to find it)
[06:41] <kylem> probably came in one of our imports
[06:41] <BenC> it was a chunk patch to sync with libata
[06:41] <cjwatson> $ git diff-tree -p 382a6652e91b34d5480cfc0ed840c196650493d4
[06:41] <cjwatson> fatal: bad object 382a6652e91b34d5480cfc0ed840c196650493d4
[06:41] <cjwatson> ah
[06:41] <BenC> cjwatson: git-diff-tree -p --pretty SHA
[06:41] <kylem> cjwatson, git show
[06:41] <BenC> cjwatson: ah, you don't have upstream in there
[06:42] <BenC> should we just revert that one patch?
[06:42] <cjwatson> ah, I have a different tree for that
[06:42] <kylem> BenC, testing.
[06:42] <BenC> if we can leave adma on for default transactions we can avoid the "my driver performance sucks" crew
[06:42] <kylem> yup.
[06:42] <kylem> reverts cleanly, testing now.
[06:43] <cjwatson> it does say it fixed some timeouts ...
[06:43] <kylem> boots.
[06:43] <cjwatson> oh, no, maybe not
[06:43] <kylem> yeah, the language is murky.
[06:44] <BenC> cjwatson: it fixes some previously fixed ones in a different way
[06:44] <BenC> from the sound of it
[06:44] <mjg59> Well, worst case is that we revert back to edgy levels of support for that hardware
[06:44] <cjwatson> mm
[06:44] <cjwatson> can we bonnie++ the resulting system or something? :)
[06:44] <mjg59> BenC: The i2c_ec patch went in, right?
[06:45] <kylem> NCQ isn't always a win.
[06:45] <BenC> kylem: so reverting that patch with current code works?
[06:45] <cjwatson> bit concerned that just booting might be a weak test there
[06:45] <BenC> mjg59: yes
[06:45] <mjg59> Excellent, thanks
[06:45] <cjwatson> (I don't care about performance, more that it doesn't fall over under load)
[06:45] <kylem> BenC, yes in my testing tree (which is .21-rc6) building ubuntu images now
[06:45] <cjwatson> mjg59: anything else you know about?
[06:45] <cjwatson> of the release-critical ohmygod kind
[06:45] <mjg59> Nothing from me
[06:46] <cjwatson> I thought it might be worth an explicit check :)
[06:46] <cjwatson> thanks
[06:46] <mjg59> Yeah, I forgot about that one because it got downgraded to medium for some reason
[06:47] <mjg59> Basic problem was just that something we'd ended up pulling in expected the ACPI device semantics from 2.6.21
[06:47] <cjwatson> it was critical when I first saw it
[06:47] <mjg59> I bumped it back up yesterday
[06:47] <cjwatson> kylem: can you arrange for as many people on the team as possible who use sata_nv to try this out?
[06:48] <kylem> cjwatson, just ping them in #c?
[06:48] <kylem> or check the hw db?
[06:50] <cjwatson> #c, #distro, distro-team@
[06:50] <kylem> yup.
[06:51] <BenC> I'll have kernels built with this in about 30 minutes
[06:51] <BenC> i386 and amd64
[06:52] <kylem> ok
[06:55] <kylem> BenC, this should be a suitably large hammer for now. I'm going to try and snoop the taskfile and unset ADMA for these commands and submit the patch upstream when i get a bit of free time.
[06:55] <BenC> kylem: ok
[06:56] <BenC> kylem, mjg59: thanks for the time...maybe we get a suitable kernel for release
[06:56] <kylem> heh
[06:57] <BenC> at least -15.24 is almost done building to free up the buildd's
[06:58] <BenC> builds started
[06:59] <cjwatson> let me know when it's ready (by whatever means necessary) and I'll contact Tollef if he isn't around
[06:59] <cjwatson> so we can make sure it builds on palmer again
[07:08] <BenC> is palmer the faster machine?
[07:10] <kylem> BenC, patch hitting your mailbox.
[07:10] <kylem> alternate fix, reverting that commit is fine too though.
[07:11] <BenC> I've already got the revert in here and building/preparing :)
[07:11] <kylem> beauty.
[07:12] <kylem> i fired the fix upstream since it was so simple to filter.
[07:12] <BenC> kylem: your fix will filter into gutsy, so for feisty we'll stick with edgy type performance
[07:14] <kylem> BenC, worst case scenario is we fix it right in -updates, with this, everyone should be able to at least boot.
[07:16] <cjwatson> sounds like the right decision
[07:17] <kylem> with ben's ignore_hpa patch, if this crops up in another controller we aren't able to test on, we should can at least tell them to disable it to get it installed.
[07:17] <kylem> but from a cursory glance, i don't think it will be.
[07:31] <lfittl> kvm, seems broken (kvm-api-9 dependency can't be fulfilled), any time when this will be fixed?
[07:33] <cjwatson> somebody oughta fix that, I agree; is it just a rebuild?
[07:39] <cjwatson> * refs/heads/Ubuntu-2.6.20-12.20: fast forward to branch 'Ubuntu-2.6.20-12.20' of git+ssh://rookery/srv/kernel-team/private/ubuntu-feisty old..new: 3ffd70d..3ffd70d
[07:39] <cjwatson> error: Ref refs/heads/Ubuntu-2.6.20-12.20 is at 3ffd70ddba9d846eefd2d201404ad4c8a99d2899 but expected d02602542ef5ceb2af1765a179a9af6224136afe
[07:39] <cjwatson> does anyone know what I'm supposed to do about that?
[07:47] <rtg_> cjwatson: I just edited .git/refs/heads/Ubuntu-2.6.20-12.20 and made it d02602542ef5ceb2af1765a179a9af6224136afe. It was happy after that.
[07:48] <cjwatson> huh :-)
[07:49] <cjwatson> nope, two git pulls later and it's unhappy again
[07:54] <rtg_> cjwatson: Yeah, it does it to me too. Serious git training is something I'm going to extract from Ben and Kyle at UDS so I can understand some of these bizarre problems.
[07:55] <kylem> we could do a git bootcamp at uds if you wish? i could make slides
[07:55] <rtg_> Man, I would hug you for that, but it might wig you out :)
[07:56] <kylem> haha.
[07:56] <cjwatson> bootcamp> I'd like that, if I have any time
[07:56] <kylem> i suspect a few other people in the company would like it too
[07:56] <kylem> i'd like someone to give me a bzr boot-to-the-head heh
[07:56] <kylem> cjwatson, are any of our bzr team coming?
[07:57] <cjwatson> not sure, but plenty of distro are very capable with bz
[07:57] <cjwatson> r
[08:14] <zul> bug or annoy?
[08:56] <PhinnFort> where can I find a list/download the patches that are applied against the ubuntu kernel?
[08:57] <PhinnFort> i'm especially interested in the usplash patch
[09:08] <PhinnFort> :S
[09:15] <cjwatson> that's one of the things the "u" stands for, yes :-)
[09:19] <PhinnFort> :D
[09:19] <PhinnFort> that means I won't have to worry about ck stepping on other patches' toes
[10:10] <nott2> have they up loaded the new fix for kernel 2.6.20-14 ?
[10:25] <cjwatson> 21:10 <cjwatson> -15.24 is in the archive and built everywhere
[10:25] <cjwatson> 21:11 <cjwatson> except possibly ia64, and if not that's on its way
[10:25] <cjwatson> 21:11 <cjwatson> -15.24 should work for everyone except people using sata_nv
[10:25] <cjwatson> 21:11 <cjwatson> for sata_nv, -15.25 has been uploaded
[10:25] <cjwatson> 21:11 <cjwatson> but it has not yet built
[10:25] <cjwatson> 21:11 <cjwatson> (in progress, hamsters running as fast as they can)
[10:25] <cjwatson> 21:12 <cjwatson> so sata_nv users should stay on -13 until -15.25 is available, and everyone else should use -15.24
[10:25] <cjwatson> 21:12 <cjwatson> and REPORT REGRESSIONS ASAP
[10:25] <cjwatson> nott2: ^--
[11:12] <nott2> cjwatson: so the new kernel is uploaded ?
[11:13] <nott2> got a error "403" from the website when trying to update about hour ago....
[11:17] <nott2> just try to get a update, nothing YET....


[03:04] <set_> What are some reasons why my website would only show on my network and not be live on the WWW?
[03:08] <tomreyn> firewall, port forwarding, routing, public domain name, authoritative DNS records, public ip addresses.
[03:12] <set_> Dang.
[03:12] <set_> I used port forwarding.
[03:13] <set_> I have a cname and an A record.
[03:15] <set_> Is port forwarding incorrect for a server or should I have used dynamic DHCP?
[03:16] <set_> I am using apache2, Ubuntu Server, and a couple files for security (https).
[03:26] <tomreyn> set_: it's a bit difficult to tell without further information on your network architecture and on how users are supposed to access.
[03:27] <tomreyn> is this an organozation environment, a home user setup, do you have a static ip address (or multiple)?
[03:34] <set_> Oh.
[03:35] <set_> I am using this server as a home server for website traffic.
[03:35] <set_> I have one IP Address for my machine (for now). I do not think it is a static ip address yet.
[03:47] <tomreyn> set_: then you probably have a home router, which you need to configure to do port forwarding for tcp port 80 and 443. and you'll need to use "dyndns" (offered by multiple companies, some offers are free, such as https://afraid.org)  to make your website constantly reachable from the internet.
[03:47] <tomreyn> this is more complicated than i have time to explain now. you will need to look this up more, something like "how to host ubuntu webserver from home"
[03:51] <set_> Okay.
[03:51] <set_> Thank you for your support.
[20:02] <AvidWolf43> hey everyone
[20:02] <AvidWolf43> I am having a hell of a time trying to get landscape to work with azure using landscape quickstart. Can anyone assist?
[20:21] <tomreyn> AvidWolf43: this is not a "no", but note that IRC is usually just volunteer support, and today is a national holiday in many christianity influenced countries
[20:24] <AvidWolf43> thanks tomreyn I'm aware its volunteer support, I chime in and help when I can. I am also aware yesterday was easter in my part of the world, and that some businesses are closed today observing the holy holiday, just wanted to see if anyone who is not religiously observant and has any exp dealing with landscape is available to chime in
[20:25] <teward> well are you trying to get landscape server working or landscape client?
[20:25] <teward> server is hard, client is easy :p
[20:25] <AvidWolf43> server :(
[20:25] <AvidWolf43> i can access it locally with links browser
[20:26] <AvidWolf43> I think its more an azure dns redirect issue
[20:26] <teward> sounds about right, or their default firewalls
[20:26] <teward> if you can't access it from the outside it's either DNS or firewall usually
[20:26] <AvidWolf43> i can access via ip addr externally if I append /account/standalone/standalone-settings
[20:27] <AvidWolf43> actually scratch that
[20:27] <AvidWolf43> i can access via ip addr externally if I /append new-standalone-user
[20:27] <AvidWolf43> if I try to navigate to standalone-settings, thats when I get a redirect to a long azure internal dns
[20:28] <AvidWolf43> and i created a new network resource group for this allowing 80, 443 so it should be ok


[13:26] <jarnos> I want to build a source package for my ppa, but debuild -S fails, because there is no secret key for the email I gave in changelog. How to add such a key?
[13:28] <jarnos> Can I use the ssh key I have given in my Launchpad profile.
[13:30] <cjwatson> debuild/debsign requires a gpg key, not an ssh key
[13:31] <cjwatson> https://help.launchpad.net/YourAccount/ImportingYourPGPKey
[13:32] <cjwatson> (includes advice on creating gpg keys too)
[20:15] <mwhudson> omg pandas migrated
[20:18] <jarnos> cjwatson, as for the Launchpade help page, I don't know which is the Passwords and Encryption Keys tool, but I have seahorse installed and that has somewhat different kind of UI.
[20:18] <jarnos> cjwatson, this seems to be an old issue https://askubuntu.com/q/161595/21005
[20:25] <jarnos> cjwatson, so I created a PGP key pair using seahorse. I am using Xubuntu 18.04. The hkp://keyserver.ubuntu.com has not been added there, but there are couple of other. Should I use that "Hockeypuck" server for Launchpad? Is that a HTTP key server or should I use Custom type?
[20:37] <jarnos> There I have to choose a port, too.
[21:06] <jarnos> cjwatson, Also the output of gpg --list-keys has changed so that the page is out of date.
[23:18] <cjwatson> jarnos: Sending your key to the hockeypuck server at keyserver.ubuntu.com is correct.  As far as I know seahorse is the same as the Passwords and Encryption Keys tool, but different desktop environments may call it something slightly different and I expect there are some variations in its UI between desktop environments and versions.
[23:18] <cjwatson> jarnos: gpg --list-keys will differ in some aspects, but nothing particularly important.
[23:23] <jarnos> cjwatson, the key id is not shown, but fingerprint on a separate line. But that can be used as the argument for --send-keys.
[23:23] <cjwatson> Sounds like you've worked it out
[23:41] <jarnos> cjwatson, yes. I uploaded the package by default method; if I set sftp there was an error when running dput: paramiko must be installed to use sftp transport. It was too complicated, but I guess the default method will do.


[06:14] <andrejz> Hi!
[06:14] <andrejz> when trying to compile a pdf for precise-e2 i get the following error
[06:14] <andrejz> ! LaTeX Error: Missing \begin{document}.  See the LaTeX manual or LaTeX Companion for explanation. Type  H <return>  for immediate help.  ...                                                                                l.1591 \DeclareTextCommand[\textBeam}{P                                        U}{\9043\223}%* U+2393 ?
[06:15] <andrejz> this also happens in english version


[04:24] <megawattz>  can someone help i tried to install ubuntu 12.04 LTS 32bit but everytime it loads to install i get a black screen
[10:31] <mssmss> hi .. looing for some help on edubuntu client display problems...
[10:31] <mssmss> looking ..
[11:17] <mssmss> Hi can anyone help me ltsp client widescreen display issues ?
[12:47] <mssmss> Hi can anyone help me ltsp client widescreen display issues ?


[12:39] <BenC> damnit, ppc failed to build
[05:51] <infinity> BenC : Still around?
[06:05] <jianggw>  http://ubuntuforums.org/attachment.php?attachmentid=3590&d=1132034495 is a structure chart of community drawn by me.Is it correct?
[06:07] <jianggw> in the webpage http://www.ubuntulinux.org/community/processes/council,it wrote:The Chairman of the Community Council is yet to be determined.Isn't sabdfl the chairman?
[06:12] <infinity> Ouch.  I had a PPC buildd still churning on the -1.1 kernel build... With a 50 gig log file.
[06:26] <infinity> BenC : ^^^
[06:27] <infinity> BenC : Same thing on two ia64 buildds, with -1.1 and -2.2... Stuck in config loops.
[06:46] <fabbione> morning
[11:49] <maks_> zul: your blog isn't syndicated on planet.u.c??
[11:54] <janimo> any easy (bandwidth-wise too) way of switchung to vanilla linus branch inside the ubuntu git tree?
[11:55] <janimo> current ubu kernel doesn;t boot and I want to see if it's same with upstream
[01:36] <BenC> infinity: wow, I knew they would hang in the config, but I didn't think it would do some weird loop and fill the log file
[01:39] <doko> BenC, do you already build the kernel with 4.0?
[01:39] <janimo> BenC, is there an easy way to switch the ubuntu git  tree to a vanilla one without excessive downloading?
[01:40] <janimo> I'd like to see if vanilla fails to boot as well
[01:40] <janimo> if not I'll probbaly dl from kernel.org
[01:46] <jbailey> BenC: Side effect of no tty?
[02:13] <zul> gday
[02:13] <BenC> doko: these kernels are built with gcc-4.0
[02:13] <BenC> janimo: not really
[02:14] <janimo> thanks, I'll use kernel.org then
[02:14] <BenC> janimo: there is one way to help
[02:14] <BenC> but it's hard to explain
[02:15] <BenC> repo's can share the .git/objects directory
[02:15] <doko> BenC: hmm, svenl did claim that the 64bit kernel cannot be built, see #336167
[02:15] <BenC> doko: it built for me
[02:15] <janimo> BenC, thanks, I guess I'll just go tar.gz since git repos take up a _lot_ of space too
[02:15] <doko> anyway, it's a svenl report
[02:16] <BenC> maybe they did something to work around it in 2.6.15
[02:16] <BenC> hehe, very true
[02:16] <janimo> basically I have a softlock on boot on a HP laptop and want to track it down
[02:16] <janimo> will send feedback as I progress
[02:16] <BenC> janimo: that's why all my repo's share the objects, reduces space
[02:16] <janimo> why doesn't git do that by default since objects are immutable?
[02:16] <BenC> janimo: regression between breezy and dapper kernel?
[02:16] <janimo> yes, 12 works 15 nope
[02:17] <BenC> janimo: there's probably a way to do the clone and tell it to use something else for the shared objects
[02:17] <janimo> break in some acpi list setup
[02:17] <BenC> janimo: ah, ok
[02:17] <janimo> ok I'll read up the horribly detailed git docs
[02:18] <janimo> bbl
[02:33] <BenC> jbailey: ping
[02:34] <jbailey> BenC: pong
[02:35] <BenC> jbailey: do you have a G5 that you can use to test a 2.6.15 kernel?
[02:35] <jbailey> BenC: Yes. ppc64-smp, but it's my main machine so I don't like to reboot often.  Can we time it for lunch time or end of day?
[02:36] <BenC> jbailey: sure, I'll put the image at p.u.c/~bcollins/2.6.15/powerpc/
[02:36] <BenC> thanks
[02:37] <jbailey> 'kay, lemme know.
[03:25] <zul> blah
[04:13] <CataEnry> hi all
[04:20] <BenC> hello
[04:27] <janimo> BenC if we find bugs which are in upstream too, tell you or lkml?
[04:28] <janimo> i.e are you the MUX for all ubuntu work :) ?
[04:28] <BenC> if you know the correct upstream person, then to them directly
[04:29] <BenC> but mainly you can go through me (bugzilla) and I'll proxy
[04:29] <BenC> if there's an upstream person, they'll be the one asking you to do things, so me being int he middle of a quick debug cycle is a waste
[04:31] <janimo> ok, I am recompiling now I think I found the commit which broke booting on my laptop
[04:31] <janimo> was in 2.6.12 got reversed in 13
[04:31] <janimo> worked in breezy but does not now
[04:38] <makx> fabbione: ping
[07:46] <zul> feck!!!
[07:56] <lamont-away> Default I/O scheduler
[07:56] <lamont-away> > 1. Anticipatory (DEFAULT_AS) (NEW)
[07:56] <lamont-away>   2. Deadline (DEFAULT_DEADLINE) (NEW)
[07:56] <lamont-away>   3. CFQ (DEFAULT_CFQ) (NEW)
[07:56] <lamont-away>   4. No-op (DEFAULT_NOOP) (NEW)
[07:56] <lamont-away> choice[1-4?] : Default I/O scheduler
[07:56] <lamont-away> > 1. Anticipatory (DEFAULT_AS) (NEW)
[07:56] <lamont-away>   2. Deadline (DEFAULT_DEADLINE) (NEW)
[07:56] <lamont-away>   3. CFQ (DEFAULT_CFQ) (NEW)
[07:56] <lamont-away>   4. No-op (DEFAULT_NOOP) (NEW)
[07:56] <lamont-away> choice[1-4?] :
[07:56] <lamont-away> fabbione: that's why buildd.mmjgroup.com was ENOSPC
[07:57] <lamont-away> BenC: you have time to make sure hppa doesn't go into a terrible loop?  (or maybe we could teach make oldconfig to _DIE_ when it gets EOF, instead of looping...
[08:08] <CataEnry> bye all :)
[08:11] <BenC> lamont-away: yeah, I was trying to figure that out aswell
[08:11] <lamont-away> BenC: you have an hppa box?
[08:11] <BenC> not running yet
[08:11] <BenC> still sitting with my other servers from the move
[08:12] <lamont-away> BenC: I'll figure out what config file options we need to add.. I still haven't bothered figuring out jit yet...
[08:13] <lamont-away> so I'll probably just paste you some options...
[08:32] <zul> BenC: might arent you popular today
[08:33] <dilinger> BenC: autograph my chest!
[08:36] <lamont-away> BenC: wow.  mega changes in the config
[08:36] <lamont-away> BenC: are any of the hppa cvs/jit/whatever changes merged into that source?
[08:36] <BenC> dilinger: I have a broken PCI card I can use to carve it in
[08:36] <lamont-away> because I expect there is a new config set for hppa with the right answers...
[08:37] <BenC> lamont-away: no, nothing
[08:37] <BenC> lamont-away: and there's no "hppa" changesets listed in git-log, so it's probably going to be a mess to get the patch to apply :)
[08:38] <BenC> dilinger: append :) to that
[08:38] <lamont-away> BenC: ok.  I'll just ignore the poor beast for a day or 3. :-(
[08:39] <lamont-away> but it would be nice if make oldconfig died instead of looping...
[08:39] <lamont-away> your fame would be uncountable...
[08:39] <BenC> lamont-away: working on it
[08:40] <dilinger> hehe
[08:41] <BenC> sweet
[08:42] <BenC> if I do silentoldconfig, it will die with an error if tty is not valid, and it has a question
[08:42] <BenC> shit
[08:42] <BenC> make-kpkg calls oldconfig, not me :/
[08:42] <dilinger> yea
[08:43] <dilinger> i did that for debian's kernel packaging
[08:45] <dilinger> er, sorry, as a helper script, to verify that the configs were correct
[08:47] <dilinger> http://svn.debian.org/wsvn/kernel/dists/trunk/scripts/testconfigs?op=file&rev=0&sc=0
[08:49] <BenC> ok, I've got a fix that works
[08:50] <BenC> checks stdin for feof() if fgets() fails
[09:25] <zul_> hmm...
[09:26] <zul_> jbailey: ping
[09:36] <jbailey> zul_: On phone.
[09:36] <jbailey> 'sup?
[09:36] <zul_> jbailey: i got a basic git package together last night im going to try to finish it off tonight and ill send you the diff so you can have a look.
[09:37] <jbailey> Ah, cool!
[09:43] <zul_> just let me know you need
[10:46] <zul_> laster
[11:32] <CataEnry> hi all


[20:28] <minasota> 6 days of command line only... Using tmux to serve all my cl needs.
[20:29] <minasota> I'm confident in time I can be more productive on far less resources once I learn/remember all keybindings
[20:30] <minasota> It's also nice to browse the web and see just the content I'm interested in without all the distractions


[15:17] <aisrael> I want to execute a post-initiation piece of user-data. I tried adding the data to /var/lib/cloud-scripts/per-boot but the script fails. What should that script look like?
[15:24] <rharper> http://cloudinit.readthedocs.io/en/latest/topics/examples.html#run-commands-on-first-boot
[15:30] <aisrael> rharper: I tried that, but seeing an error in cloud-init.log. Here's the script: http://pastebin.ubuntu.com/23480882/
[15:31] <aisrael> and the relevant log: http://pastebin.ubuntu.com/23480880/
[15:33] <rharper> aisrael: and the first paste is the contents of that 99-test ?
[15:33] <aisrael> rharper: Correct
[15:33] <smoser> well, it says:
[15:33] <smoser>  ['/var/lib/cloud/scripts/per-boot/99-test']#012Exit code: -#012Reason: [Errno 8] Exec format error#012Stdout: ''#012Stderr: ''
[15:33] <smoser> oh. yeah. so aisrael if you want to just execute something per boot
[15:34] <smoser> the things in that dir need to be executable
[15:34] <smoser> they're things to execute, not cloud-config
[15:34] <rharper> aisrael: if you use runcmd, it's exec directly from cloud-init.   vs.  adding a file to that dir
[15:34] <rharper> what I suggested is different than writing files to per-boot dir
[15:36] <aisrael> smoser: Is there a way to run a bit of cloud-config on every boot? For background, I'm writing a cloud-init charm layer, where the underlying machine has been pre-allocated (think manual provider)
[15:38] <smoser> you can change the runcmd to run every boot. the thing that stinks about doing that is that you have to re-define all of 'cloud_final_modules' (see /etc/cloud/cloud.cfg) in order to modify the frequency of scripts-user
[15:40] <aisrael> smoser: ok, supposing I did that ([scripts-user, always]), would I then put that cloud-config into /etc/cloud/cloud.cfg.d?
[15:40] <smoser> http://paste.ubuntu.com/23480925/
[15:41] <smoser> you can put it in user-data, or you can modify the file in /etc/cloud/cloud.cfg or add it to a file in that dir.
[15:41] <rharper> aisrael: fwiw, your examine with runcmd works fine on a new instance; I think your failure was related to the modifications of files in the local per-boot dir
[15:42] <smoser> right.
[15:42] <smoser> aisrael, you can also use write_files to put something into /var/lib/cloud-scripts/per-boot
[15:42] <smoser> and that thing that you write there will run once per boot
[15:43] <rharper> that seems best
[15:44] <smoser> aisrael, http://cloudinit.readthedocs.io/en/latest/topics/modules.html#write-files
[15:48] <aisrael> Ok, let me see if I can get this working via cloud.cfg. It's not writing files, per se, that I need but to inject custom cloud-config into an already bootstrapped instance.
[15:50] <smoser> aisrael, oh. well, that will be more difficult.
[16:08] <aisrael> smoser: rharper: Thanks for the info!  I'm not sure what my path forward on this will be, but I have a clearer idea now.
[16:09] <smoser> aisrael, you can 'cloud-init single --frequency=always --name=<that-name>'
[16:09] <smoser> but you have to know what that-name is. ie, which cloud-initmodules will need tob e run for your config.
[16:10] <aisrael> smoser: ok, that makes sense
[19:14] <smoser> rharper,
[19:14] <smoser> http://pad.ubuntu.com/tMdgYGEvgL
[19:14] <smoser> look at the bold
[19:14]  * rharper looks
[19:14] <smoser> i'm not sure if we want Before=basic.target there.
[19:15] <smoser> versus before=sysinit.target
[19:15] <rharper> hrm
[19:15] <rharper> lemme look at my yakkety instance
[19:15] <smoser> pitti reviewed that and acked it at https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/310547
[19:16] <rharper> you have Before=basic.target twice
[19:16] <rharper> line 24 and 26/27
[19:18] <rharper> http://paste.ubuntu.com/23481950/
[19:18] <rharper> smoser: I think looking at that, basic.target is too late
[19:19] <smoser> rharper, its not twice. where do you see that ?
[19:19] <rharper> I mentioned the lines
[19:20] <rharper>  - add Before=basic.target (**wonder if this is right**)
[19:20] <rharper> - add Before=basic.target
[19:20] <rharper>       this is done to become part of "early boot" in order to to be able to affect mounts (http://pad.lv/1611074)
[19:20] <smoser> oh. in the pad.
[19:20] <rharper> yes
[19:20] <rharper> sorry
[19:21] <smoser> i thought you mean tin the .service
[19:21] <smoser> adjusted the pad
[19:21] <rharper> so, the -replace 'Wants'/After local-fs.target with 'systemd-remounte-fs.service' is much earlier
[19:21] <rharper> if local-fs.target is good enough? why would we wait longer ?
[19:22] <smoser> we dont wait longer.
[19:22] <smoser> we are now running earlier (possibly)
[19:22] <smoser> after local-fs.target would possibly include all the local systemd generated .mount
[19:23] <smoser> which we have to run before
[19:24] <smoser> i think its right.
[19:25] <rharper> smoser: so, Xenial without the SRU is running *too late* for mount;  what did we put in Yakkety ? Before=local-fs.target ? and slangasek suggests systemd-remount-fs.service ?
[19:26] <smoser> slangasek saw what he believed was a loop
[19:26] <rharper> smoser: I'm confused between what we did in yakkety, vs. where Xenial is at (I'm ignoreing where Xenial is at, and interested in changes to cloud-init trunk to understand the changes; then we can look at the Xenial -> SRU changes
[19:26] <smoser> but not one i'd seen in practice.
[19:26]  * rharper looks a this cloud-init-loca.service now
[19:26] <smoser> sure. thats fine. thats ultimately what we're doing.
[19:26] <rharper> the Wants=local-fs.target with an After=local-fs.target
[19:27] <rharper> is what we have in yakkety now
[19:27] <rharper> for cloud-init-local.service
[19:27] <rharper> that *functions* for early mount
[19:27] <rharper> and slangasek suggests that makes a loop or something like that ?
[19:27] <smoser> right.
[19:27] <smoser> well, he did.
[19:27] <rharper> Im not seeing it either
[19:28] <smoser> which is why i dropped the local-fs stuff
[19:28] <smoser> i'm not sure it is or not
[19:28] <smoser> but essentially saying : After=local-fs.target
[19:28] <smoser> *and*
[19:28] <rharper> it seems we need a Before=sysinit.target *AND* a After=systemd-remount-fs.service
[19:28] <rharper> maybe that RequiresMountsFor does the trick
[19:28] <smoser> no.
[19:28] <smoser> shoot.
[19:29] <smoser> so... we drop the local-fs.target
[19:29] <smoser> as we dont need that and because we're writing things to /etc/fstab, it seems like there could be a loop there.
[19:29] <smoser> as we say that those mounts should not be processed untill after cloud-init.service
[19:30] <rharper> ahh
[19:30] <rharper> I see
[19:30] <smoser> but we said cloud-init.service should be after local-fs.target (which would include them)
[19:30] <smoser> it seems reasonable
[19:30] <rharper> yes
[19:30] <smoser> but i'd never seen it
[19:30] <rharper> oddly neither have I
[19:30] <rharper> and there's no complains
[19:30] <smoser> no 'break's or complaints or anything
[19:30] <rharper> complaints from journalctl
[19:30] <rharper> right
[19:30] <smoser> so i suspect that sytemd resolved it elsewhere
[19:30] <smoser> probably by adjusting the .mount things
[19:30] <rharper> well
[19:30] <rharper> clearly from the chain, local-fs.target is *reached* prior to cloud-init-local running
[19:31] <rharper> and trivially cloud-init.service
[19:31] <smoser> i assume it changed the meaning of local-fs.target
[19:31] <rharper> so it must not be a hard requirement w.r.t fstab writing
[19:31] <smoser> so at the moment i think that Before=basic.target is ok,
[19:32] <smoser> at least i dont have any fallout of that that i'm aware of
[19:32] <rharper> it's clearly OK, as basic.target is much later
[19:32] <smoser> i think i'll prepare sru with it as it is in zesty
[19:32] <rharper> the question is whether we want to ensure we run even earlier
[19:32] <smoser> much later than waht ?
[19:32] <rharper> say Before=sysinit.target
[19:32] <rharper> or local-fs.target
[19:33] <smoser> yeah, so i suspect that cloud-init.services 'Before=basic.target' ends up not doing anything
[19:33] <rharper> smoser: so, I think we have to be after local-fs.target in that, we can't assume we can write to /etc/fstab unless we have local-fs.target, right ?
[19:33] <smoser> shoot
[19:33] <smoser> yeah, so i suspect that cloud-init-local.service  'Before=basic.target' ends up not doing anything
[19:34] <smoser> as cloud-init.service is Before=sysinit.target and After=cloud-init-local.service
[19:34] <rharper> well, it's before it, but that's not really making it run "early"
[19:34] <smoser> so cloud-init-local.service gets forced early due to cloud-init.service's Before=sysinit.target
[19:34] <smoser> so i think this is fine.
[19:38] <rharper> smoser: we might want to do an in HO with slangasek in a bit
[19:38] <smoser> :)
[19:38] <jgrimm> +1
[19:38] <rharper> I think cloud-init-local.service should be explicit
[19:46] <smoser> rharper, yes, we should change it , but it does not actually change anything
[19:46] <smoser> added https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/310919
[19:48] <rharper> smoser: yes
[20:44] <powersj> smoser: ping re: set_hostname vs change_hostname
[20:44] <powersj> err s/change/update/
[20:44] <smoser> powersj, thinking
[20:46] <smoser> ok. so
[20:46] <smoser> update_hostname runs PER_ALWAYS (every boot)
[20:46] <smoser> (more coming)
[21:03] <smoser> powersj, http://pad.ubuntu.com/NtJAvEJEiJ
[21:07] <powersj> smoser: thank you. Let me think about that and implications with testing them
[21:43] <powersj> harlowja: around? question re: cc_ssh_authkey_fingerprints
[22:11] <smoser> rharper, http://paste.ubuntu.com/23482707/
[22:11] <smoser> does that seems right ?
[22:11] <rharper> systemd-networkd.service is After dbus.target should say After=dbus.service
[22:12] <rharper> and sysinit.target is before dbus.service; hence the loop
[22:13] <rharper> dbus.service which runs after sysinit.target, but cloud-init.service is Before=sysinit.target
[22:13] <rharper> smoser: and the last paragraph is spot-on
[22:15] <smoser> rharper, fixing
[22:31]  * rharper relocates home
[22:46] <vans163> question. Does cloud-init automatically resize the root partition to the size of the image?  Say i download a cloud image that is 2gb max size, i do qemu-img resize img.img 50G, making it 50G now, when it first boots using the cloud-init iso will the root partition autoresize to 50G/
[23:00] <powersj> vans163: I think so... take a look at https://cloudinit.readthedocs.io/en/latest/topics/modules.html#resizefs
[23:04] <vans163> powersj: ty guessing default may not be true
[23:54] <smoser> vans163, yes.
[23:54] <smoser> was it not doing that ?
[23:55] <smoser> you can tell it not to. but generally thats the desired behavior