[00:52] <mwhudson> so i've been told a bug i reported is fixed in a new package "which is due to be installed in the Debian FTP archive"
[00:52] <mwhudson> can i see this new version somehow?
[00:52] <mwhudson> it's not in http://packages.debian.org/sid yet
[00:53] <ScottK> mwhudson: Is this the python-defaults one?
[00:54] <ScottK> mwhudson: If it is, that was uploaded to Experimental, not Sid.
[00:54] <mwhudson> ScottK: yes
[00:54] <ScottK> It's in Experimental then.
[00:55] <mwhudson> ScottK: so what is experimental then?  is it a bit like -proposed for ubuntu?
[00:55] <ScottK> No.
[00:56] <ScottK> It's for stuff that's not suitable for Unstable and then Testing.  In this case, because Debian is frozen for the Squeeze release, it was uploaded there to keep Unstable clear for any emergent bug fixing needed for Squeeze.
[00:56] <mwhudson> ah ok
[00:57] <mwhudson> can/should i do anything to prod the fix into maverick?
[00:58] <ScottK> At this point you probably will.  I'd ask doko about it.
[00:58] <mwhudson> ok
[01:00] <doko> ScottK: ?
[01:01] <ScottK> doko: Do we want to update python-defaults from experimental before release?
[01:01] <ScottK> The 2.6.6-2 upload that was done today?
[01:01] <doko> ScottK: yes, but not now
[01:01] <ScottK> doko: OK.  When?
[01:02] <doko> oh, python-defaults, not 3. yes this is ok
[01:02] <ScottK> OK.
[01:02] <ScottK> mwhudson: It it's not done by Wednesday, please remind me.
[01:02] <mwhudson> ScottK: ok
[07:35] <pitti> Good morning
[07:35] <bilalakhtar> good morning pitti !
[07:43] <pitti> hey bilalakhtar, how are you?
[07:44] <bilalakhtar> pitti: fine, you?
[07:44] <pitti> bilalakhtar: I'm great, thanks! back from a week of vacation
[08:32] <tkamppeter> pitti, hi
[08:32] <pitti> hello tkamppeter, wie gehts?
[08:32] <pitti> tkamppeter: I saw your jockey patches, thanks! will look at them today
[08:33] <tkamppeter> Gut, Du hast gefehlt auf dem IRC.
[08:34] <pitti> tkamppeter: right, was on holiday, far away from the internets
[08:36] <tkamppeter> pitti, the patches are very important, as Epson expects their packages to auto-download on Maverick and Ricoh is complaining for more than a year that PPD package auto-download is too slow, most important factor being Jockey, but the s-c-p part I have also accelerated by the compressed PPD archives and a bug fix in s-c-p.
[08:37] <tkamppeter> pitti, the slow and space-consuming Foomatic XML database is also replaced by a compressed PPD archive now.
[09:07] <amitarora> pitti: ping
[09:07] <pitti> !ping | amitarora
[09:07] <pitti> bah
[09:07] <pitti> amitarora: hello; please just ask your question, don't ping
[09:07] <amitarora> pitti: I got your reference from amitk .. this regarding bug# 627975
[09:08] <amitk> bug 627975
[09:08] <amitarora> pitti: the bug has a patch for PowerTOP which makes it work on ARM boards as well ..
[09:08] <amitarora> pitti: its been accepted upstream. The last comment has the details ..
[09:09] <amitarora> pitti: can you please help getting it merged with PowerTOP branch for Maverick release ?
[09:10] <pitti> amitarora: yes, I can sponsor it; I'll assign it to me
[09:10] <amitarora> pitti: great, thanks!
[09:23] <tkamppeter> pitti, an important bug we need to get fixed for Maverick is bug 494141. The fix is already described in the bug report, but I cannot upload it as it has to be done in the Samba package. It is a one-line patch on /etc/init/smbd.conf.
[09:24] <pitti> tkamppeter: can you please discuss that one with slangasek?
[09:26] <tkamppeter> slangasek, can you have a look at bug 494141? It is a one-line patch which will help users a lot, both in Maverickj and as SRU for Lucid.
[09:37] <popey> greetings earthlings!
[09:38] <pitti> \\//
[09:38] <popey> bug 631103 could do with some attention, simple packaging error. Could a core-dev please take a look?
[10:43] <tkamppeter> pitti, about bug 604698, can we simply take my patch to do the Jockey (list packages) part and for the key verification part for Maverick simply include the Epson key in the distro (there is no other key yet) and implement the general key downloading in Natty?
[10:44] <pitti> tkamppeter: we need to filter for Epson packages only then
[10:44] <pitti> tkamppeter: but yes, that would work
[10:47] <tkamppeter> pitti, if Jockey installs a package, does it go through the standard mechanism with key verification, like it happens with apt-get (there I get a warning and asked whether I really want to do it if the package does not have a known signature)?
[10:47] <pitti> tkamppeter: yes, it does use apt for every package operation
[10:57] <\sh> siretart, ping could you start a backport process for fai maverick to lucid , kthxbye :)
[11:03] <tkamppeter> pitti, so we could use my patch plus including Epson's key in Maverick. Then we will create a key download functionality in Natty. If other manufacturers show up and want their drivers in Maverick, we could perhaps even add keys as update for Maverick.
[11:03] <pitti> tkamppeter: plus a filter "only epson packages"
[11:04] <pitti> (or noarch)
[11:06] <tkamppeter> pitti, assuming that there is a non-Epson package on OpenPrinting, so having a key which is not included in Maverick. What happens if the user sees this package in Jockey and clicks on "Install". Will then a message pop up telling the user that this package has no known signature and the user gets asked whether he really wants it?
[11:07] <pitti> no, such a question would be pointless
[11:07] <tkamppeter> pitti, what would really happen in such a case?
[11:07] <pitti> it would currently just install it anyway, since apt merely gives a warning if a key isn't present
[11:08] <tkamppeter> pitti, so the selection of packages we accept is hardcoded in Jockey and not data-driven?
[11:08] <pitti> tkamppeter: it's not hardcoded
[11:09] <pitti> tkamppeter: right now we only offer Ubuntu packages, and as a compromise, (unsigned) noarch packages from openprinting
[11:09] <pitti> adding epson key and a filter for it would start hardcoding
[11:11] <tkamppeter> pitti, this (and any SRU to satisfy other manufacturers) would be a Maverick-only interim solution. From Natty on we should have real support for OpenPrinting's key link facility.
[11:12] <pitti> *nod*
[11:12] <pitti> tkamppeter: also, your patch would remove the support for unsigned PPD-only packages, AFAICS?
[11:14] <tkamppeter> pitti, no, first, I have tested with Ricoh PPD packages, second, I have added a second search task to the task list. So when starting the task list two requests per printer are sent to OpenPrinting, one for the noarches and one for the signed.
[11:14] <pitti> tkamppeter: ah, that wasn't in the originally sent patch then
[11:16] <tkamppeter> pitti, the patch attached to bug 604698 does exactly this.
[11:16] <pitti> tkamppeter: I meant http://launchpadlibrarian.net/55226929/download-also-signed-binary-printer-driver-packages.patch
[11:17] <tkamppeter> pitti, I see, the patch is the wrong way around. Take the debdiff.
[11:17] <tkamppeter> pitti, and in the debdiff the patch on detection.py.
[11:18] <siretart> \sh: I put it on my todolist, but no promises, it is rather longish :-(
[11:25] <diwic> seb128, ping
[11:25] <seb128> hi
[11:25] <seb128> contextless ping are not really useful though
[11:25] <seb128> better to just ask your question
[11:26] <diwic> seb128, you're sebastien bacher, right?
[11:26] <seb128> yes
[11:26] <seb128> why?
[11:27] <diwic> seb128, you seem to have declined bug #433654 without giving a reason?
[11:27] <seb128> could be
[11:27] <diwic> for Maverick
[11:27] <seb128> I've declined over 300 bugs
[11:27] <seb128> the list had some 600 bugs
[11:27] <seb128> still quite some to clean
[11:28] <seb128> it's just that it's not tracked as a blocker for maverick, it's not a new issue
[11:28] <seb128> nothing prevent to fix it though
[11:28] <\sh> siretart, don't worry about time...I just want to have it from my table ;)
[11:28] <diwic> seb128, okay, so I can just go requesting a sponsorship as usual given I write a patch for it?
[11:29] <seb128> it's being discussed on #ubuntu-desktop by somebody else at the same time
[11:29] <seb128> weird timing
[11:29] <seb128> or you guys just discussed it somewhere else and decide to go ping different channels?
[11:29] <seb128> but yes you can get any change uploaded
[11:30] <diwic> seb128, probably there was a comment recently that woke us both up?
[11:30] <seb128> the nomination is just a way for people to track issues for the release
[11:30] <seb128> the release team can't track every bug
[11:31] <seb128> not accepting the nomination just need not tracking it as a blocker issue for this cycle, it doesn't mean a fix can't be uploaded
[11:31] <diwic> okay, I understand.
[11:31] <seb128> need->mean
[12:03] <cjwatson> in case anyone other than me noticed, I think I see why jigdo downloads of maverick always falsely claim an incorrect checksum right now
[12:14] <cjwatson> lex79: they already seemed to be there
[12:19] <tkamppeter> pitti, bug 604698 has an updated debdiff now.
[12:20] <pitti> tkamppeter: thanks
[12:21] <tkamppeter> pitti, stop, I got into the find() trap of Python. Please wait for the next debdiff.
[12:46] <tkamppeter> pitti, I have corrected the debdiff now, take the one of comment #5.
[13:00] <tkamppeter> slangasek, hi
[13:04] <htorque> hello, is irc-logging not working? http://irclogs.ubuntu.com/2010/09/13/ is empty.
[13:05] <tkamppeter> mv, glatzor, can you have a look into bug 633913?
[13:05] <tkamppeter> mvo, ^^\
[13:06] <tkamppeter> mvo, glatzor, this is rather annoying to get all the pop-ups when system-config-printer is searching a driver for an unsupported printer.
[13:24] <apw> pitti, something has gone very wrong with the burn down chart start value overrides for all my charts except for the overall
[13:24] <apw> pitti, i am suspicious they are all at the value defined by ['all']
[13:25] <apw> pitti, and so i am suspicious this is related to the burnup support that was merged recently
[13:30] <pitti> apw: right, they currently keep crashing
[13:30] <pitti> apw: I already mailed Clint
[13:30] <ogra> but it makes the trendlines looks so good ...
[13:47] <apw> pitti, i assume thats also why we have two days missing
[14:01] <smoser> pitti, or someone on sru team, can I please get bug 634102 into lucid-proposed soon?  this is fairly serious issue for people using our images and the new instance size on EC2. The simple diff is at http://launchpadlibrarian.net/55301846/cloud-init_0.5.10-0ubuntu1.2_0.5.10-0ubuntu1.3.diff.gz .  I'm really sorry to nag.
[14:03] <apw> cjwatson, we have an old binary package hanging around in the archive linux-libc-dev at version 2.6.35-903.8 for armel which is blocking binary uploads for armel.  this version is orphan against an old source package so I believe it should be reapable; who/how/what triggers that?
[14:04] <apw> (all in maverick)
[14:04] <cjwatson> I can check it out and remove it, but you still won't ever be able to upload the same package at the same version
[14:05] <apw> when you say same version, do you mean exactly that version?
[14:05] <cjwatson> yes
[14:05] <apw> that i can cope with
[14:05] <cjwatson> single-architecture removals don't always get noticed automatically
[14:05] <cjwatson> wait, this still means the version will go backwards
[14:05] <cjwatson> um, I don't have control over allowing that
[14:06] <cjwatson> it's disallowed because apt clients will never notice the downgrade automatically
[14:06] <apw> so the high water mark on a binary package is permentant regardless of the existance of a package at any version
[14:06] <cjwatson> yes
[14:07] <apw> cjwatson, is that something that can be fixed for this one binary package given enough genuflecting ?
[14:07] <cjwatson> I'd recommend artificially bumping the version of just that binary package
[14:07] <cjwatson> to something that's greater than 2.6.35-903.8 but less than 2.6.36-1.1
[14:07] <apw> the package was generated in error, from a different source package and should never have been installed
[14:07] <cjwatson> you can do this by invoking dpkg-gencontrol with the right options
[14:08] <cjwatson> (-vVERSIONYOUACTUALLYWANT)
[14:08] <cjwatson> so sed the source package version to replace the -21 part by (say) incrementing it by 1000
[14:09]  * cjwatson quickly ctrl-c's this removal and hopes I caught it in time
[14:09] <cjwatson> because if I remove linux-libc-dev then *nothing* will build on armel ...
[14:09] <apw> argle
[14:10]  * apw stares into the abys
[14:10] <cjwatson> you can pass arguments to dpkg-gencontrol via dh_gencontrol by saying dh_gencontrol -plinux-libc-dev -- -vblah
[14:11] <cjwatson> https://edge.launchpad.net/ubuntu/maverick/armel/linux-libc-dev/2.6.35-903.8 still says "Status: Published" so I hope I caught it
[14:12] <apw> cjwatson, ok that is totally vile ... what a mess ... will go figure out the cleanest fix
[14:34] <tkamppeter> pitti, have you seen my new debdiff?
[14:35] <tkamppeter> mvo, hi
[14:41] <tkamppeter> slangasek, ping
[14:41] <mvo> tkamppeter: hello
[14:43] <tkamppeter> mvo, it is about bug 633913, session-installer produces two annoying pop-ups when system-config-printer searches for drivers on the internet.
[14:44] <tkamppeter> mvo, first is simply an error message where session-installer should error out silently and the second is a crash (causing apport pop-up).
[14:45] <mvo> tkamppeter: ok, I check it out, thanks
[14:46] <tkamppeter> mvo, I would like to have them removed/fixed before Final Freeze so that manufacturer printer driver download goes smoothly and quickly.
[14:58] <mvo> tkamppeter: I uploaded a fix, please test once it hits the archive
[15:00] <tkamppeter> mvo, thanks, will try it as soon as it arrives.
[15:01] <kirkland> BlackZ: so have you tried booting a vm from PXE with the new etherboot package?
[15:01] <kirkland> BlackZ: does it work?
[15:01] <BlackZ> kirkland: no, that's the reason why I reintroduced the kvm-pxe package
[15:01] <kirkland> BlackZ: see: https://wiki.ubuntu.com/VirtFeatureVerification
[15:01] <kirkland> BlackZ: hallyn has a test case in there
[15:02] <BlackZ> kirkland: looking
[15:05] <BlackZ> kirkland: so, we should keep the kvm-pxe package, right? also, on http://people.canonical.com/~ubuntu-archive/sync-blacklist.txt I read "# stevenk, we don't want qemu or kvm from Debian, talk to kirkland"
[15:12] <kirkland> BlackZ: right, well, we need *some* package to provide a bunch of binary ROMs to pxe boot VMs
[15:12] <kirkland> BlackZ: currently, that's kvm-pxe
[15:13] <kirkland> BlackZ: though it could be provided by some other package, I suppose, if there's good reason
[15:13] <kirkland> BlackZ: in that case, we'd need to update the depends/recommends throughout the archive on anything that has a dependency on kvm-pxe
[15:13] <kirkland> BlackZ: this should NOT be done in maverick at this point in the cycle, IMO
[15:14] <kirkland> BlackZ: as for qemu/kvm from Debian ... again, for Maverick, we're going to want to keep the qemu-kvm that we have in Ubuntu
[15:14] <kirkland> BlackZ: for Natty, we should re-examine (lool has requested it too) re-introducing the qemu package back into Ubuntu
[15:15] <kirkland> BlackZ: and possibly sourcing qemu-kvm from Debian
[15:15] <kirkland> BlackZ: when I created the qemu-kvm package in Ubuntu, it didn't exist in Debian;  I offered it to the Debian maintainers, but instead, a DD created their own qemu-kvm package and uploaded
[15:16] <BlackZ> kirkland: agreed; currently the package from Debian (etherboot-qemu) doesn't fix LP: #570870, maybe it's a path-related issue
[15:28] <tkamppeter> mvo, the new version of sessioninstaller fixed the problem. Thank you.
[15:29] <mvo> tkamppeter: cheers
[15:29] <mvo> tkamppeter: thanks for testing
[15:34] <chrisccoulson> hi, would a member of ubuntu-release be able to spare some minutes to look at bug 531867 please? :)
[15:39] <ScottK> didrocks: Would you please wait for the release team to approve FFe's before uploading.
[15:40] <fos> A question about language-pack-kde-de-base in hardy: Since security update 20090105 a few translation files are missing. Is this a regression worth fixing?
[15:40] <didrocks> ScottK: isn't seb128's comment an ack?
[15:40] <ScottK> didrocks: He's not on the release team.
[15:41] <fos> https://bugs.launchpad.net/ubuntu/+source/language-pack-kde-es/+bug/321297
[15:41] <didrocks> ScottK: http://paste.ubuntu.com/493144/ be agreed first…
[15:42] <didrocks> ScottK: so there is a mismatch there. knowing now. thanks
[15:44] <ScottK> OK.  In any case the main thing is to get the bughugger update in now.
[15:47] <didrocks> ScottK: right, rickspencer3 will fix it soon, but not today
[15:48] <rickspencer3> maybe today
[15:53] <seb128> ScottK, hey
[15:53] <ScottK> Hello seb128.
[15:53] <seb128> ScottK, every other cycle we had delegated approved for universe
[15:53] <seb128> that's not the case this cycle?
[15:54] <ScottK> Not that I'm aware of.
[15:54] <seb128> why did that change?
[15:54] <ScottK> Not sure.
[15:54] <seb128> like the r-t doesn't want to delegate for universe anymore?
[15:54] <seb128> it doesn't seem to make sense to me
[15:55] <seb128> you guys are just claiming for extra work when you don't keep with the one you had before
[15:55] <ScottK> seb128: I'm not trying to say the current situation is right or wrong.  Just that it is what it is.
[15:55] <seb128> well are you sure there is not delegating this cycle?
[15:55] <ScottK> We've changed a number of things with the merger of the motu-release.
[15:56] <seb128> or it's just that nobody came to write an email saying who has delegation?
[15:56] <ScottK> I recall someone suggested the idea on the -release list, but no one took it up.
[15:56] <seb128> well honestly I think I'm rather helping by reviewing desktop change in universe
[15:56] <seb128> but if you feel like it's adding work fine with me
[15:56] <seb128> just seems to doesn't make any sense
[15:57] <ScottK> We've gotten rid of almost all the difference between Main and Universe in the release processes and are aiming to eliminate it entirely.
[15:58] <ScottK> It seems to me that we're keeping up with FFe requests OK, so it's not essential to have more people reviewing.
[15:58] <ScottK> Personally, I'm a lot more worried about stuff like the Mesa FFe and what the implications of that are.
[15:59] <seb128> slangasek, pitti: ^
[15:59] <seb128> would it make sense to still have delegation?
[16:00] <seb128> or extra people able to accept exceptions?
[16:01] <pitti> I'd still trust seb128 for GNOME updates or Riddell for KDE, etc., so comments from you are highly appreciated
[16:01] <pitti> NB that I'm not that active in ~release this cycle, since I'm on rotation
[16:01] <cjwatson> I'm happy with delegations; I just don't particularly want it to seem as though we're riding roughshod over universe processes - there's a social benefit in making sure we're doing things right, so if there are delegations they should be explicit
[16:01]  * cjwatson emerges briefly from trying to get kgdb to work, and dives back in
[16:08] <tkamppeter> Can it be that LP is not automatically closing bugs on uploads with "LP: #..." in the debian/changelog any more?
[16:09] <tkamppeter> pitti, did you see my last debdiff on the Jockey bug?
[16:09] <pitti> tkamppeter: I saw it, yes
[16:09] <mr_pouit> tkamppeter: it's broken
[16:09] <pitti> tkamppeter: yes, LP has a regression for that, known
[16:09] <michLinuxGuy> I am installing the beta and it seems to be frozen at "Retrieving file 2 of 6".  Is there a debug log somewhere?  If I run it from a terminal window, will I see some useful messages to stdout/stderr?
[16:12] <cjwatson> tkamppeter: bigjools has promised me that the fix will be rolled out today.  In the meantime please close bugs manually
[16:12] <cjwatson> (and you'll have to close bugs for anything during the broken period anyway - I don't think it will be retroactive)
[16:13] <tkamppeter> cjwatson, mr_pouit, pitti, thank you, I have already manually closed a ptouch-driver bug today in the morning.
[16:16] <ScottK> michLinuxGuy: You'll probably have more luck in #ubuntu-installer.
[16:18] <michLinuxGuy> ScottK: thanks
[16:19] <ricotz> could some have a look at bug 635646 ?
[16:21] <ScottK> ricotz: I'll take a look at it.
[16:23] <ricotz> ScottK, thanks
[16:39] <pavolzetor> Hallo, could someone help me with indicator applet?
[16:39] <ScottK> ricotz: Done.
[16:40] <pavolzetor> I don't know in which format should be icon passed to libindicate
[16:41] <ScottK> pavolzetor: You might have more luck on #ayatana.  That's where the relevant developers tend to hang out.
[16:41] <pavolzetor> thanks
[16:41] <ricotz> ScottK, ta
[16:41] <ScottK> No problem.
[16:45] <kees> mdke: I'm uploading a small addition to the manpages. I don't think these are translated in the standard fashion, but do I need to send a note to ubuntu-translators still?
[16:54] <tkamppeter> slangasek, around?
[16:54] <Daviey> cjwatson, Are you still around?
[16:55] <cjwatson> Daviey: yes
[16:55] <Daviey> cjwatson, RE: the avahi udeb issue...  I essentially did a rebuild
[16:55] <Daviey> cjwatson, but not convinced the shlibs issue is resolved
[16:55] <cjwatson> doesn't seem to have worked
[16:55] <cjwatson> I did suggest you test it first :)
[16:55] <Daviey> ack
[16:56] <cjwatson> oh, blast, I mistyped
[16:57]  * SpamapS absolutely despises the tab completion setup for the sqlite3 command.. :-P
[16:57] <Daviey> cjwatson, Oh well..  Are you going to be able to fix it shortly.. if notm, i don't mind taking it.
[16:58] <cjwatson> Daviey: avahi 0.6.27-2ubuntu3 will be in the archive in a bit.  Once the binaries for that are published, you can rebuild eucalyptus
[16:58] <cjwatson> Daviey: I suggest doing it locally first to check though
[16:58] <Daviey> cjwatson, wilco... I guess i should test this from a local archive :)
[16:58] <Daviey> hah
[16:59] <cjwatson> ah, if you're going to increment Build-Depends, then you can upload straight away
[16:59] <cjwatson> it'll just dep-wait
[17:00] <Daviey> cjwatson, That is what i was *planning* to do... but i take your point about testing it locally first.
[17:03] <smb> pitti, Hi Martin. May I ask for some sru love for the Hardy kernel and Lucid LBM and mvl-dove kernel in the accept queue? They are feeling unnoticed (well ok not the lbm one)
[17:16] <ScottK> http://asset.soup.io/asset/1068/5622_78d3.png
[17:17] <ion> Heh
[17:32] <SpamapS> pitti: still around? I just pushed up fixes for the problems w/ the wi tracker
[17:34] <pitti> SpamapS: back from dinner
[17:35] <pitti> smb: probably not today; I had too much to do with post-holiday catch-up, I'm afraid
[17:35] <smb> pitti, NP. I know the feeling
[17:39] <slangasek> tkamppeter: replied on the bug
[17:40] <pitti> SpamapS: thanks, merged
[17:40] <slangasek> ScottK, seb128, pitti, cjwatson: I'm certainly ok with having such delegations, but am also unlikely to drive them forward right now, sorry
[17:42] <SpamapS> pitti: do you know if the 'all' charts have been showing as all foreign for a long time?
[17:43] <pitti> SpamapS: I'm not aware of that; but then again, I haven't actually looked at the charts that often in this cycle (I'm primarily focused on OEM matters)
[17:43] <SpamapS> pitti: got it, I think it may have been forever.. but not sure. :P
[17:45] <SpamapS> pitti: and thanks for merging. :)
[17:47] <tkamppeter> slangasek, what is suitable for an SRU, switching CUPS to upstart or making samba re-scanning for CUPS?
[17:47] <slangasek> tkamppeter: samba rescanning
[17:49] <Laney> re-ping — can someone please look at sponsoring bug 539814?
[17:49] <tkamppeter> slangasek, how will this re-scanning work, is this some change in the upstream code of Samba? Will you do this fix?
[17:49] <slangasek> it would need to be an upstream code change
[17:50] <slangasek> I'm not in a position to implement it right now, no; someone should take it to upstream
[17:51] <tkamppeter> pitti, WDYT, is there perhaps a solution on CUPS which is viable for Maverick (at least as SRU) to make CUPS being started before SAMBA?
[17:55] <pitti> tkamppeter: I don't know how you can express that in upstart, I'm afraid
[17:55] <pitti> you'd need to add a wait condition to samba which says "if cups is installed, wait for it to start, otherwise start right away"
[17:55] <pitti> Keybuk: ^ can this be expressed somehow?
[17:56] <slangasek> pitti: it can, but it gets tricky because you may also have cups installed without samba
[17:56] <slangasek> so what you want is cups 'start on starting smbd or filesystem'
[17:57] <Keybuk> you can't do that, no
[17:58] <Keybuk> you do what slangasek said
[17:59] <pitti> ah, and this will hold smbd in limbo while cups is being started?
[17:59] <Keybuk> in the starting state
[17:59] <Keybuk> so not limbo
[17:59] <Keybuk> o/~ how low can you go?
[18:00] <pitti> ah, thank you
[18:00] <pitti> so, seems upstartification of cups is in order then
[18:01] <tkamppeter> pitti, could we do an upstartification of CUPS in Maverick? Or at least as SRU for Maverick?
[18:01] <pitti> upstartification is not SRUable
[18:01] <pitti> so for maverick it might land still, yes; it's not that hard to test, after all
[18:02] <tkamppeter> pitti, did you already upstartify another package?
[18:03] <pitti> I wrote a tiny upstart job or two, nothing serious so far
[18:04] <tkamppeter> pitti, probably then it is better if upstartify CUPS, also because of the handling with Debian (does Debian also use upstart)?
[18:11] <tkamppeter> pitti, probably then it is better if you upstartify CUPS, also because of the handling with Debian (does Debian also use upstart)?
[18:14] <pitti> tkamppeter: Debian doesn't use upstart right now, so this would be Ubuntu specific
[18:14] <pitti> (i. e. dpkg-vendor query in debian/rules)
[18:16] <tkamppeter> cjwatson, in bug 636887 a user complains that during an update of Lucid the file /usr/lib/cups/backend/hp (probably the package hplip) gets lost. Can it be due to hplip only being recommended in ubuntu-desktop? Should we perhaps promote it to Depends:
[18:16] <pitti> Keybuk: while we are at this, do you think it's less of an evil hack to have cups' postinst add lp, ppdev, and parport_pc to /etc/modules? instead of having this in the init/upstart script?
[18:17] <Keybuk> I think that if it needs them, it should modprobe them
[18:17]  * ogra_ac disagrees
[18:17] <pitti> ok
[18:17] <ogra_ac> we dont have parports on arm :P
[18:18] <pitti> parport_pc has modaliases, so this one should really just go
[18:18] <ogra_ac> there should be a check if such a device is available at all
[18:18] <pitti> but lp and ppdev don't
[18:18] <pitti> ogra_ac: well, I surely hope that invalid modules in /etc/modules would just be ignored? (I'd test that, of course)
[18:18] <Keybuk> aren't lp and ppdev built in? :p
[18:18] <pitti> they aren't
[18:18] <ogra_ac> they arent
[18:18] <Keybuk> oh
[18:18] <pitti> I wouldn't mind at all if they were, of course
[18:18] <Keybuk> right, parport_pc is autoloaded
[18:18] <ogra_ac> currently ther is an ugly hack in teh upstart script
[18:19] <pitti> but I'd still need those for Debian
[18:19] <Keybuk> just modprobe them then
[18:19] <ogra_ac> building them in would be good
[18:19] <ogra_ac> then we could handle it in teh kernel config
[18:19] <ogra_ac> based on the arch
[18:20] <Keybuk> assumedly the parport_pc module doesn't even exist on arm?
[18:20] <Keybuk> so the modprobe would be a no-op anyway
[18:21] <ogra_ac> it does
[18:21] <ogra_ac> sadly
[18:21] <Keybuk> hmm, no, wait that's autoloaded
[18:21] <Keybuk> so it's only ppdev and lp
[18:21] <Keybuk> and you want those on arm, right? :p
[18:21] <ogra_ac> we had a bad bug that took us out of business because it was added to teh init script
[18:21] <Keybuk> how the hell did it take you out of business?
[18:21] <ogra_ac> and the kernel just locked up when it loaded
[18:21] <pitti> someone added parport_pc despite the modaliases, since it reportedly is required on some systems
[18:21] <Keybuk> did the module getting loaded cause the roof of your house to collapse?
[18:21] <Keybuk> well, that's a kernel bug
[18:21] <Keybuk> fix that bug
[18:21] <ogra_ac> already fixed
[18:22] <pitti> ogra_ac: do we really need to build parport_pc for arm systems in teh first place?
[18:22] <ogra_ac> was in the beginning of maverick
[18:22] <pitti> that's soo 1980
[18:22] <ogra_ac> no, we dont
[18:22] <ogra_ac> on arm you will always only have network or usb printers
[18:22] <pitti> as the world should be
[18:23] <ogra_ac> well, someone might develop an arm based network hub for printers at some point
[18:23] <ogra_ac> one that also supports parport
[18:23] <ogra_ac> but we'll worry if that happens :)
[18:23] <pitti> one might also develop an USB<->grammophone adapter *shrug*
[18:23] <ogra_ac> lol
[18:24] <ogra_ac> they exist
[18:25] <pitti> Keybuk: seems with upstart scripts I can completely drop all that pidfile voodoo?
[18:25] <ogra_ac> www.amazon.de/Lenco-3866-USB-Plattenspieler-silber/dp/B000KPQ7U2
[18:25] <ogra_ac> ;)
[18:26] <Keybuk> pitti: well, upstart always knows the pid, so sure
[18:32] <apw> pitti, i think those changes have merged up, but the burndown charts seem to still have bad starts
[18:32] <pitti> SpamapS: ^
[18:32] <pitti> apw: have to leave now, can you please take this up with SpamapS ?
[18:32] <SpamapS> ?
[18:32] <SpamapS> otp...
[18:33] <apw> SpamapS, ... the burndown charts, the start of the burndown lines seem to be fubar'd ...
[18:33] <apw> its looking like they are all the ['all'] value for the milestone versions, the overall graphs seem ok start wise
[18:34] <apw> so i suspect that the ['foo'] entries are working and the [('foo', 'milestone')] entries are not
[18:38] <pitti> tkamppeter: ok, I have a first upstart script for it, but I need to continue tomorrow; Taekwondo time now
[18:39] <SpamapS> pitti we should spar in orlando ;)
[18:39] <pitti> SpamapS: Kihap!
[18:46] <SpamapS> apw: ah so its missing the trend start settings?
[18:47] <apw> SpamapS, i'd say so, it looks like its chosen 'all'
[18:49] <SpamapS> apw: so the team entries are broken?
[18:49] <apw> SpamapS, if you look at the kernel team ones, the overall cycle one 'c-k-t' in the array appears sane and what i set
[18:50] <apw> SpamapS, the ones for the individual milestones are off the chart
[18:50] <apw> SpamapS, so the ones which would be [('c-k-t', 'maverick-alpha-1')] ... those look to have a massive value which I conjecture is the ['all'] value
[18:50] <SpamapS> apw: whoa! hah ok I see it now!
[18:51] <SpamapS> apw: and I think I know where its borked in the code too
[18:52] <apw> SpamapS, yay, i've never had to actually run the collector so have no test environment to debug it
[18:52] <SpamapS> apw: you can always just download maverick.db ;)
[18:52] <apw> SpamapS, well indeed, i guess i mean i only ever play with the wiki stuff not the rest of the report stuff
[18:52] <apw> as that bit always just works ... oops
[18:58] <SpamapS> http://paste.ubuntu.com/493232/
[18:58] <SpamapS> thats the offending code.. but it looks right to me.. hrm
[18:58] <apw> unless milestone is broken
[18:59] <apw> there is also an override in there in places, which might be makeing those get ignored
[18:59] <apw> generate-all:    report_tools.run_reports(my_path, opts.database, basename, opts.config, trend_override=str(trend_starts['all']))
[19:00] <apw> SpamapS, i am mildly interested in that line
[19:00] <apw> SpamapS, i had not realised I can trivially test this as its a report side thing ... perhaps you could pm me the incantation to run the reports
[19:00] <apw> and then i can try and debug it
[19:00] <SpamapS> apw: ./generate-all
[19:00] <SpamapS> ;)
[19:01] <apw> heh ... stupid apw, ok if you don't fix it before me, i'll have a poke later/tommrrow
[19:01] <SpamapS> actually its     ./generate-all -d path/to/maverick.db -c config/maverick.cfg
[19:01] <SpamapS> I'm thinking maybe trend_starts doesn't get passed in properly.. debugging now..
[19:02] <apw> ah ok let me know if you find it :)
[19:02] <SpamapS> oh and -o /path/to/output/dir
[19:02] <SpamapS> see Its not that easy.. there's still an incantation. ;)
[19:03]  * SpamapS should probably stop thinking in-channel
[19:22] <SpamapS> apw: oops.. if should have been elif ;)
[19:28] <apw> SpamapS, doh so it is
[19:28] <apw> SpamapS, you got a merge ?
[19:28] <SpamapS> https://code.launchpad.net/~clint-fewbar/launchpad-work-items-tracker/server-team-mods/+merge/35320
[19:31] <apw> SpamapS, ok that looks totally sane, merged
[19:33] <apw> SpamapS, we'll find out in an hour if it worked
[19:44] <jdstrand> slangasek: hey. would you mind looking at bug #628924 and giving an ACK or NAK as an ubuntu-sru member?
[19:46] <apw> ogasawara, ok those patches seem good to my testing, and they are in the pipe.  i will also kick off an armel build now but the more testing the better ... we do not want to double-beep the archive
[19:47] <shadeslayer> jono: around?
[19:48] <ogasawara> apw: ack.  I'll test it as well before I push.
[19:48] <jono> shadeslayer, hey, on the phone
[19:49] <shadeslayer> ok..
[19:53] <SpamapS> apw: cool thanks!
[20:15] <didrocks> cjwatson: hey, I got some reject when uploading gnome-bluetooth (dpkg-source can't extract it). kenvandine got the same issue last week and the workaround was to regenerate the tarball. Should I proceed or do you have some time to investigate?
[20:23] <james_w> didrocks: where's the tarball?
[20:24] <james_w> or better, the source package
[20:24] <didrocks> james_w: http://ftp.gnome.org/pub/gnome/sources/gnome-bluetooth/2.31/gnome-bluetooth-2.31.90.tar.gz
[20:24] <didrocks> hum, source package, can upload it somewhere, one sec
[20:28] <didrocks> james_w: you should be able to dget -x http://people.canonical.com/~didrocks/gnome-bluetooth_2.31.90-0ubuntu1.dsc
[20:28] <james_w> merci
[20:29] <didrocks> merci à toi :-)
[20:36] <james_w> didrocks: go "+1" this: https://bugs.edge.launchpad.net/soyuz/+bug/637507
[20:36] <james_w> apologies for that not clicking the other day
[20:38] <didrocks> james_w: confirmed. waow what an old bug, reading the link
[20:39]  * kenvandine is surprised we don
[20:39] <didrocks> james_w: the workaround is to redo the tar?
[20:39] <james_w> didrocks: which one is old?
[20:39] <kenvandine> t see it more
[20:39] <james_w> didrocks: that's the only one I know of
[20:40] <didrocks> james_w: (comment from william is quite old)
[20:40] <james_w> only just over a year old :-)
[20:40] <james_w> shows how many bugs are reported on Launchpad
[20:41] <didrocks> yeah, just suprised we don't get it more
[20:41] <didrocks> thanks a lot james_w :-)
[20:41] <james_w> np
[20:42] <james_w> seb128: retracers should work again on edge
[20:43] <james_w> seb128: lifeless recommends switching to production anyway
[20:43] <seb128> james_w, thanks, what was the issue?
[20:43] <seb128> james_w, the issue with production is that fixes can take ages to land and that we don't test what's coming next
[20:43] <james_w> seb128: edge was using mixed revisions of the code across different appservers, which screws up the API
[20:44] <seb128> ie if edge is broken and get rolled in production we are screwed
[20:44] <seb128> pitti, ^ just fyi
[20:44] <james_w> seb128: indeed, however lifeless is also on a quest to get rid of the split
[20:44] <seb128> james_w, ok, thanks for figuring that out
[20:45] <james_w> np
[21:29] <strycore> #ubuntu-app-devel
[21:30] <strycore> + /join plz , 'kthxbye
[21:46] <slangasek> jdstrand: ack or nack?  There's a choice? :)
[21:46] <jdstrand> slangasek: at least theoretically
[21:47] <jdstrand> slangasek: seriously though, there is a bit going on there and as this is an SRU and we don't have an exception in place yet, I felt uncomfortable pushing to -security without your guys
[21:47] <jdstrand> s/your guys/you guys/
[21:57] <jdstrand> slangasek: thanks for your ack. I'll copy over
[23:10] <ScottK> jdstrand: Somehow the -update for chromium-codecs-ffmpeg ended up in Main.
[23:10] <jdstrand> ScottK: I'll fix it. thanks
[23:11] <ScottK> jdstrand: You're welcome.
[23:14] <ScottK> jdstrand: Should I be suprised it looks different now?
[23:17] <jdstrand> ScottK: I haven't changed anything yet, but am presently
[23:17] <ScottK> OK.
[23:18] <ScottK> Looks like i have some kind of oxygen (KDE) theme running now.
[23:18] <jdstrand> yeah, went from 5.0 to 6.0
[23:18] <jdstrand> 5.0 is no longer supported
[23:19] <ScottK> OK.
[23:19] <ScottK> Seems to work OK, it was just a bit suprising.
[23:20] <jdstrand> welcome to the new world of browser updates
[23:20] <ScottK> Yeah.  No kidding.


[21:27] <Jordan_U> Any recommendations for software for a school bell system? Just needs to play sounds (our school's PA system is connected to the computer) at the right times, and be configurable by less tech savvy people (so cron + mplayer is not a usable solution).


[07:48] <msikma> I hate walking into #ubuntu and people randomly going "Windows sucks, Mac sucks, Ubuntu is god".
[07:50] <z_diver> seems to be lots of that everywhere you go these days.
[07:50] <z_diver> drains you
[07:50] <msikma> I'm fine with people exclaiming that they find Ubuntu much better, but there's never a reason to bash other people for using something else and proclaiming that their system is absolutely awful in every way.
[07:51] <msikma> I'm never going into #ubuntu again.
[07:53] <z_diver> sometimes you can get a good technical answer, never is a while and a half
[08:00] <msikma> There is no technical explanation for saying that the other major operating systems are "completely worthless and ugly and unstable and slow and [insert more words here] ".
[08:02] <z_diver> oh, yeah!  You're right.  I've seen it different at times.  I think they are bored and waiting to have a party if / when the website gets updated.
[08:08] <msikma> Speaking of the website, wasn't there a discussion going on about a front page redesign?
[08:09] <msikma> I think that it needs to. The current design, which seems to be different from what it's always been, is a little awkward.
[08:09] <z_diver> Yeah, I almost wrote to Henrik about that
[08:10] <z_diver> I like the new site, I think just because it's different.
[08:10] <msikma> Yeah, I like it too. The old one sported almost exclusively text. But I don't really agree with that navigational item at the top of the page on the front page.
[08:10] <z_diver> But I've noticed that Canonical is run off a similar template so I'm not sure how far they want to go.
[08:10] <msikma> And the way the text is below that seems a little misplaced. I'll make a quick suggestion later.
[08:11] <z_diver> There are a few mistakes too.
[08:11] <z_diver> the top header isn't quite aligned right
[08:12] <z_diver> Thought I should look into it but then I noticed even Canonical is like that.  do you see that?
[08:12] <msikma> It's just overall a little badly designed, I guess. The idea is nice, but it's inconsistent with itself.
[08:12] <msikma> I'm not sure what you mean. Canonical's front page looks like Ubuntu's old front page.
[08:13] <z_diver> after the ubunto logo there is a bit of a change on the bottom shadow of the beige header
[08:14] <z_diver> firefox shows it anyway.  I'll test some other browsers.
[08:16] <msikma> Ohh
[08:16] <msikma> Yeah, now I see it.
[08:16] <msikma> That's an error.
[08:16] <msikma> Heh, that's pretty bad.
[08:17] <z_diver> well, I just tested on Safari and on IE for mac.  Woao
[08:17] <z_diver> site completely disintegrates on ie mac
[08:18] <msikma> Seems they just forgot that color. It's embedded in the Ubuntu logo image. Internet Explorer 6.0 also shows it.
[08:18] <z_diver> not too big a deal because nobody uses it anymore but there is nothing for 1000 pixels or more under content.
[08:19] <z_diver> canonical has the same error.
[08:20] <z_diver> I'm sure it's just because of the recent updates.  I might let Henrik know but I'm sure he's got plenty to take care of atm.
[08:20] <msikma> You should probably mail it to the Ubuntu-art list and Ubuntu-devel list.
[08:21] <z_diver> On IE for Windows, how is the Ubutu nav menu to the right.  All one color?
[08:21] <z_diver> or is the header slightly darker?
[08:22] <z_diver> Header being the light grey colored "ubuntu" logo thing.
[08:22] <msikma> Looks fine. No gamma issues there.
[08:22] <z_diver> On all my mac browsers it's slightly off.
[08:22] <msikma> Hmm
[08:22] <msikma> Oh, wait, it IS off.
[08:22] <msikma> By a very slight amount.
[08:22] <z_diver> yeah
[08:23] <msikma> That must be the image itself rather than IE's faulty rendering of some of them.
[08:23] <z_diver> wesafe color issue or something.
[08:23] <z_diver> *websafe
[08:23] <msikma> Nah.
[08:23] <msikma> You don't even have to recognize web safe's existence.
[08:23] <msikma> Web safe colors is the most 1984 thing in web development ever.
[08:24] <z_diver> mac gamma then?
[08:24] <z_diver> can you see the dif in IE?
[08:25] <z_diver> I take that back, FF on mac is fine
[08:25] <msikma> I can see the difference in IE and not in Firefox. Must be a wrongfully set gamma value in the PNG.
[08:25] <msikma> Internet Explorer renders images darker if this is so.
[08:26] <z_diver> safari has it also
[08:27] <msikma> 2.0?
[08:27] <z_diver> 2.03
[08:37] <msikma> Well, I'm leaving for work.
[08:37] <z_diver> Interesting...  Camino is fine with the gamma issue on the menu AND it fine on the underline part.
[08:37] <msikma> See you around. I'll drop by this channel at work.
[08:38] <z_diver> ok
[08:38] <msikma> Really? Camino uses the same rendering as Firefox.
[08:38] <msikma> Both use the Gecko engine.
[08:38] <z_diver> yeah
[08:38] <msikma> Maybe it updated? Try hard refreshing in Firefox.
[08:38] <z_diver> but it has the line going all the way to the tabs
[08:38] <z_diver> then it stops and after the tabs./
[08:38] <msikma> I really gotta go now, though. I work on a Mac at work so I'll try to figure out if I can see that, too.
[08:38] <msikma> Later!
[08:41] <z_diver> Well, I"m out of here too.    Night!
[10:51] <onkarshinde> anybody talking here?
[11:03] <lapo> hi
[11:18] <onkarshinde> hi
[02:28] <msikma>  "Theme idol idea"? (Referring to the "That's a wrap everyone!" mail by Viper550 on the list)
[02:28] <msikma> That's got to be the worst idea I've ever heard.
[03:19] <lapo> msikma: I think there's too much talking at the moment, we'll need to do a point in the future choosing some common directions to follow and start from there
[03:20] <lapo> at the moment there's to much traffic on that ml, almost impossible to follow, well at least for me
[03:22] <lapo> bersace: I'm happy you're putting some love on the a sane scanning interface, if you need any help (my c skills are rotting so artistically speaking) feel free to ask
[03:24] <bersace> lapo: thanks :)
[03:24] <bersace> source code tree is rawly available at http://bersace.ath.cx/flegita
[03:24] <bersace> i'm currently building library
[03:24] <msikma> lapo: the worst thing that can happen is people ignoring any kind of planning we may come up with. V550 was just stating all kinds of things in that post, like "We need to choose a completely different color scheme for Edgy". Perhaps we must, but what position is he in to say whether we should?
[03:25] <bersace> lapo: just put your comment at http://live.gnome.org/GnomeScanning
[03:25] <bersace> i really need external point of view in order to design rocking UI !
[03:28] <lapo> you should ask mpt about gui design
[03:31] <lapo> msikma: I think a meeting is required
[03:32] <msikma> Indeed.
[03:32] <msikma> If we're getting feedback from a lot of people soon, we might want to wait for that.
[03:32] <lapo> msikma: regarding colors, I think the colors ubuntu is using are quite bad, but kinda unique so I'm fine with them, and I think changing them all is really a dumb choice
[03:33] <msikma> I think that changing them simply "because they need to be different" isn't a valid argument.
[03:33] <lapo> yeah
[03:33] <msikma> Maybe we do need to completely change them around, I don't know. But not for this reason.
[03:33] <msikma> (I don't think we do, by the way.)
[03:34] <lapo> I'm more for evolution then revolution
[03:35] <msikma> Me too.
[03:35] <msikma> I also wonder what Julian is talking about when he mentions that Mac OS users are "_begging_" Apple to "replace the Finder".
[03:36] <msikma> I've never heard of that. Sounds like weasel words to me.
[03:50] <bersace> lapo: mpt ?
[03:54] <lapo> bersace: he is a gui designer he usually hang on #ubuntu-deskop
[03:54] <bersace> lapo: thx
[03:59] <bersace> We may get inspired by https://wiki.ubuntu.com/DesktopTeam
[04:09] <defunkt> i can help with any graphics if need be
[04:40] <msikma> I seriously wonder what Julian meant when he said that people are begging Apple to replace the Finder. I've really never heard of that. I don't even know how to respond to that particular thing in his mail.
[04:59] <lapo> I think the vast majority of apple users doesn't even know what the finder is :-)
[05:05] <msikma> Oh, I'm sure they know what the Finder is, but I doubt that they really think of it that critically. It's just "the system".
[05:05] <msikma> But I think that Mac OS users are generally a little more computer-savvy. I have no doubt that hardly anybody knows what Explorer is, though.
[05:06] <msikma> Huge mail sent to art list... I still hope that it won't spawn a massive debate.
[05:07] <msikma> blah.
[05:07] <msikma> I only just sent the first response and already I don't feel good about it.
[05:08] <defunkt> so what has the artwork team been doing for ubuntu...like specifics
[05:09] <lapo> defunkt: arguing on the mailing list atm :-)
[05:09] <defunkt> whats wrong with the mailing list?
[05:09] <lapo> too much traffic
[05:09] <defunkt> ah
[05:13] <lapo> nice email msikma
[05:13] <lapo> a fully agree
[05:13] <lapo> I
[05:13] <msikma> Yeah, the mailing list is a little high traffic. I'm going to be gone for the weekend on a family trip, and I probably won't be able to check my mail, and I fear for when I get back :)
[05:14] <msikma> But I'll try to smuggle my laptop along
[05:14] <msikma> Also, thanks.
[05:21] <troy_s> But I think that Mac OS users are generally a little more computer-savvy. -- that's completely incorrect.  Mac tries to market to folks who know nothing about computers.
[05:22] <troy_s> defunct:  Paris is going to lead to some concrete goals.  From there, it will be documented on the wiki.
[05:26] <troy_s> defunkt:  due to a lack of cohesive structure, mark has ended up dumping a large chunk of what an art team should handle back into canonical's hands.  of course, if everyone doesn't pitch in and do a little work, probably not.
[05:28] <defunkt> ok awesome
[05:28] <defunkt> well if i can do anything, please let me know
[05:28] <defunkt> i have to go to lunch tho, bbiaf
[06:05] <msikma> troy_s: they do, but mostly in the context of the iPod, I think. But I don't know for sure because almost all designers I meet use Macs, as well as most other people involved in the creative chain. They're a little more tech-savvy.
[06:22] <msikma> Well, I'm gonna quit, see you all when I get home.
[06:22] <msikma> Damn, I worked... 10:30 hours today.
[06:22] <msikma> Oh well.
[06:22] <msikma> Bye
[07:29] <jd_miam> (hi)
[07:29] <defunkt> howdy
[11:33] <MiniJames> hey
[11:33] <MiniJames> Congrats on the launch ;)


[00:22] <trinikrono> hey does anyone know where the default time for inactive monitor times in gnome power manager are set, in ubuntu or upstream i have this bug 371195 that i would like to get triaged
[00:22] <ubot2> Launchpad bug 371195 in gnome-power-manager (Ubuntu) "Blacklight stays lit (affects: 1) (heat: 10)" [Wishlist,Confirmed] https://launchpad.net/bugs/371195
[02:19] <trinikrono> hey guys
[02:19] <trinikrono> if i have a bug filed a against a package
[02:20] <trinikrono> and it says that is crashed on resuming from hibernation, should i file it against linux also?
[02:23] <hggdh> trinikrono: what crashed? The application, or Linux?
[02:24] <trinikrono> hey hggdh, the application , in this case it was checkgmail
[02:24] <trinikrono> i meant if to file it against the kernel also (linux package)
[02:25] <hggdh> trinikrono: right now I see no reason to open a task for linux
[02:25] <trinikrono> okie
[02:25] <trinikrono> was jut curious here
[02:26] <hggdh> what might have happened is (something like) checkgmail tried to use the network just after resuming, it was not yet there, and the appl crashed
[02:27] <hggdh> until something can be tied to kernel resume, this is still only an application issue
[02:27] <trinikrono> hggdh: next one bug 151226, i believe this bug can be closed now
[02:27] <ubot2> Launchpad bug 151226 in checkgmail (Ubuntu) "Synaptic recommends libsexymm2, which is useless (missing Perl bindings) (dups: 1) (heat: 18)" [Undecided,Incomplete] https://launchpad.net/bugs/151226
[02:28] <trinikrono> the question is weither it is invalid or fix released
[02:28] <trinikrono> since it works fine now
[02:28] <trinikrono> it is a pretty old bug they filed
[02:31] <hggdh> trinikrono: state it is working on <release>; the bug was opened against Hardy, it seems. Hardy desktop is still supported
[02:33] <hggdh> trinikrono: it is not invalid, anyways, this is a real bug. It can go to either wontfix or fix released
[02:33] <hggdh> from where it is now
[02:33] <hggdh> but I would still keep it open
[02:33] <trinikrono> okie
[02:33] <trinikrono> i was thinking fix released
[02:35] <trinikrono> we dont have a response for fix released?
[02:54] <hggdh> trinikrono: sorry, got busy
[02:54] <trinikrono> well i found a nice one on the responses page
[02:54] <trinikrono> i am sending out gentle reminders on bugs now
[02:54] <hggdh> trinikrono: usually, when (say) a Lucid bug gets fixed on the Maverick version, we willclode the bug fix released
[02:55] <hggdh> but, in this case, this was opened on Hardy, and lagged unresolved until Lucid
[02:55] <trinikrono> well its okie now
[02:55] <hggdh> so... yes, you can close fix released. BUT -- make sure you write down the workaround in the bug description
[02:56] <trinikrono> no workaround now
[02:56] <trinikrono> it just works now :D
[02:56] <trinikrono> before they where complaining about dependcies when installing the package
[02:56] <trinikrono> but now it works fine
[02:56] <micahg> hggdh: hi :) are you familiar with a lack of context menu on indicators?
[03:08] <hggdh> hi micahg. I guess you mean the lack of left-click actions?
[03:10] <micahg> hggdh: right click :)
[03:10] <hggdh> micahg: sorry, the usual confusion on left-handed people ;-)
[03:11] <hggdh> micahg: IIRC, this is proposital -- there should not be any need of conext menus on indicators
[03:12] <hggdh> (which, I agree, is a major change in paradigm)
[03:12] <micahg> hggdh: right, I was wondering if you could pen a canned response quoting that lack of need, I see bugs frequently reporting the issue
[03:13] <hggdh> micahg: oh. K. I will research the official explanations, and try something
[03:13] <micahg> hggdh: thank you, feel free to hand off to someone else that might know more :)
[03:13] <hggdh> micahg: easy, everybody knows more than I do :-)
[03:14] <micahg> hggdh: you know that's not what I meant ;)
[03:14] <hggdh> :-)
[03:23] <trinikrono> excuse me guys
[03:24] <trinikrono> isnt firefox 3.6 in lucid?
[03:24] <micahg> trinikrono: yes
[03:25] <trinikrono> lol? bug 597691
[03:25] <ubot2> Launchpad bug 597691 in ubuntu (and 1 other project) "Please push to latest FF (3.6.*) (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/597691
[03:25]  * micahg wishes people would stop filing those
[03:25] <trinikrono> what is the issue here?
[03:25] <trinikrono> clearly i am confused lol
[03:25] <micahg> trinikrono: actually, I think the user just wants the latest zeitgeist
[03:26] <trinikrono> so its a package request for zeitgeist?
[03:26] <micahg> trinikrono: not really sure
[03:28] <micahg> trinikrono: you could ask the user to clarify the request
[03:28] <trinikrono> for real
[03:28] <trinikrono> ima gonna use the !vague thing
[03:29] <trinikrono> also can i assign it to firefox?
[03:29] <micahg> trinikrono: k
[03:29] <trinikrono> or just make sure what he is doing first
[03:29] <micahg> trinikrono: please no unless it's a firefox request
[03:29] <trinikrono> okie
[03:29] <micahg> trinikrono: thanks
[03:30] <drew212> micahg: do you have time to tell me what should be in a proper bug report?
[03:30] <micahg> drew212: bug or crash report?
[03:30] <drew212> crash
[03:31] <micahg> drew212: k, so, a proper crash report will contain a coredump that can be retraced by the retracer
[03:31] <micahg> drew212: what
[03:31] <micahg> drew212: what's uploaded is a .crash file by apport
[03:32] <micahg> drew212: the problem is not everyone's machine can generate these
[03:32] <micahg> drew212: the alternative is a  local gdb backtrace
[03:32] <micahg> drew212: questions?
[03:32] <drew212> aren't there times where apport fails?
[03:32] <micahg> drew212: yes
[03:33] <drew212> so how can we tell whats a good one and whats a bad one?
[03:33] <micahg> drew212: well, the retracer will tell you if it can't do the job (i.e. *-retrace-failed tags)
[03:34] <micahg> drew212: otherwise, you might see some of the files from a .crash attached to a bug w/out the coredump and stacktraces
[03:34] <drew212> so how do we get a local gdb backtrace if it fails?
[03:34] <micahg> !backtrace | drew212
[03:34] <ubot2> drew212: To get a backtrace of a failing application please read: https://wiki.ubuntu.com/Backtrace
[03:36] <drew212> are there times when apport gets a successful backtrace but it doesnt contain the information needed?
[03:36] <micahg> drew212: yes, flash can be a good example
[03:37] <drew212> is there anything in the files i should look for? (an example would probably be beneficial)
[03:38] <micahg> drew212: well, it takes practice to read a backtrace
[03:38] <micahg> drew212: the stacktrace and threadedstacktrace files should be what to look at
[03:39] <drew212> alright
[03:41] <drew212> micahg: ill hit you up if i have any questions later, thanks! ;-)
[03:41] <micahg> drew212: k, np
[03:41] <micahg> drew212: it took me quite a while to be able to read the stacktraces usefully
[03:49] <trinikrono> micahg: what should i do if users complain about a memory leak in a application in a bug
[03:49] <trinikrono> what i mean is what to ask for
[03:49] <micahg> trinikrono: which bug?
[03:50] <trinikrono> bug 382267
[03:50] <ubot2> Launchpad bug 382267 in checkgmail (Debian) (and 1 other project) "memory leak (affects: 5) (heat: 37)" [Undecided,New] https://launchpad.net/bugs/382267
[03:50] <micahg> trinikrono: https://wiki.ubuntu.com/Valgrind
[03:51] <micahg> trinikrono: there should be a response for it too
[03:51] <trinikrono> yes vlagrind  i was wondering what that was lol
[03:53] <micahg> hggdh: still around?
[03:57] <trinikrono> and providing i get the op to get a valgrind log
[03:57] <trinikrono> what will we do with it micahg
[03:57] <micahg> trinikrono: that I don't know :)
[03:58] <trinikrono> i must say it looks like quiet alot of work to do
[04:02] <micahg> trinikrono: memory leaks aren't easy things to fix
[04:02] <trinikrono> should i look for a upstream bug now?
[04:08] <trinikrono> micahg: it appears to be upstream also, so i will go and put the link to the upstream bugtracker
[04:09] <micahg> trinikrono: great
[04:38] <ddecator> looks like micahg does a good job of taking my place ;)
[04:38] <micahg> ddecator: ?
[04:39] <trinikrono> lol
[04:39] <trinikrono> i was writing so much my pen died
[04:39] <ddecator> micahg: you're doing a good job of answering the questions of both of my students, haha
[04:39] <micahg> ddecator: ah, wanna take my 2?
[04:39]  * micahg hasn't contacted them yet
[04:39] <trinikrono> i am one
[04:39] <ddecator> micahg: oh, didn't know you had two
[04:40] <micahg> ddecator: yeah, and I can't handle any right now, all I can do is answer quick Qs
[04:40] <ddecator> sounds like the admins are doing a good job
[04:40] <ddecator> micahg: well i appreciate you helping them out :)
[04:41] <micahg> ddecator: np, we help each other :)
[04:41] <trinikrono> ddecator: you know i am now reading about the launchpad email interface, its good right?
[04:41] <ddecator> trinikrono: i've never actually used the email interface, but i've seen comments submitted that way
[04:42] <trinikrono> ddecator: maybe because your inbox is beyond repair lol?
[04:43] <ddecator> trinikrono: haha, only at the moment. i keep meaning to tackle all of my bugmail, but other things keep coming up
[04:43] <trinikrono> ddecator: you ever had to track a memory leak?
[04:44] <ddecator> trinikrono: can't say i have..
[04:44] <ddecator> trinikrono: other than watching top to see if memory usage skyrockets
[04:44] <trinikrono> i found one in checkgmail bug 382267
[04:44] <ubot2> Launchpad bug 382267 in checkgmail (Debian) (and 2 other projects) "memory leak (affects: 5) (heat: 38)" [Undecided,New] https://launchpad.net/bugs/382267
[04:44] <trinikrono> so far all i did was add a bug tracker and put !valgrind
[04:47] <ddecator> trinikrono: looks good so far :)
[04:52] <trinikrono> i wanted to try out the email interface, but it says i need to sign messages =\
[04:52] <trinikrono> i use gmail
[04:53] <ddecator> sign like with a pgp key?
[04:53] <trinikrono> yes, i regeistered the one in launchpad
[04:56] <micahg> trinikrono: you can use gmail w/Thunderbird for signing
[04:57] <trinikrono> what about evolution?
[05:01] <micahg> trinikrono: idk, probably
[05:01] <ddecator> seems like there would be a way
[05:01]  * micahg is on the Mozilla Team, not GNOME :)
[05:01] <trinikrono> lol you guys dont use the email interface much?
[05:01]  * ddecator uses gmail in prism :)
[05:21] <trinikrono> shucks
[05:21] <trinikrono> looks like im with you guys on the thunderbird bandwagon
[05:23] <ddecator> i can't get used to tb until it has conversation style threading
[05:23] <micahg> ddecator: well, you get message based threading
[05:24] <ddecator> micahg: yah, i enabled that, but i didn't like it as much
[05:43] <nigelb> micahg: how do I change default template for thunderbird mails?
[05:43] <nigelb> file-> save as -> templates doesn't work :/
[05:43] <micahg> nigelb: probably in preferences
[05:53] <trinikrono> hey is it hugday today?
[05:54] <nigelb> if its thursday in your tz, yes
[05:55] <ddecator> so yes :)
[05:55] <ddecator> idk if i ever got an email saying what the focus is..
[05:57]  * micahg got the emails but forgot
[05:57] <micahg> fontconfig :)
[05:58] <ddecator> huh...i wonder if my filter accidentally caught it
[06:00] <ddecator> huh, the one from two bugdays ago did, but i never got one for today's :(
[06:22] <trinikrono> apparently you can just reply to the bug email address and it comes up in launchpad with pgp keys or anything
[06:22] <trinikrono> i mean none
[06:27] <ddecator> yah, it shows up as a comment
[07:37] <trinikrono> so how do we triage font bugs lol?
[08:14] <trinikrono> i saw something in QA wiki that said i should assign myself to a bug until a bug triaged, does that stand?
[08:33] <kermiac> trinikrono: only assign yourself to a bug report if you intend to fix the bug
[08:34] <trinikrono> :D, thats what i thought must be a old wiki
[08:34] <kermiac> trinikrono: have you got a link to that wiki page?
[08:35] <trinikrono> https://wiki.ubuntu.com/QATeam/TriageAtOpenWeek
[08:35] <trinikrono> apparently thats how they used to do it
[08:36] <kermiac> ok, thanks trinikrono
[09:28] <trinikrono> is there any triagers online
[09:34] <kermiac> trinikrono | !ask
[09:34] <kermiac> haha fail
[09:34] <kermiac> !ask
[09:34] <ubot2> Please don't ask to ask a question, simply ask the question (all on ONE line and in the channel, so that others can read and follow it easily). If anyone knows the answer they will most likely reply. :-)
[09:35] <trinikrono> :D does dpkg reconfigure fontconfig-config work for you in lucid?
[09:35] <trinikrono> doesnt work for me in jaunty
[09:35] <trinikrono> or look at bug 349663
[09:35] <ubot2> Launchpad bug 349663 in fontconfig (Ubuntu) "debconf options still present but not working (affects: 12) (dups: 3) (heat: 50)" [Low,Confirmed] https://launchpad.net/bugs/349663
[09:39] <kermiac> trinikrono: that command doesn't appear to do anything for me on Lucid either.
[09:40] <kermiac> trinikrono: I experienced the same behaviour as the last comment in that bug report
[09:43] <trinikrono> nice
[09:44] <trinikrono> so just to find a upstream bug then we can triage it?
[09:50] <kermiac> trinikrono: yup, that seems like the right way to go (although I'm def. not an expert in that package). FWIW asac set that bug to triaged over a year ago & somone (wrongly) changed it to confirmed
[09:52] <trinikrono> so you will put it back to triaged and  i will close it?
[09:55] <trinikrono> ouch and they say to use it on a wikipage
[09:55] <trinikrono> https://wiki.ubuntu.com/Fonts#Enabling%20Bitmapped%20Fonts
[10:07] <kermiac> trinikrono: "sudo dpkg-reconfigure fontconfig" (from the wiki page) worked for me
[10:08] <trinikrono> well apparently they pulled the -configure
[10:20] <trinikrono> kermiac: you still there, bug 539008 i think can wishlist
[10:20] <ubot2> Launchpad bug 539008 in fontconfig (Ubuntu) "Microsoft Sans Serif maps to Thai font even on european setups (affects: 2) (heat: 38)" [Undecided,New] https://launchpad.net/bugs/539008
[10:21] <trinikrono> or ask that they test in maverick
[10:57] <vish> xteejx: you had me confused for a sec there ;)
[10:57] <vish> xteejx: i usually close 3-4 bugs together :)
[10:58] <xteejx> vish: Ohhh right didn't realise thought you'd missed 1 :)
[11:31] <chilicuil> hi there, I've seen here: https://wiki.ubuntu.com/UbuntuBugDay/Planning that today is gonna be a hug day, I wonder what time is gonna be the meeting if any, what I need to do to help?, this will be my first first time
[13:20] <smallfoot-> why i get sata errors on my disk if my cd drive is plugged in?
[14:13] <seb128> pedro_, hey
[14:13] <pedro_> bonjour seb128
[14:13] <seb128> pedro_, how are you?
[14:13] <seb128> pedro_, busy today? ;-)
[14:14] <seb128> pedro_, I've a mission for bugsquad ;-)
[14:14] <pedro_> seb128, like always ;-)
[14:14] <pedro_> seb128, sure, what's the mission? ;-)
[14:14]  * pedro_ listen
[14:14] <pedro_> reading works too
[14:15] <pedro_> morning kamusin
[14:15] <seb128> pedro_, so gst0.10-python has some 139 bugs registered
[14:15] <seb128> I noticed that yesterday and wait "no way so many people use that"
[14:15] <seb128> pedro_, so it seems checkbox files all the "sound is not working correctly" bug there for some reason
[14:16] <seb128> pedro_, could somebody try to figure what would be the right component for those bugs, it's not gst0.10-python in any case
[14:16] <seb128> pedro_, and maybe reassing all the current bugs to that component or something
[14:16] <seb128> pedro_, and make sure checkbox got updated to stop doing that?
[14:17] <pedro_> seb128, yeap I'll coordinate something to move those bugs from there and ping cr3 about the checkbox part
[14:17]  * pedro_ kicks cr3
[14:17] <seb128> thanks
[14:17] <kamusin> hey pedro_ :)
[14:17] <pedro_> thanks seb128
[14:19] <pedro_> kamusin, ready to squash some bugs on the bug day?
[14:23] <kamusin> always ready haha (go go go #chi)
[14:36] <genux> hi all, if someone going throught a bug from start to finish today ?
[14:36] <genux> so that I can follow what you are doing ?
[15:49] <vish> pedro_: did the bugsquad/BC mailing list get the mail about the mentorship student pruning mail i sent a few hrs ago?
[15:49]  * vish seems to be having problem with mail
[15:50] <pedro_> vish, yes! thanks for the update ;-)
[15:50] <vish> pedro_: cool ,thanks..  files a bug in rt :)
[15:50] <vish> * /me
[15:51] <vish> i dont seem to be getting copies of the mails i send :/
[15:52] <pedro_> is your alias linked to a gmail address?
[15:52] <pedro_> i don't get any copy i send trough my gmail account
[15:52] <pedro_> seems its designed to be that way...
[15:52] <vish> pedro_: yeah , gmail.
[15:53] <pedro_> well could be the same
[15:53] <vish> hmm.. so not a bug
[15:53] <pedro_> yeah
[15:54] <pedro_> vish, there's maybe something to check/uncheck in the web preferences though
[15:55] <vish> pedro_: i checked that in the mailman mailing list prefs but still it doesnt work , and the mails to the lp mailing list [BC] should have worked.. seems gmail is doing something ;)
[15:56]  * vish checks gmail prefs , probably something hiding there
[15:56] <vish> pedro_: thanks for the confirmation, about gmail thingee..
[15:56] <pedro_> vish, if you find it  please let me know ;-)
[15:57] <vish> pedro_: sure thing
[15:57]  * vish  had asked nigelb and he scared me ..
[15:57] <vish> nigelb: pff
[16:11] <Pici> jpds: *poke*, got a question about old-releases.u.c
[16:13] <jpds> Hello.
[16:15] <Pici> jpds: Is it worth filing a but/rt ticket about old-releases' intrepid backports/proposed missing packages for i386 arch?
[16:15] <jpds> Pici: ŧ
[16:15] <jpds> Pici: Which packages is it missing for example?
[16:16] <Pici> jpds: All of them? There simply isn't a binary-i386 folder in (for example) http://old-releases.ubuntu.com/ubuntu/dists/intrepid-backports/universe/
[16:18] <jpds> Pici: Ports is there, the [now un-]supported intrepid archive is yet to be moved over.
[16:18] <Pici> jpds: Ah. Okay.
[16:35] <jpds> Pici: Can you try again? We've moved the x86 stuff across.
[16:36] <Pici> jpds: You didn't need to do it now... but it looks good at-a-glance to me.
[16:37] <jpds> Pici: Sooner is better than later™.
[16:37] <Pici> jpds: Thanks
[16:37] <jpds> [Though intrepid will sit on archive.u.c for a little longer]
[18:24] <psusi> bugs are not the place for help requests right?  so if someone has managed to mess up their system but otherwise does not really have a bug to report, should they be sent to the ubuntu forums for help and the bug report closed?
[18:24] <dutchie> perhaps there should be a bug against whatever allowed them to mess up their system ;)
[18:28] <psusi> I mean like if say, they filed a bug report against nethack because they were playing that when their system crashed, and now they can't boot or access the filesystem and are asking for help repairing the system to boot or at least recovering their data... that doesn't really belong in a bug report does it?
[18:30] <ddecator> psusi: if it's a support question, there is a "Covert to Question" link that can turn the report into a question on LP Answers
[18:31] <psusi> hrm.. maybe you could take a look at bug #598086 and see what I mean...
[18:31] <ubot2> Launchpad bug 598086 in dmraid (Ubuntu) "system stops booting after message JDB: barrier-based sync failed on md1-8 - disabling barriers ... wrong # of devices in RAID (affects: 1) (heat: 8)" [Undecided,Incomplete] https://launchpad.net/bugs/598086
[18:32] <psusi> this doesn't actually have anything to do with the dmraid package...
[18:32] <EricJ> similar to a problem of mine, tho.
[18:35] <psusi> so you think I should convert it to a question?  but what is the question and what package?  since it doesn't really have anything to do with dmraid...
[19:23] <psusi> hrm... the help page on lp says that after 2 weeks of being in needs information state, questions are supposed to automatically expire, but that does not seem to be happening...
[19:24] <elopio> pedro_: are you available now?
[19:24] <pedro_> elopio, hey, yes ;-)
[21:27] <htorque> hello, a "New" bug was fixed with an update - should i mark it "Fix Released" or "Invalid"?
[21:28] <BUGa_LegendSeker> you don't
[21:28] <BUGa_LegendSeker> LP should do it
[21:28] <BUGa_LegendSeker> if the package states the bug
[21:29] <htorque> no it doesn't, the bug is "New"/"Unconfirmed"
[21:30] <psusi> if it was fixed intentionally it will automatically be marked fix released.. if the user just finds that the problem does not occur with a new version, that is different
[21:33] <htorque> i _assume_ it was fixed due to an intentionally fixed other bug (a race condition - the bug(s) i'm talking about are SIGSEGVs)
[21:34] <BUGa_LegendSeker> https://bugs.edge.launchpad.net/ubuntu/+source/pavucontrol/+bug/598260
[21:34] <ubot2> Launchpad bug 598260 in pavucontrol (Ubuntu) "pavu control lost icon (affects: 1) (heat: 6)" [Undecided,New]
[21:34] <BUGa_LegendSeker> can anyone please confirm? thanks in advance
[21:56] <xteejx> Evening all


[00:23] <skellat> xnox: That's what I saw looking at the branch via Launchpad Librarian.  I hope Noskcaj comes up with something interesting to scratch whatever itch he's got in the matter.
[01:07] <luke_> Anyone around?
[01:09] <pleia2> usually, we all kind of lurk
[01:09] <luke_> i wanted to join the testing team
[01:10] <pleia2> great :)
[01:10] <pleia2> did you have any questions in particular?
[01:10] <luke_> not really, just want to jump in there :)
[01:11] <pleia2> that's the way to do it!
[01:11] <pleia2> middle of the night for the guy who leads up testing, but most of us can answer questions if you encounter any issues
[01:11] <luke_> how does the testing work? can you break it down for me?
[01:12] <pleia2> http://xubuntu.org/news/want-to-help-out-xubuntu-test-raring/ is an article from a few months ago when we were testing raring (now testing saucy)
[01:12] <pleia2> explains a lot of the basics
[01:13] <pleia2> https://wiki.ubuntu.com/Testing/ISO/Walkthrough has a full walkthrough of testing ISOs
[01:14] <luke_> is there any code testing? what i mean by that is unit testing?
[01:14] <Unit193> Nobody tests me, I'm (mainly) stable.
[01:15] <pleia2> we currently don't do any traditional unit testing
[01:15] <Unit193> Sometimes it's requested to test some application, like Mugshot.
[01:15] <luke_> okok
[01:16] <pleia2> since Xubuntu is made up of a bunch of applications we pretty much trust that the source of the software has done testing and we mostly test things as a whole - installation of Xubuntu, basic functionality of key applications
[01:16] <pleia2> all manual at this point
[01:16] <luke_> ok
[07:04] <elfy> pleia2: thanks for talking to luke last night
[07:05] <elfy> which just looks too odd now I posted it ...
[07:06] <Noskcaj> hey elfy
[07:06] <elfy> hi Noskcaj - thanks for keeping up with merges
[07:06] <Noskcaj> np
[07:07] <Noskcaj> I've made an OEM slideshow for xubuntu, hopefully it will get accepted soon
[07:08]  * elfy read that
[07:08] <elfy> might not have had much time this week - but I have been reading the backlog
[09:40] <knome> Noskcaj, have you sent your form to the magazine?
[09:41] <Noskcaj> knome, yep
[09:41] <knome> Noskcaj, okay, good
[09:41] <knome> Noskcaj, and have you already got the agreemend and signed that?
[09:41] <knome> *agreement
[09:41] <Noskcaj> i think so
[09:41] <knome> okay, good good
[09:42] <knome> we're able to finish this magazine thing soon then
[09:42] <Noskcaj> knome, just incase you've not read the scrollback, i made an oem slideshow for xubuntu
[09:42] <knome> i didn't, you didn't ping me
[09:44] <knome> where do you have the branch?
[09:51] <Noskcaj> lp:~noskcaj/ubiquity-slideshow-ubuntu/oem-xubuntu i thinl
[10:01] <knome> ok, i'll try to check it out today
[17:19] <bluesabre> maybe I should put this here instead, so that knome, mrpouit/mr_pouit, or micahg might see
[17:19] <bluesabre> https://code.launchpad.net/~smd-seandavis/xubuntu-default-settings/lightdm-gtk-greeter-updates/+merge/177959
[17:20] <bluesabre> also, ochosi/mrpouit: the gtk theme in saucy is still the old one without gtk 3.8 or lightdm-gtk-greeter 1.6 support
[17:37] <Unit193> Ah, so could poke https://blueprints.launchpad.net/ubuntu/+spec/xubuntu-s-artwork
[17:42] <bluesabre> thanks Unit193
[17:43] <Unit193> Heh, sure.
[17:52] <knome> bluesabre, saw that, didn't have time to review yet
[17:53] <pleia2> jjfrv8: are we pretty much all set for 12.04 docs?
[17:53] <knome> pleia2, yup
[17:53] <pleia2> need to get it all wrapped up for sru
[17:54] <knome> pleia2, i just came home and i can run through it with you if you have time
[17:54] <pleia2> and I should upload it to docs.xubuntu.org
[17:55] <pleia2> knome: I can make that work, give me 20 min or so?
[17:55] <knome> yeah, same here (i need to plug in and that)
[18:15] <pleia2> knome: hihi
[18:15] <knome> o/
[18:15] <pleia2> ok, shall I download and build this thing?
[18:16] <knome> pleia2, so basically, the 1204 docs should be fine in the technical side (eg. the menu paths should be correct etc etc)
[18:16] <knome> sure, if you want to have a look at it ;)
[18:17] <knome> i've gone through all of jack's MP's, and merged
[18:17] <pleia2> great
[18:17] <knome> they are all fine, and we will want some of them applied to the saucy docs as well
[18:17]  * pleia2 nods
[18:18] <pleia2> do we need to do a specific call for starting on the saucy docs, or does jjfrv8 have that handled?
[18:18] <knome> i've asked him to send the same improvements as MP's to the saucy branch and AFAIK, some other people are working on it, but a call never hurts
[18:19] <pleia2> ok, I'll see about doing that soon
[18:19] <pleia2> so what else needs to be done with precise?
[18:19] <knome> after all, the saucy docs are more open to all kind of improvements and expansions
[18:19]  * pleia2 nods
[18:19] <knome> well, probably a quick run-through and then the SRU
[18:19] <pleia2> ok, looking now
[18:19] <knome> cheers
[18:20] <knome> i think the SRU was also a good test for the docs to see if it's release-agnostic enough (and i think we passed)
[18:22] <knome> ah, i see something that can be further improved :)
[18:23] <knome> hmmwait
[18:23] <knome> no, it's there
[18:26] <pleia2> :)
[18:28] <knome> we should probablt note that apt-offline isn't available by default in 12.04
[18:29]  * pleia2 nods
[18:30] <pleia2> http://docs.xubuntu.org/1204/ but didn't link it to the main page yet
[18:33] <knome> pleia2, pushed rev 65
[18:33] <pleia2> k
[18:36] <knome> i'm ok for the docs to start going the SRU route.
[18:36] <knome> woo!
[18:36] <pleia2> +1
[18:36] <GridCube> when its the next meeting?
[18:37] <GridCube> its its or is
[18:37] <knome> is
[18:37] <knome> we should schedule.
[18:37] <GridCube> mmmhmm i fail at is
[18:38] <knome> eg tala ekki islensku a annan weg
[18:38] <GridCube> i would really like to have some follow ups for the mir subject
[18:38] <GridCube> even if there is some test i could help do
[18:38] <knome> from non-xubuntu side, or xubuntu people poking at the mir team?
[18:39] <pleia2> GridCube: Unit193 and I have been talking about it for days :)
[18:39] <knome> Unit193 has been building some ISOs and stuff
[18:39] <pleia2> GridCube: did you see Unit193's iso?
[18:39] <GridCube> how are we going and stuffs
[18:39] <GridCube> no
[18:39] <pleia2> Unit193: link for GridCube plz
[18:39] <GridCube> was a mail about it?
[18:39] <Unit193> 3 pings all very quickly, I broke something...
[18:39] <pleia2> no, just on irc
[18:39] <GridCube> oh ok
[18:39] <pleia2> and we've been updating http://etherpad.ubuntu.com/xubuntu-mir
[18:39] <knome> Unit193, if it's okay for you, can you send a mail to the list announcing the mir ISO?
[18:39] <pleia2> I think I might make a youtube video
[18:40] <knome> woo pleia2 on a video!
[18:40] <Unit193> http://vanir.unit193.tk/dump/xubuntu-13.10-xmir-i386.iso.zsync or http://vanir.unit193.tk/dump/xubuntu-13.10-xmir-i386.iso
[18:40] <pleia2> Unit193: assuming it's ok to share that iso link (on your home connection?)
[18:40] <Unit193> (There's an md5sum file too.)
[18:40] <Unit193> pleia2: VPS, just crappy domain.
[18:40] <pleia2> ah ok
[18:40] <knome> we don't care if you don't care...
[18:40] <knome> pleia2, can you talk with jjfrv8 about a shell?
[18:41] <GridCube> its safe enought to install on real hardware? like if i install it on a partition of my netbook?
[18:41] <pleia2> knome: of course
[18:42] <knome> pleia2, ta
[18:42] <Unit193> GridCube: Well you can't use it in a VM, but live booting is a fine test.
[18:42] <pleia2> jjfrv8: if you'd like a shell, just email me your preferred password and your id_rsa.pub key to use (or link to one in lp)
[18:42] <GridCube> live ok
[18:42] <knome> GridCube, never install testing stuff on production machines.
[18:42] <GridCube> that could do
[18:42] <Unit193> (I use grml-rescueboot: drop ISO in /boot/grml/, sudo update-grub, and reboot.)
[18:43] <GridCube> thats why i'm asking, i would like to know if its safe enough because this might be our default desktop in less than 2 months
[18:43] <knome> jjfrv8, if you need help with the shell stuff, feel free to ask me or pretty much anybody in the channel
[18:43] <GridCube> i find this matter really worrying
[18:44] <GridCube> well i have to go home now
[18:45] <Unit193> Dowh, was going to ask him for his inxi -G...
[18:49] <skellat> This still bothers me as a boot result from the latest ISO: https://wiki.ubuntu.com/skellat/audiobox-profile?action=AttachFile&do=view&target=IMG_0039.JPG
[18:50] <pleia2> knome: oh right, so you handling getting the docs srued now?
[18:51] <knome> pleia2, was hoping you would have done that, but i can do that as well
[18:51] <knome> pleia2, or we can delegate to skellat if he's up to it
[18:54] <pleia2> knome: I don't know how :)
[18:54] <skellat> https://wiki.ubuntu.com/StableReleaseUpdates
[18:55] <skellat> And I need to scramble to find a charger for my laptop...
[18:55] <skellat> brb
[18:56] <knome> pleia2, i don't know the exact process either, but AFAIK, it's similar to freeze exception paperwork
[18:56] <pleia2> I don't know how to do that either ;)
[18:57] <knome> stop giving excuses! :P
[18:57] <skellat> pleia2: There is a bug that has to be filed.  The wiki link has the template
[18:57] <pleia2> I vote for delegate to skellat
[18:58] <knome> me too, if he's up to it
[18:58] <knome> skellat, you comfortable with doing it?
[18:58] <pleia2> it just magically creates the package from the branch?
[18:58] <knome> pleia2, i don't know about building magic...
[18:58] <skellat> pleia2: No, there is an SRU team to review things
[19:00] <skellat> There is criteria to consider here for if we qualify for SRU process: https://wiki.ubuntu.com/StableReleaseUpdates#When
[19:00] <knome> skellat, we do.
[19:00] <knome> skellat, there will be nobody saying we can't do that SRU. if somebody says, point them to me
[19:01] <skellat> Okay
[19:01] <knome> skellat, it's a no-brainer: it affects nobody except xubuntu, it can't break other packages
[19:01] <skellat> pleia2 will need to work with me on this as I need a bug control master to nominate for series once I do the paperwork
[19:01] <knome> skellat, neither me or pleia2 can do that afaik
[19:01] <knome> or we can probably both nominate
[19:01] <knome> so just ping us if you need us.
[19:01] <skellat> If you can change severity, you can do it
[19:02] <knome> skellat, so can i mark you as the assignee now? ;)
[19:02] <skellat> Not yet
[19:02] <skellat> Is the changelog completely done for this?
[19:02] <knome> i'm comfortable with out changelog
[19:02] <skellat> We'll need to insert some "Closes LP#" language in there
[19:02] <knome> *our
[19:03] <knome> you need to file that bug first then...
[19:03] <skellat> But I gotta create the bug first so we can have that
[19:03] <knome> yeah
[19:03] <knome> so can i now set you as the assignee? be assured i will give you all the support you need.
[19:03] <knome> :)
[19:04] <skellat> Go for it
[19:04] <knome> thanks
[19:04] <bluesabre> Unit193: is inxi in the repos or just that ppa?
[19:04] <skellat> Did we actually ship proper documentation with 12.04?
[19:04] <bluesabre> it seems like that would be super helpful to have in the repos
[19:04] <Unit193> !info inxi saucy
[19:04] <knome> skellat, not really, the docs were from far away
[19:04] <bluesabre> woot!
[19:04] <skellat> bluesabre: It should be in ppa:skellat/tests done via backportpackage
[19:05] <Unit193> bluesabre: Installed in the ISO too, for reasons. :P
[19:05] <bluesabre> :)
[19:05] <knome> thanks again skellat. i'm just so much more comfortable somebody running the process, even if they asked me about it every day.
[19:07] <knome> so anybody else want to take any other bug assigned to xubuntu-team at http://status.ubuntu.com/ubuntu-s/group/topic-s-flavor-xubuntu.html ?
[19:07] <knome> looks like there aren't too many. yay!
[19:08] <knome> elfy, can you confirm if the testcase bug statuses are up-to-date?
[19:08] <knome> elfy, seems like there are many inprogress
[19:09] <knome> elfy, and/or todo
[19:09] <bluesabre> i'll take this one:
[19:09] <knome> elfy, if you want, i can run through them with you later today
[19:09] <elfy> the in progress ones are afaik
[19:09] <bluesabre> [smd-seandavis] Work to gain packageset uploader rights for Xubuntu through Developer Membership Board process: TODO
[19:09] <knome> bluesabre, that's already assigned to you :P
[19:09] <bluesabre> :D
[19:09] <knome> elfy, abiword is set as "TODO"
[19:10] <knome> elfy, xfce appearance settings as "INPROGRESS"
[19:10] <knome> but i thought i have already done those.
[19:10] <elfy> I'll loook
[19:10] <knome> done as in added to the tracker
[19:10] <knome> cheers
[19:10] <knome> anything that is in the tracker (even the admin side) can be marked fix released
[19:10] <ganglere1> How do the "Test Needed" qa's work? They're in need of a test case to be written?
[19:10] <knome> ganglere1, yes
[19:10] <elfy> ganglere1: yep
[19:11] <elfy> I might to be honest move the autopilot ones
[19:11] <elfy> not really any chance of them getting sorted afaik
[19:12] <bluesabre> elfy, I can help a bit with the autopilot ones if I find free time
[19:12] <elfy> ok
[19:12] <bluesabre> I played with it a bit, doesn't seem too hard
[19:12] <elfy> tbh I am still firmly on the fence
[19:12] <knome> elfy, oh, ah, those are autopilot tests
[19:12] <elfy> knome: some are :)
[19:12] <knome> elfy, we should rename the bugs that it was clear they are
[19:12] <elfy> I'll sort it out in a bit
[19:13] <elfy> yep
[19:16] <elfy> knome: http://packages.qa.ubuntu.com/admin/config/services/qatracker/testcases
[19:16] <elfy> there they need to be?
[19:16] <knome> elfy, yup
[19:16] <elfy> thought so
[19:17] <bluesabre> oh good, I didn't have to ask for the link
[19:17] <Unit193> We aren't shipping translations in docs?  I've been seeing po files come in.
[19:17] <elfy> I'll work through it all now
[19:17] <skellat> !info xubuntu-docs precise
[19:17] <knome> Unit193, no, i should look how to do that.
[19:18] <Unit193> knome: That, re-write SD, setup meetings, you have a lot. :P
[19:19] <knome> Unit193, sure.
[19:19] <knome> Unit193, rewriting the SD is taking half-a-day and just getting on with it :)
[19:21] <skellat> LP Bug 1207493
[19:24] <knome> skellat, does those changes look like what you need?
[19:27] <skellat> knome: Which changes are you referring to?
[19:28] <skellat> Ah
[19:28] <skellat> Those changes
[19:28] <skellat> Not fix completed
[19:28] <skellat> Was the changelog updated to add the LP bug number?  If not, I'm working on a merge proposal real fast.
[19:28] <knome> skellat, i'll do that in a minute
[19:29] <skellat> I'm pushing a branch up now for MP
[19:31] <skellat> knome: https://code.launchpad.net/~skellat/xubuntu-docs/precise/+merge/178156
[19:35] <knome> skellat, thanks, merged
[19:35] <elfy> knome:  when you got a minute can we just run through adding a testcase
[19:36] <knome> elfy, sure
[19:36] <knome> elfy, are you ready now?
[19:39] <elfy> yep
[19:39] <elfy> sorry - not looking at timestamps :)
[19:41] <elfy> knome: whenever you are
[19:42] <knome> lol
[19:42] <knome> so open the admin
[19:42] <knome> then go to the testcases tab, and click "add a testcase"
[19:42] <elfy> yep
[19:42] <elfy> then find the id
[19:42] <knome> now you should have the bzr branch open
[19:42] <knome> no
[19:42] <knome> you don't input the id
[19:43] <knome> just get a test from the branch that doesn't have an ID
[19:43] <elfy> they all have that I can see
[19:44] <skellat> knome: The SRU is filed and our involvement for the moment is done.
[19:44] <knome> skellat, ta
[19:44] <knome> elfy, in that case, there is no testcase to add.
[19:44] <elfy> mmm
[19:44] <knome> elfy, or somebody has come up with an ID
[19:44] <elfy> so it's there somewhere?
[19:44] <knome> anyway
[19:45] <knome> you basically copy-paste the testcase content
[19:45] <knome> and add the title
[19:45] <elfy> oh
[19:45] <knome> THEN the tracker will show what ID is linked with that test
[19:45] <knome> and then rename the file in the branch and commit/push the changes
[19:46] <knome> so as testcases in the branch shouldn't be given ID's if nobody has added them to the tracker
[19:47] <elfy> knome: so something is wrong - in http://packages.qa.ubuntu.com/admin/config/services/qatracker/testcases
[19:47] <elfy> 1589 is Xfce4 Thunar Volman
[19:47] <elfy> http://bazaar.launchpad.net/~ubuntu-testcase/ubuntu-manual-tests/trunk/files/head:/testcases/packages/
[19:48] <elfy> 1589 is Time Administration
[19:48] <knome> elfy, yes
[19:48] <knome> elfy, somebody has "guessed" an ID for time-admin in the branch
[19:48] <elfy> ...
[19:48] <knome> elfy, if you look under "Xfce", thunar volman is also 1589
[19:49] <elfy> yep
[19:49] <elfy> so someone is just guessing at id's
[19:49] <knome> yup.
[19:49] <elfy> that's helpful
[19:50] <knome> anyboby that isn't a tracker admin and inserting tests shouldn't give tests ID's
[19:50] <knome> that's what the mess was the last time as well.
[19:50] <elfy> indeed
[19:50] <elfy> well I know for fact it wasn't me - I've only looked at it the last time we did :)
[19:51] <knome> yeah.
[19:51] <elfy> right - well I - perhaps stupidly assumed these things talked to each other - and you could just tell it an ID
[19:52] <elfy> I've not got time to do all that tonight - I'm just having a break from dealing with the sso fallout
[19:52] <elfy> I'll have to look - I should be able to follow the log here
[19:52] <knome> i can fix that later
[19:53] <elfy> I've gone through the bugs - renamed OUR a/pilot stuff so it is obvious
[19:53] <elfy> checked all the bugs - marked those on tracker as released
[19:53] <elfy> EXCEPT settings manager - that needs to be checked to make sure all bits are tested somewhere
[19:54] <elfy> so https://blueprints.launchpad.net/ubuntu/+spec/xubuntu-s-qa is up to date
[19:54] <knome> ta
[19:54] <elfy> 10 left commited - working from the bottom - stuff at top is all autopilot
[19:55] <knome> :)
[19:55] <elfy> still showing 13% of 56  - I guess it's not caught up
[19:55] <knome> yeah, it's not live
[19:55] <knome> it'll update at some point
[19:56] <elfy> Last updated: Thu 01 August 2013, 18:59 UTC tomorrow I guess :D
[19:56] <knome> that's an hour ago
[19:57] <elfy> yea - bet it'll do it 2/8/13 @ 18:59 :)
[19:57] <knome> it used to be once in an hour-3 last cycle
[19:58] <elfy> knome: just so I have it right in my head - a testcase on branch with a bad ID - how would you un-ID it?
[19:59] <elfy> I'll work on it all over the weekend then
[19:59] <knome> elfy, just rename it to not have an ID.
[20:00] <knome> elfy, or add it to the tracker and rename to new ID
[20:00] <knome> elfy, but as i said, i can look into that later today... :)
[20:00] <elfy> ok
[20:00] <knome> (once i've stopped confusing poor balloons)
[20:00] <elfy> ok
[20:00] <elfy> :)
[20:02] <lderan> poor balloons
[20:06] <Unit193> Also, ISO is growing it would seem. :/
[20:06] <elfy> don't know about confusing balloons - does me
[20:07] <elfy> I just find it hilarious how unjoined up the qa stuff is
[20:08] <knome> there's just a bit too many levels for packages
[20:09] <knome> for ISO's, they all make sense
[20:11] <elfy> not what I mean - in a sensible world - you'd merge a testcase - give it a number - go to packages.qa - give that the number - done
[20:12] <knome> in the ideal world, there was a script that did that for us
[20:12] <elfy> :)
[20:12] <knome> and that would be completely doable with the API
[20:18] <lderan> doable you say mmmm
[20:18] <knome> ;)
[20:18] <knome> well there is a python API...
[20:18] <lderan> python you say mmmm
[20:19] <lderan> i can give it a shot :)
[20:19] <knome> heh, well you should ask balloons first ;)
[20:20] <lderan> where is this balloons?
[20:20] <knome> #ubuntu-quality
[20:21] <knome> but it's my turn to pester him now >:)
[20:21] <knome> he's the ubuntu/canonical qa lead
[20:21] <lderan> okay i shall poke him after
[20:33] <jjfrv8> knome, hi. I'll e-mail pleia2 the info she requested for getting the screen set up.
[20:33] <knome> jjfrv8, awesome. if you need help with that, or setting the screen up after, just ping people in the channel
[20:35] <jjfrv8> I was trying to avoid letting the world see how ignorant I was about that stuff :) I've got it running now headless on a Raspberry pi but that has its disadvantages too.
[20:36] <Unit193> Hah!  Awesome!
[20:36] <knome> :)
[21:07] <elfy> knome: ok - blueprint is up to date again
[21:11] <knome> elfy, goodie
[21:12] <elfy> there's still a few to do - I'll look at those over weekend - need to do it myself
[21:12] <knome> mhm
[21:12] <knome> or just wait others to pick them up
[21:13] <elfy> no - I meant there are 3 merged that need to go into packages tracker
[21:13] <elfy> not testcases :)
[21:13] <knome> aha
[21:13] <elfy> I'll also look at testcases that can be in testsuites
[21:14] <knome> did you read my discussion with balloons today?
[21:14] <elfy> kind of - in between talking to people in forum :(
[21:14] <knome> we probably want to leave the obviously shared stuff, like firefox and thunderbird, out of the xubuntu product
[21:14] <elfy> yea - wouldn't move anything that was like that
[21:15] <knome> yup, good
[21:15] <elfy> xfce window manager for instance - needs to be on packages and in xfce testsuite
[21:15] <knome> yup!
[21:16] <elfy> I'd forgotten you had to recreate the testcase - which was why it was making no sense to me :)
[21:16] <knome> hehe
[23:10] <pleia2> knome: any reason not to link up new 12.04 docs on the website now? (updated to version 65)
[23:10] <pleia2> s/website/docs site
[23:10] <knome> no
[23:10] <pleia2> k, on it
[23:11] <knome> ta
[23:13] <pleia2> there we go, shiny
[23:13] <knome> ooh ooh :)
[23:14] <knome> i like our docs progress.
[23:14] <pleia2> yeah, we're like a real operating system \o/
[23:14] <knome> haha
[23:14] <knome> something like that
[23:15] <skellat> pleia2: Once you're done, could you pretty please update LP Bug #1207493  with a comment to mention you've updated the website docs and give a link to such?
[23:17] <skellat> Adding the comment will help with questions from the SRU team
[23:18] <pleia2> hmm, should probably just add xubuntu-website to the affected projects
[23:19] <pleia2> there we go
[23:19] <skellat> Noo
[23:19] <skellat> Not that
[23:20] <knome> pleia2, not really...
[23:20] <knome> :)
[23:20] <pleia2> oh?
[23:20] <skellat> I meant literally just add a comment stating "Our online public-facing documentation has been just updated at http://docs.xubuntu.org to reflect what is in the requested stable release update."
[23:20] <knome> s|org|org/|
[23:21] <pleia2> skellat: ah, well this communicates the same thing, should be ok
[23:21] <skellat> Just need something like that to add tracking for the SRU team.
[23:22] <skellat> Okay.  Somebody needs to poke Scott Kitterman or Brian Murray to look at the SRU proposal then.
[23:23] <knome> skellat, done @#ubuntu-release.
[23:23] <pleia2> thanks knome
[23:23] <knome> no problem
[23:28] <GridCube> pleia2, can i pm you?
[23:28] <pleia2> GridCube: shoot
[23:40] <Unit193> So since it's being sent to the list, any last changes requested to the page?
[23:41] <pleia2> it's lovely
[23:41] <pleia2> but it is testing of XMir - so might want to be clear about that
[23:42] <pleia2> XMir != Mir :)
[23:42] <Unit193> Hah, only because Pasi made it to be. ;)   I thought that was pretty clear, but alrighty.  XMir uses Mir, sooo.
[23:42] <Unit193> But, sure.
[23:42] <knome> Unit193, yeah, i get that highlight too :)
[23:42] <Unit193> Figured you would.
[23:43] <pleia2> quick, stop talking about gnome with a k behind his bad!
[23:43] <pleia2> back too!
[23:43] <Unit193> But you wouldn't if I used your surname!  (Mainly because I would spell it very badly.)
[23:43] <pleia2> Unit193: pro tip: it's in his whois
[23:43] <Unit193> (And /who, ident)
[23:44] <pleia2> indeed
[23:44] <knome> lol ;)
[23:44] <knome> heh, actually i do have my surname on the highlight too
[23:45] <knome> maybe you should all try to spell it without looking at it
[23:45] <Unit193> s/Mir/XMir/ done.
[23:45] <knome> and i could add that to the hilight list too :P
[23:45] <Unit193> ohanillaL
[23:45] <pleia2> canonifolks tell me that mailing list archive queuerunner is going again, should take a few hours to get archives up to date again
[23:46] <pleia2> maybe by tomorrow we can tweet GridCube's ml post
[23:46] <knome> duh. :)
[23:46] <Unit193> GridCube: Thanks for posting!
[23:46] <knome> Unit193, i see what you did there!
[23:47] <Unit193> Hrm, I didn't make a note that it had to be on real hardware, and that virtual machines don't count...
[23:48] <knome> Unit193, you can still fix that.
[23:49] <Unit193> Hrm, wording, wording... After making public! :D
[23:51] <Unit193> I didn't indicate the use of DVDs, but people are smart enough to figure that out, right?  "...to add the ISO to grub.  However you do it, you can not use a virtual machine." ? :P
[23:51] <knome> they can just ask if they don't understand.


[07:49] <ubunjusty> hello?
[07:40] <NachXs> Hola
[07:41] <NachXs> NickSern NachXs
[07:41] <NachXs> NickServ NachXs


[00:04] <ochosi> anything else? :)
[00:19] <bluesabre> ochosi, don't think so, currently
[00:19] <bluesabre> unless you want to add some translations for sgt-launcher
[00:19] <bluesabre> https://translations.launchpad.net/sgt-launcher
[07:50] <flocculant> bluesabre: thanks for the ping - glad to see the back of that issue finally :)
[10:13] <knome> bluesabre, Games;Puzzles;  <-- surely shouldn't be translated?
[10:13] <bluesabre> knome, correct
[10:13] <knome> why is it a translatable string then :P
[10:13] <bluesabre> Good question
[10:13] <bluesabre> oh maybe
[10:14] <bluesabre> knome, that one should be, yes
[10:14] <bluesabre> that's the Keywords key
[10:14] <knome> right...
[10:14] <knome> "SGT Puzzles Collection is a simple-to-use launcher for Simon Tatham's Portable Puzzle Collection." doesn't make sense btw
[10:14] <knome> but i'll translate it anyway
[10:14] <knome> :P
[10:15]  * bluesabre shrugs
[10:15] <slickymasterWork> which reminds me that I have to find the time to start translating also
[10:16] <knome> bluesabre, "Playing a short game of Galaxies" is a description for an image?
[10:16] <bluesabre> yes
[10:17] <knome> for translation purposes, is the game in progress in the screenshot?
[10:19] <knome> well, it's now translated as i it
[10:19] <knome> it is*
[10:19] <knome> i guess even an unstarted game can be called in progress too :P
[10:19] <knome> and translated
[10:20] <bluesabre> knome, doesn't seem to matter, captions are not displayed in gnome-software, but it is http://i.imgur.com/dSlbzEg.png
[10:20] <knome> good
[10:20] <slickymasterWork> we have to be broad in our definition of 'in progress', knome
[10:20] <knome> finnish is a weird language...
[10:21] <knome> it's really hard to be ambiguous
[10:21] <knome> or at least the text then feels weird
[13:12] <flocculant> davmor2: update manager - 1 line with aptdaemon from -proposed - commented on the bug the other day, which will be as much as I'll do as I never really use it ;)
[13:13] <davmor2> flocculant: know that feeling I've been forcing myself by setting daily update checks
[13:14] <flocculant> davmor2: well I use synaptic anyway as I update then have a butchers in -proposed
[13:14] <davmor2> flocculant: :)
[13:14] <flocculant> much like gnome-software I check it once a cycle then purge it :D
[13:15] <flocculant> davmor2: would have said in -desktop but don't much want a discussion about it :)
[13:15] <davmor2> flocculant: I know the feeling :)
[13:15] <flocculant> at least you get paid in more than ethercookies :D
[19:05] <knome> pleia2, so i got my package from the mail and can confirm i got a piqué polo shirt too
[22:34] <pleia2> dev server needs a new kernel, so I'm going to reboot it in 5 minutes unless there are any objections
[22:35] <knome> go ahead
[22:36] <pleia2> k :)
[22:37] <Unit193> Oh noooo!  End of the worldsirens.webm!
[22:37] <Unit193> EndOfTheWorldSirens.webm*
[22:37] <pleia2> rebooting
[22:38] <pleia2> and now in the shiny new kernel :) go about your day
[22:53] <knome> pleia2's in the new kernel?
[22:53]  * knome goes look at the kernel
[22:53] <knome> must be a mini-pleia2
[23:58] <bluesabre> evening all


[02:19] <InHisName> Nuttin's since 3pm ???? !! ???
[02:21] <waltman> everyone's out partying for SFD?
[02:21] <waltman> or watching the Phillies?
[02:22] <jedijf> lol, everyone going to bars saying "free as in beer?"
[02:22] <jedijf> somehow, i don't think that will work; but maybe worth a try
[02:23] <InHisName> "free in the beer" ?
[02:25]  * InHisName feels the ZZzzzz s catching up soon
[02:31] <ChinnoDog> lol
[02:41] <waltman> how was SFD?
[02:43] <jedijf> not much of an sfd thing anymore after 5 years with the same crowd, but great presentation on 3d printing
[02:44] <waltman> cool
[02:44] <waltman> personally I'm waiting for 4d printing.
[02:45] <jedijf> i guess, trying to get more /new/ people out to a meatspace event is the key...and the difficulty, it seems
[03:28] <ChinnoDog> My camera won't mount in Xubuntu :\
[03:28] <ChinnoDog> What is the magic here? It is recognized in lsusb
[03:28] <ChinnoDog> Bus 001 Device 012: ID 04a9:30fc Canon, Inc. PowerShot A620 (PTP mode)
[10:03] <rmg51> Morning
[10:04] <JonathanD> Morning.
[10:16] <InHisName> Morning rmg51 & JonathanD & any awake silent ones
[10:16] <JonathanD> Those awake silent ones scare me a little.
[10:17] <InHisName> OOOooooooo
[10:51] <rmg51> walk time
[10:51] <rmg51> later
[10:51] <rmg51> o/
[12:00] <waltman> Morning.
[12:43] <rmg51> o/
[19:17] <Adom> Afternoon.
[19:58] <rmg51> afternoon Adom
[20:49] <Adom> so ive been here once or twice in the past (chatted with erstazi for a bit, he's also from Erie). is there anything more to the ubuntu PA users group or whatever? just curious.
[21:41] <rmg51> this is part of it
[21:42] <rmg51> some areas also hold different types of events
[21:42] <rmg51> not much going on in Erie
[21:42] <rmg51> but don't let that stop you
[21:43] <rmg51> anyone can hold an event
[21:43] <rmg51> https://wiki.ubuntu.com/PennsylvaniaTeam/EventsTeam
[21:44] <Adom> what do events normally consist of? just some geeks hangin out talking about linux? (cuz im all for that)
[21:44] <rmg51> that will give you an idea of what we did in the past
[21:44] <rmg51> some have done an Ubuntu Hour
[21:45] <rmg51> they can be just what you said
[21:51] <Adom> looks like ErieLUG has no leader, but the meeting rooms are stilled booked first Saturday of each month. I might stop down and see if anyone goes. then just hang out and play with gnome3 finally.
[21:51] <Adom> because, let's face it, unity is crap.
[21:51]  * Adom crosses his arms.
[21:52] <rmg51> not a big fan of Unity
[21:52] <rmg51> at least not yet
[22:23] <waltman> does *anyone* like unity?
[22:25] <rmg51> jedijf:  :-D
[23:55] <jedijf> i think JonathanD too
[23:56] <jedijf> the 6 week rule applies, you can't comment until you use it, generally people don't like change
[23:58] <rmg51> hard to use it when Unity won't even boot :P
[23:58] <rmg51> that is the one second rule
[23:58] <rmg51> if it won't boot don't use it