[12:42] hey chrisccoulson, my Firefox has just lost the global menu. Now I don't have any menus at all. Is there any quick way to fix this? [12:44] dpm - restart unity-panel-service :) [12:45] chrisccoulson, 'unity-panel-service: unrecognized service' [12:48] dpm - oh, "killall unity-panel-service" will restart it [12:50] chrisccoulson, hm, that restarted the panel, but firefox still has the same problem. After restarting FF, there is some progress: I can see global menus, but I cannot see the close, minimize and maximize buttons (and the FF window does not come up when I click on the icon in the launcher) [12:51] dpm, sounds like something else is broken in unity (bamf, maybe?) [12:51] you're probably better off just restarting your session [12:52] oh, bummer :( - thanks anyway chrisccoulson for your help [13:03] hi [13:04] hi [13:08] what's blocking FF8 on oneiric? [13:10] cousin_luigi, i'm not sure anymore :( [13:21] chrisccoulson: perhaps waiting for 8.01 to realease it? [13:26] cousin_luigi, i doubt it. 8.0.1 only fixes an issue specific to mac [13:27] chrisccoulson: who's in charge about this? [13:28] cousin_luigi, well, i prepare the updates, micahg publishes them [13:37] chrisccoulson: oh [13:38] and is there some problem with 8.0? [13:40] cousin_luigi, not AFAIK [13:42] you're not the only person asking this. people are asking the same questions on forums, askubuntu, and in my inbox as well, but i don't really have an answer [13:42] you'll need to ask micahg when he's around [13:44] chrisccoulson: ok, thanks [14:10] cousin_luigi: the updates are actively being worked on. there were some regressions that had to be addressed. aiui, they have and the updates are being tested. I believe they should be out sometime today [14:10] micahg: ^ please correct me if I am wrong [14:10] ok [14:10] yes, should be going out today [14:32] hallelujah!:) [14:36] cousin_luigi: sorry for the delay [14:43] :) [14:45] bbl [15:58] chrisccoulson: I need some help with bzr. Is there a wiki page or some docs on the process that is used for beta and release branches? [15:59] chrisccoulson: Not sure if that was a question for you or micahg [18:08] micahg: I think I did something wrong with my branches. I cannot figure out how to get the changes from the beta to the release branch. [18:08] joelesko: bzr merge /path/to/beta /path/to/release [18:09] joelesko: then collapse the changelog before committing [18:09] did they release 2.5? [18:09] Yes [18:09] ok [18:09] In the source repo. [18:09] sorry for not getting the beta uploaded, I've been swamped, will try to get 2.5 uploaded later this week [18:12] micahg: np. [18:13] I know it will not be done, but git is really great at managing branches. [18:14] ah, yeah, I think bzr can handle that inherently as well, it's just LP isn't quite set up to deal with it properly [18:17] I hope it will one day. I thought you used the bzr bundle command to track the atomic commits. [18:18] * micahg knows not of bzr bundle [18:19] Bundle will not work though with the way I did the branch in SM. Just not used to having seperate directories for each branch. Git can spoil. [18:19] git can spoil you, fast and easy [18:21] If I was reading it correctly, bzr bundle will bring all the commits from a dev branch to the release branch. That way if you want to remove just 1 commit in release, it would be easy [18:21] I was thinking that's what you were doing. === ]reed[ is now known as [reed] [18:57] micahg: sorry I was wrong. bundle looks just like merge. I was getting confused with the way git handles it. [19:27] good nite [20:14] micahg: I updated my dev branch for 2.5 from the beta branch. Do I need to propose for merge? [20:39] joelesko: yes