[00:09] kenvandine, http://www.sofaraway.org/ubuntu/tmp/Gwibber-darktheme-not-so-great.png [01:02] asac: what's the progress of the m-d package autodetection? [01:23] !test [01:23] yes, I'm alive. [01:25] darn. connection is dead [01:25] good night [01:25] !! [01:25] !test [01:25] yes, I'm alive. [01:28] asac: ubufox is gonna need some work for Lucid...http://theunfocused.net/2009/10/06/firefox-3-6-knows-when-your-plugins-are-out-of-date/ [01:42] fta, how does gilouche look now though? [01:42] no change [01:43] humm [01:43] ok [01:43] ryan said gilouche shouldn't pick up anything from the gtk theme [01:43] like the others do [01:44] ui is frozen :( [01:44] humm [01:44] damn [01:45] it's crashing [01:46] dbus related [01:46] http://paste.ubuntu.com/286626/ [01:46] oh... that's good then! [01:46] woot [01:47] ok, so that helps me know what to do for exception handling :) [01:47] much better than just hanging... [01:47] i'll work on that later tonight [01:48] great [07:10] asac, hi === micahg1 is now known as micahg [08:22] morning [08:25] morning bdrung_ [09:45] asac: do you want to implement something, before i release m-d 0.17? [09:45] morning [09:45] wait [09:45] bdrung_: does that mean that we need to have the extensions use 0.17 instead of 0.16 [09:47] eagles0513875: hi, you do not need to bump the build-depends. it is a bug fix release, so only package which fail with 0.16 requires 0.17 [09:48] ok bdrung_ is that going to be in the repos or will i have to install it form upstream [09:49] eagles0513875: it will be in the repos sooner or later (uploaded to debian and sync to ubuntu) [09:49] alright cuz i get 16 from upstream [09:49] but not at home at the moment so i dont have internet access from my karmic partition [09:50] eagles0513875: 0.16 is in karmic, too [09:50] at the time it wasnt yet [09:50] this blows i cant even download stuff via vm :( [09:51] at least i have irc access lol [09:55] bdrung_: im planning on rolling my own distro based on kubuntu how could i create my own repos since i only want certain packages that will pertain to what my distro will be focusing on [09:58] eagles0513875: you can use a ppa if you want it public. there are tool to create a repo if you want a local repo. i use a flat format (drop all .deb files into a directory) and apt-ftparchive to create it. [09:59] bdrung_: which in ur opinion is better. im thinking of making a gaming distro for gamers and game developers woudl it be better in a ppa or local repo [10:00] eagles0513875: the packages in the ppa must be free (= libre) and the space is limited: 1 GB, you can increase it to 2, 3 GB an so on. [10:01] ok so if one doesnt have the bandwith it would be better to use the ppa's [10:01] eagles0513875: why do you want to create an own distro instead bringing the packages into ubuntu? [10:01] they are probably there [10:02] eagles0513875: yes [10:02] i would like to do something like ubuntu studio but focused on gaming and game development [10:02] in all honesty i havent seen anythign focused on gamers [10:02] eagles0513875: so you do not need an repo, you only need an installation cd/dvd [10:02] right now you got me thinking again [10:03] keep it as my own distro or create it to add to the ubuntu line [10:04] an own distro is lot more work to maintain [10:05] ya i hear ya on that [10:05] you think it would catch on with gamers and game developers? [10:14] hi [10:14] * asac goes and gets some coffee [10:15] morning asac [10:15] seems the network storm at my provider is over ;) ... no reconnect for hours ;) [10:15] hehe asac there was a netsplit just now [10:16] yeah. but netsplit is better than /me going crazy because my net connection goes up/down all the time ;) [10:16] bbl gonna grab lunch [10:16] asac: bdrung_ said something bout dev scripts 0.17 before not sure if u saw it [10:18] yeah. i will talk to him [10:18] have to get some coffe first ;) === jtv is now known as jtv-sprint [11:35] mac_v: intertestingly redhat folks said they think our current wireless icons are the ones that should be used for 3g ... and wifi be something more like what is used on mac for wifi [11:35] from what i understand thats more like the favicon from there: http://wireless.kernel.org/en/users/Download/stable/ [11:35] but no guarantees on that. .. just guessed that from the verbose description of how it looks on mac ;) [11:36] i can screen shot what wifi looks on mac since im on one [11:36] eagles0513875: thx!! [11:36] no problem [11:37] eagles0513875: maybe capture screens for states: connected, disconnected, CONNECTING [11:37] now to figure out how to screenshot [11:37] haha [11:37] alt + print ;) [11:37] hehe will have to do it from home then lol [11:37] in java lecture atm [11:38] eagles0513875: you can take screens in lectures ;) [11:38] shouldnt be bad [11:38] hehe ya i know [11:38] asac: interesting indeed ;) ... [11:38] but i have to be careful [11:39] unless mac_v is on a mac and can do the screens [11:39] lol [11:39] eagles0513875: not using a mac here ;) [11:39] heheh then whats with the name :P [11:40] eagles0513875: it was supposed to be "mach" .. but the nick was taken :( [11:40] asac, is it possible to import history.dat from firefox to epiphany? [11:40] asac, in a sane way [11:40] mac_v: anyway, they seem to spy on us ;) ... dan knew everything about our current artwork and had this discussed with his UX folks etc. [11:40] well ill try and get the screen shots. if im not mistaken though asac wicd has something similar to what mac has [11:40] which i find cool because i have absolutely no idea what fedora uses atm ;) [11:40] \o/ [11:41] i cant install wicd to confirm because all downloads are blocked form here for the love of god and its upsetting [11:41] mac_v: so what he basically said was that they think our current wifi icons are good for 3g + signal strength :) [11:42] eagles0513875: i want mac screens [11:42] ;) [11:42] the genuine ones [11:42] ok well i forgot i have an hr and a half free after this i can do it in [11:42] asac: ah... wait .. i think i had screenies from ... [11:42] if its wicd i will always keep in mind: "wow, mac must suck" [11:42] heheh no its not wicd [11:42] av`: i dont think there is away for that [11:42] atm [11:42] but the look is similar to that of wicd if i am not mistaken [11:43] asac, damn it : / anyway is the epiphany-webkit PPA package (webkit team) the latest one? [11:43] asac, I mean the one with those crashes fixed [11:43] av`: also i think firefox uses sqlite ... so the .dat is something youstill have from ffox 2 [11:43] av`: no. the latest is the current epiphany-browser source in the archive (it ftbfs) [11:44] asac: this seems to be from leopard > http://seanmcgrath.files.wordpress.com/2007/10/sean-leopard-desktop.png [11:44] if you want to check what we can do about the build failure thatw ould be cool ... otherwise is on my list for after lunch [11:44] asac, that's the synced package from debian [11:44] mac_v: yeah. thats what he was talking about ;) [11:44] but i dont like using the curves :( ... the icons wont be crisp [11:44] mac_v: he said its used in multiple places already ... like mac, android, etc. [11:44] asac, it works on debian but ftbfs here [11:45] mac_v: but its obvious why our UX team wants greyscale tray icons :/ [11:45] yeah , UX loves OSX [11:45] :/ [11:45] i hate greyscale ... at least thats what i have in mind if i see firefox on mac [11:45] i just looks "sad" ... like grey weather [11:46] hehe , i dint like it initially either... /me like color icons everywhere... [11:46] asac: but they make some sense' [11:46] cool. lets start a new distro ;) [11:46] i always wanted to make a pink distro for girls ;) [11:46] ;p [11:47] i have no idea what makes and what makes not sense [11:47] asac: hmm... there was a recent SiDa group for that [11:47] all i know is that its not good to switch to greyscale until we moved 90% of apps there [11:47] so you dont see grey and acolored icon [11:48] asac: the UX says , the notification icon are a constant presence , so using color gives the icons undue prominence... but rather if we use color only for errors , then the icons will pop-out when the icons gain color... [11:48] notification area icons* [11:49] mac_v: notification icons are a bit different to tray icons ... for me notificafion icons are the ones you see in notify-send ;) [11:49] i meant tray icons ;p [11:49] mac_v: yeah. i like the "color" approach for errors [11:49] do we do that for nm-no-connection atm? [11:50] asac, 3.7 is red [11:50] yup , for any errors [11:50] warnings > battery low [11:51] asac: is devscripts .17 in repos now? [11:52] asac: whats happening with translations for the extensions [11:53] asac: i want to drop lsb-release from m-d and release 0.17 to debian and 0.17ubuntu1 to ubuntu. objections? [11:53] bdrung_: let me know when its released so i can repush bindwood [11:53] eagles0513875: no, i will ping you, when it's released. [11:54] eagles0513875: does bindwood have problems with 0.16? [11:54] eagles0513875: otherwise you do not have to wait [11:54] bdrung_: when i installed it from upstream 0.16 and built it and tested it it didnt work. then there was some updates which allowed it to work to firefox or something not sure which but its working now [11:55] bdrung_: i also havent implemented everything that is in the wiki checklist [11:56] eagles0513875: can you give me a link to your current version of bindwood? [11:56] c [11:57] https://code.launchpad.net/~eagles051387/firefox-extensions/bindwood.ubuntu.lp425631 [11:57] thats my last push with devscripts 0.16 on firefox on kubuntu [11:58] bdrung_: why do we want to drop lsb-release again? [11:58] bdrung_: why cant we stay with 0.16 of devscripts for karmic and then push to 17 for 10.04? [11:59] eagles0513875: we dont need to bump all extensions to >= 0.17 [11:59] 0.16 should be fine for most and if its not needed we dont need to bump the lower version [11:59] eagles0513875: 0.17 fixes some bugs [12:00] asac: wouldnt it be better to try keep all extensions at the same version [12:00] bdrung_: gotcha [12:00] no [12:00] ok [12:00] you dont raise build depends if its not needed [12:00] asac: instead of having one version for Debian and Ubuntu (using lsb-release), i want to have two different versions in Debian and Ubuntu [12:00] that eases work for backporters etc. [12:00] ahhhh ok [12:00] bdrung_: for now i dont see the benefit of maintaing different branches [12:01] bdrung_: let me know if you have issues with bindwood [12:01] bdrung_: we can ship some config file [12:01] that contains info about the release [12:01] if we dont want to run lsb-release at runtime [12:01] but even that .... what is the win? [12:02] asac: 1. fix http://qa.debian.org/debcheck.php?dist=unstable&package=mozilla-devscripts [12:02] asac: 2. it will be faster! [12:04] asac: and we do not have to update the debian version, if we change something of the ubuntu magic [12:04] bdrung_: for 1. we can use build-time dependency [12:04] i dont see 2. as an issue [12:04] bdrung_: isnt that going to create more work in a way for those of you who are upstream maintainers [12:05] bdrung_: well. its well understood that its a win of having packages in sync [12:05] so better make the package that it works everywhere [12:05] so i sbuild-time dependency ok? [12:05] producing a "default" config file or somethign that tells "DISTRO=Debian/Ubuntu" ? [12:05] asac: ok, will make a built time dependency [12:05] yes. just try to not make the xpi.mk a .in ;) [12:06] asac: how about putting the magic into a separate file? [12:06] which magic? [12:06] i think that having a conffile with a key DISTRO=... would be good [12:07] at best so that we can still override it with DISTRO=xxxx [12:07] during make [12:07] like make -f /usr/.../xpi.mk DISTRO=ubuntu [12:07] asac: line 81 till 141 [12:08] bdrung_: we can move debian parts to xpi-debian.mk ... and ubuntu parts top xpi-ubuntu.mk ... and then include the right one based on the DISTRO config [12:08] or make a unified xpi-pkg-data.mk [12:08] with the appropriate if/else [12:09] i think we should go that way ... and later make .conf files out of that info [12:09] etc. [12:09] xpi-pkg-data.mk sound good [12:10] and on installation is either xpi-pkg-data-Debian.mk or xpi-pkg-data-Ubuntu.mk copied to /usr/share/mozilla-devscripts [12:10] bdrung_: actually i would also like a DISTRO=all feature ... so i can produce .debs that work everyhwere (if i release them outside the distro) [12:10] bdrung_: for "all" we should ship everything everywhere ... just a different default [12:11] i would prefer if the .deb is identical minus the default conf for the DISTRO value [12:13] asac: ok. so how to implement the DISTRO value? [12:15] asac: im out for now will get u those screen shots [12:15] ping me when i get on later [12:15] ship a xpi-defaults.mk.in debian/rules with just DISTRO =? @distro@ for now [12:15] then in xpi.mk include all xpi-data-X.mk if DISTRO = all [12:15] otherwise just xpi-data-$(DISTRO) [12:16] TARGET_DISTRIBUTION is probably mayb a better more meaningful variable name [12:16] or just TARGET=... [12:16] k [12:16] maybe XPI_TARGET [12:16] so we dont conflict [12:16] with eventual other uses of TARGET [12:17] asac: why not TARGET_DISTRIBUTION? [12:17] its quite long and we probably need to prefix it with XPI_ anyway [12:17] and when we prefix it we can use the namespace as we like [12:17] and XPI_TARGET_DISTRO? [12:18] that would work for me. also XPI_DISTRO ;) [12:18] asac: didn't we use MOZ_ as prefix? [12:18] just choose something [12:18] bdrung_: hmm. not sure. i think we mixed it up somewhat [12:19] seems we used MOZ_XPI_ [12:19] except for MOZ_EXTENSION_PKG [12:19] so MOZ_XPI_DISTRO = ... [12:19] maybe? [12:19] and MOZ_EXT_NAME [12:20] asac: or do we want to drop MOZ_ for the future? [12:20] asac: then i would choose XPI_DISTRO [12:21] i dont think we should drop MOZ_ ... i think the MOZ_EXT_NAME came in late ;) [12:21] i want to provide a rather stable api than always transitioning ;) [12:22] asac: so rename MOZ_EXT_NAME to MOZ_XPI_EXT_NAME (it is new and not used yet)? [12:22] so MOZ_XPI_DISTRO [12:22] yes. for excersize we should provide backward compatibility (we dont know if its used outside of debian) [12:23] like move MOZ_EXT_NAME to deprecated section etc. [12:23] asac: yes to the rename? [12:24] ack ... and support MOZ_EXT_NAME too (as deprecated) [12:25] arg, supporting MOZ_EXT_NAME? [12:25] that's not simple [12:26] asac: what is with MOZ_XPI_MOZILLA_EXTRA_DIRS? there is a "TODO: implement this!" [12:26] ifneq (,$(MOZ_EXT_NAME)) MOZ_XPI_EXT_NAME ?= $(MOZ_EXT_NAME) ... doesnt that work? [12:27] yes. thats a bug from what i can tell [12:27] k, somethink like that should work [12:27] the difference to MOZ_XPI_MOZILLA_DIRS is that its ment to be absolute paths [12:28] rather than just the dir name used in MOZILLA_DIRS /usr/lib/$(MOZ_XPI_MOZILLA_DIRS)/extensions [12:28] asac: but do we need this? [12:29] i think this can come handy for all the stuff we dont have in -data [12:29] again mosly for outside-distro stuff [12:30] mostly [12:30] do you have a laptop with bluetooth? [12:31] (using right now i mean ;)) [12:31] ship 61-gnome-bluetooth-rfkill.rules, which enables access to /dev/rfkill for users (LP: #436694, #441800); also see rh:514798 [12:31] https://edge.launchpad.net/~asac/+archive/ppa/+packages [12:31] need someone to verify that before i upload ;) [12:32] * asac gets his lappy [12:37] * asac needs to upgrade 1000M of packages :/ [12:49] asac: i have a laptop with bluetooth, but have no device to connect to. [12:50] bdrung_: the important part is to see if the "turn off/on" menu entry appears and _works_ ;) [12:50] asac: how to manage packages that are in debian and ubuntu? prefer the configs of debian? [12:50] no device needed [12:51] asac: can test it later, first is m-d [12:51] bdrung_: sure. i am upgrading system on my own now ... so go for md ;) [12:51] bdrung_: what are the "configs" of debian? [12:52] asac: the _sol and _eol variables [12:53] bdrung_: example? [12:53] which package? [12:53] asac: xulrunner-1.9 xulrunner-1.9.1 [12:53] why would those be different? [12:54] asac: what to do with packages that are not in debian and ubuntu? [12:54] doesnt debian have xulrunner-1.9.1 in experimental? [12:55] asac: if i define them with ?= and include debian first, then ubuntu defines will be ignored [12:55] asac: yes, xulrunner-1.9.1 is available [12:56] i think _sol and _eol should match for most packages. otherwise we need xpi-data-all.mk [12:56] which might be a good idea actually [12:56] ship xpi-data-all ... including all and defining common packages [12:57] asac: you mean a xpi-data-common package? [12:57] not package ... .mk [12:57] bdrung_: i was not talking about different packages ... just different .mk files [12:57] (in case we misunderstood) [12:58] s/package/file [12:58] bdrung_: i would say ship a -all.mk [12:58] in that way we can just include [12:58] xpi-data-$(MOZ_XPI_DISTRO..) [12:58] .mk [12:58] so that we have xpi-data-common.mk xpi-data-Ubuntu.mk xpi-data-Debian.mk and xpi-data-all.mk [12:58] and -all includes all distros we have specific packages for [12:58] bdrung_: yeah. either make -common or put that in -all [12:59] xpi-data-Ubuntu.mk depends on xpi-data-common.mk [12:59] xpi-data-Debian.mk depends on xpi-data-common.mk [12:59] sure [12:59] i understand [12:59] its ok to have -common [12:59] and xpi-data-all.mk depends on xpi-data-Ubuntu.mk xpi-data-Debian.mk [12:59] yep [12:59] k, will implement this [13:58] asac: which id does sunbird have? [14:02] bdrung_: https://wiki.mozilla.org/Talk:Extension_Dependencies [14:02] {718e30fb-e89b-41dd-9da7-e25a45638b28} [14:02] {718e30fb-e89b-41dd-9da7-e25a45638b28} [14:02] i think that one [14:02] {e2fda1a4-762b-4020-b5ad-a41df1933103} [14:02] lightning [14:02] (sunbird === iceowl ... lightning == iceowl-extension [14:03] seems there also is a [14:03] :( [14:03] lets ignore that ;) [14:04] ignore or ignore it totally? [14:13] for now [14:13] dont implement that variant atm [14:13] ;) [14:15] bug 444540 [14:15] Launchpad bug 444540 in mozilla-devscripts "add support for rdf:alt targetApplications" [Wishlist,Triaged] https://launchpad.net/bugs/444540 [14:18] asac: why did you open a bug. now i have a reason to implement it. ;) [14:18] haha [14:18] just so we dont forgert [14:18] and maybe loose the example ;) [14:18] its wishlist and i milestoned it as Ubuntu:later [14:19] so you dont feel its important [14:19] its in fact a real minor corner case imo [14:19] if we dont get a real bug report its just "nice to have" [14:20] asac: a realworld example would be better for testing [14:21] LaPingvino: hi [14:21] hello [14:21] It was a long time ago [14:21] but then I talked with you about language packs [14:22] for firefox [14:22] sorry, i dont think i remember that :) [14:22] maybe if i know more context [14:23] for the Esperanto translations to be available for use in linux [14:23] I guess it won't be updated for Jaunty any more and I have to check Karmic on it? [14:23] asac: should we recommend firefox-3.5 first? [14:23] yes [14:23] bdrung_: imo we shouldnt start to tweak ordering [14:23] but maybe i am wrong ;) [14:23] asac: you are wrong :p [14:24] * LaPingvino returns quickly, off for sanitary reasons [14:25] why does ordering matter? [14:25] the idea of recommends was that you can install it even without a package [14:25] the main use case is to install extensions _after_ installing the target application anyway [14:25] so its fulfilled [14:26] tweaking order is mostly useful for seeding software etc. but those should select the target application explicitly too [14:26] or if our extension is a build depend ;) [14:26] asac: in this case it does not matter. but if you have nothing installed, then the first will be pulled [14:27] yes. but thats really uncommon. and going through the maintenance burden and paying the price that backports are not trivial feels not worth it [14:27] * LaPingvino returned [14:28] i think in the end we might have some priority mechanism. but i think its not completely understood how we want to do that [14:29] asac: that yes was turned to me? [14:29] LaPingvino: yes ;) [14:30] ah, I will download the beta then [14:30] if something is wrong you'll know, but I suppose it's all right then :) [14:31] thanks a lot [15:03] asac, how it's epi triaging going? [15:03] did you find a fix for the ftbfs? [15:04] not looked [15:04] if you want to look you have 2h time ;) [15:05] gonna have a look at it in a few, then I'm off for 5 hours [15:05] yes so that works ;) [15:05] will be back in 2h if you dont have a fix will take over ;) [15:06] ok, if I find something, gonna leave you a message [15:06] kk [15:40] asac, fixed [15:41] asac, preparing a debdiff for you to apply, so you can upload it [15:53] asac, mail sent to asac@u.c [15:53] asac, with a link to the debdiff [15:54] cya later === Moot2 is now known as MootBot [16:54] micahg1, asac: ff 3.7 needs some lobe [16:54] love [16:57] fta2: what failed? [16:57] a patch [16:58] I don't see it [16:58] look at yesterday's builds [17:00] ok, I don't know if I can get to this soon, but I can for sure fix tonight [17:50] hey guys [17:53] hi [17:53] eagles0513875: bindwood builds with m-d 0.16 [17:54] bdrung_: for me when i first built it with 0.16 it wasnt working for me on kubuntu karmic 64bit [17:54] now it is i think asac updated something which is now allowing it to work [17:55] eagles0513875: your explanation sound weird. building with 0.16 should be reproducible [17:55] this was prior to 0.16 getting synced downstream i believe [17:56] once it was synced downstream i believe thats when it started working [18:15] eagles0513875: get over that incident. all is fine now. done. [18:16] asac: i am m8 bdrung_ was nice enough to confirm that its working for me and me not going crazy thinking it was a fluke that it randomly started working [18:17] yeah [18:17] thought i had lost my mind [18:18] asac, did you check my debdiff? [18:18] av`: yes. did you reproduce it in pbuilder and that really fixes it? [18:19] asac, it builds fine here [18:19] yes. but did you confirm that it didnt work without that fix [18:19] for me that felt more like a warning and not the real error [18:19] we have a problem with the girepository thing [18:19] from the log [18:19] av`: maybe upload to a ppa with ~ppa appended so we can see [18:19] asac, no the problem is a missing directory [18:19] asac: pushed m-d. it is ready now for release. if there are no objections, i will release it in some hours, when i am back from brass practice [18:20] asac, GVFS-RemoteVolumeMonitor-WARNING **: cannot open directory /usr/share/gvfs/remote-volume-monitors: Error opening directory '/usr/share/gvfs/remote-volume-monitors': No such file or directory [18:20] aborting... [18:20] it aborts cause of that ;) [18:20] bdrung_: can we do the release tomorrow. its probably fine, but would like to look at the changes for the new debian/ubuntu split stuff [18:20] and wont have time today [18:20] 19:20 < av`> asac, GVFS-RemoteVolumeMonitor-WARNING **: cannot open directory /usr/share/gvfs/remote-volume-monitors: Error opening directory '/usr/share/gvfs/remote-volume-monitors': No such file or directory [18:21]