[09:54] <inkernod> Alguien que hable español?
[09:55] <head_victim> !es | inetpro
[09:55] <head_victim> !es | inkernod
[09:55] <head_victim> sorry inetpro, tab complete failed :/
[09:55] <inkernod> tnks
[09:55] <inetpro> head_victim: np
[09:56] <inkernod> ubottu: hi
[09:58] <inkernod> have you ever used a bt phone in ubuntu for thetering
[09:59] <head_victim> inkernod: ubottu is a bot that I used to provide you with a link to a spanish speaking channel (Unfortunately I only speak english)
[09:59] <Myrtti> ubuntu support is at #ubuntu
[09:59] <Myrtti> support in spanish at #ubuntu-es
[09:59] <inkernod> ok
[16:02]  * slangasek waves
[16:02]  * stgraber waves
[16:04] <slangasek> #startmeeting
[16:04] <meetingology> Meeting started Wed Jan 18 16:04:15 2012 UTC.  The chair is slangasek. Information about MeetBot at http://wiki.ubuntu.com/AlanBell/mootbot.
[16:04] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[16:04] <jodh> o/
[16:04] <slangasek> [TOPIC] lightning round
[16:04] <ev> hi
[16:04] <slangasek> $ echo $(shuf -e cjwatson brry doko stgraber jodh ev bdmurray slangasek)
[16:04] <ev> come on, big money big money, no whammy
[16:04] <slangasek> bdmurray cjwatson doko ev jodh slangasek stgraber barry
[16:04] <ev> damn
[16:05] <ogra_> is bby barry with a cold ?
[16:05] <slangasek> hmm, where did barry's a go
[16:05] <ogra_> err brry i meant indeed :)
[16:05] <barry> there's an off-color joke in there somewhere
[16:05] <slangasek> anyway
[16:05] <bdmurray> holiday on Monday
[16:05] <bdmurray> discovered and issue with apport where bugpatterns weren't being checked
[16:05] <bdmurray> updated apport package hook for linux not to ask re kerneloops.org
[16:05] <bdmurray> uploaded an enabled version of kerneloops for precise
[16:05] <bdmurray> bug triage of ubuntu-installer bug reports I got subscribed to
[16:05] <bdmurray> debugged a cbd issue with bjf
[16:05] <bdmurray> reported bug 917903 regarding apport and gz report items
[16:05] <bdmurray> investigation into aptdaemon bug 855394
[16:05] <bdmurray> updated update-manager apport hook to include recent Aptdaemon messages from syslog
[16:05] <bdmurray> update firefox-lp-improvements to fix bug 917461
[16:06] <bdmurray> done
[16:08] <slangasek> cjwatson:
[16:08] <cjwatson> Added timestamps to live filesystem builds.  Did a bit of hopeful optimisation of update-initramfs calls but it unfortunately didn't save much.
[16:08] <cjwatson> Spruced up ubuntu-archive-tools a bit, applied GPLv3 to unlicensed files, and did some preliminary modernisation in preparation for Python 3.
[16:08] <cjwatson> Ported germinate to Python 3, by way of practice.
[16:08] <cjwatson> Helped out with lazr.uri port to Python 3.  Ported wadllib.
[16:08] <cjwatson> Trying to drain the python-debian Python 3 swamp:
[16:08] <cjwatson>  * Packaged six.
[16:08] <cjwatson>  * Filed Debian #656288 in python3-apt to deal with non-UTF-8 tag files.
[16:08] <cjwatson>  * Filed Python #13815 to make it easier to get Unicode data out of tarfile.
[16:08] <slangasek> ev: and you're next since doko is having gateway problems
[16:08] <cjwatson>  * Slogged through huge numbers of bytes/str fiddling and general confusion.  Still in progress.
[16:08] <cjwatson> Discussed Ubuntu Studio live DVD structure with Scott.  I think I now have a clear enough idea of what they need to be able to implement it pretty quickly.
[16:09] <cjwatson> ..
[16:09] <ev> - Fighting apport-retrace. Was missing gdb as apport-retrace didn't have a
[16:09] <ev>   depencency on it as the traceback is normally extracted client-side
[16:09] <ev>   (add_gdb_info). It may still be advantageous to do that work on the client,
[16:09] <ev>   but that (10s) plus adding the needed package information (add_package_info)
[16:09] <ev>   to the report (30s) takes no small amount of time.
[16:09] <ev> - Updating RT 48667 with the latest requirements and my notes from talking to
[16:09] <ev>   James on November 30th.
[16:09] <ev> - Including a SHA-512 hash of the system UUID in uploaded reports and core
[16:09] <ev>   dumps.
[16:09] <ev> - Meeting with Gerry to discuss the downloads marketing campaign and the crash
[16:09] <ev>   database.
[16:09] <ev> - Privilege dropping in whoopsie.
[16:09] <ev> - Dealing with DBus/ConsoleKit fallout from dropping privileges (at_console is
[16:09] <ev>   set for NetworkManager).
[16:09] <ev> - Reply to Christian and Nick on slideshow questions.
[16:09] <ev> - Talked through the crash UI with Matthew
[16:09] <ev>   (https://wiki.ubuntu.com/ErrorTracker).
[16:09] <ev>   - It looks like we'll need a "ignore future crashes" checkbox, after all.
[16:09] <ev>     He's working on the right UI for this now.
[16:09] <ev>   - We don't need a confidentiality warning like apport currently has, as
[16:09] <ev>     the information collected is not being shared with the general public like
[16:09] <ev>     existing reports are.
[16:09] <ev>   - Matthew will work on the administrator UI, for disabling crash and metrics
[16:09] <ev>     reporting.
[16:09] <ev>   - I will run these modifications to apport by pitti, then implement.
[16:09] <ev> - Including the system UUID with the upload of the report and the core dump.
[16:10] <ev> - Figuring out how to handle permissions around /var/crash, now that we drop
[16:10] <ev>   privileges.
[16:10] <ev> - Fixed a really nasty memory corruption bug that ate up a few hours.
[16:10] <ev> - Added tests for get_system_uuid and get_crash_db_url
[16:10] <ev> - Worked with pitti to get crash files written with 0640, so that the daemon
[16:10] <ev>   can read them as a regular user.
[16:10] <ev> - Added a test for hex_to_char.
[16:10] <ev> - Move to GNetworkMonitor from NetworkManager for the network connectivity
[16:10] <ev>   check. This means no more needing a console (NM uses at_console), and
[16:10] <ev>   actually having a "can we reach the crash server" condition.
[16:10] <ev> - Ensure that /var/crash is group owned by whoopsie and is chmod g+s.
[16:10] <ev> - Isolate whoopsie into its own mount namespace, RO bind mount / and RW bind
[16:10] <ev>   mount /var/crash into /var/tmp/whoopsie. Chroot, then drop all privileges and
[16:10] <ev>   capabilities but CAP_FOWNER, so that now we can be a regular user who has
[16:10] <ev>   the sole added ability of being able to delete files in /var/crash (which is
[16:10] <ev>   +t).
[16:10] <ev>   - The rationale for this is that users need to be able to drop 0-byte
[16:10] <ev>     .upload files in /var/crash to notify the daemon that they want the crash
[16:10] <ev>     uploaded.  The daemon then needs to be able to delete these.
[16:10] <ev> (done)
[16:10]  * doko is joining from the ac100
[16:10] <slangasek> doko: you're up then, if you're ready to report :)
[16:10] <jodh> Working on getting lp:upstart building daily. Started to write a python
[16:10] <jodh> script to autogenerate a comprehensive set of test Upstart jobs (and
[16:10] <jodh> hopefully also to autogen a script to check the results). Working to
[16:10] <jodh> resolve failing unit tests for bug 912558.
[16:10] <jodh> ♨
[16:11] <doko> may I skip? no summary on this host
[16:12] <slangasek> doko: yeah - send by email later?
[16:12] <doko> will do
[16:12] <stgraber> jodh: let me know if you need any help with the daily builds, I have that setup for quite a few projects
[16:13] <barry> doko: please take a look at debian bug 655793 (forwarded from #debian-python)
[16:13] <jodh> stgraber: thanks!
[16:14] <doko> barry: seen, maybe some issues with the branch version
[16:14] <barry> doko: we thought, maybe some of the compiler flag changes in -3 perhaps?
[16:15] <barry> doko: check with jtaylor
[16:15] <doko> barry, I get same test results with and without lto
[16:15] <slangasek>  * management sprint + travel back, Sat-Tue
[16:15] <slangasek>  * uploaded command-not-found to fix the 'sudo' group name
[16:15] <slangasek>  * helped with the new queue last week, unity 5.0 ftw
[16:15] <slangasek>  * uploaded crda, needed some tweaks for multiarch to enable a fixed apt upload
[16:15] <barry> doko: ah
[16:15] <slangasek>  * more work on hiring for our openings
[16:15] <slangasek> (done)
[16:15] <stgraber> - Testing tracker
[16:15] <stgraber>  - Production instance has been updated
[16:15] <stgraber>  - Bugfix: Handle case where we don't have any build in the build list
[16:15] <stgraber>  - Add report to look for results for a given bug number
[16:15] <stgraber>  - Admin: Add a field to set the comment we'll add to bugs
[16:16] <stgraber>  - Add lp-integration script to the branch with needed changes for new tracker + lucid
[16:16] <stgraber> - Networking
[16:16] <stgraber>  - dnsmasq and IPv6 privacy extensions are now turned on by default for everyone (thanks to cyphermox!)
[16:16] <stgraber>  - Merged ifupdown and went through its buglist which is now a lot shorter
[16:16] <stgraber>  - Prepared an SRU for bug 876829 and talked with upstream about fixing ifdown when dealing with labels
[16:16] <stgraber>  - Expecting another ifupdown upload this afternoon with the cherry-picked commit and upload of the Oneiric SRU
[16:16] <stgraber>  - One more fix to bridge-utils to deal with VLANs
[16:16] <stgraber>  - Some discussions on resolvconf and its interaction with NM's dnsmasq and libvirt
[16:16] <stgraber> - ARB
[16:16] <stgraber>  - Got unity-lens-askubuntu into Ubuntu 11.10 extras
[16:16] <stgraber>  - Did the same with unity-lens-utilities (published on Monday evening)
[16:16] <stgraber>  - Did some queue review/cleanup, discussed about improving MyApps and the ARB workflow to deal with the current backlog
[16:16] <stgraber> - Containers
[16:16] <stgraber>  - Started working on a fixed util-linux using Serge's patch
[16:16] <stgraber> - TPM
[16:16] <stgraber>  - Uploaded current trousers to my experimental PPA (build dependency for current tpm-tools)
[16:16] <stgraber>  - Started fighting with a buggy upstream tarball of tpm-tools until they eventually released a working one (a few hours ago)
[16:16] <stgraber>  - Got both of them built but still not quite working, now trying to also go with the latest opencryptoki, then rebuild tpm-tools using it.
[16:16] <stgraber> - Other
[16:16] <stgraber>  - Uploaded bugfix/translation update of Arkose to Precise and backported in the PPA
[16:16] <stgraber> - TODO
[16:17] <stgraber>  - Cherry-pick ifupdown's last label fix to Precise and include in the SRU for Oneiric
[16:17] <stgraber>  - Test the new tpm stack from the PPA
[16:17] <stgraber>  - Some more bugfixes for the ISO tracker
[16:17] <stgraber>  - Continue bug review on vlan, ifenslave-2.6, bridge-utils and resolvconf to see if I missed anything with the recent fixes
[16:17] <stgraber> (and switched from empathy to using bitlbee, now managing everything through irssi in a screen session, no more empathy/telepathy crashes or issues syncing my status across protocols!)
[16:17] <stgraber> (done)
[16:17] <barry> fixed the lintian warnings in dbus-python and got all the binary packages looking good (with help from cjwatson...thanks!).  still waiting in new queue.  build retries a few times to get success on arm* and powerpc, but now all is green.  currently working on feedparser - 5.1 (new upstream) supports it, but we have 5.0.1, upstream tarball is missing some data files and has test failures when python-chardet is installed, so reporting
[16:17] <barry> those upstream and working around them in the packaging; should hopefully be ready later today.  met w/launchpad guys to helped out with general packaging questions.  done.
[16:19] <slangasek> stgraber: how's bitlbee's VoIP integration? ;)
[16:20] <slangasek> any other questions on statuses?
[16:20] <stgraber> slangasek: hehe, that's the only bit where I'm keeping empathy (and it actually works great for that!). I just have my VOIP account, Canonical VC account and the "people nearby" account in empathy now, everything moved to my IRC server
[16:20] <cjwatson> I would look at dbus-python in NEW but the NEW queue has been going in the wrong direction for me all day
[16:20] <stgraber> *everything else
[16:21] <slangasek> [TOPIC] Bugs
[16:21] <slangasek> bdmurray: what's hot in the insect world?
[16:21] <barry> cjwatson: ouch ;}
[16:22] <bdmurray> I've run across a couple of "hot" bugs
[16:22] <bdmurray> bug 916299 seems like it would be important
[16:22] <bdmurray> additionally does anybody know what this Boot-Info-Script is?
[16:22] <cjwatson> uh
[16:22] <cjwatson> EFI is not intrinsically tied to GPT
[16:23] <cjwatson> I mean not in both directions
[16:23] <cjwatson> bdmurray: http://bootinfoscript.sourceforge.net/
[16:24]  * cjwatson marks incomplete
[16:25] <bdmurray> hmm, hadn't seen that before thanks
[16:25] <bdmurray> then bug 916209 regarding recovery mode and wubi
[16:25]  * cjwatson looks, thought I fixed that ...
[16:26] <cjwatson> ah, ok, right, I'll deal with that thanks
[16:27] <bdmurray> that's about it then
[16:28] <slangasek> bdmurray: cool, thanks
[16:29] <slangasek> [TOPIC] burndown charts
[16:29] <slangasek> [LINK] http://status.ubuntu.com/ubuntu-precise/canonical-foundations.html
[16:29]  * barry hides
[16:29] <slangasek> there was some very good progress last week during the rally
[16:29] <slangasek> and the workitems are now more accurate, which is a good thing even though it doesn't help move the graph in the right direction ;)
[16:30] <cjwatson> I'm happy to keep helping out with py3, if that's wanted - not much else on my list is desperately urgent
[16:30] <slangasek> and in fact, if we were to discount the workitems on our blueprints belonging to non-foundations people, we'd be below the trendline... so we'll blame them if anyone asks :P
[16:31] <barry> cjwatson: great!
[16:31] <slangasek> all the same, rickspencer3 wants us to be realistic about what work we're going to get done and postpone things we aren't, so that other teams know what they can rely on from us this cycle
[16:32] <slangasek> so if there's anything you think we should postpone, talk to me
[16:32] <slangasek> and if you don't think there's anything you should postpone, I'll talk to you ;D
[16:33] <stgraber> yeah, looking at it, a sixth of my work items are non-Canonical/Foundations stuff (Edubuntu website, ubiquity plugin, ...). Though I actually need to spend a weekend or so going through these :)
[16:33] <slangasek> right, it doesn't help the graph that we have overachievers taking on non-Canonical blueprints :)
[16:34] <barry> slangasek: i want to push on as much as possible this month, and then postpone whatever's left when i switch to stable+1
[16:35] <slangasek> barry: I think that's reasonable, yes
[16:35] <slangasek> particularly since most of those new workitems for python3 should be on the small end
[16:35] <slangasek> and if cjwatson can help with them too, that's all to the good
[16:36] <barry> yep.  of course, the biggest risk is that we don't know what we don't know
[16:36] <slangasek> usually :)
[16:37] <barry> :)
[16:37] <slangasek> [TOPIC] AOB
[16:37] <slangasek> anything else on your minds?
[16:37] <slangasek> reminder that I'm off this Friday, swapping for the bank holiday here
[16:37] <slangasek> barry: did you decide what day you're swapping to?
[16:37] <slangasek> or is that "later" :)
[16:37] <ScottK> python3-defaults is now sync'ed from Debian.
[16:38] <barry> slangasek: not yet
[16:38] <slangasek> ScottK: \o/
[16:38] <barry> ScottK: thanks!
[16:38] <ScottK> It's much easier than with python due to barry's upstream work on various PEP's to improve multi-version support.
[16:39] <slangasek> barry++
[16:40] <ScottK> BTW, just uploaded ipy with python3 support to Debian ... So we're making progress.
[16:41] <slangasek> good to know
[16:41] <cjwatson> I think I'll use it a lot more once we have -debian and -launchpadlib ported.  Pretty much all the archive tools could be python3 then.
[16:41] <barry> nice.  i'll submit feedparser to debian when it's ready
[16:41] <barry> cjwatson: wow, that would be fantastic
[16:44] <slangasek> #endmeeting
[16:44] <meetingology> Meeting ended Wed Jan 18 16:44:12 2012 UTC.
[16:44] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-01-18-16.04.moin.txt
[16:44] <slangasek> thanks, everyone!
[16:44] <stgraber> thanks!
[16:45] <barry> thanks!
[16:45] <jodh> thanks!
[16:45] <ev> thanks
[16:59] <balloons> hello everyone
[16:59] <Scott2> Hi
[16:59] <albrigha> hello
[16:59] <gema> o/
[17:00] <mmrazik> hi
[17:00] <balloons> let's let the fun begin
[17:00] <balloons> #startmeeting
[17:00] <meetingology> Meeting started Wed Jan 18 17:00:09 2012 UTC.  The chair is balloons. Information about MeetBot at http://wiki.ubuntu.com/AlanBell/mootbot.
[17:00] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[17:00] <alourie> o/
[17:00] <phillw> o/
[17:00] <astraljava> o/
[17:00] <balloons> so I see we have at least a few folks.. everyone ready?
[17:00] <alourie> yep
[17:01] <retoaded> and me too
[17:01] <ScottK> \o
[17:01] <balloons> [TOPIC] Previous Actions
[17:01] <nuclearbob> howdy
[17:01] <balloons> ok, so there were a couple previous actions, one of which was mine :-)
[17:01] <alourie> and one was mine :-)
[17:01] <balloons> kubuntu and ubuntu studio are on the agenda now, so that should be good going forward
[17:02] <balloons> alourie, how did the wiki migration go?
[17:02] <alourie> balloons: it went fine
[17:02] <hggdh> ~ô~
[17:02] <alourie> since about couple of hours we have a new wiki page
[17:02] <alourie> so everyone is invited to provide a feedback
[17:02] <balloons> can you let us know how you did it? I know we were wondering if it was possible to copy, etc...
[17:02] <alourie> I actually like this layout
[17:03] <alourie> balloons: ah
[17:03] <alourie> well, considering that you already merged a hefty part of it, it went quite fast
[17:03] <alourie> I just copied over relevant parts
[17:03] <albrigha> alourie: to be clear, is this the page? https://wiki.ubuntu.com/QATeam
[17:03] <alourie> albrigha: yes
[17:04] <alourie> there are still a lot of digging required for the nested stuff, I'm on it
[17:04] <alourie> but it'll take some time, as there's a /lot/ of stuff
[17:04] <alourie> ...
[17:04] <albrigha> I was going to ask about that..it seemed like AutomatedTesting has a lot of info and is rather hard to get to. but sounds like you are already looking at it :)
[17:04] <alourie> albrigha: yes, I am
[17:05] <alourie> I am looking into all things /QA wiki/, so if anyone has ideas/suggestions/questions, fire them up to me
[17:05] <balloons> yes, I agree.. General page cleanup is next and the more eyes on it the better
[17:05] <gema> alourie: link AutomatedTesting in a visible place
[17:05] <gema> I am taking care of linking all the important new stuff we do for automation there
[17:06] <gema> thanks !
[17:06] <gema> ..
[17:06] <alourie> gema: there's an "Actions" link on the main page, that leads to all activities
[17:06] <alourie> including Automation
[17:06] <alourie> would you like Automation to be special and have a separate link on the main page?
[17:06] <gema> I don't find the Actions link
[17:07] <albrigha> I don't see it either
[17:07] <balloons> i see activities
[17:07] <alourie> sorry
[17:07] <balloons> and it's there.. it's not a prominent link though on the main page
[17:07] <alourie> I meant Activities
[17:07] <gema> that may be it, yep, it needs to be on the main page not just under activities
[17:07] <gema> imo
[17:07]  * balloons likes the beaker graphic with the cd in it
[17:08] <alourie> balloons: for ISO testing? :-)
[17:08] <gema> maybe a bullet point under What kinds of things does the Ubuntu QA Team do or so
[17:08] <gema> ..
[17:08] <alourie> gema: maybe we could bulletlist activities alltogether?
[17:08] <gema> alourie: indeed
[17:08] <alourie> great
[17:09] <balloons> do we want aactivities on the top of the page next to roadmap, schedule
[17:09] <alourie> balloons: I'm not sure
[17:09] <albrigha> I say so..it seems like it's pretty important..
[17:09] <alourie> testing is not the only thing we do
[17:09] <gema> I think we should discuss this on the list
[17:09] <gema> and move on
[17:09] <gema> or else we won't get through :)
[17:09] <balloons> ok, so no actions right now
[17:09] <alourie> +1
[17:09] <alourie> balloons: put this on my actions list
[17:10] <balloons> [ACTION] alourie to feature AutomatedTesting wiki page prominently in wiki, based upon list discussion
[17:10] <meetingology> ACTION: alourie to feature AutomatedTesting wiki page prominently in wiki, based upon list discussion
[17:10] <alourie> thanks
[17:10] <balloons> let's move on then
[17:10] <alourie> great
[17:10] <alourie> thanks for the feedback!
[17:10] <balloons> [TOPIC] Blueprints Updates and Community Tasks
[17:10] <balloons> alourie, your welcome.. at a glance the wiki is already nicer
[17:11] <alourie> yep
[17:11] <balloons> ok, does anyone have any updates on tasks to sharE?
[17:11] <balloons> let's start with you alourie
[17:12] <alourie> ahm
[17:12] <alourie> ok
[17:12] <balloons> :-)
[17:12] <alourie> I think we need to get moving with test cases rework. I have no updates yes, but I intend to get started with rewriting. gema - is there any update on the meeting with Mozilla folks?
[17:13] <gema> alourie: on my todo list
[17:13] <gema> alourie: I need to talk to them this week
[17:13] <gema> balloons: give me an action
[17:13] <balloons> alourie, I also wanted to discuss the rework.
[17:13] <alourie> oh, great
[17:13] <alourie> balloons: go ahead
[17:13] <balloons> [ACTION] gema discuss case conductor with mozilla folks and provide update
[17:13] <meetingology> ACTION: gema discuss case conductor with mozilla folks and provide update
[17:14]  * txomon|nqas has arrived
[17:14] <balloons> sure. So I wanted to make sure I understood the process for how the test cases were being reworked
[17:14] <balloons> txomon|nqas, welcome :-)
[17:14] <alourie> balloons: ok
[17:14] <balloons> let me find my steps..
[17:15] <alourie> so we have decided to rewrite them, mainly because wiki doesn't seem to be a good management tool
[17:15] <balloons> yes.. in a nutshell, essentially using the gdoc to rewrite then place back in the wiki
[17:15] <gema> no, we have decided to rewrite them because they were wrong
[17:15] <gema> and we are moving to case conductor because the wiki is not a good management tool :)
[17:15] <njin> they where old
[17:16] <gema> njin: +1
[17:16] <balloons> yes gema is correct there
[17:16] <alourie> rewriting allows us to review them, fix ambiguities, update the content to a more relevant one, and remove the obsolete ones
[17:16] <alourie> because many of them are not relevant anymore
[17:16] <alourie> and just not clear enough
[17:17] <balloons> so I'm up to speed on that now :-) So the next step is to get some traction going on re-writing them, reviewing them, and getting them back into the wiki
[17:17] <njin> alourie,exact
[17:17] <alourie> balloons: wiki, for now
[17:17] <alourie> and CC later on (or any other system of choice)
[17:17]  * gema nods
[17:17] <balloons> +1
[17:18] <alourie> balloons: so action here would be getting on with it :-)
[17:18] <balloons> yes, I will take an action to solicit some folks on the list and get some cases written for next week
[17:18] <gema> balloons: maybe you could make it a bit easier for people by making sure we have a list of test cases that haven't been worked on yet available
[17:19] <alourie> gema: +!
[17:19] <alourie> that's +!
[17:19] <alourie> +1
[17:19] <gema> because now that we've started the whole thing got a bit messy x)
[17:19] <balloons> I was going to focus on an app or two at a time -- what do you think?
[17:19] <gema> sounds good to me
[17:19] <alourie> gema, balloons: I recommend going for ISO testing actually
[17:20] <gema> alourie: indeed, so that we are ready for alpha 2
[17:20] <alourie> say, begin with simple desktop 386
[17:20] <alourie> and continue from there
[17:20] <alourie> or it is x64 now?
[17:20] <balloons> did we go default 64-bit?
[17:21] <alourie> I don't know
[17:21] <gema> doesn't matter, none of them are simple by any stretch of imagination, if we are talking installs
[17:21] <alourie> yea
[17:21] <alourie> and they would be quite similar
[17:21] <alourie> in terms of test cases
[17:21] <njin> sure
[17:21] <alourie> balloons: just pick one :-)
[17:22] <balloons> sure, so I will take an action to review what's out there for i386 and x64
[17:22] <alourie> yep
[17:22] <balloons> and send to the list asking for help on rewrites
[17:22] <hggdh> all archs are important -- and we will need people to work on PPC, ARM, etc
[17:23] <alourie> hggdh: true, but we need to start somewhere
[17:23] <balloons> [ACTION] balloons to review test cases for i386,x64 and coordinate updates
[17:23] <meetingology> ACTION: balloons to review test cases for i386,x64 and coordinate updates
[17:23] <balloons> hggdh, I agree, and as long as we get one arch done we can model the rest after it
[17:23] <hggdh> indeed
[17:24] <jibel> balloons, if you start with intel you'll need to cover mac too
[17:24] <balloons> mac as in efi boot?
[17:24] <balloons> or as in ppc?
[17:24] <hggdh> mac intel
[17:24] <jibel> yes efi. amd64
[17:24] <gema> but the test cases are similar, aren't they?
[17:24] <gema> are we discussing test cases or execution?
[17:25] <jibel> if you're talking about test case there should be no difference between intel archs
[17:26] <gema> that's what I thought, we were just talking test cases, then balloons will need to move to the execution phase
[17:26] <gema> and help coordinate that
[17:26] <gema> with you, probably, jibel
[17:26] <alourie> I still say we pick one, handle its test cases, see next
[17:26] <gema> alourie: +1
[17:27] <balloons> ok, so yes test cases first
[17:28] <balloons> jibel can help coordinate execution
[17:28] <balloons> that's probably an discussion point for next week
[17:28] <balloons> make sure we followup
[17:28] <balloons> ok, let's move on
[17:29] <balloons> [TOPIC] Ubuntu Derivative Updates
[17:29] <balloons> Anyone from kubuntu on?
[17:29]  * alourie is out for few minutes
[17:29] <ScottK> Sure.
[17:29] <ScottK> Although Kubuntu isn't really a derivative.
[17:29] <balloons> hello ScottK
[17:30] <ScottK> As I mentioned last week, we've got KDE SC 4.7.4 in oneiric-proposed for testing.
[17:30] <balloons> I never know what to call them.. spins, etc.. can someone give me the right term?
[17:30] <ScottK> It's the last planned 4.7.x update.
[17:30] <balloons> will 4.8 be in precise?
[17:30] <ScottK> I prefer flavors or siblings.
[17:30] <ScottK> Yes.
[17:30] <ScottK> It's a 4.8 rc now and 4.8 final due out soon.
[17:31] <ScottK> IMO something like Mint is a derivative.
[17:31] <balloons> ScottK, noted. I'll use flavors
[17:31] <ScottK> Thanks.
[17:31] <jibel> balloons, flavors is good as per http://www.ubuntu.com/project/about-ubuntu/derivatives
[17:31] <balloons> jibel, perfect thank you
[17:32] <balloons> how about lubuntu? phillw?
[17:32] <phillw> fairly quiet, still working on one bug. the other bug that we shared with xubuntu re:language being altered when hitting return seems resolved
[17:32] <ScottK> BTW, the new multitouch stack is about to land on precise and if someone has appropriate hardware it'd be great to get some testing with Qt apps.  None of the Kubuntu developers have hardware.
[17:33] <balloons> ScottK, ohh really? I've been waiting for it to land to try out with my chromebook which has a multitouch pad
[17:33] <phillw> but my daily buold from yesterday has just failed after install.
[17:33] <ScottK> balloons: I understand the qt4-x11 build on armel is the last thing they are waiting for.
[17:33] <ScottK> It takes about a day and a half to build.
[17:34] <balloons> phillw, do you know why it failed yet?
[17:34] <ScottK> I think this needs a touch screen though.
[17:34] <phillw> balloons: no, It just sent my VM crazy when I 1st launched it. I've only just put it on so need to have a dig around.
[17:34]  * alourie I must leave now, sorry, will read logs later
[17:35]  * alourie thanks balloons for the chairing :-)
[17:35] <balloons> goodbye alourie!
[17:35] <balloons> phillw, ScottK thanks for the updates
[17:35] <balloons> How about xubuntu?
[17:36] <gema> charlie-tca doesn't seem to be here
[17:36] <balloons> yep
[17:36] <balloons> astraljava, anything on ubuntu studio?
[17:36] <njin> unity-greeter[1589] trap int3 ip:7fec4fbe4b3b sp:7fff55e32490 error:0
[17:36] <astraljava> Nothing much. We're picking up speed in getting our first ever live-dvd developed soon-ish.
[17:36] <njin> phillw:^^
[17:37] <astraljava> Other than that, it's been slow.
[17:37] <astraljava> ..
[17:37] <balloons> just curious, how much kernel testing does your team undertake?
[17:38] <njin> Xubuntu today install like a charm
[17:38] <astraljava> Somewhat, as we're going to include the -low-latency kernel.
[17:38] <njin> in my test
[17:38] <astraljava> But it hasn't reached the repositories yet.
[17:38] <astraljava> ..
[17:38] <phillw> njin: I'll wait for todays build. Mine is dated 17th.
[17:38] <njin> I too
[17:38]  * txomon|nqas would like to ask a question at the end
[17:39] <njin> also the build useed to report the bug is 17
[17:39] <balloons> ok great.. thank astraljava
[17:39] <balloons> One more update njin and txomon|nqas  :-)
[17:39] <balloons> highvoltage, anything from edubuntu?
[17:40] <balloons> or anyone else care to comment on edubuntu? stgraber? I know they said they were not usually around
[17:40] <balloons> we'll move on then
[17:40] <highvoltage> hey balloons
[17:40] <highvoltage> ah sorry I forgot about this meeting
[17:41] <balloons> hello :-)
[17:41] <balloons> no worries -- anything to share?
[17:41] <highvoltage> nothing that I have prepared now, but I'll give an update next time!
[17:41] <balloons> sounds great
[17:41] <highvoltage> how often does this meeting occur?
[17:41] <txomon|nqas> weekly
[17:41] <balloons> every weds at 1700 utc
[17:41] <highvoltage> ok
[17:41] <balloons> [TOPIC] Other Discussions
[17:42] <balloons> ok, lastly anything from the list or otherwise anyone wants to bring up
[17:42] <balloons> fire away njin
[17:43] <balloons> txomon|nqas, how about your question?
[17:43] <njin> just that today kubuntu and Xubuntu installs ok in every modality
[17:43] <njin> on real hardware
[17:44] <txomon|nqas> I have been thinking about this for a large time. I have several computers that I don't use, and that would like to use for testing, is there any app the qa has to make automated installs?
[17:44] <txomon|nqas> I mean, automatically running tests, and sending reports
[17:44] <balloons> njin: sweet!
[17:45] <gema> txomon|nqas: not yet
[17:45] <txomon|nqas> have been looking at the Orchestra project, but that is mainly focused on server deployment
[17:45] <balloons> gema, what work would need to be done to enable such things?
[17:45] <gema> balloons: we are working on a project that will allow people to do this at home
[17:46] <gema> balloons: but we are barely gathering requirements at the moment
[17:46] <txomon|nqas> gema: good to know.
[17:46] <balloons> gotcha
[17:46] <gema> balloons: having an orchestra server would be good for the time being
[17:46] <gema> and I have been told it is very easy to use
[17:46] <gema> but not everyone will be up for it
[17:46]  * txomon|nqas tryed orchestra...
[17:46] <gema> txomon|nqas: and?
[17:47] <txomon|nqas> puf, that was difficult to use in a home enviroment. It was very focussed on servers, and
[17:47] <ScottK> This week I'm expecting we'll get postfix 2.8.7 into precise and then there will be post-release updates for natty and oneiric that need testing.
[17:47] <txomon|nqas> there were lots of things not quite modularized
[17:48] <gema> txomon|nqas: agreed
[17:48] <txomon|nqas> I mean, the orchestra-provisioning
[17:48] <balloons> txomon|nqas, any other thoughts on tools? certainly I would encourage you to see what you could come up with to do the automated testing, even if there wasn't a good way (yet) to feedback
[17:48] <txomon|nqas> which is what I mainly wanted, is quite strange to my eyes (alone at least)
[17:49] <txomon|nqas> balloons: I have been using apt-cacher-ng to cache, instead of squid
[17:49] <txomon|nqas> and speeds up quite a lot installations
[17:49] <txomon|nqas> easy to configure (doesn't need btw)
[17:49] <balloons> and your mainly looking at iso installing or ?
[17:50] <txomon|nqas> balloons: I was intending to create automatic installation systems, with kickstart files
[17:50] <hggdh> ScottK: do we have tests available for postfix, or is it ad-hoc?
[17:50]  * hggdh wonders if the meeting lost focus
[17:50] <balloons> just dual convo's :-)
[17:51] <gema> hggdh: +1 :D
[17:51] <ScottK> hggdh: I think it's ad hoc, but postfix upstream is one of the most careful and reliable there is.
[17:51] <balloons> txomon|nqas, i would say keep us informed of your work and progress.. Gema as you can use feedback on requirements gathering let's plan to share and make sure txomon|nqas sees it
[17:51] <hggdh> ScottK: k
[17:52] <gema> balloons: ok
[17:52] <txomon|nqas> I would be quite interested on that
[17:53] <txomon|nqas> nothing more on my side
[17:53] <balloons> scottk?
[17:53] <txomon|nqas> will discuss this in #ubuntu-testing
[17:53] <ScottK> No.  Nothing more.
[17:53] <balloons> alright -- our time has come to an end then.. great meeting everyone. thanks for coming
[17:53] <nuclearbob> thanks for chairing
[17:53] <gema> thanks for chairing!
[17:53] <bil21al> ok yw
[17:53] <balloons> and for dealing with me as the chair ;-) See you all next week
[17:54] <balloons> #endmeeting
[17:54] <meetingology> Meeting ended Wed Jan 18 17:54:14 2012 UTC.
[17:54] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-01-18-17.00.moin.txt
[17:54] <hggdh> ScottK: I will keep an eye for it
[17:54] <phillw> balloons: thnks for chairing
[17:57] <njin> ballons, thanks
[18:00] <jibel> thanks for chairing balloons
[18:02] <bdmurray> Time for the bug squad meeting
[18:02] <bdmurray> #startmeeting
[18:02] <meetingology> Meeting started Wed Jan 18 18:02:55 2012 UTC.  The chair is bdmurray. Information about MeetBot at http://wiki.ubuntu.com/AlanBell/mootbot.
[18:02] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[18:03] <bdmurray> #topic Previous Actions
[18:03] <bdmurray> ACTION: bdmurray to perform SRU of fix for bug 904527 for Oneiric
[18:04] <bdmurray> Pedro had asked that I upload a fix for Oneiric for that
[18:04] <bdmurray> which I've done but it could use verification
[18:04] <bdmurray> Its really simple ;-) just make sure /usr/share/apport/package-hooks/source_rhythmbox.py exists!
[18:05] <bdmurray> So if anybody still running Oneiric could check that out it'd be much appreciated
[18:05] <bdmurray> moving on
[18:06] <Ursinha> (I can do that)
[18:06] <bdmurray> Ursinha: that'd be great!
[18:06] <Ursinha> :)
[18:06] <bdmurray> #action Ursinha to perform SRU verification of bug 904527
[18:06] <meetingology> ACTION: Ursinha to perform SRU verification of bug 904527
[18:07] <bdmurray> #topic Engineering Team Bug Status
[18:07] <bdmurray> Ursinha: do you have anything for us?
[18:07] <Ursinha> bdmurray, not really no
[18:08] <bdmurray> Ursinha: oh with regards to that openoffice package install failure bug
[18:08] <bdmurray> come to find out apport wasn't checking bug patterns in precise
[18:08] <bdmurray> this is fixed now
[18:08] <Ursinha> oh, argh and cool :)
[18:08] <Ursinha> thanks for fixing the world, bdmurray :)
[18:08] <bdmurray> In all fairness pitti fixed it, I just found it. ;-)
[18:09] <bdmurray> jsalisbury: Do you have anything to report?
[18:09] <Ursinha> which is fairly important too ;)
[18:09] <jsalisbury> Just a heads up, there are a bunch of duplicates coming in for bug 917962
[18:09] <jsalisbury> This bug seems to have only started today.  I'm in the process of bisecting to find what caused the regression.
[18:10] <bdmurray> I wouldn't say its only started today, we might now just be seeing it since I turned on kerneloops
[18:10] <jsalisbury> bdmurray, ahh, yes, correct
[18:10] <Ursinha> bdmurray, you turned on kerneloops again?
[18:11] <bdmurray> Ursinha: yes, I disabled the question regarding uploading it to kerneloops.org and enabled kerneloops again
[18:11] <Ursinha> great :)
[18:11]  * Ursinha takes notes
[18:11] <jsalisbury> bdmurray, it's doing its job ;-)
[18:12] <bdmurray> jsalisbury: yeah so it seems.  let me know if you need any help writing a bug pattern for that bug
[18:12] <balloons> hehe, I feel like I should be afraid to update today...
[18:12] <jsalisbury> bdmurray, will do.  I'll create the bug pattern once the root cause is identified.
[18:13] <bdmurray> jsalisbury: why wait? duplicates will just keep coming in
[18:13] <jsalisbury> bdmurray, That's the only major update I have.
[18:13] <jsalisbury> bdmurray, Just need to have time later today.
[18:13] <bdmurray> jsalisbury: okay, I wasn't sure if it was hardware specific or something
[18:14] <bdmurray> So as previously mentioned I've turned on kerneloops now
[18:14] <jsalisbury> bdmurray, no I don't believe so.  I should have the pattern done this afternoon.
[18:14] <bdmurray> I also uploaded an updated update-manager apport package hook to include Aptdaemon messages from syslog
[18:15] <bdmurray> And there will be a new version of firefox-lp-improvements shortly
[18:15] <bdmurray> That'll fix bug 917461
[18:16] <bdmurray> #topic Bug Escalations (any High or Critical bugs that community members have seen that need attention)
[18:16] <bdmurray> Are there any bugs that we need to be aware of or that need some love?
[18:18] <bdmurray> okay that's good news I hope
[18:19] <bdmurray> #topic Other Topics
[18:19] <bdmurray> Speaking of SRU verifications
[18:19] <bdmurray> There is a version of update-manager in oneiric proposed that could use some verification
[18:19] <bdmurray> it fixes bug 880704
[18:20] <bdmurray> bug 873432 and bug 873424
[18:21] <bdmurray> I'm familiar with the bugs if anybody needs help verifying them
[18:21] <bdmurray> Is there anything else to discuss?
[18:25] <bdmurray> Well then, thanks everyone
[18:26] <bdmurray> #endmeeting
[18:26] <meetingology> Meeting ended Wed Jan 18 18:26:01 2012 UTC.
[18:26] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-01-18-18.02.moin.txt
[18:26] <jsalisbury> thanks, Brian
[18:29] <Ursinha> thanks bdmurray
[20:05] <gilir> #startmeeting Lubuntu Team Meeting
[20:05] <meetingology> Meeting started Wed Jan 18 20:05:45 2012 UTC.  The chair is gilir. Information about MeetBot at http://wiki.ubuntu.com/AlanBell/mootbot.
[20:05] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[20:05] <jmarsden|work> o/
[20:06]  * gilir takes a seat
[20:06] <phillw> 0/
[20:06] <michaelrawson> o/
[20:06] <MrChrisDruif> Sit down already ;-)
[20:06] <Unit193> \o
[20:06] <gilir> as ususal, aganda is here : https://wiki.ubuntu.com/Lubuntu/IRC%20Meetings/Agenda
[20:06] <StephenSmally> 0/
[20:07] <gilir> no action from previous meeting
[20:08] <gilir> so we will go directly to team report :)
[20:08] <gilir> #topic phillw - Weekly report - Update from QA meeting and team
[20:08] <phillw> Sadly, one big bug has just surfaced.
[20:09] <phillw> I've just gotten confirmation of it & it prevents a new install of lubuntu 12.04 from running. Does not affect xubuntu or kubuntu.
[20:09] <gilir> phillw, you have a bug number ?
[20:10] <phillw> gilir: I got confirmtaion about 3 minutes ago!
[20:10] <phillw> gilir: I'll get it raised but the issue is unity-greeter[1589] trap int3 ip:7fec4fbe4b3b sp:7fff55e32490 error:0
[20:10] <phillw> also the build useed to report the bug is 17
[20:10] <phillw> same errors for me in 18 on real hardware
[20:11] <gilir> phillw, hum, we should not have unity-greeter at all on lubuntu
[20:11] <jmarsden|work> why would there be a "unity-greeter" ... exactly!
[20:11] <phillw> that is what njin from the QA team saw when he tried to confirm it for me. It fails crazily on VM. He used a 'real' machine.
[20:12] <gilir> phillw, I'll look at a daily ISO to check, maybe the last update of lighdm was not so nice :)
[20:12] <phillw> okies, I got it 1st on 17th, we re-tried once 18th came out.
[20:12] <amjjawad> that black wallpaper is so bad
[20:13] <michaelrawson> lightdm won't run at all for me. I'm all for keeping lxdm for now.
[20:13] <phillw> other than that, the new front wiki for the main QA team has been redisgned and will gradually filter through to update everything.
[20:13] <amjjawad> for me, I got it after I updated and upgraded my system
[20:13] <phillw> https://wiki.ubuntu.com/Testing/
[20:14] <gilir> michaelrawson, report a bug instead, we can't just switch this type of application when a bug arise
[20:14] <phillw> The current push is to have everything needed for alpha 2 testing.
[20:14] <phillw> end of QA report.
[20:14] <michaelrawson> @gilir, I have. Sorry for chipping in :)
[20:14] <meetingology> michaelrawson: Error: "gilir," is not a valid command.
[20:14] <michaelrawson> gilir, I have. Sorry for chipping in :)
[20:15] <gilir> thanks phillw
[20:15] <gilir> #action gilir to check the unity-greeter / black wallpaper bug on ISO
[20:15] <meetingology> ACTION: gilir to check the unity-greeter / black wallpaper bug on ISO
[20:16] <gilir> #topic Unit193 - Weekly report - Update on IRC OP's team
[20:16] <Unit193> The IRC council call for OPs has been closed and we should hear from them later this week.
[20:16] <Unit193> I'm also still looking for someone to do the OPs interview
[20:17] <jmarsden|work> Unit193: Use a mirror?
[20:17] <Unit193> jmarsden|work: Last one I tried broke :/
[20:18] <gilir> Unit193, interview for the comm team ?
[20:18] <Unit193> gilir: Yes sir!
[20:18] <gilir> well, it's not mandatory :)
[20:19] <gilir> let's see how the first ones go, maybe people will be interested after :)
[20:19] <amjjawad> no one replied Jens except me and Phill :/
[20:20] <gilir> amjjawad, I done it off list ;)
[20:20] <Unit193> Yeah, there isn't much info as to the questions and sych
[20:20] <amjjawad> gilir: aha :D
[20:20] <phillw> amjjawad: also chris druif has replied.
[20:20] <amjjawad> phillw: that's cool :)
[20:20] <gilir> Unit193, anything else ?
[20:21] <Unit193> That's all I can think of for now
[20:21] <gilir> ok thanks Unit193 :)
[20:21] <MrChrisDruif> YOU FORGOT ME?
[20:21] <gilir> #topic MrChrisDruif - Weekly report - Update on Wiki / Docs team
[20:21] <gilir> MrChrisDruif, I follow the agenda order ;)
[20:22] <MrChrisDruif> We've had a small issue regarding installing non-platform apps like ktouch on lubuntu
[20:23] <MrChrisDruif> I asked if others could look up if others could find any info on the wiki regarding this issue. I've not had any response yet
[20:23] <gilir> MrChrisDruif, is there a bug report somewhere (upstream or on launchpad) ?
[20:24] <MrChrisDruif> And still haven't really started with the restructuring of the wiki and help pages
[20:24] <MrChrisDruif> gilir; No, it was a question coming from amjjawad from the forum.
[20:24] <amjjawad> MrChrisDruif:  we need to talk sometime soon regarding that :)
[20:25] <amjjawad> I mean regarding the Wiki Pages and the re-organization of it
[20:25] <MrChrisDruif> If it had performance issue. gilir; if you know anything about it, info would be appreciated
[20:25] <gilir> MrChrisDruif, no sorry, never use it
[20:26] <MrChrisDruif> Alright, then I'll send a query to the mailing-list to find info about it
[20:26] <gilir> but maybe you could report a bug on upstream bug tracker, if you can't find information about this issue
[20:26] <gilir> yes, maybe someone on the mailing know something
[20:27] <MrChrisDruif> Other then that nothing to report
[20:27] <amjjawad> and I'll try to do some search on the forum in case I can find something useful :)
[20:27] <gilir> thanks MrChrisDruif :)
[20:27] <MrChrisDruif> amjjawad; thanks. About restructuring the wiki you can post to the wiki mailing-list
[20:27] <amjjawad> MrChrisDruif: please CC me when you will send that email :)
[20:27] <MrChrisDruif> If you've got ideas, just share them
[20:27] <amjjawad> MrChrisDruif: I thought we can chat ?
[20:28] <gilir> #topic gilir - Weekly report - Devs teams report
[20:28] <gilir> No big and visible progress here
[20:28] <StephenSmally> i have to say a thing
[20:28] <gilir> work on lxfind continue
[20:29] <StephenSmally> gilir: yes, i'm implementing popup menu right now
[20:29] <MrChrisDruif> gilir; Q: will LSC ever replace gdebi?
[20:29] <wxl> yey lxfind!
[20:29] <gilir> some progress on the packaging of the artwork, if you have the staging PPA, you may see some new stuff soon
[20:29] <wxl> (sorry just had to say thank you)
[20:29] <amjjawad> +1 for MrChrisDruif Q
[20:29] <gilir> and an update of gnome-mpalyer is in progress, available in PPA staging too
[20:30] <gilir> StephenSmally, yes ?
[20:30] <StephenSmally> mmm, no, for the moment
[20:30] <amjjawad> why not to keep it?
[20:30] <gilir> StephenSmally, you said you had something to say :)
[20:30] <StephenSmally> ah, excusme :)
[20:31] <StephenSmally> a last bug on LSC should be fixed now (using non english translation)
[20:31] <StephenSmally> so i think we will be ready to release 0.0.3 soon
[20:31] <gilir> StephenSmally, cool :)
[20:32] <gilir> StephenSmally, ping me when it's ready, so I can test it and update it on the repositories
[20:32] <StephenSmally> of course
[20:33] <gilir> StephenSmally, and remember, feature freeze will be here soon, be sure to include most feature you want before this :)
[20:34] <StephenSmally> mm, but if lsc is already in the repo...
[20:34] <gilir> nothing more from devs, unless StephenSmally or jmarsden|work want to add anything
[20:34] <StephenSmally> shouldn't be possible update it without problems?
[20:34] <jmarsden|work> Nothing from me, except that lightdm/black screen issue needs fixing :)
[20:34] <gilir> StephenSmally, yes, but feature freeze applied to all packages in repo
[20:35] <jmarsden|work> StephenSmally: You can't add new features even to an existing app after Feature Freeze without getting an FFe
[20:35] <gilir> StephenSmally, after this, we can't add new feature, we focus on bug fixing
[20:35] <StephenSmally> Argh, ok, i will be fast as possible ;-)
[20:35] <StephenSmally> another little things,
[20:35] <gilir> that's mean I need to finish the session manager really soon :/
[20:35] <amjjawad> StephenSmally: will LSC do the same function that Gdebi does?
[20:35] <wxl> ooh i forgot to ask, does lxfind do regex at all?
[20:35] <wxl> probably not
[20:36] <StephenSmally> i opened a topic on the Ubuntu Italian forum to collect feedbacks and hints about lubuntu
[20:36] <StephenSmally> wxl: since you use find as backend, yes, no with the native glib backend
[20:37] <wxl> StephenSmally: so if i understand you correctly, you're saying part of the backend does, but the other doesn't, so long story short, no
[20:37] <StephenSmally> LxFind supports 3 kind of backends
[20:37] <StephenSmally> Locate, Find and the Glib one
[20:38] <wxl> ah so it just selects the right one; got it
[20:38] <amjjawad> StephenSmally: will LSC do the same function that GDebi does?
[20:39] <StephenSmally> amjjawad: no, not at the moment
[20:39] <amjjawad> but in future yes, right?
[20:39] <amjjawad> StephenSmally: and for me to know more about LSC and can answer such Qs on the Forum ... will user be able to install and use LSC on any variant?
[20:39] <StephenSmally> amjjawad: we will see, if gdebi is too old or if is unuseful have to apps instead of one yes
[20:40] <michaelrawson> amjawad; I have LSC on ubuntu, if that helps.
[20:40] <StephenSmally> Yes, LSC haven't got any dependencies related to Lubuntu specifically, runs on any Debian Base distro
[20:40] <amjjawad> michaelrawson: that is good to know :)
[20:40] <amjjawad> StephenSmally: thanks :)
[20:40] <amjjawad> one last Q
[20:40] <amjjawad> will LXFind be available in 12.04?
[20:41] <StephenSmally> mm, i think gilir will ask better
[20:41] <amjjawad> gilir: ?
[20:42] <StephenSmally> (Feature freeze, you know, we need tester and need fast builds, launchpad takes hours to build)
[20:42] <gilir> amjjawad, not by default, it's too short, but yes in the PPA
[20:42] <amjjawad> gilir: thanks a lot. I need to be ready to answer that on Forums :)
[20:42] <michaelrawson> gilir; permamently in PPA, or in 12.10?
[20:43] <jmarsden|work> Who knows what will be in 12:10, at this point? :)  probably lxfind can be in 12.10 if it matures by then...
[20:43] <gilir> michaelrawson, no, we can reconsider it for 12.10
[20:43] <michaelrawson> yup, thanks gilir.
[20:43] <MrChrisDruif> StephenSmally; I'm not seeing a definitive answer if it'll support .deb installation
[20:43] <amjjawad> gilir: what about LXScreenshot?
[20:44] <gilir> amjjawad, as I said on the ML, we need to compare it with scrot, to see if we can replace it
[20:44] <StephenSmally> MrChrisDruif: not in Precise
[20:44] <amjjawad> so that means not yet decided. Thanks G
[20:45] <gilir> any more questions ? :)
[20:45] <amjjawad> gilir: wubi?
[20:45] <MrChrisDruif> But eventually yes? Maybe with backports eventually in Precise?
[20:45] <amjjawad> in 12.04?
[20:46] <gilir> amjjawad, I had no news about it, still in progress for 12.04
[20:46] <phillw> amjjawad: wubi will support 12.04 lubuntu
[20:46] <amjjawad> Ok, thanks gilir  :)
[20:47] <amjjawad> phillw: so is it official?
[20:47] <gilir> phillw is more up-to-date than me :)
[20:47] <phillw> amjjawad: the fix has been made, we awair beta1 for full testing.
[20:47] <amjjawad> ok then it's kind of official :) thanks phillw
[20:48] <amjjawad> I'm done with Qs so far
[20:48] <phillw> amjjawad: https://bugs.launchpad.net/wubi/+bug/907524
[20:48] <gilir> #topic jmarsden|work Mailing list migration
[20:49] <amjjawad> thanks phillw, I subscribed to that bug :)
[20:49] <gilir> jmarsden|work, I planned to just close the team for new member, and remove current members to be sure nobody post to the old mailing list
[20:50] <gilir> jmarsden|work, if you have a better idea, go :)
[20:50] <amjjawad> gilir: why we do this? because we have sub-teams now?
[20:50] <jmarsden|work> That's fine, I was wondering when we will do it, I am still seeing some people (phillw and amjjawad from memory) use the old list...
[20:50] <gilir> amjjawad, no, because we have a new-and-more-official mailing list
[20:51] <amjjawad> gilir: ok but what about the members?
[20:51] <amjjawad> they need to join the NEW one first!!
[20:51] <gilir> jmarsden|work, I planned to wait some days after the annoucement of the new mailing list, but I can do it shortly now
[20:51] <gilir> amjjawad, I already send 2 mails on the old mailing about it
[20:52] <gilir> I think it's enough :)
[20:52] <amjjawad> gilir: true but I'm sure most did not read it yet :(
[20:52] <michaelrawson> o/
[20:52] <jmarsden|work> I think we need a clear decision; it's Ok with me if the etam thinks we need a longer period for people to move over... but ... yes, peole alread had notice.
[20:52] <gilir> I'll see if I can send a message with the kick of the members
[20:52] <amjjawad> gilir: I'll make sure to update the threads on UF
[20:52] <amjjawad> so that most of them who are already there will be informed
[20:53] <jmarsden|work> Thinking about this... which "team" is responsible for the mailing list? :)
[20:53] <amjjawad> michaelrawson: where do you think we need to put that? what thread?
[20:53] <michaelrawson> IDK. all of them!
[20:53] <Unit193> One last email to say why they were removed, and remove them all, simple
[20:53] <amjjawad> I can't put that on all of them, it's cross posting and you know what is next ;) michaelrawson
[20:54] <michaelrawson> I meant LOST and LOSG and possible the 12.04 thread. :)
[20:54] <gilir> jmarsden|work, I don't know if we really need a team on this :)
[20:54] <amjjawad> jmarsden|work: I say we don't need that
[20:54] <amjjawad> each sub-team will take care of its own list
[20:54] <amjjawad> lubuntu-user will be for everyone
[20:55] <Unit193> If people are subscribed to the mailing list, they should just need an email about it
[20:55] <amjjawad> michaelrawson: I'll see where to put that, most likely Lubuntu One Stop Group :)
[20:56] <michaelrawson> you could also possible ask the fridge, etc to put out something. IDK, I agree with gilir in part.
[20:56] <michaelrawson> is it possible to send a message every time someone posts to that list, warning them it's closing soon, and where to look for new one?
[20:56] <gilir> michaelrawson, maybe a blog post on a Ubuntu Planet should be enough ?
[20:56] <michaelrawson> probably. :)
[20:57] <michaelrawson> I am googling ubuntu planet. :)
[20:57] <wxl> as an aside to the topic but consistent with this current tangent, amjjawad i think you should create a facebook GROUP for us
[20:58] <wxl> pages are easy to ignore
[20:58] <gilir> any ubuntu member volunteer for this blog post ? :p
[20:58] <amjjawad> wxl: there is a group but i have no clue who is in charge???
[20:58] <phillw> gilir: I'll giver it a go :)
[20:58] <gilir> phillw, your blog is aggregate on the planet ?
[20:59] <wxl> amjjawad: we'll chat later about this. i'm sure you could get in touch and have him/her make you an admin
[20:59] <phillw> gilir: I thought you wanted s.o. to report it ubuntu planet?
[20:59] <amjjawad> I tired and he/she ignored me as usual wxl
[20:59] <wxl> amjjawad: then make a new group! :D
[20:59] <amjjawad> phillw: what do you think? new group?
[20:59] <wxl> amjjawad: e.g. "Official Lubuntu"
[20:59] <amjjawad> I'm not an admin on Lubuntu Page yet??? so what gives? phillw ?
[21:00] <amjjawad> I've been calling for that since ages!
[21:00] <phillw> amjjawad: I rarely use fb!
[21:00] <amjjawad> many do phillw
[21:00] <amjjawad> I'm UP to this as forever
[21:00] <amjjawad> :)
[21:00] <amjjawad> my requests were being ignored
[21:00] <amjjawad> I'm active on Fb
[21:00] <amjjawad> just like UF
[21:01] <gilir> phillw, we will talk about it later, maybe I can do a blog post about Lubuntu devs for 12.04, include this information
[21:01] <wxl> ACTUALLY i'd be happy to help out with a facebook group as part of support
[21:01] <amjjawad> I'm creating too many pages but I don't think it's very good idea. We need to focus on few official pages
[21:01] <phillw> okies gilir
[21:01] <michaelrawson> well...me too, but I'm with phill on fb usage.
[21:01] <gilir> ok, it's time, if nobody have important stuff to add, I'll finish the meeting
[21:01] <wxl> pages don't push notifications, but groups do, which is why i suggest groups
[21:02] <amjjawad> wxl: i don't mind :)
[21:02]  * MrChrisDruif uses fb a lot. But google+ for Ubuntu related stuff
[21:02] <wxl> sounds like this is our personal project amjjawad :D
[21:02] <amjjawad> I need the green light
[21:02] <amjjawad> I already made G+ for Lubuntu ;)
[21:02] <gilir> #endmeeting
[21:02] <meetingology> Meeting ended Wed Jan 18 21:02:46 2012 UTC.
[21:02] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-01-18-20.05.moin.txt
[21:02] <amjjawad> Lubuntu page on fb has more than 3K users
[21:02] <wxl> i hate G+
[21:02] <phillw> gilir:  thanks for chairing :)
[21:03] <Unit193> gilir: Thanks
[21:03] <gilir> thanks guys :)
[21:03] <amjjawad> wxl: and michaelrawson  let's talk on the offtopic :)
[21:03] <amjjawad> meet me there ;)
[21:03] <michaelrawson> okay. :)
[21:03] <wxl> ok
[21:03] <wxl> thanks all
[21:03] <michaelrawson> yup, thanks gilir, everybody.
[21:03] <michaelrawson> bye!
[21:13] <michaelrawson> hi StephenSmally
[23:48] <vibhav> When will the meeting start?
[23:49] <benonsoftware> vibhav: Which meeting?
[23:49] <vibhav> North and South American regional approval board
[23:49] <benonsoftware> vibhav: This time tomorrow
[23:50] <vibhav> Why tomorrow?
[23:50] <benonsoftware> Let me double check
[23:50] <vibhav> ohhh
[23:50] <vibhav> thanks benonsoftware
[23:50] <Pendulum> vibhav: the meeting is tomorrow.


[01:33] <akk> On pangolin, my audio is silent, and when I look in alsamixergui, it looks like PCM is permanently muted. Clicking on it doesn't un-mute.
[23:10] <philipballew_> bkerensa, was your Chinese food uds idea an official idea or were you going to have it as informal?
[23:12] <bkerensa> informal
[23:13] <bkerensa> :D
[23:13] <philipballew_> alright. Just making sure.
[23:13] <philipballew_> I just used the word ubuntu in a college paper!
[23:14] <philipballew_> the professor better give me an A...
[23:14] <bkerensa> lol
[23:14] <philipballew_> It even fits!


[18:04] <TheLordOfTime> is there any way to pull apport logs to figure out where it filed a crash bug?  because Unity or xserver died and it gave me no information about what died, and it looked like it filed a crash bug based on the windows that popped up, but I'd love to see where that bug is located... if anywhere.
[18:07] <Ampelbein> TheLordOfTime: If apport filed a bug it was under your user name on lp.
[18:07] <Ampelbein> At least that's how I remember it working
[18:13] <hjd> TheLordOfTime: Not sure how apport's workflow is organized, but have you checked under /var/crash whether the crash report is still there?
[18:23] <TheLordOfTime> Ampelbein: not there.
[18:23] <TheLordOfTime> hjd: one moment
[18:24] <TheLordOfTime> hjd: i see two sets of items from today's crash...
[18:24] <TheLordOfTime> hjd: two .crash files (xorg and compiz)
[18:24] <TheLordOfTime> two .upload files
[18:24] <TheLordOfTime> and two .uploaded files
[18:25] <TheLordOfTime> not sure whether those got dumped to errors.u.c or whether one actually created a crash bug
[18:25] <TheLordOfTime> (although in Precise i doubt it'll ever be fixed)
[18:26] <TheLordOfTime> Ampelbein: that was my thought as well, but I looked and nothing shows up in my bugs list when I look at myself on LP
[18:26] <TheLordOfTime> which i found strange :/
[18:26] <TheLordOfTime> maybe it just uploaded to errors.u.c instead?
[18:32] <hjd> TheLordOfTime: Hm, not sure about the .uploaded files. All I know is that the crash reports are stored there, and it is possible to manually submit them.
[18:33] <hjd> It was never really clear to me when things would go to LP and when the would go to errors, though


[09:06] <JamesPage> doko:  ttx mentioned to me that there was a situation developing in Debian re ant - can you fill me in on the details?
[09:15] <ttx> I thought it was about adopting the ant1.7 and ant (1.8) debian packages, but we seem to already have them
[09:15]  * ttx is a bit confused as well
[09:19] <JamesPage> ttx: we do - lucid has 1.7 and maverick has 1.8
[09:21] <ttx> JamesPage: maverick also has "ant1.7" that is bound to 1.7
[09:21] <ttx> for packages incompatible with ant 1.8
[09:21] <persia> I suspect the "situation developing" was that some software suddenly didn't work with 1.8, and needed to be switched to build with ant1.7
[09:22] <persia> I suspect it to be mostly "developed" at this point, but there may still be things needing modification.
[09:23] <ttx> persia: doko wanted us to handle something when Natty opens
[09:23] <ttx> so I think he had something specific in mind
[10:35] <doko> JamesPage, ttx: we still have ant1.8 in the archive, which should be removed, I see that the default is already 1.8, so maybe I wasn't awake when telling you about getting it fixed early for natty
[10:36] <ttx> ack
[10:41] <JamesPage> doko: ok - will ant1.8 be removed for maverick or natty?
[10:51] <doko> JamesPage: yes, if you take care of it ;p
[10:51] <doko> file a bug report and subscribe ubuntu-archive
[10:52] <doko> if we don't have any b-d's or b's on ant1.8 we could do it even now
[10:59] <JamesPage> No b-d's or b's on ant1.8 in either lucid or maverick - I'll file a bug report now :-)
[11:00] <JamesPage> doko: should this be removed for just maverick as its now the default ant option?
[11:04] <doko> JamesPage: yes, I introduced ant1.8 late in lucid to get a recernt ant without changing the default. debian did decide to update to 1.8 and provide an ant1.7, but that was too late for lucid
[11:04] <JamesPage> doko: OK understand - just read the bug report associated with the lucid FFE
[11:09] <JamesPage> doko, ttx: raised under bug 645063
[11:09] <ubot2> Launchpad bug 645063 in ant1.8 (Ubuntu) "Please remove ant1.8 from maverick archive (affects: 1) (heat: 8)" [Undecided,New] https://launchpad.net/bugs/645063


[13:46] <wolfger> morning?
[13:46] <wolfger> Happy Saturday #11  :-D
[16:07] <cmaloney> Happy not quite saturday
[16:07] <cmaloney> Still working and what-not
[19:01] <gamerchick02> NEW GLASSES! (in about two weeks)
[19:01] <gamerchick02> i'm so excited. sorry
[19:22] <cmaloney> I'll be more excited for you in about two weeks
[19:48] <gamerchick02> :-D thanks
[19:49] <gamerchick02> my experience was great. getting two pairs, sunglasses and regular.
[21:21] <rick_h_> afternoon
[21:21] <rick_h_> gamerchick02: ooh, let me know how that goes. I always debate that
[21:29] <gamerchick02> i will! and i'm going to probably take a selfie and post on the plus
[21:29] <gamerchick02> hah
[21:30] <rick_h_> lol
[21:50] <cmaloney> rick_h_: I see the photos are coming in. :)


[05:35] <didrocks> good morning
[06:02] <duflu> Hi didrocks
[06:10] <didrocks> hey duflu
[06:24] <oSoMoN> good morning desktoppers
[06:30] <duflu> Hi oSoMoN
[06:31] <oSoMoN> hey duflu
[06:59] <seb128> goood morning desltopers
[07:04] <duflu> Hi seb128
[07:07] <seb128> duflu, hey, how are you?
[07:08] <duflu> seb128, I feel great. Just a little annoyed that emails, travel planning and family issues have taken up a few hours today. How are you?
[07:09] <seb128> duflu, I'm alright thanks!
[11:58] <lissyx> oSoMoN, no edge snap installable on aarch64 ?
[12:06] <oSoMoN> lissyx, no, because nightly snaps are built on github, i.e. amd64-only
[12:12] <lissyx> doh
[12:12] <lissyx> oSoMoN, I guess that's  a question for you https://bugzilla.mozilla.org/show_bug.cgi?id=1795838#c5
[12:12] -ubottu:#ubuntu-desktop- Mozilla bug 1795838 in Release Engineering "Nightly snap package stopped updating" [--, New]
[12:27] <ogra> oSoMoN, https://discourse.ubuntu.com/t/ubuntu-on-the-visionfive-and-the-nezha-boards/29858/24 ... i assume the chances for a riscV firefox build are not very high currently ?
[12:28] <oSoMoN> ogra, I don't know how much work that would involve, and it's not on the plan, but that can be discussed if there is a real need
[12:29] <ogra> (the build time might clash with the FF release schedule 🙂 )
[12:32] <lissyx> ogra, I think there are some people hacking risc-v support?
[12:32] <lissyx> I dont know the status though
[12:32] <lissyx> but I'm pretty sure I saw some bugs about that where there was activity
[12:34] <ogra> sure, the question is if RISCV is even suitable though ... the current build times are hilarious ... and it could well be that RISC-V is still building the last version while amd64 already releases the next binary 😉
[12:34] <lissyx> cross compilation?
[12:34] <ogra> hmm, not fun
[12:35] <ogra> (in .deb based environments that is)
[12:36] <ogra> snaps make that surely easier ... but our builds sadly still consume debs as dependencies and such ...
[12:40] <lissyx> ogra, I've so far failed to find how to perform aarch64 cross compilation for snap
[12:40] <lissyx> no doc on that matter, only a few forum posts (and I think it was you replying ?) suggesting to do on host
[12:40] <lissyx> and my last tentative on some gcp aarch64 beefy system badly failed :(
[12:40] <ogra> i do it all the time bu only for bootloaders and kernels where you do not have any dependencies ... as soon as you need to link against a lib or such, it gets really hairy
[12:41] <ogra> snapcraft has many builtins that make cross building easier ... but yu still have to deal with a) te code and b) the debian packages to be pulled in and found correctly during the build
[12:42] <ogra> s/te/the/
[12:42] <ogra> and something like firefox is really not the package to start learning it either 🙂
[14:42] <lissyx> ogra, when I was working on deepspeech, we solved that simply by pulling some debootstrap-populated sysroot
[14:43] <lissyx> still a few hacks required, but it was much much much more convenient than anything else
[14:43] <lissyx> especially building tensorflow for armhf/aarch64, we would not have been able to perform that decently on CI with real hardware
[14:47] <ogra> well, you could do the same in snapcraft ... through a separate part that creates your sysroot (well, in that case, even just wget an ubuntu-base tarball for arm)
[14:49] <lissyx> except I'm not really at ease with snapcraft and I was hoping it would be handled for me easily, since it relies on multipass and other techniques
[14:55] <ogra> well, it defaults to lxd now, only on MAC it uses multipass ... but either way, you'd then run a foreign arch VM which is essentially just a native build, not cross