[05:02] <raining_> Hi, everyone
[05:02] <raining_> I need some help for my skype
[05:02] <raining_> I use ubuntu 10.10 x86_64
[05:02] <raining_> and I installed ibus-qt4
[05:03] <raining_> but I cannot use ibus for skype
[05:03] <raining_> pls give the solution
[05:13] <TheMuso> raining_: Please go to #ubuntu for support.
[05:18] <raining_> ok thanks
[06:45] <RAOF> So, I have this theory I want to test.  The only problem is that it requries a kernel recompilation.
[06:45] <RAOF> We would be so much more productive with infinite computation resources :)
[07:23] <pitti> Good morning
[07:24] <didrocks> good morning
[07:25] <pitti> bonjour didrocks
[07:26] <didrocks> hey pitti, how are you? Still packing? :)
[07:27] <pitti> didrocks: yeah, still quite a lot to do
[07:32] <didrocks> pitti: good luck :)
[07:32] <smspillaz> morning everyone
[07:33] <pitti> didrocks: thanks
[07:33] <pitti> hey smspillaz
[07:33] <smspillaz> heya :)
[07:33] <didrocks> hey smspillaz
[07:47] <Sweetshark> Good Morning, Desktopers!
[07:47] <pitti> hey Sweetshark
[07:47] <mvo> didrocks: eh, I just had a notification appear on top of my screensaver … is that a known issue?
[07:48] <mvo> good morning btw :)
[07:48] <mvo> (with compiz of course)
[07:48] <didrocks> mvo: hey, not it's not known :/
[07:48] <didrocks> smspillaz: maybe a regression from your restack branch? ^^
[07:48] <didrocks> hey Sweetshark
[07:49] <smspillaz> didrocks: likely not
[07:49] <smspillaz> mvo: stacking issues are known, but they are difficult to debug
[07:49] <mvo> I had that a while ago (weeks?) but then it went away
[07:50] <smspillaz> didrocks: I doubt the restack branch would do it
[07:50] <mvo> right, I'm worried about notification as they may lead to information discoulusre :/
[07:50] <mvo> (from IM for example)
[07:50] <didrocks> smspillaz: can you have a look with mvo? Still looking at incoming bugs
[07:50] <smspillaz> mvo: if you could find a way to get compiz into the state there that happens then I can look into it for you
[07:51] <smspillaz> mvo: I'm aware of the security risks here, but this is partly due to the fact that the screensaver model on linux is completely broken anyhow
[07:51] <mvo> I can try to reproduce now, its on this machine soI will be on and off irc
[07:52] <mvo> smspillaz: I remember we had similar issue back in the old days and solved it with some slegdehammer approach (but I may be wrong its a long time ago). something like "strcmp(w.name, "gnome-screensaver") ;)
[07:52] <smspillaz> indeed
[07:52] <smspillaz> we could have something like that
[07:52] <mvo> (truely ugly though)
[07:53] <smspillaz> right
[07:53] <smspillaz> IMO, we should kill gnome-screensaer and move screensaver handling into the window manager
[07:54]  * mvo scratches head - of course, now its no longer reproducable
[07:54] <mvo> fine with me
[07:56] <RAOF> smspillaz: Or… move both into the compositor, and have it be the display server? :P
[07:59] <smspillaz> RAOF: sounds like an amazing idea!
[07:59] <smspillaz> mvo: indeed, it's a very difficult thing to reproduce
[07:59] <smspillaz> mvo: which sucks, because it makes my life that much harder :)
[08:00] <smspillaz> RAOF: not having the screensaver and window manager be the same thing is insane
[08:00] <smspillaz> RAOF: the way the gnome-screensaver ensures that it is on-top of everything is right now is to flood us with restack requests
[08:01] <smspillaz> it's more cpu taxing for you screensaver to be on than off
[08:01] <smspillaz> even if it is just "blank"
[08:20] <vish> pitti, didrocks: is making changes like Bug 760656 appropriate for an SRU? … seems like a very odd choice deciding to change the branding after release.. :s  why not just upload the change now?
[08:20] <ubot2> Launchpad bug 760656 in unity "Launcher: Background lighting and border is displayed for Workspaces, Apps, Files, Trash (should be turned off)" [Undecided,Triaged] https://launchpad.net/bugs/760656
[08:21] <vish> btw, hi.. ;)
[08:25]  * Sweetshark remembers something ...
[08:26] <didrocks> vish: no, don't know why sladen is telling that…
[08:26] <didrocks> vish: I already told him it was way too late and risky
[08:27] <didrocks> vish: anyway, I didn't set it to the upstream 3.8.12 milestone which makes the authority or SRU on purpose
[08:27] <vish> didrocks: hmm.. yea, either we do it now or we postpone for O..
[08:27] <didrocks> vish: even now, we are in hard freeze today
[08:28]  * vish nods
[08:28] <didrocks> vish: and I had a quick look at this part of code one week ago, I already told sladen the amount of change was too high (in addition to another UI freeze breakage…)
[08:28] <didrocks> seems it doesn't worth it
[08:29] <vish> hmm..
[08:30] <fta2> seems under unity, the "API mismatch" after an nvidia driver update no longer triggers the please restart thingy like it used to
[08:31] <didrocks> fta2: oh really? next time I saw that (one week ago?), it was working
[08:32] <didrocks> previous*
[08:32] <fta2> didrocks, my 2 desktops were both sluggish, the logs show tons of NVRM warnings
[08:33] <Sweetshark> vish: I just updated your email in the copyright file ...
[08:33] <didrocks> fta2: not sure it's under unity, let's try to touch the file
[08:34] <fta2> didrocks, happened on my 2 main desktops running natty/unity
[08:34] <didrocks> fta2: touching /var/run/reboot-required worked
[08:35] <didrocks> fta2: so, shouldn't be unity related, maybe the package didn't touch it
[08:35] <fta2> maybe that file hasn't been touched then, too late to check, i rebooted both
[08:38] <didrocks> pitti: thanks for accepting unity (I guess it's you as it wasn't acked yesterday evening ;))
[08:40] <vish> Sweetshark: awesome thanks :)
[08:56] <pitti> didrocks: yes, did a queue run this morning
[08:56] <pitti> "last call for train to natty; please get seated, doors closing"
[08:57] <didrocks> pitti: not sure if you want to track this one: bug #767613
[08:57] <ubot2> Launchpad bug 767613 in unity "unity does not start with nvidia173.14.30" [High,New] https://launchpad.net/bugs/767613
[08:58] <pitti> didrocks: would be interesting to see if it also happens with nvidia-current
[08:58] <didrocks> pitti: apart from that (this seems a nvidia regression), all unity land should be done by now
[08:58] <didrocks> pitti: well, let me reboot :)
[08:58] <didrocks> if you don't see me back, call the police!
[08:58] <pitti> didrocks: oh, you get that, too?
[08:58] <pitti> I just asked on the bug
[08:59] <didrocks> pitti: I just updated my machine with nvidia 270
[08:59]  * pitti throws a tracking transponder onto didrocks' back
[08:59] <didrocks> fta2: confirmed, the package doesn't touch the file btw
[08:59] <didrocks> pitti: heh ;)
[09:01] <seb128> hey desktopers
[09:02] <pitti> bonjour seb128
[09:02] <pitti> seb128: formally rodrigo_ just got his third +1 on the desktop list; but do you want to follow up as well?
[09:02] <seb128> hey pitti, how are you?
[09:03] <seb128> pitti, I was going to yes
[09:03] <pitti> seb128: I'm fine, thanks! hurt my toe in the soccer game yesterday, but that'll pass
[09:03] <seb128> utch
[09:04] <pitti> didrocks: he's alive!
[09:04] <didrocks> pitti: \o/
[09:04] <didrocks> pitti: I don't have the same card, but at least, not all nvidia revisions regressed ;)
[09:05] <seb128> pitti, done
[09:05] <seb128> doh
[09:05] <pitti> seb128: yay
[09:06] <seb128> oh, really done with an email subscribed to the list this time :p
[09:07] <didrocks> seb128: oh got puzzled by sending from the wrong adress to ubuntu-desktop ML? :)
[09:08] <seb128> I hacked my @ubuntu.com to @canonical.com yesterday to reply to an email
[09:08] <didrocks> seb128: how hacked? :-)
[09:08] <seb128> seems people tend to send me email on that one using seb128 rather than my name
[09:08] <seb128> well edited the account and changed my email
[09:09] <seb128> I should add some extra dumb accounts for the variants I don't use but people write to
[09:09] <seb128> I tend to use seb128 at ubuntu and s.b at canonical
[09:09] <seb128> but people write to seb128 at canonical for some reason
[09:10] <seb128> well anyway boring email story :p
[09:10]  * cdbs has a dream to work one day for canonical, though he already is contracted for unity :)
[09:28] <pitti> vish: yes, such things really shouln't be changed post release
[09:49] <aquarius> hm. I keep getting GPU crashes (I think that's what they are), and then when I reboot the machine to get my display back, I ge tthe "System program problems detected" dialog. When I say "yes, report the problem", I get *another* crash dialog saying "apport-gpu-error-intel.py closed unexpectedly". I think this means that the program trying to diagnose the crash is itself crashing?
[09:50] <aquarius> So I have two questions: how do I diagnose and report the GPU crash, and am I correct in my assumptions? :)
[09:52] <seb128> aquarius, hey, do you confuse us with #ubuntu-x? ;-)
[09:53] <aquarius> seb128, well, I think this is more an apport problem; once I've got apport able to report the actual gpu bug, I will then go and whine at the X people about not making my GPU hang in the first place. But if I whine at them now they'll say "file a bug" and I'll say "I can't, apport won't let me" :)
[09:54] <mvo> pitti: could you have a quick look at http://paste.ubuntu.com/596843/ and apply upstream if it makes sense? just look at software-center and gir and this is the first bit I stumbled on
[09:54] <seb128> aquarius, no, it seems that the apport-gpu-error-intel.py code shipped with the xorg packages is buggy
[09:55] <pitti> mvo: oh, absolutely
[09:56] <aquarius> seb128, oh, they own the apport-gpu thing? right, cool, I'll go talk to them about it :)
[09:56] <seb128> aquarius, yes
[09:56] <mvo> thanks!
[09:56] <seb128> mvo, you want to use gtk3
[09:56] <seb128> ;-)
[09:56] <pitti> mvo: it's already fixed in GTK3
[09:57] <pitti> right, if you start porting now, do use gir1.2-gtk-3.0
[09:57] <pitti> it's a lot more stable, and in oneiric we'll use that anyway
[09:57] <mvo> ok
[09:57] <mvo> I don't really want to start now, just play with it to get a feeling for the task at hand
[09:59] <pitti> mvo: anyway, http://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24&id=baf8bf967dfcde1b101d513c5102872a9b0ac571
[10:00] <mvo> cool, thanks
[10:00]  * mvo switches to gtk3
[10:00] <pitti> mvo: it currently looks ugly due to missing theme, but for porting it's still better
[10:01] <pitti> there's some things which are principally broken in gtk2 and can't be fixed easily
[10:01] <pitti> such as menu popups
[10:01] <mvo> ok
[10:01] <mvo> it currently segfaults for me a lot, but I guess that is because of leaking import pygtk/import gtk somewhere
[10:01] <pitti> mvo: you know about the porting guide, btw?
[10:01] <pitti> right
[10:01] <mvo> the gtk2 -> gtk3 one?
[10:01] <pitti> that, too, but I meant the pygtk -> pygi one
[10:02] <pitti> https://live.gnome.org/PyGObject/IntrospectionPorting
[10:02] <pitti> I recycled my UDW talk to this
[10:02] <seb128> didrocks, no luck for those nvidia crash since pitti turned apport off yesterday, we will need to get someone to manually turn it on again
[10:02] <mvo> aha, nice
[10:03] <didrocks> seb128: right, anyway, I have something online within the day to get it manually reported
[10:03] <mvo> I was usuing the talk and the gir s far, nice to see it in one good page
[10:03] <seb128> didrocks, ok
[10:09] <pitti> mvo: so pygi-convert left some imports which are pulling in gtk?
[10:09] <pitti> mvo: one thing that's currently missing from that is appindicator -> gi.r.AppIndicator; do you use that?
[10:19] <didrocks> pitti: seb128: can you force bug #768178 to be retraced please? (it's the nvidia issue)
[10:19] <seb128> didrocks, ok
[10:19] <didrocks> thanks :)
[10:21] <seb128> didrocks, do you know what architecture it is?
[10:21] <didrocks> i686 ?, asking (he's on #ayatana)
[10:22] <seb128> didrocks, if you have access to the bug it's in the tag
[10:22] <seb128> need-<arch>-retrace
[10:22] <didrocks> seb128: yeah, i386
[10:25] <seb128> didrocks, retraced
[10:25] <didrocks> seb128: thanks! rock :)
[10:25] <seb128> yw
[10:26] <seb128> didrocks, retracing worked, i.e the stacktrace has symbols etc
[10:26] <didrocks> seb128: yeah, seeing, that, I'm attaching to the other bug
[10:29] <mvo> pitti: yeah, it looks like it, I don't use appindicator. one I had to manually kill is gtkspell, there seems to be no gir yet
[11:04] <chrisccoulson> good morning everyone
[11:04] <chrisccoulson> nice day outside :)
[11:04] <didrocks> hey chrisccoulson
[11:05] <chrisccoulson> hi didrocks, how are you?
[11:05] <didrocks> chrisccoulson: I'm fine thanks, the bug rush is mostly behind now (let's cross fingers ;))
[11:05] <chrisccoulson> heh :)
[11:05] <didrocks> and you?
[11:07] <chrisccoulson> didrocks, good thanks. just looking at a bug someone reported this morning against my firefox extension
[11:08] <chrisccoulson> i think it's the first real bug!
[11:08] <chrisccoulson> how dare they ;)
[11:08] <chrisccoulson> bug 767966 (quite bad) :(
[11:08] <ubot2> Launchpad bug 767966 in firefox "globalmenu extension pollutes main window javascript scope" [Undecided,New] https://launchpad.net/bugs/767966
[11:08] <didrocks> chrisccoulson: how come??? :-)
[11:08] <chrisccoulson> i should definitely get that one fixed before people start complaining i break their other extensions ;)
[11:09] <didrocks> chrisccoulson: heh, of course, everyone will blame you (or rather unity :p)
[11:09] <chrisccoulson> lol
[11:09] <didrocks> chrisccoulson: FYI, I tried again firefox4 and LP… still not a joy :/
[11:09] <chrisccoulson> it's normally me who gets the blame isn't it?
[11:10] <chrisccoulson> didrocks, that sucks. however, they are planning to completely rewrite the drawing code in a future firefox version ;)
[11:10] <didrocks> chrisccoulson: well, as it's in "unity", it's "unity broke xxxx" (we get a non negligeable of such reports ;))
[11:10] <didrocks> chrisccoulson: hope it will be done, I would prefer using our defaults ;)
[11:10] <micahg> chrisccoulson: are you still planning another upload to natty?  I was going to stage the security update later today (could hold off till tomorrow)
[11:11] <chrisccoulson> micahg - there won't be another upload (too late)
[11:11] <micahg> chrisccoulson: :(, SRU?
[11:11] <chrisccoulson> and we'll need to fix bug 767966 in the next update
[11:11] <ubot2> Launchpad bug 767966 in firefox "globalmenu extension pollutes main window javascript scope" [Undecided,New] https://launchpad.net/bugs/767966
[11:13] <micahg> chrisccoulson: k, well, if you get the SRU team ACK, feel free to commit
[11:14] <chrisccoulson> didrocks, http://is.gd/YubTDn ;)
[11:16] <didrocks> chrisccoulson: oh nice, hopes the ball won't be dropped since :)
[11:27] <chrisccoulson> seb128, i fixed the nautilus errors btw ;)
[11:27] <chrisccoulson> https://code.launchpad.net/~chrisccoulson/ubuntuone-client/lp767825/+merge/58594
[11:27] <chrisccoulson> simples :)
[11:27] <seb128> bah, u1 again!
[11:27] <chrisccoulson> yep
[11:29] <seb128> get didrocks to get the unity fix in for the next upload, likely to be a SRU since I'm not sure we want uploads to clean log spamming today
[11:30] <didrocks> seb128: this is a workaround, not a fix, Jason was relunctant to integrate it
[11:30] <didrocks> I asked him to look at it
[11:30] <chrisccoulson> why is it a workaround?
[11:30] <seb128> ok
[11:30] <chrisccoulson> the issue is that the menuitems don't exist if the menu was never opened
[11:30] <didrocks> and asked him to answer, but seems the info was lost
[11:30] <chrisccoulson> so i just add a check for that
[11:31] <didrocks> chrisccoulson: look at the fixme you removed :)
[11:31] <chrisccoulson> didrocks, yeah, but the fixme seemed to be describing the issue that my change fixes
[11:31] <chrisccoulson> (ie, there are invalid pointers, because no menuitems exist)
[11:32] <didrocks> chrisccoulson: the ref should be destroyed before if they are invalid, I think that was Jason's point
[11:32] <didrocks> chrisccoulson: discuss that with him once he's back online. Anyway, will be in a SRU
[11:41] <Sweetshark> hmm: I get "start: Job failed to start" from the recent apport update ...
[11:46] <ogra_> Sweetshark, its probably already in easter holiday mood :)
[12:30] <mvo> seb128: are you happy with me doing #760707 as a SRU?
[12:37] <seb128> mvo, yes, we will not get imports and translations before the langpack exports anyway
[12:37] <seb128> brb
[12:44] <seb128> re
[12:44] <seb128> mvo, so patch piloting today? ;-)
[12:45] <mvo> seb128: yeah
[12:45] <mvo> seb128: I disagree about the importance too btw ;) for the i18n issue, but *shrug*
[12:46] <seb128> mvo, yeah, my triaging scripts default to low and an overwrite those by hand usually when needed, I disagree with it as well so feel free to fix it ;-)
[12:47] <mvo> awsome!
[12:47]  * mvo sets it to whishlist
[12:48] <didrocks> chrisccoulson: you worked with Jason on the thunderbird fix not kept in the launcher, isn't it?
[12:48] <mvo> just kidding, medium
[12:48] <seb128> mvo, lol
[12:48] <seb128> didrocks, you want to ruin his day saying the fix doesn't work? :-)
[12:48] <seb128> mvo, thanks
[12:49] <didrocks> seb128: that's my greatest sadic pleasure, you know that!</kidding> :-)
[12:49] <didrocks> chrisccoulson: you should follow up on bug #765736
[12:49] <ubot2> Launchpad bug 765736 in unity "Thunderbird won't stay in launcher and no quicklist" [High,Fix committed] https://launchpad.net/bugs/765736
[12:49] <seb128> bug #768243 as well btw
[12:49] <ubot2> Launchpad bug 768243 in unity "tvtime and some other applications can't be added in unity launcher" [Undecided,New] https://launchpad.net/bugs/768243
[12:50] <seb128> didrocks, you marked miro as a duplicate you are sure it's the same issue?
[12:50] <didrocks> seb128: not sure, I was infering as it wasn't working before the fix, and I installed it to test the fix
[12:50] <didrocks> (and it works)
[12:50] <didrocks> btw, time to uninstall it, I don't use that :)
[12:50] <seb128> ok
[12:51] <seb128> I got quite some craps installed for testing purpose
[12:51] <didrocks> seb128: such a sacrifice! :-)
[12:51] <didrocks> anyway, need to reinstall my box once the first testing iso are published
[12:52] <didrocks> cleanswap will be needed here
[12:52] <seb128> sometimes I wonder if installing the new version would be easier than upgrading
[12:52] <seb128> less to download if you have the iso ;-)
[12:59] <chrisccoulson> didrocks, hmmm, will have another look in a bit. it certainly worked for me after applying the fix (and i tried with italian too)
[14:25] <mterry> seb128, so in this last-minute rundown to 11.04, what's the best use of my time?  Continue working on bugs for maybe SRUs, do ISO testing, upgrading testing?
[14:25] <seb128> hey mterry
[14:25] <mterry> seb128, hi@
[14:25] <seb128> mterry, I think we are good for natty
[14:25] <mterry> ! even
[14:25] <ubot2> Factoid 'even' not found
[14:25] <mterry> seb128, so confident!  ;)
[14:26] <seb128> lol
[14:26] <seb128> I didn't say we are gold ;-)
[14:26] <seb128> but remaining issues can be sorted in sru
[14:26] <mterry> seb128, OK so blueprint prep and such?
[14:26] <seb128> I've no specific issue on my list but I might bounce a few bug worth fixing in srus on your list if I cross some
[14:27] <mterry> seb128, k
[14:27] <seb128> so meanwhile you can do upgrade and iso testing, bug triage, blueprints start on merges for next cycle
[14:27] <seb128> whatever you prefer ;-)
[14:27] <seb128> I think current iso have ubiquity issues
[14:27] <pitti> chrisccoulson: lol @ https://bugzilla.mozilla.org/show_bug.cgi?id=647959
[14:27] <seb128> so maybe wait the next round for that
[14:27] <ubot2> Mozilla bug 647959 in CA Certificates "Add Honest Achmed's root certificate" [Normal,Resolved: invalid]
[14:27] <didrocks> hey mterry
[14:28] <didrocks> zomg, pitti told "lol". /me shocked
[14:28] <mterry> didrocks, hello!
[14:28] <pitti> hey mterry
[14:28] <pitti> didrocks: this bug really deserves it, have a look :)
[14:28] <seb128> kenvandine, mterry: why you guys write softwares that have several desktop entries?
[14:29] <chrisccoulson> pitti - lol, where did you find that?
[14:29] <chrisccoulson> :-D
[14:29] <seb128> like deja-dup has 2 icons in a dash search
[14:29] <seb128> gwibber has 3
[14:29] <kenvandine> :)
[14:29] <pitti> chrisccoulson: it made it all the way up to heise.de
[14:29] <chrisccoulson> heh :)
[14:29] <kenvandine> seb128, with the dash that does make it more cluttered...
[14:29] <didrocks> pitti: excellent, I really like "Honest Achmed is at least more honest than Comodo."
[14:30] <kenvandine> we wanted them to be pretty separated, considering we want you to be able to configure the service with the client running
[14:30] <seb128> pitti, do you think trivial bug fixes to not spam .xsession-errors with warning are worth an upload or are SRU material rather?
[14:30] <pitti> seb128: bring 'em on
[14:30] <mterry> seb128, well...  deja-dup-preferences was written as a separate app from the main deja-dup executable.  And so it needs its own .desktop file to be recognized by unity at all
[14:31] <pitti> seb128: well, for today it's fine anyway; probably not over Easter holidays any more
[14:31] <seb128> mterry, is there any usecase to call it out of the deja-dup ui?
[14:31] <seb128> chrisccoulson, dobey: can we get the nautilus gconf spamming fix uploaded?
[14:31] <mterry> seb128, it would be nice if unity let you say, "these two .desktop files are part of the same app" and join them
[14:32] <kenvandine> mterry, but not if you want them launchable independent of each other
[14:32] <Sweetshark> pitti: ooold, that was on heise yesterday already
[14:32] <pitti> Sweetshark: I know, but still funny ;)
[14:32] <seb128> mterry, well either they are useful and should each be listed or not, I would tend to think that the preference dialog being a different binary is not something the user need to care about
[14:32] <mterry> kenvandine, well, even if they were launchable separate, it would be nice if you could tell unity to display them under the same "app"
[14:33] <kenvandine> if we get multiple actions in unity
[14:33] <mterry> seb128, I agree!  But unity doesn't let you hide such technical details.  It will show different execs as different entries
[14:33] <seb128> mterry, NoDisplay=true?
[14:33] <mterry> seb128, I don't think that works once it's running...  You are talking about from the Applications Lens?  I thought you were talking Launcher
[14:33] <Sweetshark> pitti: I esp. like the "once we are too big to fail, we wont have to justify ourselves anyway" part
[14:33] <seb128> mterry, what is the point in having a .desktop for it anyway? rather than just calling the command from the deja-dup ui?
[14:34] <pitti> Sweetshark: it's not funny because it's so true :-(
[14:34] <Sweetshark> yep
[14:35] <mterry> seb128, that was a baby step towards the more dramatic UI overhaul in Oneiric.  The idea is that backup features could be seen as just a feature of the OS, and so should have an entry in your system settings.
[14:35] <mterry> seb128, in Oneiric it only lives in system settings
[14:35] <dobey> seb128: what nautilus gconf spamming fix?
[14:35] <seb128> mterry, ok
[14:36] <seb128> dobey, bug #767825
[14:36] <ubot2> Launchpad bug 767825 in ubuntuone-client "nautilus plugin spamming ~/.xsession-errors" [Undecided,New] https://launchpad.net/bugs/767825
[14:36] <mterry> seb128, the application lens hides that a bit because it doesn't represent categories very well.  so you just see two entries
[14:36] <seb128> dobey, see chrisccoulson's merge request
[14:37] <seb128> mterry, right, makes sense, you can see natty is close I'm spending time playing with things ;-)
[14:38] <mterry> heh
[14:46] <dobey> seb128, chrisccoulson: is that an issue on maverick as well?
[14:46] <seb128> dobey, dunno but it's one of the spammers in natty
[14:46] <seb128> so it would be nice to get it in
[14:47] <seb128> dobey, I would say that if nobody complained in 10.10 yet we can do without fixing it there
[14:47] <seb128> but I don't think it was doing that previous cycle, I think I would have noticed
[14:48] <dobey> that's odd, because that code has changed very little.
[14:49] <dobey> chrisccoulson: anyway, can you also make a branch against lp:ubuntuone-client/stable-1-6 with that change, and propose merging it into stable-1-6 as well; since that's the stable branch we're using for 11.04
[14:49] <chrisccoulson> dobey, sure, can do
[14:50] <dobey> cheers
[15:15] <dobey> ah crap
[15:19] <dobey> chrisccoulson: btw, do i need to do the upload to ubuntu for that patch, or do you have privs to do it?
[15:19] <chrisccoulson> dobey, i'm not sure i can upload it
[15:20] <chrisccoulson> 1 second, i'll just check
[15:20] <dobey> ok
[15:20] <chrisccoulson> no, it doesn't look like i can upload that
[15:21] <dobey> ok
[15:27] <chrisccoulson> dobey, https://code.launchpad.net/~chrisccoulson/ubuntuone-client/lp767825-stable-1-6/+merge/58684
[15:27] <seb128> DBO, chrisccoulson: did you guys look at bug #757011?
[15:27] <ubot2> Launchpad bug 757011 in unity "Keep in launcher option for Emacs does not save over restarts" [Low,New] https://launchpad.net/bugs/757011
[15:28] <dobey> chrisccoulson: thanks
[15:28] <chrisccoulson> seb128 - when i tried it the other night, the launcher matching was working ok (I didn't see any issue with emacs)
[15:29] <chrisccoulson> i'll have a look again in a bit
[15:29] <seb128> chrisccoulson, how, weird, it doesn't work here if I run emacs for the run a command or command line, it only works if I run it from the application place, which use gio on the .desktop which work...until you try to start it again by clicking the launcher icon
[15:29] <seb128> chrisccoulson, emacs23 there btw
[15:46] <dobey> seb128: ubuntuone-client is in the upload queue with chrisccoulson's fix
[15:46] <seb128> dobey, thanks!
[15:46] <seb128> pitti, ^
[15:47] <pitti> cheers
[15:58] <pitti> seb128: did cyphermox mess with your nm-applet, too? :-)
[15:59] <seb128> pitti, no, but docking and undocking my laptop switches between wifi and eth, the dhcp gives me a new ip and irc reconnect...
[15:59] <seb128> (I've been testing an unity bug)
[15:59] <cyphermox> seb128, I so need to figure out if this can be fixed somehow
[15:59] <seb128> should be stable now ;-)
[16:00] <cyphermox> like, keepalive and stuff in some way to have irc stay online as much as possible, if your IP doesn't change too much
[16:36] <hosk> i don't get the unity panel, unity --reset produces http://pastebin.com/bH5SR8Ur , im in virtualbox, i have 3d accel enabled and the latest vb-guest additions, any thoughts or tips on how to search for a bug report that might already be filed?
[16:39] <hosk> preliminary research says it's unsupported GL, i'll see if i can install other drivers
[16:40] <fagan> em does apt.ubuntu.com know about natty yet?
[16:40] <fagan> its saying im not running ubuntu
[16:41] <fagan> :/
[16:42] <fagan> (and it links from developer.ubuntu.com so it would be nice if our own links worked in our own distro)
[16:42] <hosk> guess i am already running all add'l drivers i can, i feel like i've seen others running unity panel in it
[16:42] <hosk> maybe i need specifically the OSE version of guest additions
[16:46] <chrisccoulson> oh, uploads are still being accepted for natty?
[16:46] <davmor2> pitti: Yay my sansa fuse is showing up as a music player again thanks dude :)
[16:46] <chrisccoulson> fagan, which browser are you using?
[16:46] <pitti> davmor2: yippie
[16:46] <fagan> chrisccoulson: chrome
[16:47] <fagan> ahhhhh
[16:47] <fagan> thats why
[16:47] <chrisccoulson> yep
[16:48] <fagan> chrisccoulson: ooooh it doesnt work in firefox either on my machine
[16:48] <fagan> weird
[16:48] <chrisccoulson> fagan - that's bug 709125. it needs a server-side fix though
[16:48] <ubot2> Launchpad bug 709125 in apturlredirector "User agent doesn't include Ubuntu in it so apt.ubuntu.com doesn't work" [Critical,Fix committed] https://launchpad.net/bugs/709125
[16:48] <fagan> chrisccoulson: ah ok
[16:49] <chrisccoulson> firefox sends out a X-Ubuntu header when accessing apt.ubuntu.com now
[16:49] <fagan> chrisccoulson: thats cool I was just wondering
[16:49] <chrisccoulson> i've still got no idea who really maintains apt.ubuntu.com. we should get them to fix it :)
[16:50] <fagan> I get why we moved from apturl but its good anyway
[16:50] <fagan> chrisccoulson: id say ask on rt
[16:50] <davmor2> the snap to grid doesn't work with Control Centre.  It you snapping it to the left you lose the one side and to the right it snaps back to the middle of to screen.
[16:51] <fagan> chrisccoulson: if we are going to link it on our developer website we kinda have to be able to use it :)
[16:52] <fagan> apturl at least worked for the ubuntu people everyone else got something weird but it worked
[16:56] <hosk> Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x4401449 (hosk@hosk-); these messages lack timestamps and therefore suck.
[16:57] <hosk> i was generally just entertained by this message
[17:03] <chrisccoulson> hmmm, i guess i'm going to have to downgrade to firefox 4 for a bit :(
[17:36] <hosk> i can't unity --replace because gnome-panel is all up in my junk
[18:03] <didrocks> pitti: around? got a jockey question :)
[18:13] <pitti> didrocks: spotty
[18:13] <didrocks> pitti: well, we were discussing about blacklisting the nvidia driver 173 as we get one crash since the update and not sure if other cards work with it
[18:14] <didrocks> pitti: but we will rather add this support to the test tool it seems
[18:15] <chrisccoulson> BINGO!
[18:16] <chrisccoulson> i think i've just cracked an annoying firefox bug
[18:16] <chrisccoulson> damn you firefox sync
[18:16] <didrocks> pitti: do you know who will be there tomorrow to eventually acked the new nux upload?
[18:16] <pitti> didrocks: I think it depends on whether the driver is generally broken (then we'll disable it in jockey) or just in rare cases for unity (then we can check in the test tool)
[18:17] <pitti> didrocks: the american folks at least, i. e. skaet
[18:17] <didrocks> pitti: the thing is that we don't really know, and nobody tested it
[18:17] <didrocks> pitti: so blacklisting until the SRU seems the safest
[18:17] <pitti> didrocks: ok
[18:17] <didrocks> skaet: ready to ack an nux upload for blacklisting this case tomorrow?
[18:17] <pitti> didrocks: did you talk to tseliot about it already?
[18:18] <didrocks> pitti: this morning, right, but didn't think to ask if he tested it with unity (compiz alone works)
[18:20] <pitti> oh, interesting
[18:20] <pitti> didrocks: then we probably should also keep it for Kubuntu and classic users?
[18:21] <didrocks> pitti: yeah, the unity test tool to only blacklist it in the unity case sounds good
[18:47] <didrocks> pitti: FYI, we are headed to a 0-day SRU to either blacklist the driver or fix the issue (and profit)
[18:47] <didrocks> as people need an internet connection to install the driver, there is a high chance they install the update as well
[18:50] <pitti> didrocks: yes, they'll install from natty-updates right away, unless they are using a DVD source
[18:51] <didrocks> pitti: so, seems quite safe to head for a 0-day SRU
[18:51] <pitti> didrocks: yes, I agree
[18:52] <didrocks> pitti: ok, let's go to that road then! Thanks for the feedback :)
[18:54] <skaet> pitti, didrocks,  just back from lunch and read through the backscroll,  yup, on standby for that blacklist update (and SRU path).
[18:54] <didrocks> nice :)
[18:55] <flacoste> hey folks, just a big thank you for your work on Natty, i've really enjoyed my 2.5 weeks with it so far
[18:55] <flacoste> works like a charm
[19:14] <pitti> kenvandine: why does it read the entire whitelist and then return true? it would be easier to return true right away?
[19:14] <kenvandine> i was keeping the diff small :)
[19:14] <kenvandine> i could change that though
[19:15] <pitti> kenvandine: it's an one-line change either way?
[19:15] <pitti> not a biggie, though
[19:15] <pitti> anyway, gotta run, have a nice Easter holidays everyone!
[19:15] <kenvandine> i guess it would still be one line
[19:15] <mvo> bye pitti
[19:22] <sabdfl> you guys have done a brilliant job with some really tough stretch goals this cycle
[19:22] <kenvandine> sabdfl, thx :)
[19:22] <sabdfl> thank you!
[19:22] <kenvandine> it's been fun though!
[19:22] <sabdfl> heh
[19:22] <kenvandine> sort of... hehe
[19:22] <sabdfl> hopefully, calmer fun in oneiric
[19:22] <kenvandine> indeed
[19:22] <sabdfl> now we have the foundations in place we are going to rock the planet
[19:23] <kenvandine> looking forward to that!
[19:23] <sabdfl> i'd like to see ubuntu go viral in 11.10 and 12.04, where people just start "doing it" on all their spare and primary computers
[19:23] <sabdfl> i think we can pull that off
[19:23] <kenvandine> that would be sweet
[19:23] <kenvandine> charging forward in fixing bug #1
[19:23] <ubot2> kenvandine: https://bugs.launchpad.net/ubuntu/+bug/1 (Not reporting large bug)
[19:24] <kenvandine> ha, funny... ubot2 refuses to talk about bug #1
[19:24] <ubot2> kenvandine: https://bugs.launchpad.net/ubuntu/+bug/1 (Not reporting large bug)
[19:26] <sabdfl> ubot2, you're a wimp
[19:26] <ubot2> Factoid "you're a wimp" not found
[19:26] <sabdfl> exactly
[19:26] <kenvandine> :-D
[19:27] <JFo> sabdfl, I may have an O song mashup for your enjoyment in Budapest :-)
[19:27] <JFo> working on finishing it now
[19:33] <chrisccoulson> pitti - there?
[19:33] <kenvandine> chrisccoulson, nope, he is gone
[19:34] <chrisccoulson> kenvandine, yeah, i thought so. i thought i would just try my luck anyway ;)
[19:35]  * bjf -> lunch
[19:37] <dobey> JFo: i'm sure i will be astonished by said mashup :)
[19:41] <kenvandine> JFo, looking forward to hearing it!


[08:49] <ricotz> hello :), unfortunately the ppc64el and s390x builders are still not working smoothly
[09:23] <cjwatson> ricotz: We're already resetting failures every half an hour and it isn't helping.  I've filed a ticket
[09:25] <ricotz> cjwatson, alright, thank you


[00:16] <raidghost> How hard is it supposed to be to get iommu to work 100% successfully. Allready added iommu=on and intel_iommu=pt in kernel config, and update-grub, rebooted
[00:16] <raidghost> But still Error starting domain: unsupported configuration: host doesn't support passthrough of host PCI devices is the happy message ive got
[00:17] <raidghost> libvirt kvm
[05:35] <cpaelzer> good morning
[06:24] <samba35> can some one help me with some basic (???) problem ,i am trying add parameter in file /sys/bus/pci/devices/0000:01:00.0/driver/unbind but i am not able to edit /write to file even file permisson is 666 and it give message/error when i type file unbind
[06:24] <samba35> unbind: ERROR: cannot read `unbind' (Input/output error)
[06:25] <samba35> i am trying this on 16.04.4 and beta 18.04
[06:25] <samba35> what wrong i am doing
[06:26] <OpenTokix> samba35: What is your end goal with this operation, what are you trying to do?
[06:26] <samba35> i want to configure pci passthrough where i want to add device id to this file
[06:26] <samba35> i try echo command also
[09:30] <olivierb-> Hello everyone, imagine that I have an ubuntu xenial server with 2 net itfs which are on separate networks and for which 2 DHCP servers answer. Any clue why the "secondary" DNSes always take precedence over the ones received from the 1st/main itf ?
[09:31] <olivierb-> are there any options I need to set in the DHCP servers so that one always take precedence ? any other way to solve this ?
[09:39] <blackflow> olivierb-: should be possible to configure the dhcp client to disregard dns entries from one of the interfaces
[09:41] <blackflow> olivierb-: looking at the dhclient.conf manpage, theres interface { ... }  section where you could supply different options for different interfaces.
[09:56] <olivierb-> blackflow many thanks, will definitely have a look at this
[10:41] <OpenTokix> olivierb-: you can ignore dns-entries in your dhclient-config.
[13:24] <frickler> coreycb: oh, great, I've been meaning to ping you about neutron-dynamic-routing releases but it looks like you're already on it https://bugs.launchpad.net/bugs/1750121
[13:25] <coreycb> frickler: yes. i may not be able to upload until friday though as bionic is 1 day from release and in final freeze.
[13:25] <coreycb> thedac: fyi ^
[13:26] <frickler> coreycb: I'm more interested in the Pike update anyway, but no need to hurry, I do have local builds for now
[13:28] <coreycb> frickler: ok. it needs to land in pike+ releases first. definitely in progress though.
[14:01] <ahasenack> udebs, are they only used in the installer environment? Or somewhere else?
[14:01] <ahasenack> maybe in small devices, routers, that kind of thing?
[14:37] <hyperlumic> ahasenack: https://wiki.debian.org/udeb
[14:38] <hyperlumic> ahasenack: Looks like they're solely for the installer's use.
[14:38] <hyperlumic> I haven't seen them employed anywhere else, though that's hardly conclusive.
[14:38] <ahasenack> ok
[14:38] <ahasenack> I asked for more information in the bug report I got
[14:38] <ahasenack> about a missing symbol/link step in a udeb package
[14:58] <rbasak> nacc: git-ubuntu sync is scheduled in 90 minutes. Are you interested in attending these still?
[15:24] <dpb1> teward: you are famous: https://news.ycombinator.com/item?id=16921452
[15:29] <teward> I am?  What've I missed o.O
[15:29] <dpb1> teward: top comment on there is rbasak. :)
[15:30] <teward> ah, nice.
[15:30] <teward> :)
[15:39] <dpb1> teward: added an entry into the release notes, if you wanted to review or wordsmith: https://wiki.ubuntu.com/BionicBeaver/ReleaseNotes
[15:52] <dannax> hey!, Is there any up-to-date vagrant ppa? Just installed 1.9.1 from the repos and current version is 2.0.4
[15:54] <dpb1> dannax: bionic has 2.0.2
[15:55] <dannax> dpb1, thx!
[15:56] <nacc> rbasak: i can't today, I don't think
[15:56] <nacc> rbasak: in the future, yes
[15:57] <rbasak> nacc: OK. I think you should have an invite to your personal address.
[15:57] <nacc> rbasak: received thanks
[16:49] <ahasenack> I wonder where I can document in https://wiki.ubuntu.com/BionicBeaver/ReleaseNotes that cifs-utils (i.e., mount.cifs) now defaults to SMB2 or higher instead of SMB1
[16:49] <ahasenack> it's a client tool, but desktop isn't client necessarily
[16:50] <dpb1> ahasenack: just adding a 'samba' entry would be good enough
[16:50] <dpb1> under server
[16:51] <ahasenack> or maybe under "known issues", and link to the bug I am troubleshooting?
[16:55]  * ahasenack checks if that changed in artful already
[16:56] <Maxel> hi all. I'm back to trying to fix my boot partition. I've been running: dpkg --configure -a and getting part of the files rebuilt until I run out of space and empty older versions of the files in the boot partition
[16:57] <Maxel> I'm not actually sure what I'm doing or if I'm making progress, it will download one release newer each time I do this
[16:57] <dpb1> Maxel: can you clean up space in general first?
[16:57] <Maxel> I'm not sure what I should be tampering with on the boot partition
[16:58] <Maxel> I should preface this with I believe some time ago I stupidly deleted everythhing from my boot partition because apt upgrade wasn't working for me
[16:58] <Maxel> so I'm trying to get to a good state
[16:58] <dpb1> well, ya, that's not great
[16:58] <dpb1> :)
[16:59] <dpb1> Maxel: these tips: https://askubuntu.com/questions/345588/what-is-the-safest-way-to-clean-up-boot-partition
[16:59] <Maxel> luckily I haven't restarted the vm and I am hoping I can recover it
[16:59] <dpb1> honestly, read that over, it's good info
[16:59] <dpb1> even talks about what to do if you can't do it through apt
[17:01] <nacc> dpb1: TJ- has a script that does the right thing in general
[17:01] <nacc> let me see if i can find the link
[17:02] <nacc> http://iam.tj/projects/ubuntu/apt-autoremove-old-kernels
[17:03]  * dpb1 posts that as an answer
[17:04] <Maxel> nifty
[17:04] <Maxel> should I be able to run this in my current state however?
[17:04] <Maxel> where I deleted the actively running kernel?
[17:05] <dpb1> Maxel: that answer with 'Note: this is only if you can't use apt to clean up due to a 100% full /boot', I would read through and digest it
[17:05] <Maxel> oh, yeah down an answer. will do :)
[17:09] <Maxel> ok, I believe this is essentially what I am doing. one difference is flickerfly says to delete the old images while I'm just reducing them to 1 byte in size
[17:09] <Maxel> not sure if one way right or wrong
[17:14] <nacc> Maxel: no real difference, given the truncated image is unusable
[17:17] <teward> dpb1: looks good to me (for the release notes blurb).  thanks.
[17:21] <Maxel> ok, so I am going through the answer on askubuntu, and when I perform the apt-get -f install, it still doesn't have enough space
[17:21] <dpb1> Maxel: what are the numbers
[17:21] <dpb1> (df -h /boot)
[17:22] <Maxel> here: /dev/sdb1       472M  469M     0 100% /boot
[17:22] <dpb1> that is indeed small
[17:23] <Maxel> I don't remember defining the size on install
[17:23] <dpb1> du -ms /boot/* | sort -n | pastebinit
[17:23] <nacc> should be plenty big if autoremove is used
[17:25] <Maxel> whaaa, I had no idea pastebinit was built in
[17:25] <Maxel> slick
[17:25] <Maxel> http://paste.ubuntu.com/p/Wx3jrSFzZV/
[17:26] <nacc> Maxel: you can also do | nc termbin.com 9999
[17:26] <dpb1> ok, same thing you did to the kernel files, you need to do to the initrd, one at a time, oldest first.
[17:27] <Maxel> I've just been running this: echo "" | sudo tee /boot/*-4.4.0-{62,66,70,71,72,75,78,79,87,89,98,101,103,104,108}-*
[17:27] <Maxel> to clean everything up
[17:28] <dpb1> ok, that's fine, but it's missing your initrds it seems, unless you haven't ran it yet
[17:28] <dpb1> since that's where your space is going
[17:31] <Maxel> it truncates the initrd files, but when I run apt-get install, it re-downloads the files
[17:31] <nacc> Maxel: after you truncate the initrds, you should autoremove
[17:32] <nacc> then do an install, i think
[17:32] <Maxel> just apt-get autoremove you mean?
[17:32] <dpb1> sudo apt-get purge linux-image-<version>, or autoremove, if you can.
[17:34] <dpb1> ah right, the initrds are being generated again
[17:34] <dpb1> with your -f install
[17:34] <Maxel> autoremove seems to be working
[17:34] <nacc> basically, you have to tell apt to stop installing those broken packages
[17:34] <nacc> which will always put back all those files
[17:34] <nacc> autoremove gets rid of those unneeded packages
[17:38] <Maxel> ah ha, looks like it's in a good state finally
[17:38] <Maxel> now the kernel I'm currently running is still truncated though, I assume this would be an issue on boot?
[17:39] <Maxel> oh, err actually the initrd is there, but the other images are not
[17:39] <dpb1> sudo apt install --reinstall linux-image-<version>
[17:40] <dpb1> depending on which package it actually is there.  you want the full package name though
[17:40] <dpb1> on my box, I have linux-signed-image-4.4.0-121-generic
[17:41] <dpb1> and linux-image-4.4.0-121-generic
[17:43] <Maxel> neat, looks good, now I'll see if I can update
[17:46] <Maxel> so doing a apt-get upgrade I'm getting an error. grub failed to install 3 devices
[17:47] <dpb1> pastebin if you can
[17:49] <Maxel> it's pretty ugly: https://pastebin.com/UcqMkxWQ
[17:49] <Maxel> it has a ui for this error message
[17:50] <mtl_> Is upgrading to 18.04 as easy as just changing all "xenial" lines to "bionic" and running apt-get update && apt-get dist-upgrade
[17:50] <mtl_> Like in Debian
[17:51] <dpb1> sec there is a link
[17:51] <dpb1> https://help.ubuntu.com/community/Upgrades
[17:51] <mtl_> thanks
[17:52] <nacc> mtl_: you *can* do that, but d-r-u is 'better'
[17:53] <nacc> rbasak: how does the importer review look? I might have a few moments this aftenroon to refresh my cleanup MP
[17:56] <mtl_> nacc, my virtual server provider provides cloned ubuntu repositories, can you tell d-r-u to use them instead of official mirrors?
[17:56] <nacc> mtl_: no idea, sorry
[17:56] <mtl_> nacc, ok.
[17:57] <nacc> mtl_: VPS (by design) seems easier to create fresh, then migrate data then to upgrade in place
[17:57] <nacc> but that's my opinion
[17:58] <dpb1> I think d-r-u does a s/xenial/bionic/ more or less, it doesn't change the mirrors.  emphasis on think.
[17:58] <dpb1> it does remove non standard repos though, so... I wouldn't be surprised if I was wrong
[17:59] <nacc> yeah, i can't remember anymore
[17:59] <mtl_> I have the cheapest package and even snapshots are not available
[18:00] <teward> if it's a VPS then the answer I'd give is 'It Depends on the way it's Virtualized"
[18:00] <teward> if it's OpenVZ virtualized you should avoid upgrading entirely
[18:00] <mtl_> and I have lots of own configs.. :(
[18:00] <teward> if it's KVM then I'd say "YMMV, I'd suggest 'fresh systems' and then data migration."
[18:00] <nacc> teward: good point
[18:01] <mtl_> it's KVM
[18:11] <Maxel> this looks like the only note on the grub issue: https://askubuntu.com/questions/315207/grub-failed-to-install-to-the-following-devices-error-on-upgrade
[18:12] <Maxel> I'm not sure if I should stop the upgrade
[18:25] <Maxel> if I choose to not proceed from that grub error, it takes me back to a screen to decide which drives to install grub on
[18:25] <Maxel> where if I choose ok, goes back to the error screen
[18:36] <nacc> rbasak: dpb1: anything big come out of the g-u sync?
[18:46] <Maxel> how can I figure out which drive is designated boot?
[18:49] <sdeziel> Maxel: could you pastebin lsblk's output?
[18:50] <Maxel> I'm stuck in a loop of error saying it couldn't install grub, and then choosing which partitions to install it on
[18:50] <Maxel> I'm worried if I disable the drives I'm getting an error on that I wont be able to boot
[18:50] <sdeziel> Maxel: you generally don't want grub installed on a partition
[19:41] <rbasak> nacc: we skipped it
[19:50] <rbasak> nacc: the importer seems to be stuck on qt4-x11 and texlive-extra now.
[20:13] <nacc> rbasak: both are blacklisted now
[20:13] <nacc> rbasak: fyi
[20:13] <nacc> rbasak: so may be worth killing the import subjobs and seeing if it progresses
[20:59] <rbasak> nacc: did you blacklist them before, or just now?
[22:15] <nacc> rbasak: in master before i left
[22:16] <nacc> late-ish on Monday, so after your snap build presumably
[22:50] <rbasak> Ah, OK.
[22:50] <rbasak> I'll finish fixing the snap build tomorrow hopefully.
[22:56] <rbasak> dpb1, rharper: the alternate server installer URL could do with updating in https://wiki.ubuntu.com/BionicBeaver/ReleaseNotes#Ubuntu_Server
[23:00] <rbasak> Oh, it's not out yet.
[23:01] <nacc> rbasak: thanks -- yeah let me know if you need anything
[23:12] <dpb1> rbasak: yes, there will be a round of updates after they do final image builds (hope that is happening now)


[05:01] <blr> wgrant: cjwatson: if we can add tags to make it clear which part of the UI a given task refers to in the Launchpad:UI asana project, suspect that will be helpful (e.g. User Profile)
[09:35] <cjwatson> blr: ack
[10:31] <blr> cjwatson: context/getCodebrowseUrl is rendering with '?h=master', is there any way to just get the root?
[10:36] <cjwatson> blr: context/repository/getCodebrowseUrl
[10:37] <cjwatson> blr: I expect context in this case is a ref ...
[10:38] <cjwatson> so getCodebrowseUrl on a repository gives you the root, on a ref takes you straight to that ref, otherwise it ends up a bit strange
[10:42] <blr> cjwatson: awesome, that works nicely thanks
[10:44] <cjwatson> cool
[11:12] <wgrant> cjwatson: What do you think of the {Product,Distribution}.vcs design?
[11:13] <cjwatson> so I'd been sort of hoping that it could be avoided or made implicit somehow
[11:14] <cjwatson> we shouldn't be able to end up in states where the flag says git and there are only bzr branches, or vice versa
[11:14] <cjwatson> and I also think it should be possible to run both bzr dev focus and git default repo in parallel, for migration, which means that we need to be able to show both
[11:14] <cjwatson> at that point it is not clear to me what the vcs enum actually governs
[11:14] <wgrant> What value does showing both provide?
[11:14] <wgrant> eg. look at https://code.launchpad.net/launchpad
[11:15] <wgrant> It's confusing and I can't see a case where it would ever be desirable.
[11:15] <wgrant> The column probably just selects whether the code page shows bzr or git stuff by default.
[11:16] <cjwatson> I think if we aren't going to show both, we need some way to get at the default git repository for a project in the web UI that isn't /target
[11:16] <cjwatson> or, perhaps better, it should be impossible to set a default git repository for a target that doesn't have its vcs set to git
[11:16] <cjwatson> or something like that
[11:17] <cjwatson> we need to think through the migration path for a project
[11:17] <wgrant> Or someone has to click the git link if they run into a git default URL on a bzr-defaulting project.
[11:17] <cjwatson> the git link that doesn't exist yet, but yes
[11:17] <wgrant> Well yeah, once the page is split there will presumably be a link between the two halves :)
[11:18] <cjwatson> this ties into my hope to be able to make the canonical url for a default repo be (target, rootsite="code")
[11:18] <cjwatson> this only works if it's reliably shown there.  although I suppose we could do that only if vcs==git, but that starts being messy ...
[11:18] <wgrant> Is it as messy as showing both?
[11:19] <cjwatson> perhaps not
[11:19] <wgrant> The URLs already vary based on whether the repo is the default or not.
[11:19] <wgrant> Varying slightly further based on whether the *VCS* is the default doesn't seem out of the question.
[11:19] <cjwatson> this is true
[11:19] <cjwatson> so what's the URL for the default git repository on a bzr-defaulting project?
[11:19] <cjwatson> I suppose we could just send you to the unique name
[11:20] <wgrant> Right, I think the web URL is just the full URL in that case.
[11:20] <wgrant> But switching the +branches to the git view using the link at the top will also show it.
[11:20] <cjwatson> can you explain that last bit?
[11:20] <cjwatson> link at the top of where?
[11:21] <wgrant> There's some widget on the project code index which switches between the git and bzr views, defaulting to target.vcs.
[11:21] <wgrant> If target.vcs is bzr and you click on the git link, you'll presumably get the view you would get if the default was git.
[11:22] <cjwatson> I'd been working on Person:+repositories; perhaps that makes sense as a view name elsewhere as well
[11:22] <cjwatson> (or it could just be +git, but I wasn't sure if that would cause ambiguity problems)
[11:23] <wgrant> +repositories is a) realllly long and b) poor apt :(
[11:23] <wgrant> I'm not sure if +git can currently be implemented.
[11:23] <wgrant> I *think* it works, and there is one example somewhere, but I can't think what.
[11:23] <wgrant> +bug vs +bugs is just stupidity, not a technical limitation.
[11:24] <cjwatson> The only case where there's potential ambiguity is on Person itself, and the traversal there is sufficiently manual that we could probably manage to say zero remaining path elements => PersonGitView
[11:24] <wgrant> Yeah.
[11:24] <cjwatson> The reason I'd been going a little more general is that I was thinking of it as a good way to simplify things for bzr too
[11:24] <wgrant> Howso?
[11:25] <cjwatson> You could reasonably look as PersonProduct etc. as metaphorically a repository
[11:25] <wgrant> aaaaa
[11:25] <cjwatson> In the bzr sense too
[11:25] <cjwatson> And then code pages could suck a bit less
[11:25] <cjwatson> But I don't know if it's worthwhile
[11:25] <wgrant> I'm not quite sure.
[11:26] <cjwatson> Because you could see people who'd worked on a project recently, and then drill down from there to look at individual branches, rather than just getting a sea of branches
[11:26] <wgrant> So, convince me about your plan for eg. the project code index.
[11:26] <wgrant> Hm, true.
[11:26] <wgrant> But that's less interesting in the git future.
[11:27] <cjwatson> I think that should be approximately the git view, though.
[11:27] <wgrant> Yep.
[11:27] <cjwatson> So, I think I'm fine with the project code index being switchable; the dual view was admittedly (in the MP description) a stopgap
[11:28] <wgrant> Oh yeah, and it's a fine stopgap, because it still isn't quite clear how to do it properly.
[11:28] <cjwatson> It needs to be switchable on "Configure code hosting" or whatever replaces it (since +setbranch is series-specific)
[11:29] <wgrant> Do you have an idea on how to obviate Product.vcs, though?
[11:29] <wgrant> Ah yeah
[11:29] <wgrant> We discussed this on the call last week, sorry.
[11:29] <wgrant> Kit's working on a Product-wide +setbranch equivalent.
[11:29] <cjwatson> Right
[11:29] <cjwatson> So it's not so much that I have a clear plan as that I'm trying to understand how we avoid inconsistencies in yours :)
[11:30] <cjwatson> If the view switches then at least people have a clear incentive to set it to the right thing
[11:30] <wgrant> The default git repo URL is the only serious issue I see.
[11:30] <wgrant> And that's only an issue during migration.
[11:30] <cjwatson> If you're happy with a conditional canonical URL that depends on the vcs enum, I think that satisfies my concerns.
[11:31] <cjwatson> I just don't want to be stuck with the canonical URL being ugly forever.
[11:31] <wgrant> So, the canonical URL itself can't be that.
[11:31] <wgrant> We'll have to do something a bit magical.
[11:31] <wgrant> because eg. the API
[11:31] <wgrant> But maybe the web canonical_url can be different.
[11:34] <cjwatson> So, what's the preferred migration path for a project?  We have docs somewhere (say, a help popup) giving some advice on migrating to git (maybe an auto-importer in the magical future, but I remain to be convinced about the tractability of that for an entire set of branches without manual gardening).  You do that and push to the default repository path.  Product:+branches notices and gives you a view for git stuff, and maybe an AJAX ...
[11:34] <cjwatson> ... switcher to change over.  What do the view names become here?
[11:34] <wgrant> The easiest way is a query string on the end of +branches.
[11:34] <cjwatson> Or perhaps Product:+branches and Product:+git, and the default view depends on vcs?
[11:34] <wgrant> It's awkward, but currently we have no way to configure default view name very eaisly.
[11:35] <cjwatson> Hm.
[11:35] <wgrant> We could do it, though.
[11:35] <wgrant> It would require a small amount of infrastructure work.
[11:36] <wgrant> Auto-importer is difficult due to various gardening that can be required.
[11:36] <wgrant> eg. for LP I have to replace two whoamis to get something that git fsck is happy with (and thus GitHub will accept, for example).
[11:37] <cjwatson> I think my latest prototype reimplemented BranchListingView etc., but it would probably be possible to crowbar it all into the same view in order to support both.
[11:37] <cjwatson> Right, my experiences with converting stuff to git have all employed various bits of manual gardening.
[11:38] <cjwatson> Mostly using http://www.catb.org/~esr/reposurgeon/ once I discovered that it existed.
[11:38] <cjwatson> (Because this is the sort of job where having a DSL can really improve your life)
[11:39] <cjwatson> So I think I'm OK with the vcs plan; now that we've talked through it it makes a bit more sense to me.
[11:40] <wgrant> I think you click the code settings link, where you can get instructions on pushing to the other VCS.
[11:40] <wgrant> Once a repo exists for the other VCS, the default code listing grows a switcher.
[11:40] <cjwatson> Yeah, probably shouldn't clutter the default view with that sort of instructions.
[11:48] <wgrant> (what this doesn't handle is hiding the switcher once both types exist, but meh)
[11:52] <cjwatson> You could do that by deleting all the bzr branches.
[11:52] <cjwatson> Or something.
[11:52] <cjwatson> Except you probably wanted to keep MP history.
[11:53] <cjwatson> (I occasionally refer to years-old MP history in Launchpad ...)
[11:55] <wgrant> That's why we did git MPs a bit more sensibly, indeed.
[11:58] <cjwatson> "meh" seems like a reasonable disposal.
[11:58] <wgrant> Quite.
[11:58] <wgrant> I'm just thinking about where to put the default widget.
[11:59] <wgrant> I think ti would make sense to have it behind a link at the bottom of +edit, below the submit button, in what looks like an ignorable footer.
[11:59] <wgrant> Similar to the team ownership change view.
[12:01] <cjwatson> Shouldn't it be on Product:+setbranch?
[12:01] <wgrant> Yes, I was just thinking of the most obtuse and Launchpaddy place to put it.
[12:02] <wgrant> Product:+setbranch or equivalent is indeed where it should go in the real world.
[22:13] <bigjools> wgrant: what's the default size limit for P3As nowadays?
[22:14] <cjwatson> bigjools: 2 GiB for both public and private
[22:15] <bigjools> cjwatson: can that be upped for P3As?
[22:15] <bigjools> and hi :)
[22:18] <cjwatson> bigjools: wgrant generally processes tickets to raise limits on request pretty quickly
[22:18] <bigjools> cjwatson: the guys I work with say that it's annoying to have to do that and want to up the default
[22:19] <cjwatson> I'm sure it's possible, I think we should look at some stats for archive usage plotted against whether they're public or private, though
[22:21] <cjwatson> there might be a few possible fixes to that annoyance
[22:22] <bigjools> that would be nice :)