[02:27] <OvenWerks> is there a reason there are no beta 2 upgrade tests in the tracker?
[03:19] <OvenWerks> Ah, we have been respun again.
[03:36] <OvenWerks> I will have to resync
[08:09]  * smartboyhw adds upgrade builds to ISO QA Tracker
[08:10] <smartboyhw> OvenWerks, I've added upgrade builds to the ISO QA Tracker, please report results accordingly, I'm going to write the testing announcement now.
[08:26] <smartboyhw> Hmm, this announcement is getting a bit "Lubuntu" style-.-
[08:28] <smartboyhw> Or rather, balloons stlye
[08:28] <smartboyhw> *styl
[08:28] <smartboyhw> *style\
[08:28] <smartboyhw> *stlye
[08:28] <smartboyhw> *style
[08:28] <smartboyhw> GRRRR
[08:28] <knome> flood alert
[08:29] <smartboyhw> Sorry
[08:29] <smartboyhw> My typo is a bit serious today
[08:33] <smartboyhw> Hmm, for the title maybe it's a good idea to include statistics:P
[08:42] <smartboyhw> zsyncing the amd64 image now
[10:10]  * smartboyhw starts testing
[10:12] <smartboyhw> I'm not expecting too many problems (since OvenWerks thinks it's quite good)
[10:13] <smartboyhw> Really nice wallpaper
[10:18] <smartboyhw> Wait, a bug
[10:19] <smartboyhw> When I do the installation (not via live session), the wallpaper isn't using the new wallpaper
[10:19] <smartboyhw> Hmm.....
[10:19] <smartboyhw> I'm quite confident I saw the wallpaper during installation
[10:19] <smartboyhw> Oops, live session
[10:21] <smartboyhw> OvenWerks, can you confirm the bug for me?
[10:40] <smartboyhw> Bug 1229651
[10:43] <smartboyhw> Anyone can think of any reasons? Looked through the bzr branch, no idea
[10:47] <smartboyhw> Hmm, lightdm theme doesn't work either
[10:47] <smartboyhw> But the session itself works
[10:48] <smartboyhw> I'm thinking that the lightdm theme isn't updated
[10:49] <smartboyhw> Huh, but it is
[10:50] <smartboyhw> Hmm, wait
[10:51] <smartboyhw> zequence_, did you ask for a upload of ubuntustudio-lightdm-theme?
[10:51]  * smartboyhw checks
[10:51] <smartboyhw> Damn, Riddell didn't unblock everything
[10:51] <smartboyhw> Let me ask again
[11:15] <smartboyhw> Phew, unblocked
[11:15] <smartboyhw> Requesting respin
[11:25] <zequence_> smartboyhw: No, I didn't
[11:25] <smartboyhw> zequence_, eh?
[11:27] <zequence_> I'm just on my way out the dorr
[11:27] <zequence_> Maybe some could arrange that?
[11:27] <zequence_> Though, not sure if it's needed.
[11:30] <smartboyhw> OvenWerks, zequence_ I'm respinning
[12:22] <smartboyhw> DarkEra, OvenWerks zequence_ please update your images to 20130924.1
[12:49] <smartboyhw> Hmm, the bug still hasn't been fixed. Let me see if lightdm-theme is happening wrongly
[12:49] <smartboyhw> I'm guessing it is a ubiquity bug
[12:57] <smartboyhw> Yeah! Found the place for the fix!
[12:58] <smartboyhw> zequence_, do you think it would be appropriate to respin only because of Bug 1229651?
[13:00] <smartboyhw> I don't think so:P
[13:17] <OvenWerks> smartboyhw: I don't know where the wallpaper isset for the installonly session.
[13:17] <smartboyhw> OvenWerks, ubiquity
[13:17] <smartboyhw> Which the fix just went in.
[13:17] <smartboyhw> (But not uploaded)
[13:17] <smartboyhw> OvenWerks, you want a respin for that?
[13:17] <OvenWerks> Ok, the slide show was not updated either so that is ok
[13:18] <smartboyhw> OvenWerks, eh? Is the slideshow planned for an update soon?
[13:18] <OvenWerks> in T
[13:18] <smartboyhw> OvenWerks, that's a long way away, and now I'm not getting what your "OK" meant;P
[13:18] <OvenWerks> normally we do at least new first and last slides with the new backdrop
[13:19] <OvenWerks> ok to just leave it I think
[13:19] <smartboyhw> OvenWerks, ah
[13:19] <smartboyhw> Let's just update it later;P
[13:20] <OvenWerks> We need to have a list of places to do the backdrop. Maybe use a link
[13:31] <smartboyhw> OvenWerks, what a nice Virtualbox sound quality;p
[13:32] <smartboyhw> I can declare the image passed.
[13:32] <smartboyhw> Now, the upgrades (sigh)
[13:34] <smartboyhw> amd64 image marked as ready
[13:54] <OvenWerks> Yup setting and lightdm-theme made it to the wild since lastnight
[14:02] <OvenWerks> ok, upgrade i386 from terminal has passed. I will do resyncs for other tests tonight. Bye all
[14:03] <smartboyhw> Hello madeinkobaia :)
[14:03] <smartboyhw> OvenWerks, awesome
[14:04]  * smartboyhw decides to do image testing first
[14:04] <smartboyhw> image upgrade testing, sorry
[14:05] <smartboyhw> The terminal upgrades will simply have to wait
[14:21] <madeinkobaia> Hi all, hi smartboyhw :)
[21:12] <OvenWerks> zequence_: I added a bluprint for installer. Feel free to change almost anything about it. I am most wanting to make sure I have the things I want to change listed.
[21:13] <OvenWerks> zequence_: Also, whats with: http://status.ubuntu.com/ubuntu-s/ubuntustudio-dev.html ?
[21:13] <OvenWerks> none of the items look like ours at all.
[21:14] <OvenWerks> As if it points at the wrong blueprints
[21:14]  * OvenWerks is off to pick up a son from school...
[21:47] <OvenWerks> the new respin.... seems to have picked up lightdm-theme but not settings :P
[21:50] <OvenWerks> I am guessing this will only affect the live session and not the install, as the upgrade was fine.
[22:45] <zequence_> OvenWerks: none of our blueprints are in there anymore. We don't really need to do that
[22:45] <zequence_> OvenWerks: Important thing is we know ourselves what we need to do
[22:45] <zequence_> no idea why it is showing all those other stuff
[22:47] <zequence_> might be because ubuntu-motu is a member for ubuntustudio-dev
[22:48] <zequence_> OvenWerks: You got the idea on how I had planned to do the blueprints. There's no big hurry though. I'm still working on that, and doing an announcement later on what the deal is
[22:52] <zequence_> OvenWerks: I only changed the name to ubuntustudio-installer-t, as all our blueprints might as well be Ubuntu release based. Meaning, we work to achieve a set of goals for each cycle
[22:52] <zequence_> Well, also the approver to ubuntustudio-core and the drafter to ubuntustudio-dev
[22:53] <zequence_> ..another reason for the blueprint name is you can't have several blueprints with the same name
[22:54] <OvenWerks> zequence_: no problem thankyou for fixing.
[22:54] <zequence_> it's quite possible to have several blueprints for each project. And theydon't need to be dependencies of the main ubuntustudio project
[22:54] <zequence_> we also don't need to have bluieprints for each and every project
[22:54] <OvenWerks> I could see that
[22:54] <zequence_> only those we want to work on
[22:55] <OvenWerks> Ya, but I think these are things that need to be fixed. The ones with my name are mostly done, just waiting for saucy to be out of the way
[22:56] <zequence_> OvenWerks: Wouldn't it be better it showed installed packages being toggled?
[22:56] <OvenWerks> zequence_: did you see my email?
[22:58] <OvenWerks> I could I guess. That may give the user the idea they can use this utility to remove things too.
[22:58] <zequence_> OvenWerks: Would be better, I think
[22:58] <OvenWerks> This would be problematic with our metas as it would remove the meta but not it's depends
[22:58] <zequence_> OvenWerks: Also, why should it exit, if there's nothing to install?
[22:59] <OvenWerks> It exits with a dialog telling the user there is nothing in the list to install
[23:00] <zequence_> The way metas are handled is not a installer problem. It's how apt works
[23:00] <zequence_> If you want it to uninstall everything depending on the metas, you should add something to allow for that to happen, or just let it funtion the way apt does
[23:00] <OvenWerks> So rather than showing an empty list it shows a box with an explanation of why there is nothing to display.
[23:01] <zequence-work> When is there nothing to install?
[23:01] <OvenWerks> uninstalls would be messy.
[23:01] <OvenWerks> There is nothing to install if all the possibilities are already installed
[23:01] <zequence-work> Ok, so it's an installer. But not an uninstaller?
[23:02] <zequence-work> Doesnt make much sense, does it?
[23:02] <OvenWerks> One step at a time.
[23:02] <OvenWerks> Once I have finished what I have, I can look at uninstalling
[23:03] <OvenWerks> there are people who have hinted they would like to be able to uninstall whatever the meta installed
[23:03] <zequence-work> OvenWerks: One thing that you might want to add, if you haven't already, is do an apt-get update before even reading the available packages
[23:03] <zequence-work> OvenWerks: If there's no update before, some packages might fail to install - as they might have been updated since berfore
[23:04] <zequence-work> This is a problem with Ubuntu Software Center, believe it or not
[23:04] <OvenWerks> For that matter could add a place for adding ppas
[23:05] <OvenWerks> But ya, update might be good, I already add some activity indication in there so it should be ok.
[23:05] <zequence-work> OvenWerks: The gnome2 overrides could be from the old Gnome days, but not sure.
[23:07] <OvenWerks> I will have a look through the change log sometime.
[23:08] <zequence-work> OvenWerks: I added a workitem for it. Might be good to do the apt-get update after accepting changes instead. This way opening the app will be faster. The only thing I'm concerned about is the first ever time you try to install something, if there is a database of packages for apt at all. Never checked that.
[23:09] <zequence-work> I'd rather we work at making it able to install/uninstall
[23:09] <zequence-work> and no matter if it removes the depencies for a meta. Each package will show anyway
[23:09] <zequence-work> That could be fixed later, if wanted
[23:10] <zequence-work> Also, if there are no packages to install/uninstall, that sounds more like an error. Like starting the application without arguments, or on a system that doesn't use apt and doesn't have packages with those name
[23:13] <zequence-work> What I meant was, making it able to remove dependencies for a meta could be fixed later