[03:57] <Linolium> hi all, I have a silly question
[03:57] <Linolium> does anyone here know about the linker ld?
[04:02] <persia> Linolium: You're better off asking your question directly.  While someone might know the answer to your specific question, few are foolhardy enough to admit to complete knowledge of ld, and this may or may not be the ideal forum.
[04:02] <brandonperry> I know everything about ld
[04:02] <brandonperry> :-P
[04:02] <pwnguin> what about gold?
[04:03] <brandonperry> I lie, I have only used it a couple times
[04:03] <Linolium> I am using ld for my generated code but it is giving jmp calls the wrong address  ie. 0x80000300 instead of 0x00000300  Does anyone know what ld option can fix this?
[04:03] <Linolium> my .map file contains .=(0x80000000+SIZEOF_HEADERS) which is the problem
[04:03] <Linolium> the code itself is in the correct location
[04:04] <persia> Linolium: That's a much better question.  You might want to specify the package on which you are working, and provide a pastebin of the build log to show context.
[04:05] <Linolium> I am working in windows aiming for taito f3 system that uses a MC68020 processecor
[04:05] <Linolium> using gcc's windows distro
[04:06] <Linolium> everything is fine except for the address relocation for jumps
[04:06] <Linolium> in the code
[04:06] <persia> Linolium: In that case, I suspect this isn't the best place to get the answer.  Unfortunately, I don't know which would be the correct forum.
[04:06] <Linolium> that is what I was afraid of
[04:06] <Linolium> :: sigh
[04:06] <Linolium> ::
[04:07] <Linolium> there doesn't seem to be any place that knows ld well :(
[04:07] <pwnguin> surely mingw has a channel
[04:07] <Linolium> dunno
[04:07] <Linolium> one would hope
[04:07] <pwnguin> or a linux devices or embedded channel
[04:08] <pwnguin> i bet one of the linksys firmware channels knows the right people
[04:08] <Linolium> ok
[04:08] <Linolium> well thanks
[04:08] <Linolium> it's time for me to sleep now
[04:08] <Linolium> I'll tackle this problem more tomorrow
[04:09] <pbn> hi
[04:09] <pbn> Linolium: you are simultating the Motorola 68020 in Windows ?
[04:10] <Linolium> mame
[04:10] <Linolium> :)
[04:10] <pbn> yes, mame :)
[04:10] <pbn> I was gonna say MAME already does that :)
[04:10] <Linolium> heh
[04:10] <pbn> doesn't it ?
[04:10] <Linolium> yeah
[04:10] <Linolium> it does
[04:10] <Linolium> well, up to my function calls
[04:10] <Linolium> hehe
[04:11] <pbn> ah, now I get it :)
[04:11] <pwnguin> wait, why not ask the mame people?
[04:11] <pbn> yeah
[04:11] <pwnguin> they're all over efnet
[04:11] <pbn> I was gonna say, ask the mame developers
[04:11] <pbn> yeah they're probably on efnet
[04:11] <Linolium> efnet #mame?
[04:11] <pbn> efnet #mame probably
[04:11] <Linolium> guessing
[04:11] <Linolium> ok
[04:11] <Linolium> thanks
[04:11] <Linolium> peace guys
[04:11] <alex1> hi guys. i've enabled hardy-propesed in software updates, but can't see the patched kernel in the list of packages to be updated? I want the latest patched kernel that should be in -proposed... what am i doing wrong?
[04:12] <persia> alex1: You are confusing linux with linux-meta and #ubuntu-devel with #ubuntu
[04:13] <alex1> err sorry yeah i should've asked in #ubuntu. linux-meta?
[04:15] <alex1> oh i see. https://launchpad.net/ubuntu/hardy/+source/linux-meta  thanks :)
[06:58] <dholbach> good morning
[08:20] <pitti> Good morning
[08:21] <dholbach> hi pitti
[08:21] <dholbach> hi mvo, thekorn
[08:21]  * Hobbsee crash-tackles pitti in greeting!
[08:21] <mvo> hey dholbach
[08:21] <mvo> hi pitti
[08:22] <pitti> tkamppeter: which "custom options" patch do you have in mind? why isn't it going into 1.4?
[08:22] <pitti> tkamppeter: please don't upload anything into Ubuntu yet
[08:22] <pitti> tkamppeter: (I mean cups)
[08:22] <pitti> tkamppeter: I wait until the cupsys -> cups rename makes it past Debian NEW
[08:23] <pitti> tkamppeter: of course feel free to commit stuff to the svn
[08:23] <pitti> Riddell: was on VAC on Friday; doko and I wanted to attack  MIR today
[08:23] <pitti> hey Hobbsee, hi dholbach!
[08:23] <pitti> *group hug*
[08:23] <Hobbsee> :)
[08:29]  * pitti hugs mvo, too
[08:32] <dave_> Interested in MOTU!
[08:34] <persia> dave_: Come to #ubuntu-motu !
[09:04] <thekorn> hello dholbach
[10:18] <pitti> asac: what's your feeling on bug 233922? ready for -updates? looks good from my POV so far?
[10:18] <wgrant> Don't we have RC2 now?
[10:19] <pitti> that's a different issue
[10:19] <pitti> the -proposed ones should go to -updates first
[10:19] <wgrant> Is it really safer to push two large changes to -updates than one larger one?
[10:20] <pitti> wgrant: we know that the current set is good
[10:20] <pitti> if we keep piling up new uploads in -proposed, testing all the changes gets too complicated
[10:20] <pitti> and we don't have -rc2 packages
[10:20] <wgrant> OK.
[10:25] <pitti> seb128: bonjou!
[10:25] <asac> wgrant: yeah RC2 should be much quicker
[10:25] <pitti> bonjour, even
[10:25] <asac> pitti: i'd say its good. ill go through the bug reports once more and let you know later
[10:25] <pitti> asac: cool, thanks
[10:25] <seb128> guten tag pitti
[10:28] <\sh> asac: rc1 is much faster then the orig hardy one
[10:29] <asac> \sh: hehe ... i referred to the time that is needed till it hits the archive ;)
[10:30] <asac> but yes, there have been additional performance boosts and a few more IO bustage fixes
[10:30] <Q-FUNK> to which package could I reassign Bug #236961 that would remotely make sense?
[10:30] <\sh> asac: oh...damn..I'm still lacking reality ;) free beer in a pub is nice but makes life a hell
[10:32] <Q-FUNK> same question for Bug #236732
[10:32] <asac> \sh: i know what you mean :)
[10:33] <pitti> Q-FUNK: installer errors -> debian-installer or ubiquity, upgrade errors -> the package that failed the upgrade, or if it is a bug in the upgrader itself, 'update-manager'
[10:33] <\sh> asac: but at least we won ;)
[10:34] <Q-FUNK> pitti: I regularly get people who presume that upgrade-system is a generic package name to report an upgrade failure. figuring out which package to reassing these 3 to is challenging.
[10:34] <cjwatson> Q-FUNK: looks like a dirty CD drive to me; a CD drive cleaning kit might well work wonders. I very much doubt it's an installer bug as such, because actual corrupt packages (as he's reporting) would happen to everyone. However, there's an outside chance that the kernel's driver for his CD is busted, in which case 'linux' would be the appropriate package
[10:34] <cjwatson> Q-FUNK: I doubt we can do anything about his problem in either debian-installer or ubiquity
[10:36] <Q-FUNK> cjwatson: looking at his bug, I'm thinking more of e general failure in his IDE controler, for which he is evidently blaming his upgrade.
[10:36] <cjwatson> Q-FUNK: could be; by "driver for his CD" I guess I was including everything in the relevant stack
[10:36] <Q-FUNK> cjwatson: replying to someone who already made up their mind thta whatever fried his hardware is our fault generally is a lost cause.
[10:37] <cjwatson> I'd probably include some advice about CD drive cleaning, and toss it over to linux in case they can make anything of it
[10:37] <cjwatson> it may be that there is at least something recoverable from dmesg
[10:41] <Q-FUNK> could be, indeed
[10:41] <dholbach> mvo: thanks for doing your share of sponsoring :)
[10:41] <mvo> dholbach: heh :) funny that you noticed
[10:41] <dholbach> mvo: I sure did :-)
[10:42]  * mvo hugs dholbach
[10:42]  * dholbach hugs super-soccer-mvo :)
[10:43]  * mvo is more super-keen-injury-mvo now :P
[10:51]  * ogra hrms about the kino bug dholbach just assigned to him
[10:52] <dholbach> ogra: what's wrong?
[10:53] <ogra> well, its unsolvable, dv1394 is going away in the kernel and Keybuk wont make udev create /dev/raw1394 with world permissions ...
[10:54] <ogra> its an ancient butg (might be a duplicate of a 4 digit ubuntu bugzilla bug even
[10:54] <dholbach> I can't do much about it
[10:54] <ogra> me neither
[10:55] <ogra> apart from changing the concept of ieee1394 completely :)
[10:55] <persia> ogra: juju juju juju
[10:55] <dholbach> if there's no other option at all to fix it, close it "won't fix" - I just wanted to get it through the sponsorship queue
[10:58] <highvoltage> ogra: would it be inappropriate to link to a wiki page explaining how a user could make their own udev rule, even if it's unsupported?
[10:59] <ogra> dholbach, wont fix will result in another bug agin ....
[10:59] <ogra> i'D like to quiten it down
[10:59] <ogra> highvoltage, sounds like an excellent idea, i tried to gather some info half a year ago for such a site
[11:00] <pitti> dholbach: bah, I never got a mail for bug 232452; #$*(#$
[11:00] <ogra> but didnt get any input (i dont own a dv cam)
[11:00] <dholbach> pitti: AFAIK the LP bug about "subscription to a bug should send a mail rightaway" is closed now - so it should work out better in the past
[11:01] <pitti> right
[11:01]  * dholbach hugs pitti
[11:01] <pitti> . o O { most of the work for sponsoring is to forward these patches upstream }
[11:09] <Q-FUNK> pitti:  seems that someone finally confirmed that my new -geode package works, in combination with the new -nsc package I had to produce to eliminate PCI ID conflicts. both are in my PPA, but might need some cleanup before they can be merged in.
[11:11] <highvoltage> Q-FUNK: ah, are you the q-funk that's been talking to (I think his nick is coolio on freenode) about these drivers? I need to assist him with it at some point.
[11:12] <Q-FUNK> highvoltage: my nick is q-funk everywhere, so probably not. :)
[11:12] <highvoltage> bah! :)
[11:14] <Q-FUNK> highvoltage: but what was the issue he had?
[11:15] <highvoltage> Q-FUNK: he has new thin clients from Via with brand new display chips, which don't work well with Edubuntu currently, he told me he talked to someone on #edubuntu who said that they're working on packages for these driverse
[11:15] <highvoltage> Q-FUNK: but I haven't had chance to catch up on it yet.
[11:16] <Q-FUNK> highvoltage: via doesn't use the -geode driver, though. IIRC they have someone making them custom X drivers that might eventually be merged.
[11:17] <DktrKranz> sponsors for main, mind reviewing scons merge from bug 226783? thanks.
[11:49] <tkamppeter> pitti, hi
[11:50] <tkamppeter> Riddell, hi
[11:53] <Riddell> hi tkamppeter
[11:54] <tkamppeter> Riddell, there is a probvlem with the build server and Qt. I tried my first upload as core-dev, HPLIP 2.8.5, and I got an FTBFS with the following error:
[11:54] <tkamppeter> The following packages have unmet dependencies:
[11:54] <tkamppeter>   python-qt4: Depends: python-elementtree but it is not installable
[11:55] <pitti> tkamppeter, Riddell: bug in python-qt4
[11:55] <tkamppeter> The package tried to pull python-qt4 with its build dependencies.
[11:55] <pitti> p-e is an intregral part of python2.5 and doesn't need to be depended on for 2.5 (and to be in main)
[11:56] <pitti> -> depends: python2.5 | python-elementtree
[11:56] <tkamppeter> pitti, Riddell, any chance that this get fixed soon?
[11:56] <Riddell> tkamppeter, pitti: I can fix that now
[11:58] <tkamppeter> Riddell, great, HPLIP 2.8.5 needs testing, upstream has done a lot on hp-toolbox and there are a lot of new bugs which need to get to upstream so that Intrepid gets a nice 2.8.7.
[12:00] <tkamppeter> Riddell, pitti, after Riddell has fixed python-qt4, what has to be done so that the build server does a new build of the same HPLIP package?
[12:00] <pitti> tkamppeter: you can retry the build
[12:00] <pitti> tkamppeter: please tell me when the fixed pakcage is in the archive
[12:00] <tkamppeter> Riddell, can you also check whether perhaps python-qt3 suffers the same problem?
[12:00] <pitti> tkamppeter: then I'll show you
[12:01] <pitti> Riddell: I'm always amazed how many arithmetic libraries for the same purposes one can invent...
[12:08] <Riddell> surely not exactly the same purpose
[12:14] <munckfish> When uploading bzr source branches to LP is it ok to upload multiple sources and link them with a single product as a collection? E.g. Cell SDK would be the product, under which I'd want bzr branches for cell-gcc, cell-binutils and so on.
[12:15] <munckfish> Rather than having separate LP products for each e.g. Cell GCC, Cell binutils etc
[12:22] <Riddell> tkamppeter: python-qt3 does not seem to have that issue
[12:23] <pitti> Riddell: indi failed to upload; did you get an explanation via mail?
[12:23] <pitti> Riddell: ah, because it was NEWed incorrectly
[12:23]  * pitti fixes
[12:30] <pitti> Riddell: ok, I processed MIR up to what I can
[12:36] <zul> morning
[12:46] <Riddell> pitti: ok, thanks
[12:48] <nixternal> woo, go pitti go!
[12:50] <cjwatson> munckfish: while it would work, it's not really kosher
[12:51] <cjwatson> munckfish: Launchpad projects are supposed to correspond to single atomic upstream projects
[12:52] <cjwatson> munckfish: I suppose it depends on whether you think that cell-gcc is just a branch of gcc (my view) or whether it's part of a separate Cell SDK entity that's permanently forked gcc
[12:52] <munckfish> cjwatson: hi, yes this is the problem I have - for normal GCC I'd say keep it separate of course
[12:52] <munckfish> however, all of these related bits from the Cell SDK page are like a forked collection
[12:53] <munckfish> I sort of felt it important to group them together so that was obvious
[12:53] <munckfish> I also realise they will go away eventually
[12:53] <munckfish> but having struggled to create a cross tool chain with gcc-4.3 et al, I'm thinking of continuing to maintain these cell-* sources
[12:54] <munckfish> So, do you still think separate or collection?
[12:57] <cjwatson> munckfish: I would still lean towards separate, but seems like a grey area. Perhaps ask #launchpad for a ruling
[12:57] <munckfish> cjwatson: ok, I'll do so
[12:57] <munckfish> thx for your opinion
[13:05] <Hobbsee> cjwatson: btw, any chance of seeing the new vim in intrepid anytime soon?  looks like there's a request for sponsorship, with your name on it :)
[13:07] <alex-weej> seb128: can you push a patch for https://bugs.launchpad.net/ubuntu/+source/gnome-applets/+bug/211604 so people stop complaining about invisible trash icons? the patch is upstream on gnome but it's not going anywhere.
[13:07] <nixternal> Hobbsee: you call me a vista lover, yet you are requesting vim? vi vi vi - the sign of the devil!
[13:09] <Hobbsee> nixternal: at least vim runs on ubuntu.  the same cannot be said for vistsa.
[13:10] <seb128> alex-weej: I've read your comments, but do you care to explain what it's doing and why?
[13:10] <Hobbsee> -s
[13:10] <alex-weej> seb128: it's the same fix that went into many other applets that used to break
[13:10] <seb128> alex-weej: that's not very useful to me to understand what it's doing and why
[13:10] <alex-weej> bonobo-activation-server is *allowed* to exist across login sessions, the fact that it does is in most cases a bug, but it still shouldn't break objects
[13:11] <alex-weej> the trash applet needs a DBus connection since the move to GIO
[13:11] <seb128> alex-weej: isn't that bug #49594?
[13:11] <alex-weej> seb128: yes, but it's a separate bug that is not important
[13:11] <seb128> well, it leads to similar issues
[13:11] <alex-weej> if the trash applet process gets activated by bonobo, it inherits the activation server environment by default
[13:12] <alex-weej> bonobo specifically has mechanism to allow the activated object to inherit specific env variables from the *activator*
[13:12] <alex-weej> i.e. trash applet will take the dbus session bus address from gnome-panel
[13:12] <alex-weej> if the patch is applied
[13:13] <seb128> why is it working for me without the patch then?
[13:13] <alex-weej> because your b-a-s exits
[13:13] <alex-weej> trust me, it needs to be in and it will fix this bug.
[13:14] <seb128> seems to be a workaround, but it it makes things work better while the libbonobo issue is still there
[13:14] <alex-weej> no it's not
[13:14] <alex-weej> there are legitimate cases for b-a-s to exist cross-session, and fixing bug 49594 won't fix this bug in 100% of cases
[13:14] <seb128> we had bugs about the trash not showing an icon way before gio and dbus use
[13:14] <alex-weej> seb128: probably because it still used dbus with gnomevfs
[13:15] <alex-weej> seb128: i wrote a patch last year to cause b-a-s to exit with the session, thus resolving 49594. it was rejected.
[13:15] <alex-weej> i learnt from the devs that it is supposed to be allowed to outlive a session
[13:16] <seb128> but in such cases it has a wrong environment
[13:16] <alex-weej> and that fixing dbus-using activated objects is done by telling b-a-s to pass the env vars from the activating process
[13:16] <seb128> ie, outdate dbus bus informations
[13:16] <alex-weej> well, it's up to you. the bug will be accepted upstream eventually because it is the right thing to do. if you want to keep triaging these bugs then suit yourself :P
[13:17] <alex-weej> and i made all of these arguments about it the first time round. turns out i just didn't understand the bonobo architecture properly.
[13:17] <alex-weej> let me find the bug.
[13:17] <seb128> alex-weej: as said before I don't discuss this change, I'm trying to understand what else is broken there
[13:17] <x_dimitri> what practical advice would you give an open-source enthusiast who would like to get involved as a contributing developer to ubuntu?
[13:18] <x_dimitri> I'm talking about coding skills to master (language, paradigms e.t.c.)
[13:18] <alex-weej> you just said what is broken. there is /nothing/ wrong with b-a-s having "outdated" DBUS_SESSION_BUS env. it shouldn't really be there in the first place, as b-a-s outlives dbus sessions
[13:18] <x_dimitri> among other things
[13:18] <dholbach> x_dimitri: check out http://wiki.ubuntu.com/MOTU/GettingStarted and the pages linked from there
[13:18] <alex-weej> assuming the ideal case that it wasn't there, the env var would have to be passed from the activating process anyway
[13:18] <ogra> x_dimitri, start in #ubuntu-motu, look through the different available tasks, grab oe and start working on it :)
[13:18] <alex-weej> and the way to do that is with the .server definition file XML
[13:19] <seb128> alex-weej: is there any case when we want to get the environment from b-a-s then? why not defaulting to use the activator one?
[13:19] <alex-weej> yes there is case for getting env from b-a-s
[13:19] <seb128> alex-weej: there is lot of .server around and I'm wondering if it makes sense to start change all of those rather than changing b-a-s
[13:19] <x_dimitri> dholbach: thanks. I have seen those.
[13:20] <dholbach> x_dimitri: great
[13:20] <alex-weej> for every other env var that also outlives dbus sessions
[13:20] <x_dimitri> :-)
[13:20] <x_dimitri> ﻿ogra:what does 'oe' mean
[13:20] <ogra> one
[13:20] <alex-weej> seb128: don't worry about changing b-a-s. the real fix is to move panel applets away from bonobo. it's coming!
[13:20] <ogra> missed a char
[13:20] <seb128> alex-weej: well, LC_ALL can change between sessions too, etc
[13:20] <alex-weej> it can change *within* sessions
[13:21] <seb128> alex-weej: should we apply the same trick to other environment variable?
[13:21] <x_dimitri> ogra: oh, ok. Thank for your suggestions guys..
[13:21] <alex-weej> it's not a trick, it's documented exactly for this case. it's the best of a bad situation.
[13:21] <seb128> alex-weej: right but that's not common case
[13:21] <x_dimitri> lemme see what the guys in #ubuntu-motu ahve to say
[13:21] <alex-weej> i have to study
[13:21] <alex-weej> cya
[13:21] <seb128> alex-weej: ok, so should we use this documented case to make sure than other things, ie the locale, are correctly set too?
[13:22] <pitti> asac: how's the rc1 bug front?
[13:24] <zul> pitti: ping
[13:26] <cjwatson> Hobbsee: I've been off for several days and am catching up; it would be best for somebody else to take it if possible
[13:29] <asac> pitti: so far it looks good. how long will you be on today? I'd like to clean the relevant bugmail folders before we push this. is there still some time?
[13:33] <pitti> asac: guaranteed until 18:00 CEST, then sporadic
[13:39] <asac> pitti: ok thanks. Ill hurry - still need to do a quick lunch though ;)
[13:45] <pitti> asac: enjoy
[13:59] <cr3> why does archive.ubuntu.com/ubuntu/dists/dapper/Release mention "ia64" under Architectures, also mentions main/binary-ia64/Packages.bz2 with a size of 616356 bytes, but there's no such file under archive.ubuntu.com/ubuntu/dists/dapper
[14:00] <elmo> cr3: because the archive is split between archive.ubuntu.com and ports.ubuntu.com after Releases files are generated
[14:01] <cr3> elmo: hm, that makes my life complicated but nothing which can't be worked around. thanks for the explanation
[14:03] <ogra> cr3, note that the ports url uses ports.ubuntu.com/ubuntu-ports instead of /ubuntu
[14:03] <ogra> its not obvious and there is no link or anything on ports.ubuntu.com/ so you could see that
[14:03] <cr3> ogra: thanks for the note, but I see no "ubuntu-ports" subdir under http://ports.ubuntu.com/
[14:04] <ogra> yeah
[14:04] <ogra> its a redirect apparently
[14:04] <cr3> ogra: man, the weirdness just doesn't stop :)
[14:04] <ogra> yeah
[14:04] <ogra> took me ages to figure that out
[14:05]  * ogra wouldnt have found out if inifinity wouldnt finally have told him
[14:06] <cr3> ogra: what's wrong with just using ports.ubuntu.com/, couldn't that have worked?
[14:06] <cjwatson> ogra: /ubuntu-ports is just a redirect to / though
[14:06] <ogra> cr3, thats not te url used in the tools (apt-setup for example)
[14:06] <cjwatson> cr3: that should work fine
[14:06] <ogra> yes, it should
[14:06] <cjwatson> ogra: it's not the "official" URL, but it'll work
[14:06] <ogra> its just inconsistent
[14:06] <ogra> indeed
[14:06] <cjwatson> the reason we generally use /ubuntu and /ubuntu-ports and such is to aid mirrors
[14:07] <ogra> i dont understand the reason for -ports though
[14:07] <ogra> ah
[14:07] <cjwatson> so that if somebody is mirroring a zillion different free software distributions they don't have to have a virtual host for each
[14:07] <ogra> right
[14:07] <cr3> I love asking these questions which seem just weird but have a perfectly reasonable explanation
[14:07] <ogra> makes sense
[14:07] <cjwatson> and /ubuntu-ports so that they don't have to figure out how to merge it back into /ubuntu
[14:16] <\sh> is mono somehow uninstallable in intrepid?
[14:43] <cjwatson> seb128: do you have any idea how I would go about fixing bug 236988? According to the freedesktop.org wm-spec, _NET_WM_STATE_FULLSCREEN goes above _NET_WM_STATE_ABOVE (and presumably this has to be the case so that fullscreen > panels)
[14:45] <tkamppeter> pitti, according to LP (https://bugs.edge.launchpad.net/ubuntu/intrepid/+source/python-qt4/4.4.2-0ubuntu2) Riddell's fix is up. How do I proceed to rebuild HPLIP?
[14:46] <Riddell> tkamppeter: go to the build page in launchpad
[14:46] <Riddell> click retry
[14:47] <Riddell> https://edge.launchpad.net/ubuntu/+source/hplip/2.8.5-2ubuntu1/+build/632305
[14:47] <seb128> cjwatson: not sure, gnome-keyring seems to use _NET_WM_STATE_MODAL, _NET_WM_STATE_ABOVE, but mvo might know better
[14:48] <seb128> that would also be a wm bug
[14:48] <seb128> s/would/could
[14:49] <cjwatson> you aren't supposed to use gdk_window_set_modal_hint on non-transient windows, apparently, and gnome-ssh-askpass doesn't have anything it could be transient on
[14:50] <pitti> tkamppeter: right, what Riddell said; you have to do that for all architectures where it failed
[14:52] <cjwatson> gdk_window_set_modal_hint doesn't obviously help, anyway
[14:52] <cjwatson> but I have to go
[14:52] <mvo> cjwatson: I have a look
[14:52] <seb128> cjwatson: gnome-keyring does that
[14:53] <seb128>         /*
[14:53] <seb128>          * We do this to guarantee the dialog comes up on top. Since the code that
[14:53] <seb128>          * that prompted this dialog is many processes away, we can't figure out
[14:53] <seb128>          * a window to be transient for.
[14:53] <seb128>          */
[14:53] <seb128>         gtk_window_set_keep_above (GTK_WINDOW (dialog), TRUE);
[14:53] <seb128>         gtk_window_set_resizable (GTK_WINDOW (dialog), FALSE);
[14:53] <seb128>         gtk_window_set_type_hint (GTK_WINDOW (dialog), GDK_WINDOW_TYPE_HINT_NORMAL);
[14:53] <mvo> (and check against gksu as well)
[14:54] <cjwatson> seb128: doesn't help - must be doing something else as well
[14:54] <tkamppeter> Thanks, pitti and Riddell. I see this button for the first time, is it a new LP feature or a core-dev-only feature?
[14:54] <pitti> tkamppeter: it has recently been made available to developers
[14:54] <seb128> ok, so I don't know
[14:54] <cjwatson> (or else gnome-keyring has the same problem!)
[14:55] <tkamppeter> Feature request: "Retry all failed archs" button.
[14:57] <tkamppeter> pitti, with "developers" you mean core-devs or also MOTUs? Or does it depend in which repository the package resides (I only want to know it to tell the correct thing to others who ask me)?
[14:58] <pitti> tkamppeter: feature request> there is a script which automates this; I'll show you next time
[14:58] <pitti> tkamppeter: I'm not sure; I guess if you can upload a package, you can rebuild it now
[15:04] <tkamppeter> pitti, HPLIP is now successfully built for 5 architectures (in the queue for the 2 missing ones). So these 5 are already on the way to the mirrors now?
[15:05] <pitti> tkamppeter: yes, in one or two hours (depending on whether they finished building more than 3 minutes ago)
[15:06] <tkamppeter> pitti, in former times I have seen a lot of "give-back" messages here on the IRC. Was this the retrying of a build when the first build went wrong?
[15:06] <pitti> tkamppeter: exactly
[15:06] <pitti> tkamppeter: "give back" is the term for historical reasons (it's still called like that in Debian)
[15:07] <pitti> seb128, pedro_, bdmurray: can anyone of you play a bit with an NTFS volume to verify bug 229000?
[15:07] <tkamppeter> pitti, then all except amd64 will make it in one hour and amd64 perhaps only in two hours.
[15:09] <tkamppeter> pitti, what means if the "successfully built" for an arch switches from ACCEPTED to DONE?
[15:10] <pitti> tkamppeter: "ACCEPTED" is the queue which holds built packages; the next publisher run (at :03 hourly) picks up those and puts them into the actual archive
[15:10] <seb128> pitti: just playing on a ntfs partition and looking if everything works correctly?
[15:10] <seb128> pitti: there is no TESTCASE on the bug
[15:10] <pitti> tkamppeter: when that happens (aronud :05 hourly) it will get to DONE
[15:11] <pitti> seb128: no, reproducing the actual bug is really hard
[15:11] <pitti> seb128: I described my own testing in the bug (test suite, some operations in nautilus, etc.)
[15:11] <tkamppeter> pitti, thanks.
[15:18] <tkamppeter> pitti, can I also build Debian or Ubuntu packages with a .orig.tar.bz2 instead of a .orig.tar.gz file?
[15:19] <pitti> tkamppeter: that feature is in hardy; so it depends on whether soyuz is running on hardy now; cprov?
[15:22] <cprov> pitti: we haven't backported it to edgy. Let me check it again.
[15:22] <tkamppeter> pitti, can you have a look at CUPS bug 2814?
[15:23] <pitti> cprov: edgy!
[15:23] <tkamppeter> pitti, one minute this was not the right one.
[15:23] <tkamppeter> pitti, it was the right one.
[15:25] <cprov> pitti: confirmed, it's not there. Please file a bug so it can be done at some point in before LP 2.0.
[15:25] <pitti> tkamppeter: ^
[15:25] <seb128> pitti: ok, I didn't try the testsuite thing you mentionned but normal usage (copies, move, renaming, deleting, mount, unmounting, browsing the drive, dnd, etc) works correctly, I've added a comment to the bug
[15:26]  * pitti hugs seb128, thanks
[15:26]  * seb128 hugs pitti
[15:26] <tkamppeter> pitti, it is about some enhancements to CUPS to really support the custom options which Mike has introduced in CUPS 1.2 (string, password, numeric, ...) but they got never really used. Currently, I am on the way to get them advertized to the manufacturers and supported by the Common Printing Dialog.
[15:27] <asac> pitti: ok, lets feed this to the masses :/
[15:28] <pitti> asac: rumble!!!
[15:28] <tkamppeter> pitti, Lars Uebernickel (developer of foomatic-rip 4.0 and now GSoC student for the CPDAPI DBUS interface for the Common Printing Dialog has written two CUPS patches for these options.
[15:29] <ogra> asac, food ?
[15:29] <tkamppeter> One is for a special PPD keyword to restrict the allowed characters in string options, the other is about supporting the options in the CUPS web interface-
[15:29] <ogra> yummy
[15:29] <asac> pitti: should i set to verification-done?
[15:29] <pitti> asac: please do, and describe the amount and quality of feedback you got
[15:29] <tkamppeter> pitti, CUPS bug 2807
[15:30] <tkamppeter> pitti, and CUPS bug 1729
[15:32] <tkamppeter> Mike has rejected bug CUPS bug 2814 and he did not answer yet to the last patch for CUPS bug 1729.
[15:33] <pitti> tkamppeter: I don't want to permanently carry large patches which are rejected upstream; we've been through this :/
[15:35] <tkamppeter> pitti, so I leave them out as long as Mike does not accept them. If Mike turns away from the custom options I make them my baby with system-config-printer and the Common Printing Dialog. Perhaps Mike will return to them when I have made them common practise. Support from inside CUPS is a nice plus but not required.
[15:35] <asac> pitti: commented.
[15:35] <pitti> tkamppeter: ok, thanks
[15:37] <pitti> tkamppeter: please file the orig.tar.bz2 thing as a bug against soyuz
[15:40] <tkamppeter> In s-c-p and CPD I am upstream and I can publish specs on OpenPrinting, so no support from Mike Sweet required.
[15:42] <tkamppeter> pitti, how do I report a bug on soyuz, which project? Which package?
[15:42] <pitti> tkamppeter: "soyuz", no package
[15:42] <pitti> bugs.lp.net/soyuz/+filebug
[15:49] <tkamppeter> pitti, someone else reported this already as bug 225151.
[15:57] <pitti> seb128, asac: note that epiphany-browser has a newer version in intrepid, and xulrunner is already updated in intrepid, so I won't copy the lot from hardy-proposed to intrepid
[15:58] <pitti> asac: bug 236984 is still open in intrepid?
[15:59] <asac> pitti: yeah. its fix committed as our development branch is already on RC2 ... waiting for the queue to clear
[15:59] <pitti> ok
[16:07] <pitti> asac: xul and related copied, mass-copying of language packs in progress
[16:10] <asac> pitti: ok ... let the fun begin.
[17:30] <kees> pitti: er, I'm looking at "cron" to advise kirkland on doing a debdiff, and I'm not sure what version number to recommend.  :P
[17:31] <kees> 3.0pl1-104+ubuntu1?  104ubuntu2 won't work due to the +build1, iiuc
[17:34] <slangasek> 104ubuntu2 > 104+ubuntu1, no?
[17:40] <pitti> kees: argh, I was so proud that we're finally back in sync :)
[17:40] <pitti> kees: 104+ubuntu1 will work, yes
[17:40] <kees> pitti: heh.  yeah, we've got a small correction that is unACKd upstream
[17:41] <kees> they call /usr/bin/editor instead of /usr/bin/sensible-editor
[17:41] <kees> and since kirkland is making changes to sensible-editor, this got examined at the same time.  :)
[17:42] <pitti> kees: sorry for the weird version number in the first place; but it was the least evil-looking way to bump the number to something non-ubuntuish
[17:42] <kees> yeah, I think it's the right solution; I'd just never hit this corner-case before.  :)
[17:43] <kees> mvo: are the changes to apt-listchanges for "dapper->hardy" still needed?
[17:43] <kees> mvo: I'm going to assume "no", please let me know if I should re-add them.  I'm requesting a sync for it since the other changes (security) are already upstream.
[17:44] <mvo> kees: no
[17:44] <kees> mvo: perfect :)
[17:44] <mvo> kees: you assumed right :) its only needed for very old installs
[17:44] <kirkland> kees: updated patch uploaded to https://bugs.edge.launchpad.net/ubuntu/+source/cron/+bug/222830
[17:45] <kirkland> kees: btw, previous one did not update the Maintainer field ;-)
[17:45] <kees> bryce: can you check on efibootmgr?  if the ubuntu changes are upstream, can you do a "requestsync" for it?
[17:45] <kees> kirkland: ah yes, good catch.  I would have noticed when I compiled it.  ;)
[17:46]  * kirkland is glad he cleaned that one up before getting smacked by kees ;-)
[17:46] <kees> hehe
[17:51] <kees> argh, libx86
[17:55] <kirkland> kees: is that 'argh' intended for me?
[17:57] <kees> kirkland: no, just myself, I'm looking at my merges
[17:58] <kees> ogra: say, can you do the powernowd merge?  while I touched it last, it was just a bug fix and I'm not entirely familiar with the code-base.
[17:59] <ogra> me neither
[17:59] <ogra> i only touched it once in my life iirc
[17:59] <ogra> but if its needed, i'll take a look
[18:05] <kees> ogra: ah, heh, okay, perhaps we can find someone else.  :)
[18:23] <Mirv> since the language packs copying to -updates is not immediate but takes time, there might be a corner case situation right now that updating now results in eg. firefox failing because the firefox translations move and some packages updateable while some not
[18:23] <Mirv> at least I was able to update my laptop so that Firefox gives some error on launch at the moment, though starts nevertheless
[18:25] <ion_> I had to disable the Finnish language pack in my father’s Firefox in 8.04 because some functionality didn’t work.
[18:25] <Mirv> ion_: well the printing problem is known and fixed now in the new packs
[18:26] <Mirv> ion_: also it's a matter of changing one "%" in the jar package
[18:26] <ion_> Yeah, i’ll re-enable it when i visit them the next time.
[19:15] <blueyed> Can somebody from ~ubuntu-archive, please approve virtualbox-ose-modules for Hardy?
[19:19] <ogra> blueyed, oh, did you enable lpia there as well ?
[19:19] <ogra> that would be very handy
[19:23] <blueyed_> sry.. system froze hard.. :/
[19:29] <bryce> kees: the ubuntu change for efibootmgr is to build on lpia - I'm assuming that's not something upstream is interested in
[19:29] <kees> bryce: ah, okay.  well, in that case, it might be time for a re-merge.  I was just browsing MoM and noticed it since I was the uploader for it.
[19:30] <ogra> blueyed, did you enable lpia there as well ? hat would be very handy
[19:30] <ogra> *that
[19:30] <bryce> kees, ok I can take a look at it in a bit
[19:30] <blueyed> v-o-m for lpia? could do, if you know that it works..
[19:31] <blueyed> ogra: ^^
[19:34] <slangasek> blueyed: well, please bear in mind that if you're adding functionality instead of just rebuilding for the ABI change, vbox will need to go through the full SRU process
[19:35] <Mirv> (lang packs all synced now)
[19:36] <blueyed> slangasek: sure.. and since I have no means to test it (apart from ppa) and not much time at hand, please ACK the current upload.
[19:37] <ogra> blueyed, i only need the guest modules/utils, adding them would help with UME testing since you cant have 800x480 without the vbox X driver
[19:39] <ogra> Keybuk, hey, what about making kino and friends polkit capable, then we could have a fine grained access model for 1394 devices :)
[19:42] <blueyed> ogra: feel free to add it then.. :)
[19:44] <blueyed> ogra: it's in Intrepid after all: https://edge.launchpad.net/ubuntu/intrepid/+source/virtualbox-ose-modules/24.2
[19:44] <ogra> blueyed, i know :)
[19:50] <Mirv> gash, by updating langpacks at the wrong time I was able to break firefox (profile) completely
[19:51] <Mirv> it doesn't help that the rest of the packages came along now.
[19:53] <Mirv> uh, ok, great actually, I just happened to had a hidden firefox on other desktop. it's fail-proof after all.
[20:15] <highvoltage> ogra: not sure if you're interested in this, but this is what one of my friends have been doing in Nigeria: http://blog.wizzy.com/post/OLPC-and-Classmate-in-Nigeria
[20:17] <ogra> rinning XP ?
[20:17] <ogra> *running
[20:19] <laga> seems like intel is just throwing money at the problem :)
[20:19] <ogra> not really
[20:19] <laga> WiMAX for $10000/month? :)
[20:20] <hwilde> asus eeepc is going to have wimax builtin
[21:20] <kestaz> how to compile kernel-ppa sources ?
[22:21] <asac> Mirv: so no issue?
[23:55]  * kees nominates gcc-4.3 as second only to openoffice.org in least-easy-to-understand-build-system
[23:56] <mneptok> awalton_1: meep
[23:56] <mneptok> kees: gcc gets extra points for its masturbatory nature.
[23:56] <kees> mneptok: heh, true.
[23:56] <slangasek> kees: I counter-nominate mpich!
[23:57] <mneptok> kees: ask me about m_meeks' world sometime :)
[23:57] <kees> slangasek: eek, I don't want to look now
[23:57]  * slangasek grins
[23:58] <kees> I'm beating my head against how to run the gcc testsuites using the locally installed gcc.  /me has given up now and is just building gcc again... hopefully I can poke into the Makefile what I need.
[23:58] <kees> I'm too dense for doko's hints to penetrate my brain.  runtest hates me. wheee
[23:59] <kees> at least it's a parallel build