[00:46] Sorry about the offtopic, but .. what are the possible locations for a startup file to be? I've searched all the ones I know but can't find the script which is getting started at boot time (and I don't want him to). [00:49] gouki: /etc/init.d [00:49] gouki: You looked there? [00:49] Did a -R ls on all folders, TheMuso [00:49] WHats the package? [00:50] synergys [00:52] thats not in hardy... [00:55] !? [00:55] I don't get it. I'm not using Hardy [00:55] Well I don't easily have access to gutsy atm [00:55] so I can't check there [00:56] There was never a package called synergys in Ubuntu. [00:57] gouki: Are you using Ubuntu? :) [00:57] I know there isn't a package called synergys. I'm talking about a script, not a package. [00:57] The software is called Synergy [00:58] What I'm asking is, where could this script be listed to start at boot time... [00:58] gouki: dpkg -L syngergy will show you all files belonging to that package. [00:58] syngergy even [00:58] gah [00:58] you know what I mean [00:58] TheMuso: but only if it's packaged, and he's suggested it isn't packaged [00:59] slangasek: Right. [00:59] Mind is sorta elsewhere, on other things. [00:59] TheMuso: I have already done that. Still, no indication of the script on a startup directory [01:01] BRB [01:03] keescook: Hmm... "sponsoring trigger creation patch "? Who wrote it? [01:03] keescook: ...and you forgot to add debian/grub.trigger [01:03] :) [01:18] * keescook cries [01:19] soren: fixed. === `23meg_ is now known as mgunes [02:24] azeem: ping === cody-somerville is now known as somerville32 === lando_ is now known as lando [04:37] after i apt-get source a package, i can build it with configure/make, but how do i build the package? [04:40] sparr_: dpkg-buildpackage does that [04:41] sparr_: https://wiki.ubuntu.com/PackagingGuide/Complete might be some good reading === asac_ is now known as asac === HypnoToad is now known as BenderUnit22 [05:56] was gthumb removed from the default install as part of hardy-reducing-duplication? [05:56] I believe so, yes. [07:07] hi [07:08] where can I find nautilus team? [07:09] I'm testing ubuntu alpha 4 [07:11] Good morning [07:11] yes, good morning... [07:11] tkamppeter_: you can just upload them, so that they will be in NEW [07:13] good morning pitti [07:13] hey mvo [07:14] today is the feature freeze.... [07:16] I have a question [07:16] morning pitti and mvo [07:16] with the new nautilus, why can't I copy a file to the same directory? [07:17] hey LaserJock [07:17] mvo: I took care of desktop-multiplier, btw [07:17] hopefully you won't be getting more emails about that ;-) [07:19] right... keep ignoring me... [07:19] gnudles: Have you checked out the nautilus bugs on launchpad? [07:19] gnudles: I doubt people are ignoring you, probably they just don't know the answer [07:20] gnudles: This is possibly not the best place for such a question, either (#ubuntu-bugs or #ubuntu+1 are possibly better). [07:22] gnudles: Also, it works for me. Although the question seems somewhat odd: why would you want to copy something to the same place? [07:22] good morning [07:22] Howdie dholbach! [07:23] heya RAOF [07:25] RAOF: If I want to copy a source file template for example [07:25] gnudles: Do you mean 'copying a file "foo" from mydir/ to mydir/ does not produce a file "copy of mydir"'? [07:25] it shows me a dialog [07:26] Of whether or not you want to overwrite the file with the same file, yes. [07:26] This seems to be not-totally-unreasonable behaviour. [07:26] "copy of foo" you mean... [07:26] Yes. Of course :) [07:26] no [07:26] once it was like this [07:27] Ah. So this is a regression from gnome-vfs. [07:27] File a bug. [07:27] today a dialog appears... [07:27] another thing [07:28] in the dialog, you can add option for renaming if a file with the same name already exists... [07:28] LaserJock: thanks! [07:29] gnudles: A valid feature request. Again, file a bug :) [07:33] ok [07:35] great! firefox 3 at last... [07:35] :) [07:37] crap!!!!!! all my bookmarks disappeared :,( [07:45] Could a buildd-admin give-back hdf5 on lpia? Thanks. [07:52] DktrKranz: nothing to give-back, it's in depwait [07:52] mvo: should that worry me? "Fehl http://archive.ubuntu.com hardy Release" [07:52] mvo: at the end it complains about not being able to access the keyring [07:53] pitti: possible, can you paste me the exact error message? [07:54] pitti: oh, indeed! I misread. Sorry. [07:54] mvo: http://paste.ubuntu.com/4582/ [07:55] pitti: what does apt-key list say? [07:55] 'gpg: Schlüsselbund `/etc/apt/trusted.gpg' erstellt' [07:55] oh, I bet I know [07:55] meh [07:55] mvo: I ruined my file system yesterday (silly error) [07:55] and lost some files [07:55] *PPUUUHHH* [07:56] thanks [07:56] I was very worried for a moment :) [07:56] I should really reinstall this box [07:56] pitti: if you have the latest apt, please run "apt-key net-update" [07:56] just for the fun of it [07:56] right, but to get this I need apt-get working :) [07:57] heh :) ok, if you don't have a current one, then yes [07:57] "sudo apt-key update" may also help, depending on the damage on the FS [07:58] mvo: yep, that helped [08:18] hey glatzor__ [08:19] morning mvo! === glatzor__ is now known as glatzor [08:23] pitti: hi, I uploaded a new nvidia-settings which enables the binary again (sigh :), but the old upload was already sitting in NEW, so should I do something special? [08:23] tjaalton: let me reject the old one then to avoid confusion [08:24] pitti: ok thanks! [08:24] 412897 | S- | nvidia-settings | 1.0+20071221-0ubuntu | five days [08:24] | * nvidia-settings/1.0+20071221-0ubuntu1 Component: multiverse Section [08:24] tjaalton: ^ so this should be killed? [08:24] yes [08:24] done [08:24] rock! [08:26] it turned out that the binary nvidia-settings shipped with the drivers is buggy, and the separate version can be patched so.. [08:26] mvo: I am currently turning apt-dbus into an extra backend, so that it can be merged in the main repository [08:26] this should be a win-win [08:26] mvo: but the dbus backend infrastructure is still a moving target. [08:28] mvo: is there a similar function to git log -p in bzr? [08:34] hi glatzor [08:39] piiti, you mean I can directly dput them into Multiverse? [08:40] servus bryce. === tkamppeter_ is now known as tkamppeter [08:40] how are you progressing? [08:41] glatzor: pretty well - http://bryceharrington.org/files/screenrez_a.png [08:41] bryce: have you found any aspects in my user interface that you could reuse? [08:42] glatzor: definitely; I borrowed a lot of the layout and the icons [08:42] takes some time ... I am currently participating in the worldwide I-have-got-the-slowest-internet-connection-contest :) [08:43] glatzor: mpt's mockup he did for you was also quite inspiring === gnudle1 is now known as gnudles === carlos_ is now known as carlos [08:44] bryce: you had to skip the fancy widget part? [08:44] bryce: has sørensen already started on the widget? [08:44] glatzor: yeah, I evaluated the time I had until FF and decided that was going to be too ambitious [08:44] bryce: really cool [08:44] as it is I'm a couple days before === gnudles is now known as d [08:45] er, behind === d is now known as gnudles [08:45] bryce: really nice [08:46] bryce: have you heard anything from upstream yet? if they like it? [08:46] sandmann replied [08:46] I don't completely understand what sorensen's working on, but it looks quite different from our concepts. I don't understand how it's implementing multi-screen [08:46] bryce: did you see soerens reply? [08:47] sorensen said it's all in there, but I guess I'd need to study it more to see how it does it [08:47] pochu: I've not sent the extended key event stuff to Debian on purpose. [08:47] tjaalton: bryce: have you seen any code of his planned x extension? he wanted to add fade effects [08:47] I tried compiling and running his code, but the only piece I could get to run didn't do anything [08:47] glatzor: nope.. sounds nice [08:47] pochu: It's not completely finalised. [08:48] pochu: In Ubuntu I have control over both ends of the wire.. In Debian, not so much. [08:48] bryce: the actual monitor handling is now done by gnome-settings-daemon? [08:48] hum, the vmware-stuff in lrm is ancient [08:49] bryce: does gdm now use the settings-daemon in ubuntu? [08:49] tjaalton: yeah I don't know what to think of the reply. [08:49] tjaalton: There's vmware stuff in lrm? [08:49] soren: yes, player, server, tools [08:49] tjaalton: Oh, that. [08:49] soren: not built in hardy [08:49] tjaalton: Right, I remember now. [08:49] glatzor: I've not gotten to the gnome-settings-daemon part yet [08:49] question for kde people; libqwt5-qt4-dev - any plans to move this in main? [08:50] bryce: what are your plans for handling the new overriding nature of xorg.conf? [08:50] glatzor: redhat is developing a patch against gnome-settings-daemon to expand how it handles the monitor setup. I haven't looked at it though. But it would seem most sensible to follow their design. [08:50] soren: do you know if we have the right to update those? [08:51] copyright doesn't mention anything [08:51] tjaalton: No clue. Sorry. [08:51] glatzor: well, the work I'm doing is only for cases where xorg.conf does not need modification [08:51] soren: ok, no worries :) [08:51] glatzor: for situations where people do need to override things in xorg.conf, we'd need a different tool. [08:52] glatzor: there is also the case of bulletproof-x, which will need that kind of a tool as well [08:52] bryce: I'll bring back "Device" in the Screen-section, which should at least make aticonfig and nvidia-settings to work again [08:53] bryce: how does pitti now deals the proprietary driver installation? [08:53] tjaalton: good idea [08:54] glatzor: sorry, don't understand the question? [08:54] bryce: yeah, funny grammar [08:54] heya soren [08:54] bryce: Hey. [08:54] bryce: how does the restricted drivers tool change the driver in the xorg.conf now? [08:54] tjaalton, glatzor: I've been having fun today screwing up my monitors by hitting Apply on this gui. ;-) [08:55] hehe [08:55] glatzor: ahh - I gather that's what tjaalton was just referring to via aticonfig and nvidia-settings [08:55] not really [08:55] no? [08:55] jockey works right now, but aticonfig crashes [08:55] just like dc-gtk :) [08:55] heh [08:56] nvidia-settings fails to write the config, which actually is a blessing since it would write all sort of crack [08:56] dosn't jockey use the displayconfig code for the modifications? [08:57] mvo_: I haven't followed the jockey rewrite [08:57] mvo_: I knew that envy uses guidance-backends now, but didn't know that jockey did too === \sh_away is now known as \sh [08:58] bryce: the rate configuration won't be allowed in your tool? or just not yet implemented? [08:58] glatzor: it's there - but it's smart now; if you only have one rate available, it displays as a label rather than a dropdown [08:59] glatzor: jockey still uses guidance-backends nowadays [08:59] bryce: doesn't this result in small flickering when changing screens? [08:59] pitti: hello [08:59] hi glatzor! [09:00] bryce: you could also disable the combo box. [09:00] glatzor: for LCD's (which is what I took the screenshot on) 60 Hz is fine [09:01] glatzor: true... [09:01] bryce: flicking of the user interface, since it has to replace a widget when you select a different monitor in left chooser [09:01] glatzor: oh, no it's perfectly solid [09:02] I need to figure out how to do screencasts or something === hunger_t_ is now known as hunger [09:03] bryce: what is the primary status? does the applet move the panels to a different screen when it is set? [09:04] bryce: I would be careful with the same-as position, since it requires that the screens have got the same resolution [09:05] bryce: that is why I had three radio buttons (disable, extend, clone) [09:05] glatzor: the 'primary' is basically what I'm calling an output that other outputs are relative to [09:05] glatzor: however it's been proving ornery in the coding so I'm not sure having a 'primary' screen adds that much [09:06] glatzor: yes you're right about the same-as (aka clone or mirror). It probably will take a lot of testing to get right. [09:08] bryce: how do handle the virtual size issue? [09:08] glatzor: right, that's a remaining issue [09:09] glatzor: I decided to focus on only non-xorg.conf changing functionality [09:09] bryce: the other parts can perhaps never be done right :) [09:10] glatzor: my thought is to use a script or something attached to an Advanced button or something to update Virtual, but I'm ignoring it for now [09:10] advanced buttons are evil :) [09:11] yeah yeah [09:11] well ultimately (maybe xserver 1.5??) it'll become unnecessary to specify Virtual anyway [09:12] bryce: perhaps a small check if the virtual size allows to display two displays could be added to the applet [09:12] glatzor: yup [09:13] also since increasing virtual often results in forcing DRI/Compiz to have to be turned off, I thought a popup dialog warning the user might be of value [09:13] bryce: indeed [09:13] bryce: Thinking of xrandr, do drivers other than nouveau suffer from http://bugs.freedesktop.org/show_bug.cgi?id=14394 ? [09:13] Freedesktop bug 14394 in Driver/nouveau "[NV4B] Composite broken on 2nd head" [Normal,New] [09:14] The fact that the patch is against the X server makes me think so, and it's a really curious bug to run into. [09:15] interesting [09:15] RAOF, for most typical multi-head systems (at least ones I've played with), compiz gets disabled entirely because you go beyond the Virtual limits [09:15] bryce: But this kills metacity (& Kwin I think) too. [09:15] RAOF: hrm [09:16] Metacity as of .8 uses the COW. [09:17] compiz 0.7 should have "multi-head support", but I'm not sure what it means here [09:17] RAOF, hmm, well this is a configuration I've not really tested myself much [09:18] RAOF, offhand it does sound driver-specific, but I don't really know; I've never run anything like this [09:18] RAOF: have you tried the patch yet? [09:18] moin [09:18] tjaalton: Not yet. I mean to grab our X package and add the patch, but I haven't tried yet. [09:19] tjaalton: this is really more about the window managment capabilities, those got improved a lot for multihead in compiz 0.7 [09:20] bryce: I don't have a non-nvidia card handy to test, but if you've got an intel cand or somesuch that bug should be easy to trigger, if it exists. [09:21] RAOF: hmm, I have an intel box next to me, and it could borrow the monitor from the Sunray terminal ;) [09:30] mvo_: how can i see the diff of a commit after adding the "content" to the commit? [09:30] mvo_: any git gurus around? [09:31] git diff --cached [09:35] cjwatson: thanks a lot [10:08] * ogra would so love to not find a frozen laptop on his desk every morning ... *sigh* [10:11] ivoks: no, why is it needed? [10:13] Riddell: i'm asking cause this lib is needed for bacula's QT console [10:13] since we are moving bacula to main, we'll have to drop qt console :( [10:14] or build it for universe... [10:14] ivoks: so write a MIR for libqwt5-qt4-dev [10:14] Riddell: ping [10:14] Riddell: that crossed my mind too... [10:14] Riddell: could you please check your mail [10:15] iRon: doing so [10:59] cjwatson: do I need to pay attention to something special when I'll change the seeds for e. g. slocate -> mlocate? [11:00] cjwatson: e. g. I guess I should add that to the platform.hardy branch? [11:02] pitti: platform.hardy/desktop-common has dlocate [11:02] err, slocate [11:02] so it makes sense to change that, along with ubuntu.hardy/server-ship [11:02] although as I said on ubuntu-devel I think it ought to be in platform.hardy/standard really [11:02] cjwatson: right; so changes in platform.hardy will be picked up by *-meta/running update, not by merging to the other *.hardy seeds? [11:03] cjwatson: I agree about standard (and removing it from desktop and server-ship) [11:04] cjwatson: hm, installing mlocate doesn't remove slocate [11:04] pitti: changes> right [11:05] pitti: yes, seems to be intentional to ease migration, although I see the problem you're raising [11:05] I don't see anything in /etc/cron.daily/slocate that tests for mlocate presence [11:05] pitti: however, we could fix this by changing slocate's cron job not to run if mlocate is there [11:06] much like locate's cron job does [11:06] ah, it sets the /etc/alternatives/updatedb to mlocate [11:06] well, sort of does, it checks whether it's been diverted [11:06] [ -e /usr/bin/updatedb.findutils ] || exit 0 [11:07] pitti: yes, though /etc/cron.daily/slocate runs slocate explicitly [11:08] so how about: [11:08] -if [ -x /usr/bin/slocate ] [11:08] +if [ -x /usr/bin/slocate ] && [ ! -x /usr/bin/mlocate ] [11:09] the only downside I can see is that it'll mean that running slocate explicitly won't work any more, but I'm not too concerned about that [11:09] why not simply add a Conflicts:/Replaces:? [11:09] update-manager can deal with encouraging people to remove it, rather than requiring a hard Conflicts [11:09] I don't like adding Conflicts arcs when we don't have to [11:10] it would mean to leave package cruft around [11:10] sure, we can add it to the obsoleted packages [11:10] but right, I guess we'll demote slocate [11:10] in update-manager [11:10] and then u-m will clean it up, right? [11:10] pitti: I think update-manager is good enough, yeah [11:11] ... checking rdepends ... right, slocate has no rdepends at all (except *-desktop) [11:11] uploaded slocate with the above diff [11:11] thanks [11:12] cjwatson: I added slocate to the forced obsoletes, that means that for most people it will get removed (unless they object of course) [11:12] great, thanks [11:12] ok, mlocate MIR looks good, thanks for the great and detailled review [11:12] cjwatson: I'll do the seed changes, promotions, etc. now [11:13] hooray [11:15] cjwatson: I won't update *-meta yet, since the component changes need to get published first [11:16] evand, heno, can you please apply the following patch to umenu? http://paste.ubuntu-nl.org/55953/ [11:16] cannot ssh from here [11:17] cjwatson, mvo_: hm, should mlocate in standard be a recommends or a strict depends? (I lean towards recommends) [11:18] server didn't depend on it so far either [11:20] pitti: recommends, IMO [11:21] I'm surprised it isn't already a recommends in desktop-common [11:21] just an oversight, I think === cjwatson_ is now known as cjwatson [12:12] hmm, we could do with new language-support-* for the firefox upgrade [12:14] cjwatson: the split? that's on my list for today [12:19] I think actually it's that we need new mozilla-firefox-locale-* [12:22] ah, right [12:33] does anyone prefer grid layout over embedding hboxes in vboxes and vice versa? [12:40] Does anyone have a timestamp for start of FeatureFreeze? [12:59] cjwatson, mvo__: AFAIK the installer and gnome-language-selector will get along if a language does not have a language-support-XX package, right? I'd like to remove all the ones with an empty Depends: to remove some cruft [12:59] as a preparation to merging/using ArneGoetje's 'split support packages' branch [12:59] persia: the end of the day in the last timezone of the world oh please :) [13:00] pitti: sure === cjwatson_ is now known as cjwatson [13:00] pitti: oh, err [13:00] pochu: Maybe. Something like 12:00 or 24:00 UTC would work as well. I just want guidance on when to stop accepting UUS stuff that hasn't been pushed for FFe. [13:01] pitti: the installer will warn and say that the CD doesn't contain full support for your language [13:01] persia: I don't think anyone will measure that precisely [13:01] pitti: OK. I won't fuss about it then, and just stop sponsoring when it stops being a reasonable "14th February" for me. Thanks. [13:01] cjwatson: oh, even if there is a language-pack-XX in the archive, but not a -support one? [13:02] persia: sounds pragmatic and appropriate [13:02] cjwatson: well, I can leave them around for a while, they'll be practically orphaned [13:03] pitti: the check is for what's on the CD [13:03] pitti: in practice it'll always have fired for !en anyway [13:04] pitti: so it might well not matter; it only does that check for CD installs [13:04] right, we'll retain language-support-en anyway [13:04] I don't particularly mind if empty language-support-* go away [13:04] cjwatson: I meant the bits that try to install support and -pack from the network [13:04] ISTR reading the code and seeing that they are tried independently [13:05] they are, and it shouldn't care if they fail either [13:06] ok, great [13:11] piti: for munin it should be running as a munin user not nobody correct? [13:12] zul: yes; doko indicated that it already does that, though [13:12] so it might just have been a misunderstanding [13:12] ok [13:13] pitti, hi [13:13] hi tkamppeter [13:14] pitti, I have corrected the .changes file from s-c-p, was I typo in the old version number, can you upload it now? [13:15] tkamppeter: ok [13:15] pitti, I have also all files of the Brother driver now, should I put them directly into Multiverse? [13:15] tkamppeter: if you think the packaging is ok now, then please just upload them, so that they'll land in NEW [13:16] pitti: ill leave as it is then [13:16] tkamppeter: setting Section: multiverse/text would be good, yes [13:16] (but it's just a bonus) [13:17] With the section, I will tell it to the packagers, that they can correct that in a later version. [13:17] tkamppeter: btw, you know that you don't normally need to use -v, right? just for merges [13:18] So without -v it defaults to take simply one ChangeLog entry? [13:18] right [13:18] tkamppeter: nevermind about Section: we'll override it to multiverse in the NEW queue [13:18] tkamppeter: Yes. Note that it is always safe to use -v with an rmadison call to get the current version, even if you are just doing a standard update. [13:19] tkamppeter: scp uploaded [13:19] pitti, thanks. [13:25] mvo__: I would like to move the description formating done in UpdateManager/AppInstall and the changelog fetching method to python-apt [13:27] I need some MOTU-help [13:28] how do I make sure a file gets installed in /usr/share/compizconfig, which has been added via a debian/patch/02_some.patch? [13:29] obviously adding the usual bits to Makefile.am and creating a 99_autoreconf.patch does not seem to be enough [13:29] help greatly appreciated [13:36] MacSlow: For MOTU-help, asking in #ubuntu-motu is a good idea. You might find using debian/$(package).dirs to help, or debian/$(package).install, depending on the contents of your rules file. [13:41] glatzor: sure, that sounds reasonable [13:45] doko: are you Matthias that reviewed the following MIR: https://bugs.edge.launchpad.net/ubuntu/+source/mousetweaks/+bug/190208 [13:45] Launchpad bug 190208 in mousetweaks "Main Inclusion Report for mousetweaks" [Undecided,Incomplete] === mvo__ is now known as mvo === iceman_ is now known as iceman === mvo_ is now known as mvo [14:37] pitti, slangasek: thanks for your help with migrating a conffile from one package to another [14:37] pitti, slangasek: what I ended up implementing was slangasek's suggestion, with the addition of a versioned Conflicts [14:38] jdstrand: you're welcome [14:38] pitti, slangasek: you can see what I came up with at https://wiki.ubuntu.com/ApparmorProfileMigration [14:39] pitti: and I should also thank you for your apparmor/cupsys work-- as I used it as a template ;) [14:39] heh, good to hear if it was useful [14:39] totally === cjwatson_ is now known as cjwatson [14:47] calc: pon [14:47] g === \sh is now known as \sh_away [15:13] azeem: hi [15:13] heya [15:13] azeem: i heard you were going to be updating opensync in debian? [15:13] well [15:14] if the upgrade path is reasonably clear, I would, yeah [15:15] azeem: going from 0.19 -> 0.2x isn't clear? [15:16] no, both the database and the configuration format has changed [15:17] azeem: hmm [15:17] there's now a configuration updater for 0.3x, but I haven't tested it [15:17] maybe put a debconf message saying its not backwards compat would work? 0.19 is 10 releases old [15:17] it should be possible to just wipe the database and do a slow-sync [15:18] that'd be the emergency cop-out maybe, yeah [15:18] well it hasn't been updated in 16 months... [15:19] perhaps its a the DD doesn't want to do the extra work cop-out instead? [15:20] * calc doesn't know the details of the work involved but 16 months is a relatively long time [15:21] calc: in which binary package is the openoffice firefox/mozilla plugin btw? i installed openoffice.org but don't see anything ooo related in /usr/lib/firefox/plugins [15:21] looks like not much else uses the libraries, etc except opensync itself so its not a really nasty conversion [15:21] calc: it's rather the DD hoped 0.40 would be ready in time for hardy cop-out [15:21] azeem: ah i see :-) [15:22] azeem: mozilla-openoffice.org [15:22] eh? [15:22] s/azeem/asac/ I assume [15:23] azeem: oh yea [15:23] pitti or Mithrandir: please give-back: bzr doxygen. Thanks. [15:23] asac: mozilla-openoffice.org [15:23] asac: its only available on i386/powerpc [15:23] asac: its broken on the other archs aiui [15:23] geser: given-back [15:23] calc: I can upgrade those packages in Debian (in fact, the only reason I consider it now is because of hardy, lenny should be fine for 0.40), but how much time do I have? [15:23] calc: ah ... ok. that explains it [15:23] I got work to do now, and today is Valentine's day... [15:23] calc: any progress? [15:23] geser: Mithrandir beat me to it [15:24] pitti: and I didn't even use a script. :-P [15:24] * asac wonders how comes that its avail on powerpc ... strange [15:24] Mithrandir: I repaired mine, but it was too slow [15:25] azeem: aiui part of it is holding up synce 0.11 upload, but i don't know the details (which was why i was asking about it) [15:25] pitti: smart bookmarks in ff are quite fast ("us $packagename"), then one click to get to the latest build, then a click on a button per failed build. [15:25] asac: i hope to have something by tomorrow, i have a few other patches to integrate as well [15:25] Mithrandir: I typed "giveback bzr doxygen" [15:25] I wish LP had something like https://launchpad.net/distros/ubuntu/hardy/+source/glibc/latest [15:26] I haven't installed geasemonkey for ff 3.0 yet [15:26] calc: ok ... great. if you have questions let me know. maybe do a testbuild so we know that this is really pending [15:26] calc: yeah right [15:26] calc: I was rather asking, "If I don't upload today (missing FF), will somebody be able to get those packages synced for hardy still?" [15:33]