/srv/irclogs.ubuntu.com/2008/03/29/#ubuntu-devel.txt

sistpotyinfinity: unless lp confuses me again, now would be a good time to give back happy alex on lpia ;)00:06
Nafallohappy alex?00:07
sistpotyNafallo: see backlog00:07
sistpotyNafallo: (iow, the joke was already made)00:07
Nafallosistpoty: ah. I /lastlogged and couldn't see what you meant first. then I saw the "and" ;-)00:08
=== lutin is now known as Lutin
sistpotyor maybe lamont? (since infinity seems to be away)00:09
TomJaegerdpkg-buildpackage: source only upload: Debian-native package00:11
TomJaegerwhat did I do wrong?00:11
sistpotyTomJaeger: wrong name of orig.tar.gz, I assume (btw.: for such packing question I assume that #ubuntu-motu is more suited)00:12
TomJaegerokay, thanks00:12
=== elmo changed the topic of #ubuntu-devel to: Launchpad is going down from 00:55 UTC until 01:15 UTC for a code update || Archive: Feature Freeze, DocumentationStringFreeze | Ubuntu 8.04 LTS Beta released | Development of Ubuntu (not support, not application development on Ubuntu) | #ubuntu for support and general discussion for dapper/edgy/feisty/gutsy, #ubuntu+1 for hardy | #ubuntu-motu for getting involved in development | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for ht
* slangasek blinks00:42
ion_slangasek: Well, be thankful the limit isn't what it used to be in IRCnet. :-)00:45
slangasekoh, no, I'm just blinking at the downtime00:46
=== elmo changed the topic of #ubuntu-devel to: Archive: Feature Freeze, DocumentationStringFreeze | Ubuntu 8.04 LTS Beta released | Development of Ubuntu (not support, not application development on Ubuntu) | #ubuntu for support and general discussion for dapper/edgy/feisty/gutsy, #ubuntu+1 for hardy | #ubuntu-motu for getting involved in development | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://wiki.ubuntu.com/HelpingWithBugs
infinityOkay, so this is the first time (since I got a shiny new laptop with decent 3D) that I've run compiz instead of immediately switching back to metacity...01:16
infinityCan anyone tell me if I can "fix" the fact that the fancy 3D Alt-Tab switcher doesn't understand Shift-Alt-Tab to cycle backwards?01:17
sistpotyinfinity: I'd lie, if I say I could in case you'd give back alex and happy on lpia :P01:18
infinitysistpoty: I'd love to, if LP wasn't down.01:19
sistpotyinfinity: it still is?01:19
infinitysistpoty: Oh, it's back. :)01:19
sistpoty:)01:19
infinitysistpoty: So, how do I fix the compiz task switcher? :P01:20
james_winfinity: there are various plugins that provide alt-tab like switching, so it may be that one of them can do it.01:21
sistpotyinfinity: good question, I use KDE though, and I lied :P01:21
james_walthough the one that I have doesn't understand it01:21
infinityjames_w: Yeah, the default one seems to not know how to go backwards, which makes me grumpy.01:22
infinityjames_w: Given that every window manager (heck, every OS) I've used in the last decade could do so. :P01:22
james_winfinity: run ccsm01:22
james_winfinity: you may have to install it first01:22
infinitysimple-ccsm?01:22
james_wselect "Application switcher"01:22
james_wyou need the real thing I think01:23
james_wthe advanced button in simple-ccsm spawns it01:23
james_won the "Bindings" tab there is a "Prev window" setting, and it is unbound by default01:23
infinityGenius.01:24
infinityI've never looked at any of this before.01:24
infinityOf course, binding that should be the default, IMO, but I don't know how deeply I care about filing a bug to fix it this late.01:25
* infinity squeals with glee.01:26
infinityjames_w: You're my hero for the next 30 seconds.01:26
infinityjames_w: If you ever needed a favor from me, ASK FAST.01:26
james_wumm, umm...01:26
thomtoo slow01:28
ion_james_w: You had a chance to ask infinity's hand in marriage, and you blew it?01:31
james_wdammit01:32
james_wasac: I've found the problem you were having, apt-get source only responds to a source package name without a version. I think I can work around it by picking the first binary package out of debian/control. I think it's unlikely that the first package will have been added in that revision.01:37
nepbabuwhat's the status of launchpad?02:10
nepbabuis it rebooted and done it's maintenance? thanks :)02:10
james_wnepbabu: there is a #launchpad02:10
james_wlooks like it's all over though.02:11
nepbabujames_w: tia! but the SSL cert is invalid says ff02:11
james_wnepbabu: are you on firefox 3?02:12
nepbabujames_w: yes02:12
nepbabuff3b4 james_w02:12
james_wI don't know then, it works here02:12
nepbabuhmm..02:12
sistpotyany buildd admin still around who could give back hscolour and haddock on lpia?02:13
* sistpoty tries with highlighting the indirect members: elmo, Spads, lamont, Ng for the give-backs of hscolour and haddock on lpia :)02:18
TomJaegerCan somebody help me with bug #195953 ?02:43
ubotuLaunchpad bug 195953 in wacom-tools "Tablet input resolution tied to display resolution" [Medium,Triaged] https://launchpad.net/bugs/19595302:43
ion_There's the same problem with plain mice. I've been saying it should be fixed. :-)02:45
TomJaegerI'm just trying to get a new upstream version uploaded.  How would I go about getting sponsorship for the new version and do I need a freeze exception?02:53
protonchrisTomJaeger: take a look at https://wiki.ubuntu.com/SponsorshipProcess and https://wiki.ubuntu.com/FreezeExceptionProcess02:56
TomJaegerWow, that sounds complicated02:58
ScottK2TomJaeger: What package?02:58
TomJaegerwacom-tools02:58
ScottK2Is it bug fixes or new features?02:58
TomJaegerI don't know why nobody feels responsible for this02:58
TomJaegerbug fixes02:59
ScottK2TomJaeger: 20,000 packages and ~100 developers.  You do the math.02:59
andresjIs this the right channel to ask for somebody to apply a fix for a bug? https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/20855602:59
ubotuLaunchpad bug 208556 in qt4-x11 "qdbuscpp2xml uses moc-qt3 instead of moc-qt4" [Undecided,New]02:59
FujitsuScottK2: 100 developers, most of whom are inactive.02:59
ScottK2That too03:00
ScottK2TomJaeger: Since it's a Main package it's a rather simpler process.03:03
ScottK2TomJaeger: Is the release in Debian already?03:04
TomJaegerno03:04
ScottK2andresj: You will probably have more luck with that package on #kubuntu-devel03:04
alex-weejScottK2: s03:06
alex-weej"it's maths, jeremy"03:06
TomJaegerThe thing that bugs me is that all these procedures will take just a few minutes for someone who knows what they're doing, but will take me forever to figure out03:06
alex-weejTomJaeger: but once you've figured it out03:06
ScottK2TomJaeger: I can understand that, but the first thing it takes is motivation.03:07
alex-weejit's not like the people who can do it are sitting around scratching their backsides, they're busy on other things that they feel are more important03:07
ScottK2TomJaeger: I've got about a dozen things on my list to get done before release.  If I get to 4, I'll be lucky.03:07
andresjok, ScottK203:08
TomJaegerI'm more than happy doing things like tracking down bugs, providing patches and talking to upstream.  But trying to package that stupid package has been a complete nightmare so far.  I feel like my productivity there is close to zero.03:10
ScottK2OK.03:11
ScottK2I'd suggest focus on writing a bug that makes the case for why it's important and why it's safe.03:12
TomJaegerI've done that03:12
ScottK2TomJaeger: What bug?03:13
TomJaegerbug #19595303:13
ubotuLaunchpad bug 195953 in wacom-tools "Tablet input resolution tied to display resolution" [Medium,Triaged] https://launchpad.net/bugs/19595303:13
TomJaegerIf it doesn't get fixed, Tablet PCs are almost useless with hardy03:14
ScottK2Right.03:14
ScottK2slangasek: Would you please look at ^^^^ bug and give an opinion on if you'd accept a new wacom-tools version to fix it at this point?03:15
TomJaegerDo I know why the debdiff is so large? It's a complete mystery.  The diff between the two directories is 600k, and that's mainly autoconf stuff03:16
ScottK2TomJaeger: He's the Release Manager.03:16
slangasekScottK2: I would potentially accept *a* new wacom-tools version, but to know whether I'd accept *this* wacom-tools version it would have to go through the FFe process; and I probably wouldn't be the one to sponsor it myself, I think it'd be better to have it done by someone with more direct knowledge of the issues03:23
ScottK2slangasek: I understand.  I'm just looking for a rough idea of if it's worth pursuing.  Who'd be the core-dev best equipped to look into this?03:23
slangasekScottK2: bryce, maybe?03:25
slangaseki.e., Mr. Inkscape03:25
ScottK2Right.03:25
ScottK2slangasek: Thanks.03:25
ScottK2TomJaeger: Now you have an idea that this might be doable and who you want to discuss it with rather than worry overmuch about packaging it yourself.03:26
TomJaegerScottK, thanks03:27
brycehey slangasek I have something for you :-)04:27
bryceslangasek: http://people.ubuntu.com/~bryce/bisect/04:27
bryceslangasek: these are pre-git bisected -intel debs for testing.04:28
bryce(the page is still a work in progress)04:30
james_wbryce: how are you building them?04:32
brycejames_w: bunch of scripts04:32
brycejames_w: I'd gotten stuck down a rathole trying to get them to build in PPA, but PPA has turned out to be worthless for this04:33
james_wI was just wondering if you be able to basically run "git bisect run debuild"04:33
brycejames_w: well, ironically 'git bisect' never gets used04:33
james_wIt obviously wouldn't work just like that, but it's an interesting idea.04:34
james_wbryce: :-)04:34
bryceyeah basically I pull a bunch of info out of git log, sort the commit id's, then do a bunch of git reset's and such to cycle through them, plunk in debian/ dirs, debuild, pbuilder, rsync, and generate the web page04:35
ScottK2bryce: TomJaeger was here earlier looking at bug #195953 and hoping for someone to champion getting it uploaded.  slangasek pointed vaguely in your direction.04:38
ubotuLaunchpad bug 195953 in wacom-tools "Tablet input resolution tied to display resolution" [Medium,Triaged] https://launchpad.net/bugs/19595304:38
bryceScottK2: whoa that's an insanely huge debdiff04:41
brycerats, it crashed my ff304:42
ion_:-D04:42
TomJaegerbryce, the debdiff b/w 0.7.7.7 and 0.7.9.3 is more than 5M04:42
ion_A nice little 3.5 MiB debdiff.04:42
TomJaegerI made a little mistake in the "original" tarball there.  the doc directory should be one level further down.  Not that it changes anything about the size of the debdiff.04:45
brycehrm, well looks like it needs some additional packaging work before it can be put in04:45
slangasekTomJaeger: wait, why are you diffing 0.7.7.7 and 0.7.9.3 when hardy currently has 0.7.9.3?04:45
slangasekbryce: heh, my architecture is amd64, not i386...04:46
TomJaegerslangasek, just for comparison04:46
slangasekbryce: I think a git bisecting howto would've served me better :-)04:46
bryceslangasek: rats!!!04:46
bryceslangasek: back to the drawing board04:46
slangasekTomJaeger: erm, comparison of what, exactly? I don't see how 0.7.7.7 can be relevant here04:47
ion_git bisect is teh awesome. :-)04:48
TomJaegerslangasek, people are complaining about the size of the debdiff.  I'm just saying the last debdiff was even bigger.04:48
slangasekoh, I see04:48
jdongit's not the size of the debdiff that matters....04:48
TomJaegerthe issue seems to be that there is prebuilt stuff in the original tarball04:48
jdongit's the color of the pill that makes the debdiff easier to work with.04:48
ScottK2bryce: Yeah.  The packaging needs some work by someone who knows what they are doing (e.g. not me).05:11
=== elkbuntu_ is now known as elkbuntu
calchow long does it take for a bzr commit to show up in LP?05:57
jdongless than 30 minutes typically for the HTTP branch to be updated05:57
calcI did a commit 35m ago and it still isn't showing05:57
calcoh ok so it should be soon05:57
jdongthe SFTP/SSH developer one is instant of course05:58
calci did a ssh and its not showing up05:58
jdongyeah, typically for me it hasn't been more than 30 min05:58
calchmm i'll check it out somewhere and verify the commit made it05:58
calcwow this is taking a very long time to checkout06:02
Fujitsucalc: bzr-lp is particularly slow now; they're working on it.06:02
FujitsuIt'll be like this for another couple eof days, thought.06:03
calcFujitsu: ah ok06:03
FujitsuIf you use bzr+ssh, it should be quicker to update, but SFTP has to be checked to ensure you haven't uploaded evil stuff.06:03
calcyea i am using bzr+ssh06:04
calcok the commit is there, it just haven't shown up on the webpage06:04
jdongFujitsu: you mean it's *not* for my video collections?06:04
Fujitsujdong: Devastating, I know.06:04
TomJaegerI think I figured out all the different ways the debian maintainer messed with the original tarball. Things look much better now and the debdiff's down to 600k.06:09
=== andresj__ is now known as andresj
warp10Good morning06:38
=== asac_ is now known as asac
=== doko_ is now known as doko
=== hunger_t is now known as hunger
=== \sh_away is now known as \sh
tjaaltonyep, we really need the newer wacom-tools, but I never figured out how to compile it and pushed it forward. For some reason the Debian maintainer hasn't updated it, even though he promised to do it two months ago09:42
=== elkbuntu_ is now known as elkbuntu
asacjames_w: ah, good to know. thanks!11:08
pittitkamppeter_: shouldn't, but in the interest of not accidentally catching unrelated devices I'd transform the list as the existing script does11:22
pittiChipzz: gnu tar switch> right, I see; would break compatibility11:23
\shmoins pitti :)11:24
Chipzzpitti: and probably in quite a visible and especially *unwanted* way :S11:25
Chipzzpitti: as an unrelated data-point, I did man tar on my OSX system, to see which options would be different. And apparently OSX doesn't even ship BSD tar, it ships GNU tar instead. Now if even a BSD based system ships the GNU version, I very much doubt we'll want to ship the BSD version... ;)11:28
pittiChipzz: heh, indeed11:31
\shoh wow...it's a sunny day...11:32
=== evalles is now known as effie_jayx
Chipzzpitti: also, doesn't dpkg use tar internally? I'd hate to see the breakage that would cause..11:34
tjaaltonuh, so new upstream versions don't end up in quarantine11:45
tjaaltonI uploaded a new wacom-tools and thought it would end up in the queue11:46
StevenKBecause we aren't in a freeze11:48
Hobbseetjaalton: no, it's a trust system.11:49
Hobbseetjaalton: and you tend to get the Long Pointy Stick of DOOM!!!!!!!!!!!!!!!™ coming in your directino if you violate it badly.11:49
tjaaltonwell, trust me, this was needed :)11:49
tjaaltonthe old wacom-tools was broken with xserver 1.411:49
zorglu_q. before i found a channel with the ubuntu people which take care about all the server/mirror to store the .deb of ubuntu. i dont remember the name tho... anybody got suggestion?11:50
tjaaltonand the new one didn't build until Tom Jaeger fixed the issues11:50
\shasac: suddenly I see black holes with ff3 while browsing some pages...when I click on the pictures, they are display correctly...but embedded in the page they are black...11:54
pochuzorglu_: #ubuntu-mirrors12:04
zorglu_pochu: thanks12:05
Chipzz\sh: dunnow if it's related, but I've had FF beta4 do funny things for me on MacOSX too12:11
Chipzzlike only loading some of the images on a page12:11
ChipzzI didn't quite get "black holes", but rather the image with the alt tag displayed though12:12
Chipzzasac: ^^^ as a data point -> most likely an upstream issue12:13
Chipzz\sh: only happened to me after several days of browsing, and was fixed by a browser restart though12:14
asac\sh: thats the zoom level12:23
asacwe have to use in-source jpeg most likely12:23
asac(i know that its fixed that way, but i hoped to get the proper jpeg patch cherry-picked from firefox sources)12:23
\shasac: so the bug is known...12:24
asacyes12:25
asacits a blocker12:25
asacwe will revert to in-source jpeg if no solution is found12:25
\shasac: thx :) I was wondering if something was wrong on my side :)12:26
asac\sh: are those jpegs?12:26
\shasac: jepp12:27
asacok then its known12:27
\shbtw..is there any tool for metacity to configure its own compositing thingy?12:27
=== \sh is now known as \sh_away
Hobbseeazeem: ping?12:45
Hobbseeazeem: got a #debian-type question for you.12:45
j1mchi all, could anyone tell me if kubuntu has a set of targeted milestone bugs set up like ubuntu does ( https://launchpad.net/ubuntu/+milestone/ubuntu-8.04 )?12:50
j1mcmy guess would be no, but i wanted to check.12:50
Hobbseej1mc: it doens't - that's the complete list for all flavours (assuming they're all using it)12:50
j1mcHobbsee: thanks.12:51
Hobbseej1mc: see specs assigned to Riddell for the planned kubuntu stuff, though12:51
j1mcHobbsee: thanks again.  a question was asked about this in xubuntu-devel.  this is helpful information.12:52
Hobbseej1mc: xubuntu is free to add to that list, and discuss things with slangasek and other members of the release team, too12:53
j1mci will pass along that information. :)12:54
Hobbseebut please assign the bugs to some of your guys12:55
Hobbseeas you're responsible for them12:55
j1mcHobbsee: understood.  thanks.12:56
Hobbseeat least, that's hte way this all worked in gutsy.  i'm unsure if slangasek has changed protocol, as i haven't seen many non-canonical people involved in any areas of RM this cycle.12:56
azeemHobbsee: pong13:07
Hobbseeazeem: /query?13:08
azeemHobbsee: sure, but I'm probably not around long :-/13:08
Hobbseeazeem: no problem, hopefully it won't take long13:09
=== \sh_away is now known as \sh
lagaslangasek: i tried today's mythbuntu alternate disk and the udeb wasn't installed, despite it being  Priority: standard14:50
lagaslangasek: do you think you could take another look?14:53
lagaslangasek: or.. wait. when is the menu entry in d-i supposed to show up? right at the beginning or is it added later, eg after the base system was debootstrapped?14:58
=== tjaalton is now known as tjaalton_
lamontwhy do my shift and control keys not wokr anymore/16:26
* lamont applies the redmond solution16:28
lamontseb128: why doesn't my shift key love me anymore//  ditto for ctl...16:29
seb128hey lamont, dunno I'm not an xorg guy16:29
lamontheh16:29
lamontit's like gnome... ;-016:29
lamonthrm... emoticons screw up too...  amazing how much one uses the shift key...16:30
* lamont hits it with a rock16:30
kagouhey seb12816:31
Chipzzlamont: I read something about a fix for the "keys stuck" problem in X16:33
Chipzzlamont: there was a patch for that16:33
lamontChipzz: ah, cool16:33
Chipzzlamont: not sure if it got uploaded though16:33
Chipzzlamont: maybe that could possibly have the side-effect you're seeing?16:33
Chipzzlamont: the fix would be in the xorg-core package, so try downgrading that (you would also need to restart your X-server obviously)16:34
Chipzzlamont: lemme see if I can find the url in the backlog ;)16:34
wasabiThis "run this action now" dialog... may at least be putting power in my hands... but it's way too technical.16:35
wasabiPackage authentication failure of some sort.16:36
Chipzzlamont: https://launchpad.net/bugs/19421416:36
ubotuLaunchpad bug 194214 in xorg-server "Keys get "stuck" down" [Unknown,Confirmed]16:36
Chipzzlamont: hrrrm no mention of the patch being applied and uploaded yet; so that's probably not it16:37
lamontseb128: sometime, I should find out about the rising dominance of gnome-keyring-manager (or whatever the hell it is) and seahorse, and figure out what to add or remove from my sledgehammer-of-a-gnome-session16:38
lamontmaybe it's finally usable out of the box??16:39
* lamont wanders off for a while16:39
seb128lamont: the gnome-keyring new changes are cool ;-)16:40
slangaseklaga: ok, trying to take a look; it's possible that I have to set the priority to 'Standard' in the archive overrides rather than relying on what the package thinks, for that change I should probably check with cjwatson and pitti first18:46
slangaseklaga: right, it looks like the CD build takes the package priorities from the archive overrides, rather than looking inside the individual packages.  In that case, making it Priority: standard for the installer would require making it visible as Priority: standard for other install methods too, so that'll need more discussion; sorry for putting you to the effort18:53
calcRiddell: ping19:33
calcRiddell: does kde use shared-mime-data and associate programs via desktop files for mimetypes they claim to open?19:33
slangasektjaalton: ugh, 195953 should have gone through an FFe...19:48
slangasektjaalton: are you tracking this package then, to make sure there are no regressions?19:48
warrendhi19:50
warrendcan someone look at this bug? https://bugs.launchpad.net/ubuntu/+source/usplash/+bug/18876419:50
lagaslangasek: so are you going to talk to cjwatson/pitti or should i bug them myself?20:01
slangaseklaga: I'll talk to them (on Monday, I expect - I don't think either of them are around this weekend)20:04
lagaslangasek: thanks, that's much appreciated20:04
affluxdoes the livecd environment currently warn the user when he doesn't seem to have enough ram?20:46
affluxhm, I'll  better ask in -installer20:48
tjaaltonslangasek: yeah.. sorry about it :/20:49
tjaaltonslangasek: I'll monitor any issues with it, and actually the upload was broken so I'll fix it asap20:50
slangasektjaalton: ok :)20:52
tjaaltonhuh, this is strange.. it included wacom_drv.o, when it should have built .so20:55
tjaaltonbut building it locally generates only .so20:55
slangasekheh20:55
tjaaltonmaybe it's the default CFLAGS etc biting me again?20:55
slangasekthat would be strange if so20:56
slangaseka strange misfeature of the upstream build rules20:56
tjaaltonyep20:56
tjaaltonfound the bug.. now figuring out how to fix it21:02
tjaaltonfails to find the module dir21:03
tjaaltonhmmh, is 'elif -z "$FOO"' bashism? the wacom configure script seems to fail with '-z: command not found'21:21
ion_Probably missing 'test' or [ ].21:24
tjaaltonyep, test should do it, since all the other tests have it21:24
tjaaltonquality21:25
slangasekI don't think that's even a bashism, I think it's invalid shell21:26
tjaaltonright, bash fails too21:26
tjaaltonseems that no-one is using latest wacom :)21:26
tjaaltonor at least not reporting these upstream21:27
slangasekwell that's encouraging21:31
tjaaltonhehe21:34
tjaaltonanyway, a fix uploaded21:34
tjaaltonthe release is a month old, so the actual code should be quite solid :)21:35
slangasekhow do we know that, if no one's actually managing to build it successfully?21:36
tjaaltonslangasek: maybe they were built by hand?-) anyway, upstream is adamant about this being much better for xserver 1.4..21:38
tjaaltonbetter release21:38
\shkeescook / bryce: are you pushing inkscape 0.46 to hardy? editing pdfs sounds awesome :)21:47
=== \sh is now known as \sh_away
=== mjg59` is now known as mjg59
YokoZarI'm trying to track down a bug regarding Cyrillic input, but don't have a cyrillic keyboard...what's a good way to emulate that?22:00
ion_setxkbmap ru?22:01
YokoZarion_: the trouble is I don't really know what buttons to push, heh22:01
FujitsuThe GNOME keyboard layout setting thing shows the mapping when you select it.22:02
YokoZarFujitsu: ahh ok.  I should learn to look in obvious places, thanks.22:05
=== juliank0 is now known as juliank
sistpotyKeybuk | Mithrandir | doko: please give back haddock and hscolour on lpia, thanks22:52
dokosistpoty: can't do that: it's MANUALDEPWAIT23:01
sistpotydoko: what does that mean?23:01
Fujitsusistpoty: It'll automatically be retried when the dependency is available.23:03
sistpotyFujitsu: ah, thanks23:03
FujitsuMANUALDEPWAIT isn't manual at all. Isn't it great?23:04
sistpotyoh... haddock is already built... cool, but I don't see manualdepwait for hscolour on lpia?23:05
ScottK2Just for the record I'd like it noted that I'm self-censoring right now.23:05
sistpotyFujitsu: any clues about hscolour, and where I could see it being manualdepwait?23:07
Fujitsusistpoty: Looking.23:07
sistpotythanks23:08
Fujitsudoko: hppa and lpia failed to build; they're not MANUALDEPWAIT.23:09
sistpotydoko: ok, then please give back hscolour on lpia (hppa is no use to give back, we don't have ghc6 there)23:10
dokoFujitsu: according to  https://edge.launchpad.net/ubuntu/+source/haddock/0.8-2 both are "Dependency wait"23:10
Fujitsudoko: Ah, I speak of hscolour.23:11
sistpotydoko: that's haddock, and it's for gutsy (which I misread in the first place as well *g*)23:11
sistpoty(and for hppa...)23:11
dokosistpoty: done23:12
sistpotydoko: thanks!23:12
YokoZarIs there a reason why /usr/share/X11/locale/locale.dir  lists ru_RU.UTF-8/XLC_LOCALE  ru_RU.UTF-8  rather than en_US.UTF-8/XLC_LOCALE  ru_RU.UTF-8 ?23:22
slangasekbecause of KOI8, according to the diff.23:26
keescook\sh: yawp, been done: inkscape | 0.46-0ubuntu1   | hardy/main23:28
YokoZarslangasek: Which package is that?  It may be causing a rather old bug in Wine ~ cyrillic input: https://bugs.edge.launchpad.net/wine/+bug/6859423:28
ubotuLaunchpad bug 68594 in wine "No cyrillic input in apps under wine. " [Undecided,New]23:28
slangasekYokoZar: hrm? I'm talking about diff -u /usr/share/X11/locale/{en_US,ru_RU}.UTF-8/XLC_LOCALE23:32
slangasekI think you're unlikely to make a persuasive case that a wine bug should be fixed by *not* using the Russian KOI8 map23:33
slangasekand I'm not aware that XLC_LOCALE has anything to do with input anyway?23:34
YokoZarslangasek: I'm not sure why making the change fixed the problem earlier either.  Now, it looks like I can type Cyrillic characters in Wine's notepad (which is a UTF-8 app), but I don't have an ANSI app to test this on.  Wine's free fonts just started supporting Cyrillic letters too.23:35
slangasekif the problem was display of Cyrillic characters, then XLC_LOCALE would have some bearing23:37
YokoZarslangasek: that makes sense.  I'll close the bug23:38

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!