| === asac_ is now known as asac | ||
| === ara_ is now known as ara | ||
| davmor2 | /join #ubuntu-devel | 12:40 |
|---|---|---|
| cr3 | ara: ping, are you observing the same behavior as me when running the update system desktop test: only runs one, fails subsequent times | 15:01 |
| ara | cr3: not me | 15:02 |
| ara | cr3: does it always happen to you? | 15:02 |
| cr3 | ara: yep, I'll just confirm that once again.. sec | 15:04 |
| ara | cr3: It is because it waits for the policykit | 15:06 |
| ara | cr3: gksu | 15:06 |
| ara | cr3: and it does not appear again. I will change the test to bypass that in case the sudo user is already identified | 15:07 |
| cr3 | ara: desktop testing is a pain, isn't it :) | 15:09 |
| ara | cr3: :-) | 15:09 |
| cr3 | ara: maybe there should be a gksu component in your suite, so that other applications don't have to remember to perform that logic | 15:10 |
| cr3 | ara: ok, so after rebooting, the test passes. seems like you put your finger on the problem | 15:10 |
| ara | is there already :-) | 15:10 |
| ara | cr3: one question I wanted to ask you about ubuntu-desktop-testing packaging branch | 15:10 |
| ara | cr3: is a branch from ubuntu-tests, therefore i can merge easily changes to it from ubuntu-tests, but to merge changes from testing-library i have to do it manually | 15:11 |
| ara | cr3: is there a way in bazaar to say that ubuntutesting folder in packaging branch actually comes from ubuntutesting folder from testing-library? | 15:11 |
| ara | cr3: that would keep the history when I merge changes | 15:12 |
| cr3 | ara: I thought we agreed that you would create a trunk for your project instead of maintaining two branches, have things changed since our conversation? | 15:13 |
| cr3 | if these are indeed two projects, then they should be identified as such in Launchpad as two projects. the current state of branches under the ubuntu-desktop-testing project is not what I would recommend. | 15:15 |
| ara | cr3: but you created packaging from ubuntu-tests. what do you recommend now? | 15:15 |
| cr3 | ara: after reviewing my branch, you were supposed to create a trunk from that branch which would've become the main series of your project | 15:16 |
| ara | cr3: mmm, ok. I was a bit confused about what we had decided in the end. OK, I'll do that | 15:17 |
| cr3 | ara: then, since the project would be packageable, I could've proposed to create a PPA for your project. that would be nice for your users :) | 15:17 |
| cr3 | ara: wait a sec, I wouldn't mind revisiting whether you are still comfortable with that | 15:17 |
| ara | cr3: no, i think is a good solution | 15:18 |
| ara | cr3: about the PPAs... they are already at https://launchpad.net/~apulido/+archive | 15:18 |
| cr3 | ara: first, are you still comfortable maintaining the library and the tests in the same codebase? when we discussed this, we thought it would be easier to maintain for now | 15:19 |
| cr3 | ara: second, since we are now considering inclusion in universe, are you still comfortable with the current names? | 15:20 |
| ara | cr3: about the names... maybe we should include 'desktop' in the package names | 15:22 |
| cr3 | ara: I agree | 15:22 |
| ara | cr3: i.e. ubuntu-desktop-tests & desktop-testing-library | 15:22 |
| cr3 | ara: also, can the code in the testing-library be considered a contrib to the upstream ldtp which could eventually make it in the upstream codebase? | 15:23 |
| ara | cr3: no, because it is not modifying the ldtp code. it is only a wrapper | 15:24 |
| ara | cr3: about having the same codebase... I have to think about it, because if we port the library to UME, we could reuse the tests. | 15:26 |
| ara | cr3: maybe we could leave as the same codebase for this cycle and, if later UME uses the library, then we could separate it in two projects for next cycle | 15:28 |
| ara | cr3: for this one it would be enough with one | 15:28 |
| cr3 | ara: I need to head to the datacenter and I will think about this some more on my way, mostly in respect to integration with checkbox | 15:29 |
| ara | cr3: ok, see you later | 15:29 |
| cr3 | or integration with anything for that matter :) | 15:29 |
| davmor2 | Is there a meeting tonight anyone? | 17:13 |
| === ogasawara_ is now known as ogasawara | ||
| gsd | Hey, I have a small issue.. I've been using intrepid for the past week and its been going smoothly, I just recently updated and I finished cutting my firmware for my wireless card (bcm43), so i did a reboot, now I am not able to login with the error "Authenticaton failed" I rebooted and went into recovery mode and changed my password, and I am still getting "authentication failed" when trying to log in. Any idea | 22:13 |
| slangasek | gsd: bug #259867 | 22:19 |
| slangasek | gsd: since you can't log in, you will have to reboot into recovery mode; my apologies for the breakage, a fixed package is on its way | 22:20 |
| gsd | Ah no problem, thanks. ;) | 22:20 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!