[13:59] <bhuvan> any bzr expert around?
[13:59] <bhuvan> when i do bzr commit bzr+ssh://bhuvan@bazaar.launchpad.net/~ubuntu-core-doc/ubuntu-doc/ubuntu-karmic
[13:59] <bhuvan> bzr: ERROR: Cannot lock LockDir(http://bazaar.launchpad.net/%7Eubuntu-core-doc/ubuntu-doc/ubuntu-karmic/.bzr/branch/lock): Transport operation not possible: http does not support mkdir()
[13:59] <bhuvan> i'm facing that error, any clue on why it occurs?
[14:00] <bhuvan> bzr break-lock didnt help
[14:04] <jpds> You're suppose to just 'bzr commit' and then 'bzr push' to that location.
[14:04] <sommer> bhuvan: are you ssh keys on LP up to date?
[14:04] <sommer> bhuvan: I think you get different error when that happens though
[14:04] <bhuvan> sommer: i think so. i did not change it et all
[14:05] <bhuvan> i suspected the issue is because i co using http, i changed .bzr/branch/branch.conf and set as bzr+ssh
[14:05] <jpds> Why it's saying http:// when you're using bzr+shh:// I don't know.
[14:05] <bhuvan> now when i did bzr commit it complains:
[14:05] <bhuvan> Permission denied (publickey).
[14:05] <bhuvan> bzr: ERROR: Connection closed: please check connectivity and permissions (and try -Dhpss if further diagnosis is required)
[14:06] <sommer> bhuvan: maybe try re-uploading your key?
[14:06] <bhuvan> jpds, i think it was because i checked out using http://
[14:06] <bhuvan> ok, will do sommer
[14:10] <sommer> bhuvan: ya, I usually just do bzr branch lp:ubuntu-doc, then bzr commit followed by bzr push to commit up to LP
[14:11] <sommer> bhuvan: you can also bind to the branch, but if you remember to do bzr pull before committing any changes it's pretty much the same thing... from what I understand anyway :)
[14:12] <bhuvan> sommer: re-uploading the key seem to help
[14:12] <bhuvan> bzr commit says ... Committed revision 258.
[14:12] <bhuvan> bzr push says ... No new revisions to push.
[14:13] <bhuvan> sommer: do you think
[14:13] <bhuvan>  i'm alright?
[14:13] <sommer> bhuvan: did you make any changes?
[14:13] <bhuvan> yes to mail.xml
[14:14] <sommer> bhuvan: try bzr push lp:ubuntu-doc
[14:14] <sommer> maybe it just needs to know where to push
[14:16] <bhuvan> sommer: i'll try it. righ tnow, i'm doing bzr branch lp:ubuntu-doc
[14:16] <bhuvan> once it is complete, i will run bzr push lp:ubuntu-doc
[14:16] <bhuvan> thanks!
[14:20] <sommer> bhuvan: np
[19:53] <mdke> bhuvan: no, not lp:ubuntu-doc - we are in string freeze so you need to commit to the karmic branch only
[19:53] <mdke> sommer: ^^
[19:55] <sommer> oh right, I guess I assumed lp:ubuntu-doc was now karmic
[19:55] <mdke> I'll change it shortly
[19:55] <sommer> party!
[22:08] <LaserJock> hola
[22:08] <LaserJock> anybody around this time o' day?
[22:09] <mdke> LaserJock: yep
[22:09] <LaserJock> oh, you're still up
[22:09] <mdke> LaserJock: to reply to your last in -devel
[22:10] <mdke> LaserJock: you'll need to ship them with the doc itself
[22:10] <LaserJock> I got to looking at what you guys were doing a bit more in depth
[22:10] <mdke> LaserJock: if you use /usr/share/edubuntu-docs, it won't work
[22:10] <LaserJock> I'm not sure why you're symlinking "libs" but it's a bit interesting
[22:10] <mdke> LaserJock: go ahead
[22:11] <LaserJock> well, basically ubuntu-doc is taking an exclusive lock on "libs" which has been a fairly generic directory in the past
[22:12] <mdke> LaserJock: yes, it doesn't really account for derivatives which also use Gnome, I suppose
[22:12] <LaserJock> if one installs the new ubuntu-docs and *then* installs edubuntu-docs then it'd be fine I guess, but it's a bit hackish it seems
[22:12] <mdke> and which might not use ubuntu-docs
[22:13] <LaserJock> for me it's not much of a problem as Edubuntu only has one doc
[22:13] <LaserJock> but it might be something to think about in the future
[22:13] <mdke> yes, we should think that through and clean things up a bit for karmic
[22:14] <mdke> do you have an easy alternative solution? I guess the other way around may work better (ship /usr/share/gnome/help/libs/ and symlink from /usr/share/ubuntu-docs/libs)
[22:15] <LaserJock> well
[22:15] <LaserJock> what was the point of doing the symlinking?
[22:16] <LaserJock> we used to just dump in /usr/share/gnome/help/libs/
[22:17] <mdke> I can't remember what the reasoning was :(
[22:18] <mdke> probably there was some, even if twisted
[22:18] <LaserJock> well, I would have maybe called it ubuntu-libs and left the "libs" as generic if you had a particular purpose for symlinking
[22:19] <mdke> off the top of my head, I can't think of a reason for having /usr/share/ubuntu-docs at all
[22:19] <mdke> maybe I'm missing something
[22:20] <mdke> presumably ubuntu-serverguide uses it
[22:20] <mdke> I'll certainly take a look at these issues in the next release
[22:22] <LaserJock> well, in any case I can fix the immediate issue
[22:23] <LaserJock> my problem is how to deal with a package that hasn't been updated in 1 year and trying to get it all to work in one shot
[22:24]  * mdke nods
[22:24] <mdke> LaserJock: sorry if the symlink has increased that pain
[22:25] <LaserJock> well, the only thing I'm wondering about is translations
[22:25] <mdke> https://translations.edge.launchpad.net/ubuntu/jaunty/+source/edubuntu-docs
[22:26] <mdke> quite a few templates there :(
[22:26] <LaserJock> are the .ents translated?
[22:26] <mdke> they are transposed directly into the translated xml
[22:27] <mdke> i.e. the translated xml files don't use .ents
[22:29] <LaserJock> ok
[22:29] <LaserJock> so it just comes down to me needing to move my 2 files somewhere else
[22:29] <LaserJock> I guess if the structure is /usr/share/gnome/help/$$doc/$$lang/ then I could put the .ents in usr/share/gnome/help/$$doc/
[22:30] <mdke> what I think you should do is to put the ents directly inside the xml file for the relevant document
[22:30] <LaserJock> ah, well, yeah, I could do that too ;-)
[22:30] <LaserJock> heh, they are all of 8 lines
[22:31] <LaserJock> yeah, that's pretty ridiculous to separate out anyway
[22:31] <mdke> LaserJock: you can eliminate any ents which aren't actually used
[22:32] <mdke> if you have time :)
[22:32] <mdke> then regenerate the pot files for safe keeping
[22:32] <mdke> but no strings should change
[22:38] <LaserJock> it's ok for the pot to change a little isn't it?
[22:38] <LaserJock> I need to get "Hardy" and "8.04" updated to "Jaunty" and "9.04"
[22:39] <mdke> LaserJock: yeah, for serious typos like that it's ok, but notify the translators so that they can update the translations if they wish
[22:42] <mdke> LaserJock: that is, assuming that you'll be downloading the translations before Jaunty release :)
[22:48] <LaserJock> ah crap
[22:48] <LaserJock> this is just not going to be easy
[22:48] <mdke> hmm?
[22:50] <LaserJock> right now I can't generate a .pot correctly
[22:50] <mdke> error?
[22:50] <LaserJock> it spits out one giant msgid
[22:51] <mdke> whuahu?
[22:51] <LaserJock> well, I could just grab the .pots off of LP
[22:51] <LaserJock> and s/Hardy/Jaunty/
[22:52] <mdke> then they wouldn't fit the xml
[22:52] <LaserJock> presumably
[22:52] <LaserJock> well, it would fit the xml, just not the .pot generated from the xml
[22:53] <mdke> I'm not sure
[22:54] <LaserJock> hmmpf, get-pot.sh is the same between the two
[22:54] <mdke> sorry?
[22:58] <mdke> ok, I've got to crash now, catch up tomorrow