[07:03] <ara> good morning all :)
[08:52]  * ara reboots
=== mdz_ is now known as mdz
[09:23]  * mvo hugs sbeattie for the sru-versifcations on u-m
[09:33] <ara> mvo: ping
[09:34] <mvo> hello ara
[09:34] <ara> mvo: hey! I am having a broken dependency issue while partial upgrading my jaunty installation
[09:35] <ara> mvo: http://paste.ubuntu.com/159180/
[09:35]  * mvo looks
[09:36] <ara> mvo: the log seems at it had fixed the issue, but when I click on the button to start the upgrade, it just closes, and nothing it is done
[09:36] <mvo> ara: oh, that is a known bug (unfortuantely :/) - its fixed in my bzr tree and I plan to upload it today
[09:37] <ara> mvo: thanks :) (is there a bug number to subscribe to?)
[09:37] <mvo> bug 366048
[09:37] <ubot4> Launchpad bug 366048 in update-manager "update-manager crashes when upgrading cleanly re-installed box with jaunty RC to jaunty final" [Medium,Fix committed] https://launchpad.net/bugs/366048
[09:37] <ara> mvo: thanks :)
[09:37] <mvo> cheers :)
[09:42] <ara> mvo: I guess the fix is already in -proposed, isn't it?
[09:43] <mvo> ara: not yet, pitti did not want to accept it before the previous upload made it into -updates
[09:43] <mvo> but the sru-verfication seems to be pretty good so far
[09:43] <ara> mvo: ok :)
[10:13] <ara> thekorn: ping
[10:13] <thekorn> hi ara
[10:15] <ara> thekorn: just to let you know that desktop-testing-list (@gnome) is the list for discussing the work we are doing automating the desktop tests. i.e. there are people commenting on the buildout stuff that you did: http://mail.gnome.org/archives/desktop-testing-list/2009-April/msg00021.html
[10:15] <ara> thekorn: in case you're interested in subscribing
[10:16] <thekorn> ara, oh, thanks for letting me know, did not know about this list. I going to subscribe to this list now, and read the mails later today
[10:17] <ara> thekorn: :)
[10:26] <thekorn> ara, how are gnome-desktop-testing and ubuntu-desktop-testing related?
[10:27] <thekorn> is u-d-testing a fork, are changes synced betwenn both projects?
[10:27] <thekorn> or are they the same?
[10:28] <ara> u-d-t is a fork, that contains ubuntu.py (AND gnome.py). so it contains the same tests that gnome.py has + some particular tests for ubuntu applications
[10:29] <ara> the syncing between both projects is still a bit messy. We should make it a topic to discuss in the UDS
[10:36] <thekorn> ok, thanks
[10:45] <ara> jcollado: hey
[10:45] <jcollado> ara: HI
[10:46] <ara> jcollado: I am starting to review the testsuite branch
[10:46] <jcollado> ara: Thanks
[10:46] <ara> jcollado: one question, why do we have per application testsuite classes?
[10:47] <jcollado> ara: If we have different setup/cleanup/teardown methods it should be needed.
[10:47] <jcollado> ara: It depends on the test suite
[10:49] <ara> jcollado: but, if you have several applications per testsuite?
[10:49] <ara> jcollado: where do you define the setup/cleanup/teardown methods?
[10:50] <jcollado> ara: You can use a generic test suite such as SingleApplicationTestSuite
[10:50] <jcollado> ara: or create a custom one if it doesn't fit your needs
[10:53] <ara> jcollado: ok, thanks
[10:54] <jcollado> thekorn: Since I see that you weren't subscribed to the maillist, please look into http://mail.gnome.org/archives/desktop-testing-list/2009-April/msg00021.html, I had a couple of concerns regarding using buildout
[10:55] <jcollado> Mainly it seem that buildout depends on setuptools, but the packaging tools for debian depend on distutils
[10:55] <jcollado> so I'm not sure if that could be a problem
[10:56] <thekorn> jcollado, will read this mail and follow up on it a bit later today, I'm a bit busy right now.
[10:56] <jcollado> thekorn: Sure, no problem
[10:57] <thekorn> using distutils in a buildout environment is fine, because the egg receipe is creating development eggs
[10:57] <thekorn> and no `real` eggs, so using setuptools is optional
[11:16] <ara> jcollado: setup.py should be updated as well to reflect the new modules (desktoptesting/application desktoptesting/test_suite)
[11:18] <jcollado> ara: Yes, you're right. I'll take a look at this
[11:19] <eeejay> cool, udt is getting some love
=== thekorn_ is now known as thekorn
[11:40] <ara> jcollado: just this change, would do the trick:
[11:40] <ara> -    packages = ["desktoptesting"],
[11:40] <ara> +    packages = ["desktoptesting", "desktoptesting/test_suite", "desktoptesting/application"],
[11:40] <jcollado> ara: Thanks
[11:46] <eeejay> ara, jcollado: are you fragmenting gnome.py?
[11:47] <ara> eeejay: not me. I have been busy with jaunty release. I am trying catching up with gdt now
[11:47] <ara> eeejay: the msn pidging is starting to work, btw. I will try to have it finish by the end of the week
[11:47] <eeejay> ara: just wondering if the changes you and jcollado are talking about include fragmenting gnome.py, but i guess not
[11:48] <ara> eeejay: not, but that's a needed change, for sure
[11:48] <eeejay> ara: cool, i would like to start merging in my two testing branches, "dx", and "pidgin"
[11:48] <jcollado> eeejay: Application class is being moved to main.py in test-suite-class branch. Is that what are you asking?
[11:49] <eeejay> jcollado: and where does Seahorse and GEdit live?
[11:49] <ara> jcollado: have a look to the pidgin branch. the change eeejay talks about is having a module per application
[11:50] <jcollado> eeejay: They stay in gnome.py
[12:37] <jpds> bdmurray: Could you possibly test the stuff for pitti at bug #236305 when you have time? Thanks.
[12:37] <ubot4> Launchpad bug 236305 in gnome-system-tools "Creating user with username 'admin' hoses admin group, sudo config" [Critical,Fix committed] https://launchpad.net/bugs/236305
[12:41]  * ara -> lunch
[14:10] <ara> jcollado: what folder structure you were thinking on for the framework? (I am talking about the move to /src)
[14:11] <ara> jcollado: src/ubuntu-desktop-test, src/desktoptesting, src/gedit, etc?
=== asac_ is now known as asac
[14:39] <thekorn> ara, I just repiled to the questions about buildout on the ML, this also contains a possible folder structure
[14:40] <jcollado> thekorn: Thanks for your response
[14:41] <jcollado> ara: I haven't thought it through. Let's follow the e-mail thread and I'm sure we'll get to a good solution
[14:41] <thekorn> no problem, I hope it's understandable
[14:41] <ara> thekorn: what packages are necessary to run bootstrap.py
[14:41] <ara> ?
[14:44] <thekorn> ara, python, that's all, if python-setuptools is not installed systemwide, bootstrap.py will get this file as an egg from pypi.python.org
[14:48] <ara> thekorn: I just tried (I didn't have python-setuptools in my system) and it didn't work. Installing python-setuptools solved the issue
[14:53] <ara> thekorn: so, in my case, I did need python-setuptools installed
[14:53] <thekorn> ara, ok, sorry my bad,
[14:55] <thekorn> ara, but you can easily achieve a situation where setuptools is automatically downloaded from pypi by using ez_setup
[14:56] <thekorn> but right, you need python-setuptools
[15:43] <ara> schwuk: can you point me to the url where you are writing the specification for the qa.u.c landing page?
[16:03]  * ara takes a quick break
[16:33] <schwuk> ara: no spec per se, but I set up this page: https://wiki.ubuntu.com/QATeam/HomePage
[16:39] <ara> schwuk: thanks
[16:41] <stgraber> ara: is Henrik on irc.c.c ? if so can you ask him to connect on freenode ?
[16:42] <ara> stgraber: he's on holidays all week
[16:42] <stgraber> ok, thanks
[16:42] <ara> stgraber: np
=== pace_t_zulu_ is now known as pace_t_zulu
[23:58] <questionb> hello