[08:46] <davmor2> Morning All :)
[08:47] <darizzle> morning
[08:47] <darizzle> its night in australia though
[08:47] <mvo> hey davmor2
[14:49] <mvo> sbeattie: is there a chance that you (or someone from the sru-verfication team) could do some update-manager verifications soonish? its nothing major, but would be nice to make the experience more smooth
[17:24] <sbeattie> mvo: is there a way to verify bug 364620 via adept_updater instead of update_manager?
[17:24] <ubot4> Launchpad bug 364620 in update-manager "guidance-power-manager remains installed for 8.04 -> 9.04 Kubuntu Upgrade" [Undecided,Fix committed] https://launchpad.net/bugs/364620
[18:03] <mvo> sbeattie: is the TEST CASE description not working (or not good enough?)
[18:05] <sbeattie> mvo: I didn't realize you were asking to reset to intrepid rather than hardy; it doesn't particularly smell authentic to me; I am currently trying jriddell's 8.04->9.04 kubuntu upgrade script modified to pull jaunty.tar.gz from jaunty-proposed.
[18:05] <sbeattie> mvo: I am having problems reproducing the early exit of bug 363500
[18:05] <ubot4> Launchpad bug 363500 in update-manager "update-manager jaunty partial upgrade exists silently" [Undecided,In progress] https://launchpad.net/bugs/363500
[18:14] <mvo> sbeattie: it affects both intrepid and hardy, but testing intrepid should be enough, its the same code-path for both
[18:15] <mvo> sbeattie: (that was for 364620)
[18:18] <sbeattie> mvo: sure. I just, as a general rule, try to minimize variation in my before and after test runs so as to try to make sure I'm only seeing differences in behavior due to the change I'm trying to verify.
[18:19] <mvo> sbeattie: right, that makes sense of course
[18:19] <mvo> sbeattie: I'm checkiing 363500 now - trouble reproducing means it just works for you :) ? no crashes
[18:19] <sbeattie> mvo: yeah, it just goes ahead and does updates.
[18:20] <sbeattie> but then, this is in a vm with no detectable nvidia hardware.
[18:20] <sbeattie> not sure if that matters.
[18:21] <sbeattie> also, what's 'update-manager --dist-upgrade' doing differently than just plain 'update-manager'?
[18:22] <mvo> sbeattie: update-manager will never remove package (it will hold them back)
[18:22] <mvo> sbeattie: but --dist-upgrade will, its what u-m runs when it says "partial upgrade"
[18:23] <sbeattie> ah, okay.
[18:36] <mvo> sbeattie: I updated the bugreport, turns out the code is cleverer (for #363500) the code is clever than I thought and it uses the updated nvidia-common (that made it into jaunty-final)
[18:45] <sbeattie> bah, X crashed.
 sbeattie: I updated the bugreport, turns out the code is cleverer (for #363500) the code is clever than I thought and it uses the updated nvidia-common (that made it into jaunty-final)
[18:47] <sbeattie> mvo: thanks, I'll look
[19:28] <brooksbp> hello
[19:28] <brooksbp> can someone please help me with an issue in compiling the kernel?
[19:28] <brooksbp> I ran into this problem...
[19:28] <brooksbp> strip:/usr/src/ubuntu-intrepid/debian/linux-image-2.6.27-9server//lib/modules/2.6.27-9-server/kernel/drivers/atm/ambassador.ko: File format not recognized
[19:28] <brooksbp> make[3]: *** [drivers/atm/ambassador.ko] Error 1
[19:28] <brooksbp> make[2]: *** [_modinst_] Error 2
[19:28] <brooksbp> make[1]: *** [sub-make] Error 2
[19:28] <brooksbp> make[1]: Leaving directory '/usr/src/ubuntu-intrepid'
[19:28] <brooksbp> make: *** [install-server] Error 2
[19:28] <brooksbp> I don't even need this driver... so how can I get around this and finish my build?