[16:00]  * slangasek waves
[16:00] <sil2100> o/
[16:01] <barry> \o
[16:01] <robru> o~
[16:01] <caribou> ~o
[16:01] <tdaitx> ~o~
[16:02] <slangasek> #startmeeting
[16:02] <meetingology> Meeting started Thu Mar  2 16:02:00 2017 UTC.  The chair is slangasek. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:02] <meetingology> Available commands: action commands idea info link nick
[16:02] <gaughen> o/
[16:02] <bdmurray> the anticipation is killing me
[16:02] <bdmurray> whose on first?
[16:02] <slangasek> [TOPIC] Lightning round
[16:03] <slangasek> $ echo $(shuf -e barry doko bdmurray slangasek caribou infinity sil2100 robru cyphermox tdaitx xnox chiluk mwhudson)
[16:03] <slangasek> sil2100 tdaitx bdmurray infinity doko mwhudson barry slangasek cyphermox xnox caribou chiluk robru
[16:03] <sil2100> Oh my
[16:03] <robru> I win!
[16:03] <gaughen> you won sil2100!
[16:03] <sil2100> - Sick for most of the week, Mon+Tue off, lower productivity
[16:03] <sil2100> - Landing team work, silo coordination
[16:03] <sil2100> - SRU reviews
[16:03] <sil2100> - Publishing kernel SRUs (f*cked up, those were marked as ready invalidly)
[16:03] <sil2100> - Looking at walinuxagent test results, minor tweaks in packaging
[16:03] <sil2100> - Looking into ubuntu-image changelog-for-PR functionality
[16:03] <sil2100> (done)
[16:03] <tdaitx> * Short week: holiday on Monday and Tuesday
[16:03] <tdaitx> = OpenJDK
[16:03] <tdaitx>   * Bug review/test (Debian: #850268, LP: #1314113, LP: #1255821, LP: #1548434, ...)
[16:03] <tdaitx> = Merges
[16:03] <tdaitx>   * open-vm-tools got merged while I was finishing it (investigating xml-security-c/xmlsec1 dependencies)
[16:03] <tdaitx>     - there were 2 open bugs for the merge, LP: #1651608 and LP: #1666430
[16:03] <tdaitx>     - IIRC the former was set on merges ubuntu, now the later is
[16:03] <tdaitx>     - created debian bug to Build-Depends on either libssl1.0-dev|libssl-dev (Debian: #856569) to make backporting easier
[16:03] <tdaitx>     - investigating whether xml-security-c can be replaced by xmlsec1
[16:04] <tdaitx>   * ncurses (ongoing, LP: #1637239)
[16:04] <tdaitx> = OpenJDK 7 (low priority)
[16:04] <tdaitx>   * Retesting Mauve after discussion on its mailing list
[16:04] <tdaitx> = Other
[16:04] <tdaitx>   * Watched Cloud TH newest episode
[16:04] <tdaitx>   * Enjoyed Carnival holidays by setting up new router, organizing my NAS (movies and series), playing Quarriors and City of Horror with friends, all while missing the snow and cold+dry weather
[16:04] <tdaitx> (done)
[16:04] <bdmurray> fixed additional issues with the retracers-cache-restart script
[16:04] <bdmurray> submitted RT to have retracer-charm updated in staging, production
[16:04] <bdmurray> worked with webops regarding retracer memory upgrade
[16:04] <bdmurray> automated cassandra-querier reports, setup apache and vpn access
[16:04] <bdmurray> created snap daemon to clean up old crashes i.e. cronjob
[16:04] <bdmurray> investigated some missing info in snap crashes
[16:04] <bdmurray> added outstanding unattended-upgrades MPs to zesty
[16:04] <bdmurray> sponsored wget patch for X for LP: #1573307
[16:04] <bdmurray> uploaded backuppc fix for X for LP: #1612600
[16:04] <bdmurray> patch piloting
[16:04] <bdmurray> modified sru-report to show uploaders lp usernames
[16:04] <bdmurray> tested subiquity
[16:04] <bdmurray> ✔ done
[16:04] <gaughen> thanks for testing bdmurray!
[16:05] <infinity>  - Working on glibc for zesty
[16:05] <infinity>  - Working on tzadata for $world
[16:05] <infinity>  - Discussions with Steve about minimizing debootstrap set
[16:05] <infinity>  - Emergency archive surgery to revert accidental kernel promotions
[16:05] <infinity>  - Generic SRU/AA tasks
[16:05] <infinity> (done)
[16:05] <slangasek> sil2100: did invalid SRUs actually get published, then?
[16:05] <sil2100> Yes
[16:05] <sil2100> They did
[16:05] <infinity> Yeah, I'm reverting the world now.
[16:06] <doko> - rustc updates for zesty (1.15.1)
[16:06] <doko> - rustc backports for trusty, xenial, yakkety (including cmake, binutils and llvm-3.9 backports)
[16:06] <doko> - boostrapping rustc for ppc64el trusty
[16:06] <doko> - binutils 2.28 release
[16:06] <doko> - packaging of the gcc-7 offload compilers
[16:06] <doko> - Debian bug squashing party at the weekend (in Berlin), meeting rustc maintainer
[16:06] <doko> - some merges
[16:06] <doko> - openjdk-9 update
[16:06] <doko> - binutils SRU (ppc64el)
[16:06] <doko> (done)
[16:06] <barry> i guess we still skip mwhudson
[16:06] <sil2100> That's a lesson for me trying to be over-helpful, but to my defence I must say that I have not known before that I am to double-check the sanity of what the kernel team's automation does
[16:06] <barry> u-i: LP: #1667140; LP: #1625732 (very close, but seeing a very weird difficult to debug failure - anybody wanna help?)
[16:07] <barry> debuntu: alembic import into dpmt from openstack
[16:07] <barry> posted python2.7 regression information to python-dev for caribou
[16:07] <barry> --done--
[16:07] <caribou> barry: thanks for that
[16:07] <barry> caribou: np, there are some good thoughts on the mailing list you might want to follow up on
[16:08] <caribou> barry: sure will
[16:08] <barry> thanks!
[16:09] <chiluk> slangasek ?
[16:10] <slangasek>  * cloud images
[16:10] <slangasek>  * minimizing the smallest Ubuntu (LP: #1640878, LP: #1668847, et al.)
[16:10] <slangasek>  * SRU processing
[16:10] <slangasek>  * proposed-migration hinting/nudging
[16:10] <slangasek> (done)
[16:10] <slangasek> cyphermox:
[16:11] <cyphermox> yeah
[16:11] <cyphermox> - netplan:
[16:11] <cyphermox>   - adding missing STP support
[16:11] <cyphermox>   - fighting spurious autopkgtest failures
[16:11] <cyphermox>   - adding forward-declaration support (request from maas)
[16:11] <cyphermox>   - merge missing MTU support from rharper.
[16:11] <cyphermox> - subiquity:
[16:11] <cyphermox>   - snapping up subiquity
[16:11] <cyphermox>   - maas setup for rescue mode
[16:11] <cyphermox> - zesty:
[16:11] <cyphermox>   - looking at a grub fix for bad firmware behavior in some netboot cases
[16:11] <cyphermox>   - ubiquity slideshow update
[16:11] <cyphermox> - xenial SRUs
[16:11] <cyphermox> turns out a desktop with only 4gb RAM tends to slow down when you run too many VMs on it
[16:11] <cyphermox> (done)
[16:11] <xnox> zlib updates landed (after rebuilding/pushing through adt)
[16:11] <xnox> libodb everything verified and all SRUs landed
[16:11] <xnox> fix failure to boot on a cloud
[16:11] <xnox> review cloud-init changes / scoping for another cloud
[16:11] <xnox> triange all outstanding s390x issues - no NEW bugs
[16:11] <xnox> return to debugging bridge_role primary for bootstack
[16:11] <xnox> triange systemd issues - need to prepare an upload with a few bugfixes for zesty
[16:11] <xnox> ..
[16:11] <slangasek> bdmurray: have you talked with the snappy team about whether they're going to be providing a systemd timers interface?
[16:12] <caribou> BugFix:
[16:12] <caribou> LP #1638695 : Python performance regression in Xenial
[16:12] <caribou>  - Made analysis available, barry send email to python-dev ML
[16:12] <caribou>  - Disabling LTO seems to improve things
[16:12] <caribou>  - Running the benchmarks on another arch could be useful
[16:12] <bdmurray> slangasek: nobody responded to me in #snappy
[16:12] <slangasek> ooh and I need to look at the sru report to find out who's surprising on there
[16:12] <slangasek> bdmurray: hmm :/
[16:12] <caribou>  LP #1654600 : unattended-upgrades breaks shutdown when /var is FS
[16:12] <caribou>  - solution proposed in upstream Debian bug. Will upload to Z & SRU
[16:12] <caribou>  - Identification slowed down by what might be another u-u bug
[16:13] <caribou> Dev:
[16:13] <caribou>  Sosreport 3.3 trusty SRU
[16:13] <caribou>  - Need to FFE for newer upstream release as sos 3.4 is coming shortly
[16:13] <caribou> ☑ Done
[16:13] <bdmurray> caribou: what other u-u bug?
[16:13] <caribou> bdmurray: UnattendedUpgrade::RunOnShutdown doesn't seem to work as the network is off by the time it runs
[16:13] <slangasek> sil2100: yeah, I don't double-check the bug tasks.. that's what their automation is supposed to handle
[16:14] <chiluk> * lp 1647389 - Finally got a smaller reproduction environment put together for this.    Cherrypick of that patch does not apply cleanly, I'm proceeding to work through back-porting/figuring out if there are any other patches that need to be
[16:14] <chiluk> brought in.  I have a feeling there will be at least one more patch required before this is complete.  However, I finally see the light at the end of the tunnel on this one.
[16:14] <chiluk> * Recovered from a disk failure in my raid 5 *(which was also hosting the VM for the above reproducer).
[16:14] <chiluk> * DMB approved my core-dev application this week.  Thanks for that guys.
[16:14] <chiluk> - done -
[16:14] <caribou> bdmurray: unless I don't understand how it owrks
[16:14] <robru> * archive maintenance mentoring from cyphermox
[16:14] <robru> britney
[16:14] <robru> * Email Policy, emails uploaders when package stuck in proposed (in review)
[16:14] <robru> * workaround for Source PPA Policy, groups migration of packages from same bileto ticket (needs review, bug #1648000)
[16:14] <robru> (done)
[16:15] <caribou> bdmurray: I have yet to create the LP: bug
[16:15] <bdmurray> robru: what will happen with stuff already stuck in proposed? will we only get emails about new stickers?
[16:16] <slangasek> bdmurray: hmm I did merge your branch, right?  why does the sru report not look different
[16:16] <robru> bdmurray: the current code as written keeps a cache of what it has and hasn't emailed. the first run will see that it hasn't emailed anything and pump out a giant spam for everything that's been stuck for more than a day. after that it'll settle and only email new things that have been sitting for longer than a day.
[16:17] <slangasek> bdmurray: oh, it does look different, if I both reload and look at my screen
[16:17] <bdmurray> slangasek: did you see the surprising results?
[16:18] <slangasek> bdmurray: do you mean init-system-helpers? :)
[16:18] <bdmurray> slangasek: no, the number of things vorlon has unverified. ;-)
[16:18] <slangasek> oh are there a number of them?
[16:18] <bdmurray> robru: will there be an announcement before the spam event?
[16:18] <slangasek> guess I should do something about those
[16:19] <bdmurray> otherwise somebody might nag you!
[16:19] <slangasek> well I got the nag mail about init-system-helpers, that's why it's verified now ;)
[16:20] <slangasek> robru: could you draft an announcement mail for us to send out before we merge the email policy and make it live?
[16:21] <robru> slangasek:
[16:21] <robru> slangasek: sure. will send to  you for approval
[16:21] <bdmurray> robru: Also will the roll-out be for every release of just zesty?
[16:22] <slangasek> robru: can you stick it in a google doc so we can collaborate?
[16:22] <robru> bdmurray: it would be for all releases
[16:23] <bdmurray> cool
[16:23] <robru> slangasek: should I maybe make it so that it only emails packages that are 1 <= daysold <= 20 or something? to prevent emailing the dozens that are languishing for years?
[16:24] <slangasek> robru: I think we are going to want to do a dry run and see who's getting emailed for what, before we decide; but my sense is that we don't want an upper cap
[16:24] <slangasek> anything else on status?
[16:24] <robru> slangasek: well going forward, all packages would be emailed the day they turn daysold 1. The upper cap would only affect packages that are *already* daysold > 1
[16:25] <slangasek> yes
[16:25] <slangasek> and I think we do want to email the backlog
[16:26] <robru> alright
[16:26] <robru> slangasek: there's no way to do a dry run currently. should I add that?
[16:27] <slangasek> robru: doesn't need merged, but at least for a one-off locally I think we want to see who it /would/ email for what
[16:27] <slangasek> robru: anyway, we can discuss further outside the meeting
[16:27] <slangasek> maybe in the MP :)
[16:27] <slangasek> anything else on status?
[16:27] <robru> slangasek: ok well for a one-off all you have to do is comment out the smtp.send_message and replace it with a self.log(...)
[16:28] <slangasek> right
[16:29] <slangasek> [TOPIC] AOB
[16:29] <slangasek> anything else?
[16:29] <cyphermox> I want more ram?
[16:29] <infinity> You can't have more RAM.
[16:30] <cyphermox> CanadaPost is slow.
[16:30] <barry> i might be sending a long-ish email about this autopkgtest failure i'm seeing.  thoughts, feedback would be very welcome ;)
[16:32] <slangasek> going once...
[16:32] <slangasek> going twice...
[16:32] <slangasek> #endmeeting
[16:32] <meetingology> Meeting ended Thu Mar  2 16:32:41 2017 UTC.
[16:32] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2017/ubuntu-meeting.2017-03-02-16.02.moin.txt
[16:32] <slangasek> thanks, all!
[16:33] <barry> thanks!
[16:35] <caribou> thanks!


[06:05] <jibel> Good morning
[06:09] <duflu> Morning jibel
[06:16] <jibel> hi duflu
[06:33] <seb128> goood morning desktopers
[06:37] <duflu> Morning seb128
[06:39] <seb128> hey duflu , how are you?
[06:40] <duflu> seb128, I'm OK. You?
[06:40] <seb128> I'm alright!
[06:51] <oSoMoN> good morning desktoppers
[06:51] <duflu> Hi oSoMoN
[06:53] <oSoMoN> hey duflu
[06:56] <jibel> salut oSoMoN seb128
[06:56] <seb128> lut oSoMoN, jibel
[06:57] <oSoMoN> salut jibel, seb128
[07:07] <ricotz> good morning
[07:07] <oSoMoN> good morning ricotz
[07:12] <duflu> Hi ricotz
[08:00] <didrocks> good morning
[08:00] <jibel> salut didrocks
[08:04] <didrocks> hey jibel
[08:11] <duflu> Morning didrocks
[08:13] <marcustomlinson> morning all
[08:16] <didrocks> hey duflu, marcustomlinson
[08:17] <duflu> Hi marcustomlinson
[08:40] <seb128> hey ricotz didrocks marcustomlinson , how are you?
[08:43] <didrocks> salut seb128, fatigué mais ça va :)
[08:43] <didrocks> et toi ?
[08:49] <seb128> hum, I had connected the wrong power plug, the laptop battery went flat and annoyingly it doesn't power on again before a few minutes of charge when then happens
[09:04] <Laney> yo
[09:06] <duflu> sup Laney
[09:06] <duflu> ?
[09:06] <seb128> hey Laney
[09:19] <Laney> hey duflu seb128
[09:31] <marcustomlinson> hey duflu didrocks seb128 Laney
[09:31] <marcustomlinson> seb128: doing ok thanks, you?
[09:37] <didrocks> HEY marcustomlinson!
[09:41] <jibel> good morning marcustomlinson
[09:41] <jibel> and Laney
[09:45] <didrocks> oh, and Laney, sure!
[09:46] <Laney> lol
[09:46]  * Laney feels wanted
[09:46] <Laney> hi marcustomlinson jibel didrocks
[09:53] <didrocks> noooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
[09:53] <didrocks> no more kiki in the archive since focal :(
[09:59] <Laney> 's delivery service?
[10:01] <didrocks> the regexp tester!
[10:02] <didrocks> https://i.stack.imgur.com/7smzb.png
[10:06] <KGB-0> mutter pristine-tar d58def2 Simon McVittie mutter_3.38.2.orig.tar.xz.delta mutter_3.38.2.orig.tar.xz.id * pristine-tar data for mutter_3.38.2.orig.tar.xz * https://deb.li/3DKuV
[10:06] <KGB-0> mutter upstream/latest fefbd3e Simon McVittie * pushed 58 commits * https://deb.li/Bkm1
[10:07] <KGB-0> mutter tags 52f001c Simon McVittie upstream/3.38.2 * Upstream version 3.38.2 * https://deb.li/3TdQN
[10:07] <KGB-0> gnome-shell pristine-tar 38dd750 Simon McVittie gnome-shell_3.38.2.orig.tar.xz.delta gnome-shell_3.38.2.orig.tar.xz.id * pristine-tar data for gnome-shell_3.38.2.orig.tar.xz * https://deb.li/GGTU
[10:07] <KGB-0> gnome-shell upstream/latest 2f6a0c7 Simon McVittie * pushed 46 commits * https://deb.li/35kPF
[10:07] <KGB-0> gnome-shell tags 2c8868c Simon McVittie upstream/3.38.2 * Upstream version 3.38.2 * https://deb.li/PkBi
[10:17] <KGB-0> gnome-shell-extensions pristine-tar a595c5b Simon McVittie gnome-shell-extensions_3.38.2.orig.tar.xz.delta gnome-shell-extensions_3.38.2.orig.tar.xz.id * pristine-tar data for gnome-shell-extensions_3.38.2.orig.tar.xz * https://deb.li/NaiI
[10:17] <KGB-0> gnome-shell-extensions upstream/latest 9f25047 Simon McVittie * pushed 16 commits * https://deb.li/i3QcA
[10:18] <KGB-0> gnome-shell-extensions upstream/3.38.x 9f25047 Simon McVittie * pushed 16 commits (first 5 follow) * https://deb.li/2aWF
[10:18] <KGB-0> gnome-shell-extensions upstream/3.38.x 584016c Sergio Costas extensions/window-list/extension.js * window-list: Honor changes in skip-taskbar property * https://deb.li/3HQ81
[10:18] <KGB-0> gnome-shell-extensions upstream/3.38.x 1276a88 Florian Müllner extensions/workspace-indicator/extension.js * workspace-indicator: Use custom layout manager for thumbnails * https://deb.li/86Ld
[10:18] <KGB-0> gnome-shell-extensions upstream/3.38.x ed81650 Florian Müllner extensions/window-list/workspaceIndicator.js * window-list: Use custom layout manager for thumbnails * https://deb.li/3Nr6V
[10:18] <KGB-0> gnome-shell-extensions upstream/3.38.x 435879c Florian Müllner extensions/workspace-indicator/extension.js * workspace-indicator: Adjust to overview changes * https://deb.li/REZC
[10:18] <KGB-0> gnome-shell-extensions upstream/3.38.x e734fcb Florian Müllner extensions/window-list/workspaceIndicator.js * window-list: Adjust to overview changes * https://deb.li/3zAoG
[10:31] <seb128> didrocks, candidate for a snap instead? ;-)
[10:37] <didrocks> seb128: you volunteering? :p
[10:41] <seb128> not really no :p
[13:05] <dust> in the snap version of thunderbird it isnt possible to add a calendar from a local file... at creation there is no asking which file and its also not possible to edit the address of the file
[13:42] <oSoMoN> dust, would you mind filing a bug at https://bugs.launchpad.net/ubuntu/+source/thunderbird/+filebug ?
[14:20] <dust> oSoMoN, done
[14:23] <oSoMoN> excellent, thanks
[15:48] <seb128> is dpkg-gensymbols automatically writting an updated .symbols in the deb adding missing symbols with the current version?
[15:50] <Laney> not as far as I know, but it's got various levels of error reporting if you see the -c option
[15:54] <seb128> I'm a bit confused by that
[15:57] <seb128> https://paste.ubuntu.com/p/gTY5m5yw6c/
[15:57] <seb128> and rules doesn't have anything special
[15:57] <seb128> override_dh_makeshlibs:
[15:57] <seb128> 	dh_makeshlibs --add-udeb=libevdev2-udeb
[15:57] <seb128> no -c<level> or anything
[15:58] <seb128> also I learnt about (symver) in symbols today!
[16:01] <Laney> does the build log print a diff?
[16:01] <seb128> yes
[16:02] <seb128> https://launchpadlibrarian.net/509410962/buildlog_ubuntu-groovy-amd64.libevdev_1.9.1+dfsg-1ubuntu0.1_BUILDING.txt.gz
[16:02] <seb128> dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below
[16:02] <Laney> then yeah I think that is normal, the -c level controls when that fails and -c1 is the default which doesn't fail on new symbols
[16:02] <Laney> make it -c4
[16:03] <Laney> imho
[16:03] <seb128> right, I was just surprised that it ended up working
[16:03] <seb128> my review comment was 'libinput isn't going to have the right depends'
[16:03] <seb128> but he pointed out that it does
[16:03] <seb128> and he's right
[16:03] <seb128> the updates symbols ends up in DEBIAN/symbols
[16:03] <Laney> yeah but with the entire current version
[16:04] <seb128> right
[16:04] <seb128> sorry if I was not clear
[16:04] <Laney> np
[16:04] <seb128> I know -c4 would fail and is the right thing to do to make sure we update
[16:04] <seb128> and that he forgot to update the .symbols
[16:04] <seb128> I was just trying to understand why it worked
[16:05] <seb128> I guess dpkg-gensymbols does auto writting symbols with the current revision in DEBIAN/symbols even if they are not listed in debian/libname.symbols
[16:05] <seb128> which makes sense
[16:05] <KGB-0> gnome-shell-extensions tags e2f6748 Simon McVittie upstream/3.38.2 * Upstream version 3.38.2 * https://deb.li/3onCj
[16:05] <seb128> -c4 should really be the default btw :p
[16:06] <Laney> indeed
[16:30] <seb128> oSoMoN, is mozilla doing anything smart to turn a patch from bugzilla to a phabricator merge review or is that some extra steps?
[16:31] <oSoMoN> seb128, I'm not aware that they convert patch files to phabricator reviews, do they?
[16:32] <seb128> oSoMoN, I'm asking, I got lost in the documentation
[16:32] <oSoMoN> afaik they require you to submit your changes through moz-phab
[16:32] <seb128> oSoMoN, k, I'm reading mercurial stuff on https://developer.thunderbird.net/thunderbird-development/fixing-a-bug/using-mercurial-queues and attached a patch to bugzilla
[16:32] <seb128> the that doesn't mention much about phabricator though
[16:33] <seb128> https://developer.thunderbird.net/thunderbird-development/fixing-a-bug states
[16:33] <seb128> 'If everything looks good, you can access the selected bug in Bugzilla and click on the Attach File link located above the first comment.'
[16:33] <seb128> I wonder if that's outdated documentation or if thunderbird doesn't use phabricator
[16:33] <seb128> oh well, I will see what they say on the bug
[16:34] <oSoMoN> ah, so either the thunderbird team uses a different process than the firefox folks, or their documentation is outdated
[16:34] <hellsworth> haha i said good morning desktopers over on a gnome channel and wondered why i didn't hear from anyone :)
[16:34] <seb128> https://bugzilla.mozilla.org/show_bug.cgi?id=1680527
[16:34] <seb128> hey Heather, how are you?
[16:34] <hellsworth> hey seb128 I'm good thanks :) you ?
[16:34] <seb128> I'm alright!
[16:35] <oSoMoN> seb128, everytime I get to read again the mozilla docs for contributing changes, I find it daunting and unnecessarily complex
[16:36] <oSoMoN> I wonder how many good contributions get lost because of that high barrier to entry
[16:36] <oSoMoN> good morning hellsworth
[16:37] <hellsworth> hi there oSoMoN
[16:38] <oSoMoN> seb128, IIRC in the past when I or others submitted raw patch files, we were asked to do it properly using phabricator, but I guess that was for firefox only, so maybe thunderbird devs are more permissive?
[16:39] <seb128> oSoMoN, well, it's submitted like that so let's see what they ask next!
[16:43] <oSoMoN> yeah, wait and see
[17:37] <KGB-2> orca pristine-tar 2acedf6 Samuel Thibault orca_3.38.1.orig.tar.xz.delta orca_3.38.1.orig.tar.xz.id * pristine-tar data for orca_3.38.1.orig.tar.xz * https://deb.li/3u5Ue
[17:38] <KGB-2> orca upstream/stable fef70f2 Samuel Thibault * pushed 7 commits (first 5 follow) * https://deb.li/f5RD
[17:38] <KGB-2> orca upstream/stable ad04be6 Joanmarie Diggs README.md configure.ac * Post-release version bump * https://deb.li/M7OC
[17:38] <KGB-2> orca upstream/stable 5cdd8fc Henrique Machado Campos po/pt_BR.po * Update Brazilian Portuguese translation * https://deb.li/i41mG
[17:38] <KGB-2> orca upstream/stable 4f7d984 Juliano de Souza Camargo po/pt.po * Update Portuguese translation * https://deb.li/77Dl
[17:38] <KGB-2> orca upstream/stable e4d292f Simon Long src/orca/formatting.py * Add newRadioButtonGroup to formatting for unfocused radio button * https://deb.li/3F1sI
[17:38] <KGB-2> orca upstream/stable 89d4148 Joanmarie Diggs src/orca/speech_generator.py * Fix crash when generating speech for childless math element * https://deb.li/aCzE
[17:39] <KGB-2> orca tags b0b9f32 Samuel Thibault upstream/3.38.1 * Upstream version 3.38.1 * https://deb.li/3eWnz


[10:31] <LocutusOfBorg> hi, can anybody pretty-please look at virtualbox-lts-vivid?
[10:31] <LocutusOfBorg> I  would be happy to answer to any question you might have :)
[11:00] <apw> LocutusOfBorg, (not that i can approve it, but) is there a reason it has to be a seaparate package, that the support for the vivid kernels cannot be folded into the original ?
[11:00] <LocutusOfBorg> apw, https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1424769
[11:01] <ubot5`> Launchpad bug 1424769 in virtualbox (Ubuntu) "virtualbox-guest-x11 uninstallable with mesa-lts-utopic" [High,Triaged]
[11:01] <LocutusOfBorg>   virtualbox-guest-x11 : Depends: xorg-video-abi-15
[11:01] <LocutusOfBorg>                         Depends: xserver-xorg-core (>= 2:<IP_ADDRESS>2)
[11:01] <LocutusOfBorg> so I had to add a new package specially built against the -lts-vivid package
[11:01] <LocutusOfBorg> because it changed ABI, so it isn't installable
[11:01] <LocutusOfBorg> and I'm talking about the guest- package
[11:02] <LocutusOfBorg> not the host, this is why I'm building only virtualbox-guest-*, and so on
[11:02] <apw> LocutusOfBorg, ahh against xorg-lts-vivid ... then that makes perfect sense, thank you
[11:05]  * LocutusOfBorg was hoping about and answer like "hey dumb maintainer, there is this bit that fixes all the mess for you" :)
[11:06] <LocutusOfBorg> I spent months in debugging this issue, and for sure I would like to avoid having to maintain a new package :(
[11:30] <apw> we have an initramfs-tools siting in New, which it might be prudent to leave there until (say) Monday as there is also a kernel in flight
[11:59] <cjwatson> slangasek: launchpad-buildd isn't entirely trivial to set up, but it's indeed perhaps better to not have a script getting gradually staler.
[14:41] <rbasak> Is it possible to have one architecture binary package in main, but the others in universe?
[14:41] <rbasak> We're wondering in relation to DPDK and what commitment we want to make for support in main for ppc64el.
[14:42] <cjwatson> rbasak: It is technically possible in Launchpad, but makes various reports get upset and I think it's a bad idea.
[14:43] <cjwatson> rbasak: As general advice I would suggest not relying solely on the main/universe distinction to express supportedness.
[14:46] <rbasak> cjwatson: OK. Any advice on this one please? ppc64el support isn't upstream but there is a patch. We definitely want dpdk in main for amd64 for ovs, but also don't want to block anyone from having ppc64el working in dpdk but aren't sure we (Canonical) want to commit to support that (considering options).
[14:47] <cjwatson> AIUI Canonical is perfectly capable of having its support guarantees be out-of-band with the archive
[14:47] <cjwatson> Perhaps talk to STS?
[14:47] <rbasak> OK, thanks!
[14:48] <cjwatson> I think the security team still want everything in main to be supportable, but it seems quite unlikely to end up with an architecture-specific vulnerability.
[17:11] <bdmurray> slangasek: I'm not seeing Supported info for packages any more in Xenial.
[17:31] <slangasek> cjwatson, infinity: ^^ so Supported seems to have disappeared from the xenial packages files, about the time I merged the change to make xenial == trusty... where does the output of this get logged?
[17:31] <cjwatson> I didn't deploy it until yesterday, FWIW
[17:32] <cjwatson> anyway, try pepo:/srv/launchpad.net/production-logs/lp_publish/publish-ftpmaster.log
[17:33] <cjwatson> Laney: speaking of which, rsync appstream.ubuntu.com::appstream/ -> "@ERROR: Unknown module 'appstream'" - looks like your rsync fragment has somehow ended up not in /etc/rsyncd.conf
[17:33] <cjwatson> Running maintenance-check for xenial...  done
[17:33] <cjwatson> slangasek: ^- that's all it says I'm afraid
[17:34] <Laney> cjwatson: ah FFS
[17:34] <Laney> cjwatson: I just deployed the nrpe thing which exposes things over rsync, bet that clobbered it
[17:36] <cjwatson> slangasek: ah, in fact /srv/launchpad.net/ubuntu-archive/ubuntu-germinate/_maintenance-check.xenial.stderr
[17:38] <cjwatson> oh god this is a fractal of wrong
[17:39] <teward> with regards to snappy core, how is that affected by the 15.04 EOL?
[17:39] <teward> s/core//
[17:41] <cjwatson> slangasek: I think I have bodged this to not be entirely wrong.  lp:ubuntu-archive-publishing r77
[17:41] <cjwatson> bdmurray: ^-
[17:41] <cjwatson> deployed, hopefully will recover in a bit
[17:42] <cjwatson> slangasek: (the wrongness wasn't of your origin, you just tickled it by adding ppc64el/s390x)
[17:42] <slangasek> heh ok
[17:42] <slangasek> cjwatson: thanks :)
[17:42] <slangasek> fractal of wrong> I didn't *think* I was writing python...
[17:42] <slangasek> er, I mean, php
[17:43] <bdmurray> cjwatson: okay, thanks
[18:08] <Laney> cjwatson: should be back
[18:14]  * cjwatson fixes lp:ubuntu-archive-publishing harder
[18:14] <cjwatson> Laney: thanks
[18:15] <Laney> I should document the right place to get that charm from so the next person doesn't have to feel around in the dark
[18:30] <slangasek> infinity, cjwatson: should our d-i stop build-depending on cramfsprogs? (obsolete, removed in Debian)
[18:32] <slangasek> and the build-dep is powerpc only, which is why I ask you two
[18:36] <infinity> slangasek: I'd have to look at why it thinks it needs the build-dep, but I'm willing to believe it's not being used.
[18:37] <slangasek> infinity: ./build/config/powerpc/powerpc/floppy/net-drivers.cfg, ./build/config/powerpc/powerpc/floppy/cd-drivers.cfg seems to use it, are you building powerpc floppies? :)
[18:37] <infinity> slangasek: Hrm.  Or maybe it does, indeed, think it's being used.  But it certainly shouldn't need it.
[18:38] <infinity> slangasek: We're not building floppies, but I'm not convinced that "floppy" means "floppy" in that context, given the filenames.  Will have to trace through a little bit.
[18:54] <xnox> slangasek, common, we still use punchcards too, and tape =)
[18:54] <xnox> floppy is so advanced!
[19:01] <cjwatson> slangasek: fine by me if we track down any associated debris
[22:41] <cjwatson> bdmurray,slangasek: I've checked and there are in fact Supported fields for xenial now, and I think correct for the recent changes
[22:41] <cjwatson> (only checked very lightly though)
[22:57] <slangasek> cjwatson: great, thanks!


[13:04] <lool> I'm assuming no meeting today
[13:04] <lool> will cancel invite
[13:11] <ogra_> yeah
[13:11]  * ogra_ thinks we are fine without
[15:57] <jamespage> o/
[15:59] <zul> hi ho
[15:59] <roaksoax> zul: hi santa!
[15:59] <roaksoax> i mean chuck!
[15:59] <zul> roaksoax:  you are going to be in a rude shock then
[16:00] <roaksoax> zul: your "hi ho" reminded me to ho ho ho (santa)
[16:00] <zul> roaksoax:  oh...i got it from snow white
[16:00] <jamespage> ok - lets start
[16:00] <jamespage> in 1 min
[16:01] <jamespage> #startmeeting ubuntu-server-team
[16:01] <meetingology> Meeting started Tue Oct 15 16:02:04 2013 UTC.  The chair is jamespage. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:01] <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:02] <jamespage> #topic Review ACTION points from previous meeting
[16:02] <jamespage> smoser look at / assign bug 1206872
[16:02] <jamespage> well its fixed - so done
[16:02] <smoser> good.
[16:02] <jamespage> zul look at bug 1199791 1223010
[16:02] <jamespage> bug 1223010
[16:02] <jamespage> so zul - how about those bugs? gonna make saucy?
[16:02] <jamespage> :-)
[16:03] <zul> sure!
[16:03]  * zul continues studying oauth
[16:04] <jamespage> zul, do we need to fix bug 1223010 for saucy?
[16:04] <zul> jamespage:  no
[16:04] <jamespage> ok - so nothing critical for release then - good
[16:04] <jamespage> zul to look at problem in python-cliff launchpad branch
[16:04] <jamespage> package import problem I guess
[16:05] <jamespage> roaksoax to look at bug 1227353
[16:05] <jamespage> roaksoax, hows that looking?
[16:05] <roaksoax> jamespage: nothing new to report, been dealinig with current release
[16:05] <jamespage> ah - fixed for saucy I see
[16:05] <adam_g> jamespage, might want this on our tracking list, was  having trouble targetting it https://bugs.launchpad.net/cloud-archive/+bug/1238915
[16:06] <jamespage> smoser, ^^
[16:06] <smoser> oh. well that would be serious.
[16:06] <smoser> suck.
[16:07] <smoser> i'll triage and handle.
[16:07] <jamespage> smoser, thanks
[16:07] <jamespage> I nominated for saucy
[16:07] <jamespage> all done on actions - good
[16:07] <jamespage> moving on
[16:07] <jamespage> #topic Saucy Development
[16:08] <jamespage> release on thurday just in case anyone had not noticed...
[16:08] <jamespage> #link https://wiki.ubuntu.com/SaucySalamander/ReleaseSchedule
[16:08] <jamespage> #subtopic Release Bugs
[16:08] <jamespage> #link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-s-tracking-bug-tasks.html#server
[16:08] <jamespage> few things kicking around
[16:08] <jamespage> bug 1236439
[16:09] <jamespage> is going to bite upgrades from grizzly to havana - upstream working on that
[16:09] <jamespage> smb; bug 1208455
[16:09] <jamespage> any updates?
[16:09] <smb> no, sorry
[16:10] <jamespage> bug 1210054 is done
[16:10] <jamespage> bug 1223010
[16:10] <jamespage> we poked zul about already
[16:10] <jamespage> bug 1156932
[16:11] <jamespage> low priority - we'll hang with that one
[16:11] <jamespage> bug 1239156
[16:11] <jamespage> keystone and horuzon are making there way through proposed right now
[16:11] <jamespage> all other projects have rc2'ed as of now
[16:11] <jamespage> (apart from swift which I don't expect to)
[16:11] <jamespage> #subtopic Blueprints
[16:11] <jamespage> #link http://status.ubuntu.com/ubuntu-s/group/topic-s-servercloud-overview.html
[16:12] <jamespage> I had a run through blueprints earlier today and postponed/done'ed a load of wi's
[16:12] <jamespage> smoser, https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-cloud-init
[16:12] <jamespage> has the 0.7.3 release been completed yet?
[16:12] <smoser> will sort out now.
[16:12] <jamespage> other than that looks OK
[16:12] <jamespage> good
[16:13] <jamespage> roaksoax, https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-charms-ha-v2
[16:13] <smoser> 0.7.3 is done. 0.7.4 is to be done
[16:13] <jamespage> a few TODO's and BLOCKED still to complete - lets catchup next week specifically on the rabbitmq active/active stuff
[16:13] <jamespage> I think we can move forwards on that now
[16:14] <jamespage> smoser, https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-simplestreams
[16:14] <jamespage> just need updates?
[16:14] <jamespage> zul, https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-qa
[16:14] <zul> ill clean that up today
[16:15] <roaksoax> jamespage: adam_g was looking at that iirc
[16:15] <smoser> updated abovce.
[16:15] <jamespage> there is a whole load of stuff that is not going to get done this release - lets deffer and get it running early next week
[16:15] <roaksoax> (rabbitmq)
[16:15] <jamespage> roaksoax, ack
[16:15] <jamespage> adam_g, https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-charms
[16:15] <jamespage> most of the redux work is now landing - I expect we will sprint some time next week on feature catchup
[16:16] <jamespage> evilnick is not around:
[16:16] <jamespage> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-docs
[16:16] <jamespage> zul, https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-hypervisor
[16:16] <jamespage> a few things to test still but looking OK
[16:16] <jamespage> anyway
[16:16] <zul> ditto
[16:17] <jamespage> I think things look in pretty good shape - final run now :-)
[16:17] <jamespage> matsubara is picking up the final maas testing for saucy release
[16:17] <matsubara> yep, I should have an update for you today jamespage
[16:18] <jamespage> if poss I'd like everyone else to download and iso and make sure no-one changed the installer background to 'wheres chuck' while we where not looking
[16:18] <matsubara> (and hopefully no more nagging before the release :-)
[16:18] <jamespage> matsubara, w00t!
[16:18] <matsubara> I mean, release team nagging you about the tests
[16:18] <jamespage> #topic Server & Cloud Bugs (caribou)
[16:18] <caribou> I'm here
[16:18] <jamespage> caribou, all yours
[16:18] <caribou> well, one bug that I opened : bug 1239758
[16:19] <caribou> mostly to raise your attention, I see that arosales has commented already
[16:19] <caribou> I'll provide the log & keep investigating
[16:19] <caribou> then one question regarding issue with openstack specific charms :
[16:19] <caribou> how do we deal with bug reporting on those ?
[16:19] <jamespage> launchpad.net/charms please
[16:20] <jamespage> you can report bugs against any of the charms
[16:20] <caribou> ok, noted. We have an upcoming one on hacluster
[16:20] <jamespage> or are you refering to the new python-redux branches?
[16:20] <jamespage> (most of which are merged now anyway)
[16:20] <roaksoax> caribou: i tested that and I could not reproduce! did you see my comments?
[16:20] <caribou> jamespage: not specifically
[16:20] <jamespage> ack
[16:21] <jamespage> caribou, well anyways, new versions are landing this week that support havana as well
[16:21] <caribou> roaksoax: yeah a minute ago. I can reproduce it systematically.
[16:21] <jamespage> caribou, all done?
[16:21] <caribou> yep, I'm all good
[16:21] <jamespage> #topic Weekly Updates & Questions for the QA Team (psivaa)
[16:21] <jamespage> or is that plars?
[16:21] <psivaa> No updates from us for this week
[16:21] <plars> jamespage: one thing
[16:21] <jamespage> psivaa, feel free to hassle me about smoke test failures and ISO testing this week btw
[16:21] <plars> jamespage: would someone be up to help testing maas again for the release?
[16:22] <jamespage> plars, matsubara is in the hotseat for that work
[16:22] <plars> jamespage: matsubara: awesome, thanks!
[16:22] <matsubara> np
[16:22] <jamespage> okay
[16:22] <jamespage> #topic Weekly Updates & Questions for the Kernel Team (smb)
[16:22] <smb> Nothing to report (beyond many still unpacked boxes).
[16:23] <jamespage> smb, which reminds me - I need to log a bug about nested KVM virt that I see with 3.8/3.11/3.2
[16:23] <jamespage> I love a good kernel stack
[16:23] <jamespage> :-)
[16:23] <jamespage> #topic Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak)
[16:23] <rbasak> No updates from me. Any questions?
[16:23] <jamespage> rbasak, anything from the world of low-powered server devices we need to know?
[16:23] <jamespage> guess not
[16:24] <jamespage> :-)
[16:24] <jamespage> #topic Ubuntu Server Team Events
[16:24] <jamespage> so... Openstack summit in 2.5 weeks time - a few faces will be attending
[16:24] <jamespage> a few Canonical folks out next week sprinting but I think we'll still try to have a meeting
[16:25] <jamespage> anything else anyone wants to raise?
[16:25] <arosales> reminder to get your charm championship entires in.
[16:25] <jamespage> ...
[16:25] <jamespage> ..
[16:25] <jamespage> .
[16:25] <jamespage> oh - good one
[16:25] <arosales> #link https://juju.ubuntu.com/charm-championship
[16:25] <jamespage> $10k per category up for grabs!
[16:25] <jamespage> #topic Open Discussion
[16:25] <jamespage> I have something
[16:25] <jamespage> welcome to gaughen!
[16:26] <gaughen> thanks jamespage!
[16:26] <arosales> welcome gaughen !
[16:26] <jamespage> gaughen has just joined the Canonical Server Team as Engineering Manager!
[16:26] <jamespage> anything else anyone wants to raise?
[16:27]  * jamespage adds gaughen to the meeting chair rota list :-)
[16:27] <jamespage> #topic Announce next meeting date and time
[16:27] <gaughen> uh oh
[16:27] <jamespage> +7 days same time same place
[16:27] <jamespage> 22nd I make that
[16:27] <jamespage> 1600 UTC
[16:28] <jamespage> #endmeeting
[16:28] <meetingology> Meeting ended Tue Oct 15 16:28:16 2013 UTC.
[16:28] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-10-15-16.02.moin.txt
[16:28] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-10-15-16.02.html
[16:28] <arosales> thanks for charing jamespage
[16:28] <jamespage> np
[17:00] <meetingology> Meeting started Tue Oct 15 17:00:19 2013 UTC.  The chair is jsalisbury. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[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] <jsalisbury> ##
[17:00] <jsalisbury> ##
[17:00] <jsalisbury> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Saucy
[17:00] <ppisati> o/
[17:00] <bjf> o/
[17:00] <sconklin> o/
[17:00] <henrix> o/
[17:00] <sforshee> o/
[17:00] <cking> o/
[17:00] <rtg> o/
[17:00] <ogasawara> o/
[17:00] <jsalisbury> [TOPIC] ARM Status (ppisati)
[17:00] <ppisati> S/master-next: fixes for the SATA bus present on the imx6 board were
[17:00] <ppisati> committed, while support for a new imx6-variant (wandboard) is under
[17:00] <ppisati> investigation.
[17:00] <ppisati> ..
[17:01] <jsalisbury> [TOPIC] Release Metrics and Incoming Bugs (jsalisbury)
[17:01] <jsalisbury> Release metrics and incoming bug data can be reviewed at the following link:
[17:01] <jsalisbury> [LINK] http://people.canonical.com/~kernel/reports/kt-meeting.txt
[17:01] <jsalisbury> ..
[17:01] <jsalisbury> [TOPIC] Milestone Targeted Work Items (ogasawara)
[17:01] <ogasawara> [LINK] https://launchpad.net/~canonical-kernel-distro-team/+upcomingwork
[17:01] <ogasawara> [LINK] http://status.ubuntu.com/ubuntu-s/canonical-kernel-distro-team.html
[17:01] <ogasawara> || apw       || foundations-1305-arm64-bringup     || 2 work items ||
[17:01] <ogasawara> ..
[17:01] <jsalisbury> [TOPIC] Status: Saucy Development Kernel (ogasawara)
[17:01] <ogasawara> We are ~2 days away from 13.10's Final Release.  The kernel remains
[17:01] <ogasawara> frozen and we do not anticipate any further uploads before release.  All
[17:01] <ogasawara> patches coming in at this time are being queued for SRU.
[17:01] <ogasawara> -----
[17:01] <ogasawara> Important upcoming dates:
[17:01] <ogasawara> [LINK] https://wiki.ubuntu.com/SaucySalamander/ReleaseSchedule
[17:02] <ogasawara> Thurs Oct 17 - 13.10 Release (~2 days away)
[17:02] <ogasawara> ..
[17:02] <jsalisbury> [TOPIC] Status: CVE's
[17:02] <jsalisbury> == 2013-10-15 ==
[17:02] <jsalisbury> The current CVE status can be reviewed at the following link:
[17:02] <jsalisbury> http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html
[17:02] <jsalisbury> ..
[17:02] <jsalisbury> [TOPIC] Status: Stable, Security, and Bugfix Kernel Updates - Raring/Quantal/Precise/Lucid (bjf/henrix/sconklin)
[17:02] <bjf> Status for the main kernels, until today (Oct. 15):
[17:02] <bjf>   *   Lucid - Verification and Regression Testing
[17:02] <bjf>   * Precise - Verification and Regression Testing
[17:02] <bjf>   * Quantal - Verification and Regression Testing
[17:02] <bjf>   * Raring  - Verification and Regression Testing
[17:02] <bjf> Current opened tracking bugs details:
[17:02] <bjf>   * http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html
[17:02] <bjf> For SRUs, SRU report is a good source of information:
[17:02] <bjf>   * http://people.canonical.com/~kernel/reports/sru-report.html
[17:02] <bjf> ..
[17:03] <jsalisbury> [TOPIC] Open Discussion or Questions? Raise your hand to be recognized (o/)
[17:03] <jsalisbury> Thanks everyone
[17:03] <jsalisbury> #endmeeting
[17:03] <meetingology> Meeting ended Tue Oct 15 17:03:40 2013 UTC.
[17:03] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-10-15-17.00.moin.txt
[17:03] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-10-15-17.00.html
[17:03] <sconklin> thanks jsalisbury!
[17:03] <cking> blink
[19:38] <costales> Hi everyone! :)
[19:41] <pleia2> o/
[19:42] <jose> hey guys! we're starting in 20mins
[19:50] <costales> Welcome to your first meeting as council jose, skellat! :D
[19:50] <jose> :)
[19:50] <jose> 10mins to go
[19:59]  * skellat waits for the meeting to start
[20:00] <jose> #startmeeting LoCo Council October Meeting
[20:00] <meetingology> Meeting started Tue Oct 15 20:00:14 2013 UTC.  The chair is jose. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[20: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
[20:00] <costales> Let's go! :)
[20:00] <jose> #voters costales skellat SergioMeneses PabloRubianes
[20:00] <meetingology> Warning: Nick not in channel: PabloRubianes
[20:00] <meetingology> Current voters: PabloRubianes SergioMeneses costales skellat
[20:00] <jose> #voters costales skellat SergioMeneses PabloRubianes jose
[20:00] <meetingology> Current voters: PabloRubianes SergioMeneses costales jose skellat
[20:00] <jose> #chair costales skellat SergioMeneses PabloRubianes jose
[20:00] <meetingology> Warning: Nick not in channel: PabloRubianes
[20:00] <meetingology> Current chairs: PabloRubianes SergioMeneses costales jose skellat
[20:00] <jose> so, let's check the agenda
[20:01] <phillw> lubuntu meeting will be held on #lubuntu-offtopic, I'll kill the person who double booked the room later!
[20:01] <jose> #topic California LoCo Team Re-Verification
[20:01] <pleia2> o/
[20:01] <jose> pleia2: you're the team contact, right?
[20:01] <pleia2> I am
[20:02] <costales> Hi pleia2 :) Good luck!
[20:02] <pleia2> unfortunately due to timezones it's the middle of a weekday california time so everyone else is work/schooling right now
[20:02] <pleia2> (I'm on my lunch break :))
[20:02] <jedijf> yay pleia2
[20:02]  * jedijf has your back
[20:02] <costales> bon appetit!
[20:02] <pleia2> https://wiki.ubuntu.com/CaliforniaTeam/VerificationApplication2013
[20:03] <jose> checking that now
[20:03] <costales> pleia2: Amazing amount of Ubuntu Hours! It's lovely to see how active you are!
[20:04] <jose> the same I wanted to say, it's great to see that amount of activity
[20:04] <pleia2> we really like ubuntu hours :)
[20:04] <jose> may I ask, how many people show up around those?
[20:04] <pleia2> a lot of us are pretty busy, so it works out well
[20:04] <pleia2> I run the SF one, we tend to have 4-10 each time
[20:04] <costales> How does your team get people involved in running events?
[20:05] <SergioMeneses> hi guys
[20:05] <pleia2> we start folks off by getting them to do ubuntu hours, then recruit them to help out with bigger events like the southern california linux expo where we have ubucon and a booth each year
[20:05]  * SergioMeneses hugs pleia2
[20:05] <costales> pleia2: great :)
[20:05]  * pleia2 hugs SergioMeneses
[20:06] <SergioMeneses> that is great!
[20:06] <skellat> pleia2: As a minor point, would it be possible to fix California's naming on LP to be in line with the faceted team naming standard for US teams?  See: https://wiki.ubuntu.com/LoCoTeamHowto#For_the_United_States
[20:06] <pleia2> skellat: we were told we could keep it since it's legacy
[20:06] <costales> I see a really friendly team in the pictures :)
[20:06] <SergioMeneses> pleia2, I want to know if you have problems in your team or something that you will share with us :)
[20:06] <pleia2> we put it on a lot of our printed materials and things so switching now would be really painful for the team
[20:06] <skellat> pleia2: I can live with that then.
[20:07] <jose> we can make an exception
[20:07] <skellat> We'll need to update our guidelines to take that into account
[20:07] <skellat> It's a truly minor thing though
[20:07] <costales> yes skellat ;)
[20:07] <pleia2> SergioMeneses: not really, always looking for more folks to be active but we do pretty well
[20:07] <jose> any more questions?
[20:07] <skellat> o/
[20:07] <jose> go for it
[20:08] <skellat> pleia2: What can we do as LoCo Council to serve Ubuntu California?  How can we enable you, equip you, or otherwise make life easier for you at this time?  How may we serve you best?
[20:08] <pleia2> skellat: I think we're doing ok :) I know where to find you
[20:09] <jose> should we move on to voting, then?
[20:09] <skellat> I'm agreeable to that.
[20:09] <costales> It's OK for me :)
[20:09] <SergioMeneses> pleia2, we are starting with a new process of verification, do you have comments about it? something to share about your experience working on it?
[20:10] <pleia2> SergioMeneses: it feels identical to reapproval ;)
[20:10] <costales> hahaha
[20:10] <skellat> With luck that will change over time.
[20:10] <pleia2> having the loco team portal helps a ton though, I can just link to those past events instead of spending tons of time on a wiki page, which was alawys very tedios
[20:10] <jose> it's great to know that some teams find the tools useful
[20:11] <jose> anything else?
[20:11] <skellat> pleia2: One of my goals is to stress during these check-ins is that we are here to serve the local communities and to find out what needs are unmet that we can help fill.  I'm not really worried about red tape but making sure everything is equipped for success.
[20:11] <pleia2> I just got a package delivered, my saucy shirt has arrived in time for our release party on thursday! :D
[20:12] <pleia2> skellat: much appreciated, thank you
[20:12] <skellat> jose: I call for a vote
[20:12] <jose> that motion is in order
[20:12] <jose> #vote California LoCo Team Re-Verification
[20:12] <meetingology> Please vote on: California LoCo Team Re-Verification
[20:12] <meetingology> Public votes can be registered by saying +1, +0 or -1 in channel, (private votes don't work yet, but when they do it will be by messaging the channel followed by +1/-1/+0 to me)
[20:12] <skellat> +1
[20:12] <meetingology> +1 received from skellat
[20:13] <costales> +1 Keep your awesome work team!
[20:13] <meetingology> +1 Keep your awesome work team! received from costales
[20:13] <jose> +1 Keep up that activity level, awesome!
[20:13] <meetingology> +1 Keep up that activity level, awesome! received from jose
[20:14] <SergioMeneses> +1 great work
[20:14] <meetingology> +1 great work received from SergioMeneses
[20:14] <jose> #endvote
[20:14] <meetingology> Voting ended on: California LoCo Team Re-Verification
[20:14] <meetingology> Votes for:4 Votes against:0 Abstentions:0
[20:14] <meetingology> Motion carried
[20:14] <pleia2> thanks everyone!
[20:14] <jedijf> congrats ca and pleia2
[20:14] <jose> congratulations! :)
[20:14] <SergioMeneses> congrats guys!
[20:15] <jose> next up is...
[20:15] <costales> Congrats!!! :D
[20:15] <czajkowski> well done :)
[20:15] <SergioMeneses> pleia2, you're right the process is pretty similar but is the best way to get information from our teams and get in touch :)
[20:15] <jose> #topic Pennsylvania LoCo Team Re-Verification
[20:15] <jedijf> https://wiki.ubuntu.com/PennsylvaniaTeam/ReVerificationApplication2013
[20:15] <jedijf> hello council
[20:15] <costales> Hi jedijf !
[20:15] <skellat> Good afternoon jedijf!
[20:15] <jose> hey jedijf!
[20:15] <costales> Good luck team! :)
[20:16] <skellat> What end of the Commonwealth are you located in jedijf?
[20:16] <jedijf> Philly side
[20:16] <SergioMeneses> hi ubuntu pennsylvania!
[20:16] <jedijf> southeastern - the only active area - pretty much, since inception
[20:16] <skellat> Okay, I spent some time living in Indiana County working at IUP and attended Clarion University of PA
[20:16] <SergioMeneses> jedijf, \o
[20:16] <pleia2> I was at fosscon with the PA team this summer, they did an awesome job with installs and fixups for folks who came by :) http://www.flickr.com/photos/pleia2/9478617047/in/set-72157635045154436
[20:17] <jedijf> bhavani was there too!
[20:17] <jedijf> he was smitten with pastry
[20:18] <SergioMeneses> jedijf, I saw it
[20:18]  * SergioMeneses wants to go
[20:18] <jedijf> come to 2014 - we're working on a venue right now
[20:18] <skellat> jedijf: How is activity doing beyond the southeastern portion of the state?  Any signs of life or prospects to build upon?
[20:19] <skellat> I may be in Ohio but I'm only a short drive away from Erie if you want somebody to visit and speak perhaps
[20:19] <jedijf> skellat: not really, but as i was doing the reverification, i decided that over the next 2 years that roadtrips to LUGs to promote will be needed
[20:19] <skellat> That sounds good
[20:19] <jedijf> skellat: erie lug, last i heard is inactive
[20:20] <skellat> That sounds not so good
[20:20] <jose> so, I'm checking the LoCo Portal right now, and there aren't many events in there, why aren't you using it?
[20:20] <jedijf> jose: noted - also noted when mentioned to CA
[20:20] <jedijf> will add to administriva list
[20:20] <skellat> If it doesn't do what you need, what do you need it to do for you?
[20:21] <jose> or what do you use instead?
[20:21] <SergioMeneses> jedijf, you seem to be a good team but I dont see referents of the events to the locoteam portal http://loco.ubuntu.com/
[20:21] <jedijf> skellat: not that; merely an oversight
[20:21] <jedijf> SergioMeneses: that will be resolved moving forward
[20:22] <SergioMeneses> jedijf, sure! it is not a big deal, an advice
[20:22] <jedijf> the beauty and bain of multiple communication channels
[20:22] <skellat> Okay, wearing my hat as leader for Ubuntu Ohio I have already filed a few wishlist bugs against LoCo Portal myself as I don't like the way it does a few things
[20:22] <jedijf> after i use it, maybe i will do the same!
[20:22] <skellat> I encourage it
[20:22] <jose> it's a pretty useful tool which devs are keen in improving
[20:23] <jedijf> i did use the Ohio script though (member one)
[20:23] <costales> jedijf: Which type of events is working better in your team? Ubuntu Hours, Jams, Installfests...?
[20:23] <costales> :)
[20:23] <jose> or maybe you do better at talks, roundtables, that stuff?
[20:23] <SergioMeneses> before vote, I want to know if you have any problem in your team or doubts, maybe we can help you
[20:23] <SergioMeneses> jedijf, ↑↑↑
[20:23] <jedijf> costales: fosscon is now our big event - given that we've been around so long, in the philly area, we are definitely a brand
[20:23] <costales> jedijf: Great :)
[20:24] <costales> jedijf: Is a lot of work, right?
[20:24] <jedijf> our work with NTR, a computer repurposer, and the local hackerspaces, and the community in general - that's are biggest promotion
[20:24] <costales> I'm sure :D
[20:25] <jedijf> costales: like pleia2 said - more bodies would be awesome
[20:25] <jose> jedijf: have you recently had any problems or inquiries on the team in which we can give a hand with?
[20:25] <skellat> jedijf: How may we serve your community so that you may achieve greater success?
[20:26] <jedijf> one thing, as i mentioned at the bottom of app is if you could pass on any information that you feel we need to get to the community
[20:26] <skellat> I talked to Jono Bacon about that a little at Ohio Linux Fest
[20:26] <jedijf> i can tell by our forums count there are many lurkers - hopefully they come out - but even if not, giving the info is vital
[20:27] <jose> it's something we're clearly working on, but we need to coordinate it a bit to get it done in a good way :)
[20:27] <jedijf> they will come when the time suits them - just want to keep them engaged until then
[20:27] <skellat> Information gets tricky as we have to balance the business interests of Canonical and the wishes of the community
[20:27] <skellat> That is a matter on our agenda to discuss and take up with Mr. Bacon, though
[20:28] <jose> one last thing I wanted to mention
[20:28] <jedijf> this next 2 years my goal is to start Ubu hours and reach out to distant LUGs to create activity in other areas of the state
[20:28] <jedijf> jose: i'm sorry, go ahead
[20:28] <jose> as we've already said on the mailing list and to you, it would be good if we could get the name of the LP team changed to ~ubuntu-us-pa for it to follow the naming standards :)
[20:28] <jedijf> jose: on it!
[20:29] <jedijf> no printed material
[20:29] <costales> jedijf: Great news! :D I think it'd be very helpful
[20:29] <jedijf> so we're good
[20:29] <SergioMeneses> jose, agree
[20:29] <jedijf> yeah, it's even hard to find myself on the list :)
[20:29] <jose> and if you could change the team's email to the mailing list address that'd be good too
[20:29] <jose> just so people can have contact info handy
[20:30] <jedijf> piece of cake
[20:30] <jose> thanks for the cooperation
[20:30] <costales> yes jedijf, thanks :)
[20:30] <SergioMeneses> jedijf, \o/
[20:30] <jose> so, everyone's ready for a vote?
[20:30] <skellat> I call for a vote
[20:31] <SergioMeneses> skellat, agree
[20:31] <costales> I'm ready
[20:31] <jose> #vote Pennsylvania LoCo Team Re-Verification
[20:31] <meetingology> Please vote on: Pennsylvania LoCo Team Re-Verification
[20:31] <meetingology> Public votes can be registered by saying +1, +0 or -1 in channel, (private votes don't work yet, but when they do it will be by messaging the channel followed by +1/-1/+0 to me)
[20:31] <skellat> +1
[20:31] <meetingology> +1 received from skellat
[20:31] <jose> +1
[20:31] <meetingology> +1 received from jose
[20:31] <costales> +1 Keep your amazing work team! :D
[20:31] <meetingology> +1 Keep your amazing work team! :D received from costales
[20:31] <SergioMeneses> +1 good work and good advices
[20:31] <meetingology> +1 good work and good advices received from SergioMeneses
[20:31] <jose> #endvote
[20:31] <meetingology> Voting ended on: Pennsylvania LoCo Team Re-Verification
[20:31] <meetingology> Votes for:4 Votes against:0 Abstentions:0
[20:31] <meetingology> Motion carried
[20:31] <jedijf> thank you council!
[20:32] <jose> congratulations!
[20:32] <costales> Congrats team!!!
[20:32] <costales> Well done!
[20:32] <IdleOne> yay jedijf and PA!
[20:32] <jthan> IdleOne: come back to PA
[20:32] <IdleOne> jthan: not gonna happen but I am there in spirit
[20:32] <pleia2> congrats PA :)
[20:32] <SergioMeneses> congrats jedijf
[20:32] <jedijf> IdleOne: long time bud - thanks
[20:32] <jthan> IdleOne: <3
[20:33] <jose> keep up the good work, we're sure you'll get more people involved with advocacy :)
[20:33] <waltman> Has anyone mentioned yet how awesome the PA ubuntu team is?
[20:33] <jose> #topic General Announcements
[20:33] <SergioMeneses> jedijf, pleia2 remember if you have a feedback for us, please let us know :)
[20:33] <costales> waltman: +1 :)
[20:33] <SergioMeneses> waltman, :)
[20:35] <jose> first of all, we wanted to mention that we're here to help every team
[20:35] <jose> if any of you needs any help, advice, or even have feedback for us just let us know
[20:36] <jose> we're keen to improve ourselves, as well as our relationship with the teams
[20:36] <jose> then, we also wanted you to know that we have just opened a Twitter account, where we will be posting updates
[20:36] <jose> #LINK https://twitter.com/LoCoCouncil
[20:37] <jose> anything else to discuss, costales, SergioMeneses, skellat?
[20:37] <pleia2> fwiw, I'd love to see a blog post about teams that were (re)verified from the council, even if it's as simple as "congrats, here are links to their approval apps"
[20:37] <pleia2> err, verification :)
[20:37] <jose> noted, will definitely do that in a while!
[20:38] <pleia2> I know there are teams doing great work, but I often don't know about it unless I read the logs, which I don't do
[20:38] <jose> (after I poke IS :P )
[20:38] <SergioMeneses> jose, I'm ok
[20:38] <skellat> jose: I have nothing further to dispose of at this meeting.
[20:38] <SergioMeneses> pleia2, we are working on it :D
[20:38] <costales> pleia2: +1! ;) We were talking about that :D
[20:38] <pleia2> great :)
[20:38] <jose> then, that's all for now, folks!
[20:38] <jedijf> pleia2: thinking uwn?
[20:39] <costales> Thanks jose. Great chat management!
[20:39] <jose> :)
[20:39] <pleia2> jedijf: you know me
[20:39] <jedijf> :)
[20:39] <jose> thanks everyone for coming, and congratulations to us-ca and us-pa!
[20:39] <jose> #endmeeting
[20:39] <meetingology> Meeting ended Tue Oct 15 20:39:33 2013 UTC.
[20:39] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-10-15-20.00.moin.txt
[20:39] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-10-15-20.00.html


[08:19] <D_Cent> tyhicks: hi! i just solved my name_to_handle_at problem - i re-compiled the libusb4java shared object on my other raspberry pi with raspbian and put this version into my project and it seems to work correctly now :)
[08:56] <FourDollars> Hi, what is the difference between ubuntu-15.04-snappy-amd64+generic.img.xz and ubuntu-15.04-snappy-amd64-generic.img.xz?
[09:21] <JamesTait> Good morning all; happy Monday, and happy Tell a Story Day! :-D
[10:00] <ruenoak> FourDollars: I think one is Stable and one is Edge a rolling dev version, just a guess though, but the download img's are named the same
[12:09] <hawkowl> hmm okay i am having some trouble with my Python app
[12:09] <hawkowl> there's no $TEMP or $TMP passed through, it seems, so it tries the system default places, which doesn't work
[13:04] <mvo> hey jdstrand, so you mentioned earlier that you see a upgrade hang on bbb?
[13:13] <jdstrand> mvo: hi!
[13:15] <jdstrand> mvo: I did see a significant delay, yes. I'm not sure if it was related to https://bugs.launchpad.net/snappy-ubuntu/+bug/1447652 or not
[13:16] <mvo> jdstrand: I think its because there is a thing called SyncBootloader files that will always cp /boot/a -> /boot/b which is now very slow because we use sync and also not needed because ubuntu-device-flash already did that
[13:17] <jdstrand> mvo: oh, interesting
[13:17] <mvo> jdstrand: so its a separate bug, but if you don't mind, please file it because I think we need to kill that function
[13:17] <mvo> jdstrand: if you ctrl-z and ps afx you probably see a "cp -a" there
[13:17] <mvo> cp -a /boot/a /boot/b
[13:17] <mvo> to be precise
[13:19] <jdstrand> mvo: https://bugs.launchpad.net/snappy-ubuntu/+bug/1449032
[13:19] <mvo> thanks jdstrand
[13:20] <jdstrand> np
[13:25] <mvo> jdstrand: I'm doing a stop-watch test right now and its already copying for >4min :(
[13:25] <jdstrand> yeah
[14:04] <tyhicks> D_Cent: great to hear that you're unblocked and I'm glad that we don't need to allow name_to_handle_at
[14:04] <tyhicks> D_Cent: thanks for the update :)
[15:34] <leandrosansilva> Hello to all. I am doing some research for a new product where I work and ubuntu snappy came up as a possible base for it. I am looking for a operating system which allows me to perform "atomic updates", avoiding the possibility of breaking my system in case of an update failure. Do you think ubuntu snappy may me suitable for such task?


[05:39] <jphilips> if you guys werent aware of this - "Ultra rage moment, Kubuntu packed @GIMP_Official refuse to have working selections, cut and paste" - https://twitter.com/buxato_life/status/1243193514634207238
[05:51] <valorie> answered
[05:51] <valorie> even though not a guy
[05:51] <valorie> :-)
[05:52] <valorie> rage filled people perhaps should not be tweeting!
[05:52] <valorie> that was almost incoherent
 Lol, agreed
[11:33] <jphilips> well i say guys but meant my peoples :D
[11:39] <jphilips> valorie: well when you have trump rage tweeting all day, its gonna rub off on people :D
[17:36] <jphilips> curious if anyone is regularly managing the kubuntu twitter account
[18:07] <jphilips> was trying to be helpful from my personal account, but not sure what to say now :D - https://twitter.com/MstrTonyStevens/status/1243579309534650369
[18:52] <mparillo> I suppose using Twitter for tech support is difficult. One other thing I have seen when people buy hardware optimized for Windows and the disk is not recognized is for them to make sure it is in the BIOS as AHCI
[19:18] <valorie> jphilips: indeed
[19:18] <valorie> I like twitter but do not follow some accounts
[19:20] <valorie> jphilips: we use our Kub twitter but I can't say any one of us *manages* it
[19:20] <valorie> we tend to tweet our stuff, rt KDE Community and other *buntu flavors
[19:21] <valorie> not much else
[20:52] <jphilips> what is strange is that he already has kubuntu 19.10 on it and he's trying to upgrade the system and its not seeing the ssd


[04:36] <Curly> The Channel is quiet.
[04:37] <Curly> Covid-19 is still around.
[04:38] <diogenes_> Curly, it means we're weaker than bats.
[04:38] <Curly> :)
[04:38] <Curly> That's a good one.
[04:39] <Curly> How are you Diogenes?    Diogenes sounds Greek.
[04:39] <Curly> There is a Greek Diotrophes.
[04:39] <Curly> Or was also.
[04:40] <diogenes_> i'm fine thanks, yes it was a greek philosopher.
[04:40] <diogenes_> and how are you?
[04:40] <Curly> Yes in Bible days.
[04:40] <Curly> I'm not bad at all thanks.
[04:41] <Curly> I am from Massachusetts U.S.A.   And you?
[04:42] <diogenes_> from a small eastern european country and i see you're not sleepy at this late hour?
[04:43] <Curly> You are correct.
[04:43] <Curly> Late?
[04:43] <Curly> What is late for you?
[04:43] <Curly> What European Country are you from?
[04:44] <diogenes_> after 11pm my eyes get heavy.
[04:44] <Curly> I see.
[04:44] <Curly> I have been on one Linux Channel and the channelites thought I was an AI Bot.  :)
[04:45] <Curly> They asked me who was the President of U.S.A.
[04:45] <Curly> ?
[04:45] <Curly> ;)
[04:45] <diogenes_> the republic of moldova.
[04:45] <Curly> Moldove.  I don't know where that is.
[04:46] <Curly> Romania.
[04:46] <Curly> Eastern Europe.
[04:46] <diogenes_> that's expected, it's at the bottom of any list.
[04:47] <Curly> https://duckduckgo.com/?q=Maldova&t=hk&atb=v215-1&ia=about&iax=about
[04:47] <Curly> I saw the red flag there.
[04:47] <Curly> Red, Yellow, Blue
[04:48] <diogenes_> yes
[04:48] <Curly> Interesting. My heritage is from the Roman Empire and the Indo-European line of discent.
[04:49] <diogenes_> we used to be a roman province too.
[04:50] <Curly> I see. My descendents came from Roman line of descent and traveled to Africa and became the first oceanic discoverers.
[04:50] <Curly> Portuguese.
[04:51] <Curly> My dad is Portuguese, my mom is English, British, and Newfoundland.
[04:51] <Curly> That is a strange combination.
[04:52] <diogenes_> hehe indeed diversity is good.
[04:53] <Curly> Well, when you see the world now in a state of chaos, due to hatred of blacks Versus whites, that is strange, because everyone breathing has a black descendant.
[04:53] <Curly> And white.
[04:54] <Curly> And if all of humanity came from Adam & Eve, then, does it matter what color we are?
[04:55] <diogenes_> well it was never differently, people always find a reason to hate.
[04:55] <Curly> Find or Look?
[04:56] <Curly> Some people try not to Find a "reason to hate."
[04:57] <Curly> What type of work do you do Diogenes?
[04:58] <diogenes_> Cain found the reason to hate but this is not for the support channel :)
[04:58] <diogenes_> !chat
[04:58] <Curly> Thanks for the advice.
[04:59] <Curly> Thank you  Ubotu.  ;)
[04:59] <diogenes_> you're welcome :)
[04:59] <Curly> The two smileys joined each other.   ;)
[05:00] <Curly> Diogenes, why did you choose Xubuntu over other distros?
[05:01] <diogenes_> i've tried the majority.
[05:01] <Curly> And?
[05:01] <diogenes_> and you?
[05:02] <diogenes_> and i'm dual booting.
[05:02] <Curly> Well! Me! I have tried so many distros, I got tired of the install and the rediculous divergency of all of the unnecessary off-based commands and formats of thought. No UNITY.
[05:03] <diogenes_> and you chose Xubuntu?
[05:04] <Curly> I like unity. Desultory distros from programmers that want to make a name for themselves is not my cup of tea.
[05:05] <Curly> Xubuntu has a lot of order and arrangement and a good support team, i.e. LTS. That should be key in determining factor.
[05:06] <Curly> The ease of use is paramount.
[05:06] <Curly> Ease of use I am used to.
[05:07] <diogenes_> you're right, Xubuntu is awesome, it ressurected so many machines.
[05:07] <Curly> You can see the unanimity in the product of the programmers.
[05:08] <Curly> Team work is what it is all about.
[05:08] <Curly> #Xubuntu Channel on IRC is a TEAM of people who work together to enlighten those who what to be part of the team.
[05:10] <diogenes_> yes they're very friendly people.
[05:10] <Curly> True.
[05:10] <Curly> I have seem a lot of arrogance with other users of lots of software, hardware, you name it.
[05:11] <diogenes_> hehe fanboys.
[05:11] <Curly> Fanboys?
[05:11] <Curly> What is that?
[05:12] <Curly> Geisha Girls in drag?
[05:13] <diogenes_> a fanboy is a person who only likes 1 product and defends it and criticises the rivals.
[05:14] <Curly> What a wonderful sales/person that is!   <----------<     Narrow minded.
[05:15] <diogenes_> sales person?
[05:15] <Curly> That is the person who knows nothing about anything and gets hired for the first time and the boss tells that person to solicit this product and the person acts like a 50 year veteran  of the product.   He ruined his credibility when he said: "I only use Cent0s."
[05:26] <diogenes_> CentOS could boot too on that machine but there was no touchpad but with Xubuntu all worked great.
[05:27] <Curly> Xubuntu is a UNICES derivative.
[05:27] <Curly> Xubuntu is a sudo-clone of UNIX.
[05:28] <diogenes_> btw do you play any chess?
[05:28] <Curly> Xubuntu works excellent. UNIX is the father of Xubuntu and Linux.
[05:28] <Curly> Yes. There are online chess games.
[05:29] <Curly> I live with my brother and his sons always play chess with my brother. There is a chess game going on all day long. :)
[05:30] <Curly> Your queen is your King piece. Think about that.
[05:30] <diogenes_> ok when you have the desire we could play some games.
[05:30] <Curly> Sure. You name it. :)
[05:31] <diogenes_> ok you want to try?
[05:31] <Curly> Is this chess game on your server?
[05:31] <diogenes_> nope, lichess.
[05:31] <Curly> If so, I would like the source-code or a copy.
[05:31] <Curly> Paste please the URL?
[05:32] <diogenes_> ok
[05:32] <Curly> If I need to give email address and all of that forget it.
[05:33] <diogenes_> https://lichess.org/JYuP4sX3
[05:33] <Curly> By the way, look up on the internet the longest poker game.
[05:34] <Curly> I'm there. Nice.
[05:34] <diogenes_> there is chat too.
[05:39] <Curly> I didn't see the chat. Did you make your move?
[05:40] <Curly> I was distracted.
[05:40] <diogenes_> yes i did
[05:40] <Curly> Ok. You are pretty good.
[05:40] <Curly> Who do you think will win?
[05:40] <Curly> hehe
[05:41] <diogenes_> why not chatting there?
[05:41] <Curly> I was just kidding. I will go back to the game.  :)
[05:47] <Curly> Why do you have two Kngs?
[05:47] <Curly> I see two kings. Is that a fault of the game?
[05:48] <diogenes_> those are 2 queens :)
[05:48] <Curly> I am not in check.
[05:48] <Curly> You have two queens?
[05:48] <Curly> What kind of a game is that?
[05:49] <diogenes_> i promoted my pawn to a queen.
[05:49] <Curly> Does that mean you quit?
[05:49] <Curly> You are funny.
[05:50] <diogenes_> no, that means i have 2 queens now.
[05:50] <diogenes_> each player can have 9 queens.
[05:52] <Curly> 9 queens, that is cheating. Hey!
[05:53] <Curly> This game is a free-for-all. hehe
[05:53] <Curly> What is the URL so I can tell my friends to log-in?
[05:54] <Curly> I like chess but not like that 9 queens. That is absured.   hehe
[05:54] <diogenes_> https://lichess.org/JYuP4sX3
[05:55] <diogenes_> yes ask your friend how many queens a player can have.
[05:57] <Curly> You are funny. Is this something you created?
[05:58] <Curly> I love the game. Does the game timeout after a while?
[05:58] <Curly> I think you cheated because you lost the game. hehe
[05:58] <diogenes_> i set unlimited time.
[05:59] <Curly> Good.
[05:59] <Curly> Why on Earth would you have 9 queens?
[05:59] <diogenes_> https://en.wikipedia.org/wiki/Rules_of_chess#Pawn_promotion
[06:00] <Curly> That is like having all queens or all kings.
[06:01] <Curly> By the way, with chess, you have to specify the rules before you play. Not tell what the rules are afterwards. <----<
[06:01] <Curly> It is like poker.
[06:02] <Curly> By the way is there an online poker game like that?   I don't play poker but my brother does.
[06:04] <Curly> You know I won that game because you started adding more queens. That was cheating.
[06:04] <Curly> You are funny.
[06:04] <diogenes_> heh you said you can play chess so why would i give you the rules? no clue about pocker and i'll be away for awhile, thanks for chat and game, take care.
[06:04] <Curly> That is dirty.   :)
[06:04] <Curly> Cheat and run.
[06:05] <diogenes_> https://en.wikipedia.org/wiki/Rules_of_chess#Pawn_promotion
[06:05] <Curly> Only in the world of Xubuntu.
[06:05] <diogenes_> see the rules again before you call someone a cheater.
[06:06] <Curly> Hey! I am bantering you. That is the nature of the game.  I am going to rub it in.  :)
[06:06]  * diogenes_ is away
[06:06] <Curly> :)
[06:07] <Curly> I think it is an excellent web game. Bravo.
[11:35] <pmjdebruijn> hey, is xfwm 4.14.2 somewhere in the pipeline?
[11:41] <pmjdebruijn> Oh isee there's a package in groovy, which I just backported locally
[14:13] <xubuntu49i> i would like to install xbuntu on a usb (not live) and the boot-loader will be on the usb drive separate from the normal bootloader on the computer , the computer has a mint linux not wondows
[16:06] <afyo> hey guys!
[16:07] <afyo> I got an interesting error, curious if any of you have seen it before.
[16:08] <afyo> Trying to log in this morning, I was login-looped, and I did some googling and they told me to rename the .Xauthority file and try again. So I did, and it worked. Just looked at my logs and it says permission denied trynig to read/write it
[20:13] <Curly> Here is some good reading of Xubuntu:  In the Press.    https://xubuntu.org/press/
[20:18] <Curly> Afyo perhaps the .Xauthority file renamed; the error message was there before you renamed it because of the loop.
[20:19] <Curly> Did you look at the error log before or after you renamed it?
[20:29] <Curly> https://www.maketecheasier.com/fix-ubuntu-login-loop/
[22:57] <Curly> Afyo, did you fix your problem?
[23:13] <Curly> Are there any musicians here on this Channel?
[23:15] <Curly> I haven't done any research on music and programs in Xubuntu but I play Lead Guitar. I found an old Windows program called: "Hendrix"  Which you can watch each note on the fretboard and hear the notes. Also have used MIDI too.
[23:17] <Curly> Most of the software out there is cookie-cutter software. There must be a studio version.


[02:32] <StFS> Hi. I filed a bug because the headphone jack on my dock doesn't work and I'm told that some line has to be added to a "quirk table". I found a line for a T430s in sound/pci/hda/patch_realtek.c and I want to add one for my model (the T430).
[02:33] <StFS> the line I found is: SND_PCI_QUIRK(0x17aa, 0x21fb, "Thinkpad T430s", ALC269_FIXUP_LENOVO_DOCK)
[02:33] <StFS> so my question is basically, how do I figure out what the values should be for my computer/dock?
[02:33] <StFS> the bug I filed is here (it has more hw info): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1060372
[02:33] <ubot2> Launchpad bug 1060372 in linux "No audio from headphone jack on Ultrabase Series 3 with ThinkPad T430" [Medium,Confirmed]
[08:08]  * cwillu_at_work looks at smb suspiciously
[08:08] <cwillu_at_work> smb, recall anything about [PATCH] sched: Fix race in task_group()?
[08:08]  * smb hasn't done nuthing anywhere
[08:09] <cwillu_at_work> well, lkml says you reported the bug it fixed :p
[08:09]  * smb remembers vaguely... more than two days ago...
[08:09] <smb> ;)
[08:10] <cwillu_at_work> as it happens, bisect blames that patch for my server not booting anymore :p
[08:10] <smb> I believe lkml says it was Peter who fixed it. Me merely was anyoing him enough
[08:10] <cwillu_at_work> is he on irc?  I wish to annoy him too! :p
[08:11] <smb> Nah, not here... an I wonder whether that bisect is really true...
[08:11] <cwillu_at_work> I'm pretty confident
[08:11] <cwillu_at_work> I was already suspicious of that patch before I started
[08:12] <cwillu_at_work> it's one of 16 patches that 3.6-rc1 and 3.5.5 have in common
[08:12] <cwillu_at_work> and those are the two kernel versions that stopped booting
[08:12] <smb> Would "noautogroup" change something there?
[08:13] <cwillu_at_work> https://lh5.googleusercontent.com/-0DY-YYhgvzs/UHdB-BQdzMI/AAAAAAAAAEg/QhY9rgxnv98/s811/2012-10-11  <- crash in question
[08:13] <cwillu_at_work> which, on the kernel cmdline?
[08:13] <smb> yep
[08:13] <cwillu_at_work> give me a minute to try
[08:16] <cwillu_at_work> smb, yep, it boots with noautogroup
[08:18] <smb> cwillu_at_work, Ok, I might have to admit it is related. :-P Wonder what on your server is so different that it happens while on none of those I use it does...
[08:18] <cwillu_at_work> well, it's probably older than most things you're testing
[08:18] <cwillu_at_work> it's a lucid box
[08:20] <smb> That maybe, but this is in a very central place in the kernel, used not only on server and I would not think any netbooks especially powerfull...
[08:22] <smb> Hm, anyway, you should make it fail with a current kernel (for which there are still ddebs I could pull) and create a bug report with the trace, kernel version and bisection result in it
[08:23] <cwillu_at_work> the trace is rather hard to get too
[08:23] <cwillu_at_work> to
[08:23] <smb> So it is not always showing up?
[08:24] <smb> Or just scrolling off
[08:24] <cwillu_at_work> scrolling off, early'ish in boot
[08:24] <cwillu_at_work> I haven't had any luck getting netconsole to work, but that may just be me mistyping an address
[08:25] <smb> Hm, there was also some option to make earlyprintk crawl...
[08:26] <smb> or maybe pause_on_oops=<seconds>
[08:28] <cwillu_at_work> well, the trick is more getting something better than a photo, no? ;p
[08:28] <smb> ah here boot_delay=<milliseconds> (but below 10000)
[08:28] <cwillu_at_work> I can get a photo every time
[08:28] <smb> As long as the photo is not so blurry that my eyes and brain hurts it is ok
[08:28] <smb> yours is not bad
[08:29] <cwillu_at_work> well, was the above so blurry that your... k :)
[08:29]  * smb has seen much worse
[08:30] <smb> And that one at least has most of the top of the message which is also sometimes a problem
[08:30] <cwillu_at_work> yeah, if I leave it for more than 2 seconds, a whole whack of other oopsen show up
[08:30] <cwillu_at_work> short enough that autofocus becomes a problem :p
[08:30] <smb> Heh, yeah
[08:31] <cwillu_at_work> pause_on_oops sounds useful there though
[08:31] <cwillu_at_work> suspect I'll make that a local default
[08:37] <smb> Hm, on a quick glance at the code the most likely cause would be that p->sched_task_group has not been set when set_task_rq() tries to access things from it...
[08:39] <smb> but that should be at least set to &root_task_group...
[08:41] <smb> cwillu_at_work, Just to be sure, this happens on that machine also with the default/stock ubuntu kernels (to rule out any slightly different configuration)
[08:41] <cwillu_at_work> smb, lucid remember :p
[08:41] <cwillu_at_work> the kernels on the mainline page don't install from 3.6 onward
[08:41] <smb> and a 3.6 kernel in the crash ;)
[08:42] <cwillu_at_work> (complaints about libc)
[08:42] <cwillu_at_work> smb, btrfs on anything but the latest kernel is suicidal
[08:42] <cwillu_at_work> (I have extensive backups, etc)
[08:43] <cwillu_at_work> but the kernel config is just a make oldnoconfig after cp'ing the existing stock config from /boot to .config
[08:44] <cwillu_at_work> smb, I'm not looking for support, I'm just looking for the right body to poke to get it fixed in mainline :p
[08:45] <cwillu_at_work> although the noautogroup suggestion was useful, and allows me to get actual btrfs testing work done in the mean time, for which I'm grateful :)
[08:46] <smb> cwillu_at_work, Still that does not answer the question: Have you seen the crash with for example the mainline kernel we build?
[08:46] <cwillu_at_work> you don't build a 3.6 mainline kernel that will install on lucid
[08:46] <smb> ?
[08:46] <smb> Have you tried?
[08:47] <cwillu_at_work> sec, I'll get the exact error, but yeah, I've tried
[08:47] <cwillu_at_work> if memory serves, it's a libc version bump from quantal that it doesn't like
[08:48] <smb> hm, ok... that in some way sounds familiar
[08:49] <cwillu_at_work> (just waiting for linux-image-3.6.2-030602-generic_3.6.2-030602.201210121823_amd64.deb and company to download
[08:50] <cwillu_at_work> I don't blame you for making me check of course; rule #1 in #btrfs is "The user lies" ;p
[08:52] <smb> cwillu_at_work, Btw, don't know whether you know, you could checkout upstream kernels and then take the patches from the mainline page of the same version and then locally build with the exact same config
[08:52] <smb> cwillu_at_work, Well, not only btrfs ;-P But even without that there is enough space for misunderstandings
[08:53]  * xnox seriously considers to turn off his btrfs highlight =))) too much chatting going on ;-)
[08:53] <cwillu_at_work> only reason I'm asking in this particular channel is that I recognized your name on the commits :p
[08:53] <smb> And I want to make sure we don't have a case where for some reason there is a slightly different configuration which nobody was considering
[08:54] <smb> Well yeah, unfortunately the state before is as broken... which I had to fight with
[08:55] <cwillu_at_work> linux-headers-3.6.2-030602-generic depends on libc6 (>= 2.14); however:
[08:55] <cwillu_at_work>   Version of libc6 on system is 2.11.1-0ubuntu7.10.
[08:55] <cwillu_at_work> that's actually just the headers package though
[08:55]  * cwillu_at_work reboots to test
[08:57] <cwillu_at_work> and boom
[08:57] <smb> ok, so that is at least out of the way
[08:57] <cwillu_at_work> smb, image from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.6.2-quantal/ blew up in the usual way
[08:58] <smb> Now I hope I did not screw the backport...
[08:59] <cwillu_at_work> there's a 3.6 backport for lucid?
[09:00] <smb> nah, but I did make upstream backports, though 3.6 should have it from upstream *pfew)
[09:01] <smb> yeah 3.6-rc3 had it...
[09:01] <cwillu_at_work> rc1 had it
[09:01] <cwillu_at_work> and 3.5.5 had it
[09:01] <cwillu_at_work> there's only 16 patches in common between those :)
[09:02] <smb> 3.5 could even be the variant from upstream, the problem was that files were shuffled around a lot early in 3.5
[09:06] <cwillu_at_work> when I say "3.5.5 had it", I mean "the git tag v3.5.5 from upstream's -stable repo"
[09:09] <smb> I had assumed that. The patch itself was not marked stable but I submitted it at least for 3.2/3.0 (I think). Then Greg decided it should be in 3.5, too. It was ok, just not as urgent.
[09:09] <cwillu_at_work> ah, okay
[09:10] <cwillu_at_work> yeah, I haven't run a 3.2 or 3.0 kernel in a while
[09:10] <cwillu_at_work> I also haven't needed to restore from backups in a while?
[09:10] <cwillu_at_work> this is not a coincidence :)
[09:11] <smb> Yeah, yeah, barfs (<- cking ;))
[09:11] <cking> smb, don't blame me, blame the spelling checker ;-)
[10:02] <psivaa> apw: good morning and i've just added the dmesg of a failed boot with --verbose added that slangasek asked for in bug 1066883
[10:02] <ubot2> Launchpad bug 1066883 in linux "[Macmini 5,1] Fatal server error: Can not run in framebuffer mode on reboot" [High,Confirmed] https://launchpad.net/bugs/1066883
[10:10] <henrix> smb: i was reading the irc logs and i was wondering whether the bug referred by cwillu_at_work could be bug #1055222
[10:10] <ubot2> Launchpad bug 1055222 in linux "Kernel panic on reboot after sched_autogroup_enabled disabled" [Undecided,Confirmed] https://launchpad.net/bugs/1055222
[10:11] <smb> henrix, Does that not sound like the opposite?
[10:11] <smb> sched_autogroup_enabled=0 == noautogroup
[10:11] <henrix> smb: yes, it occurs only when you disable the autogroup, but the traces point to similar place
[10:12] <henrix> it's easily reproducible
[10:12] <smb> henrix, I am sure I have been using noautogroup at least recently without problems but maybe
[10:12] <smb> Again, this would require actually reading the bug report I was not aware of before
[10:13] <henrix> smb: i can reproduce it in a precise kernel and even on a quantal running 3.7-rc1
[10:14] <henrix> anyway, i'm trying to get more info about this
[10:14] <smb> henrix, I can try to see whether it crashes for me as well with sysctl but it might be a similar reason
[10:15] <smb> Assuming some init was forgotten to the copy of the autogroup variable
[10:15] <smb> (which I suspect)
[10:16] <henrix> smb: ok, thanks
[10:25]  * ppisati -> out for lunch
[11:10]  * henrix -> SIGFOOD
[12:38] <caribou> Q: I've just finished bisecting/testing a revert on latest Quantal & Precise kernels for a bug : LP: #1056746
[12:39] <caribou> right now, I've assigned the bug to myself
[12:39] <caribou> but should it be assigned to an official team instead ?
[12:40] <caribou> but 1056746 is causing iscsi to hang reboots when multipath is active
[12:40] <rtg> bug #1056746
[12:40] <caribou> bug 1056746
[12:40] <ubot2> Launchpad bug 1056746 in linux "kernel panic on iscsi target disconnect" [High,Confirmed] https://launchpad.net/bugs/1056746
[12:40] <caribou> hmm, need to go change the title
[12:42] <rtg> caribou, if you're pursuing the bug then leave it assigned to yourself
[12:42] <caribou> rtg, yep I am
[12:42] <caribou> arges will help me format the patch submission later so I don't send rubbish to the list
[12:50] <ogasawara> rtg: did quantal lbm make it through to the archive?
[12:51] <rtg> ogasawara, as did the meta package (I think)
[12:52] <rtg> ogasawara, I chatted with the folks on #ubuntu-release about it, I think I remember it being accepted, then I raced off to ride bikes and drink beer and all else was forgotten.
[12:53] <rtg> damn, another dya has started.
[12:54] <rtg> ogasawara, https://launchpad.net/ubuntu/+source/linux-backports-modules-3.5.0
[12:58] <ogasawara> rtg: right, seems like it's missing there
[12:58] <rtg> ogasawara, its there, its just not been published
[12:58] <rtg> I'll bug 'em about it
[12:59] <ogasawara> rtg: thanks, gotta jump on a call here
[13:23] <slangasek> psivaa: bug #1066883> great, thanks; will peruse that output later today
[13:23] <ubot2> Launchpad bug 1066883 in linux "[Macmini 5,1] Fatal server error: Can not run in framebuffer mode on reboot" [High,Confirmed] https://launchpad.net/bugs/1066883
[13:24] <rtg> ogasawara, no good deed goes unpunished :) bug #1068125
[13:25] <ubot2> Launchpad bug 1068125 in linux-backports-modules-3.5.0 "Quantal LBM should not generate udebs" [Undecided,In progress] https://launchpad.net/bugs/1068125
[13:25] <psivaa> slangasek: ok, yw
[13:25] <ogasawara> rtg: ack, I'll clean it up.
[13:26] <brendand> bjf, henrix - what is the cadence looking like now? will regression testing be after or before uds?
[13:27] <brendand> http://people.canonical.com/~kernel/reports/sru-report.html is not very forthcoming
[13:27] <henrix> brendand: we're holding it a little bit until the release so that we're not using the buildds for kernels
[13:28] <brendand> henrix, so it's not built yet?
[13:28] <brendand> henrix, in that case it will be after uds for regression testing i guess?
[13:28] <henrix> brendand: no, it is not. we are not supposed to upload anything to the buildds during this period
[13:28] <henrix> brendand: i believe this cycle will be extended to 4 weeks
[13:29] <brendand> henrix, ok, thanks!
[13:29] <henrix> brendand: np
[13:29] <henrix> bjf: ^ that's correct, right?
[13:30] <henrix> brendand: anyway, i expect to start uploading kernels later today or tomorrow.
[13:52] <StFS> Hi. I was just fixing a small bug with my dock audio output (added a single line to the quirk table). Anyways, I built my own kernel-image .deb but it has the same version as the one that is installed from the repo. So first question: how do I change the version number for the package that I'm building? Second question: is there some naming that I could use so that if a new kernel-image becomes available in the repo it will still be installed over the
[14:06] <henrix> StFS: you can take a look at https://wiki.ubuntu.com/Kernel/Dev/KernelBugFixing (section "Building and Uploading the Package")
[14:06] <henrix> StFS: it suggests the use of '~'
[14:19] <bjf> brendand, https://wiki.ubuntu.com/RaringRingtail/ReleaseSchedule
[14:20] <bjf> brendand, we discussed this with ara, the week of uds will be an additional verification week and the week after will be testing
[14:21] <brendand> bjf - sounds like a plan
[15:00] <rtg> ogasawara, you gonna throw up the day 0 kernel today ?
[15:01] <ogasawara> rtg: I wasn't planning on a 0 day
[15:01] <ogasawara> rtg: was just gonna let it do it's normal SRU cycle
[15:02] <rtg> ogso, just let the stable team do it ?
[15:02] <ogasawara> rtg: yep, I didn't see anything urgent on master-next
[15:02] <bjf> ogasawara, we have the conn :-)
[15:02] <rtg> ogasawara, 2 stable updates in the pipe, but should likely go through Q/A
[15:03] <ogasawara> rtg: yep, I'd prefer those get some baking before going up
[15:03] <rtg> bjf, then its officially yours. I'll go back to worrying about signed modules
[15:03] <bjf> rtg, ack
[15:03] <bjf> henrix, herton, sconklin, ^ quantal is ours
[15:04] <herton> ack
[15:05] <henrix> \o/
[15:06]  * ogasawara back in 20
[15:30] <apw> rtg, now we know the name of r, are you going to fix the repo name ?
[15:30] <rtg> apw, already did
[15:30] <apw> hmmm, my update worked, odd
[15:31] <rtg> apw, ln -s ubuntu-raring ubuntu-r
[15:32] <bjf> apw, are the buildds free to use again?
[15:33] <apw> bjf, we're not released as yet, so not sure
[15:33] <bjf> apw, ack
[15:33] <apw> bjf, oh word on the street is you are good to get back on your SRUs
[15:34] <bjf> apw, cool, thanks
[15:34] <bjf> henrix, ^ you are free to engage
[15:35] <bjf> :w
[15:36] <rtg> its a target rich environment
[15:45] <apw> rtg, so i am assuming you are owning -r rebases for now ... in the interim i am going to liase with infinity et al about what they want in R 'before' toolchain etc
[15:45] <rtg> apw, almost done
[15:46] <apw> rtg, cool.  i suspect our headers are going to be a mess after the 3.7 update, so it seems wise to put a 3.6 for the initial opening/bootstrap
[15:47] <rtg> apw, likely. there is a Ubuntu-3.6 tag
[15:48] <apw> rtg, i see it, thanks for remembering :)
[16:10] <rtg> ppisati, apw: I'm done with the ubuntu-raring smack down. went from 300'ish patches down to 108
[16:10] <rtg> ppisati, I'll start building with your arm patches here shortly
[16:11] <apw> rtg nice
[16:11] <ppisati> rtg: i've two more
[16:11] <ppisati> rtg: they are from Q, it seems you forgot them
[16:11] <rtg> ppisati, I'd gotten about as far as you did before I got tired of rebuilding and just gave up on arm altogether
[16:12] <rtg> ppisati, go ahead and post 'em and I'll pick them up
[16:12] <ppisati> rtg: ok, give 5mins and i'll send these two (usb stuff)
[16:12] <ppisati> ack
[16:32] <ppisati> rtg: patches sent
[16:50] <tyhicks> rtg, cking: bug 338914 is a pretty minor bug that no one would hit unless they tried pretty hard
[16:50] <ubot2> Launchpad bug 338914 in linux "Proper cipher support isn't checked at mount time" [Undecided,Fix committed] https://launchpad.net/bugs/338914
[16:50] <rtg> tyhicks, true, buts its also an easy patch
[16:50] <tyhicks> rtg, cking: It probably isn't worth the cycles needed for backporting and verifying it
[16:50] <tyhicks> it is easy
[16:51] <tyhicks> rtg: If you (or cking, rather) don't mind doing the work, I won't stop you. Just wanted to mention that it isn't a big deal. :)
[16:51] <rtg> tyhicks, no problem, its already in the pipeline and cking has an easy verifier
[16:52] <tyhicks> (Thanks a bunch for helping to stay on top of eCryptfs bugs in Ubuntu, btw!)
[16:52] <tyhicks> sounds good!
[16:52] <rtg> tyhicks, you're my special project :)
[16:52] <tyhicks> heh... I hope that's a good thing
[16:53] <rtg> tyhicks, nah, its just that I've always been an ecryptfs proponent, so I keep a special eye out for bug fixes etc
[16:54] <tyhicks> We definitely have the most eCryptfs users, so that's a good thing
[16:54] <cking> yup, and it's no big deal for me to keep on top of these patches to SRU
[16:57] <cking> tyhicks, BTW, I'm going to see if I can construct some eCryptfs tests to bump up the gcov coverage rate
[16:57] <tyhicks> cking: Great!
[16:58] <tyhicks> cking: I've always wanted to add eCryptfs support to xfstests to automatically pick up the large number of tests that they have (and actively add new tests), but I've never had the chance
[16:59] <tyhicks> cking: Keep that option in mind as you plan out what you want to do
[16:59] <cking> tyhicks, yep, lets call that a 13.04 work item
[17:00] <bjf> tyhicks, cking i think that would be fairly easy to add to our existing tests
[17:00] <tyhicks> Hmm... making xfstests know about stacked filesystems may help overlayfs testing, too
[17:00] <bjf> tyhicks, cking we already run the xfstests
[17:00] <tyhicks> good to know
[17:00] <cking> bjf, yep, we can discuss that at UDS
[17:19] <kroson_> Hi everyone, and congratulations for Ubuntu 12.10 release. Can you tell me if upgrading from kernel 3.5 to kernel 3.6 in 12.10 is a safe procedure?
[17:19] <kroson_> thanks
[17:40]  * rtg -> lunch
[18:02]  * ppisati -> EOD
[18:13] <alexbligh1> now you guys have got quantal out (congrats) is there a plan for quantal-backport kernel for precise?
[18:13] <alexbligh1> (as in 'in the precise repo')
[18:15] <rtg> alexbligh: yes, but you know you can also get it from https://launchpad.net/~ubuntu-x-swat/+archive/q-lts-backport until its official in teh archive
[18:30] <alexbligh> rtg, thanks. it was more for our customers than for me. AFAIK just installing the q .deb works now on p.
[18:31] <rtg> alexbligh: it'll show in due course when things have settled a bit from the release. I'll pursue getting it uploaded tomorrow.
[18:32] <alexbligh> rtg, great. No rush from me. We'll just have the normal run of people complaining that they can't install our stuff on arcane-hardware-du-jour and our normal solution is to point them at a backported kernel.
[18:38] <ogasawara> rtg: so we have bug 1026831 which is linked to from https://blueprints.launchpad.net/ubuntu/+spec/hardware-q-kernel-misc, but we also have https://blueprints.launchpad.net/ubuntu/+spec/desktop-q-xorg-lts-updates
[18:38] <ubot2> Launchpad bug 1026831 in debian-installer "Seed the correct Q LTS backport kernel meta package in the 12.04.2 point release" [Undecided,Invalid] https://launchpad.net/bugs/1026831
[18:39] <rtg> ogasawara, I'll use the second one
[18:39] <rtg> https://blueprints.launchpad.net/ubuntu/+spec/desktop-q-xorg-lts-updates
[19:13] <rtg> ogasawara, bug #1068281
[19:13] <ubot2> Launchpad bug 1068281 in linux-meta "Quantal LTS kernel in Precise" [Undecided,Fix committed] https://launchpad.net/bugs/1068281
[19:14] <ogasawara> rtg: ack
[19:36] <rtg> bjf, https://launchpad.net/ubuntu/raring still indicates armel
[19:37]  * ogasawara lunch
[19:37] <bjf> rtg, indeed it does
[19:38] <bjf> rtg, but then you know how hard it is to removes a flavour let alone an arch
[19:49] <manjo> rtg, in 12.04 we had /lib/modules/3.2.0-32-generic/build but in 12.10 we don't have the 'build' directory anymore ?
[19:50] <maxb> I have a /build on 12.10
[19:50] <rtg> manjo, likely a function of upstream build changes, but its a detail that I can't remember
[19:50] <manjo> maxb, you said /build ?
[19:51] <maxb> By which I mean I'm being a lazy typist and mean /lib/modules/$(uname -r)/build
[19:51] <manjo> rtg, I was looking for .config Module.symvers Makefile which used to be under /lib/modules/$(uname -r)/build
[19:52] <manjo> maxb, interesting I just installed 12.10 and I don't have that build directory
[19:52] <maxb> maxb@zenbook:~$ ls -lA /lib/modules/3.5.0-17-generic/build/Module.symvers
[19:52] <maxb> -rw-r--r-- 1 root root 844882 Oct  9 20:56 /lib/modules/3.5.0-17-generic/build/Module.symvers
[19:53] <maxb> manjo: And if you 'apt-get install linux-headers-generic' ?
[19:53] <manjo> hmm installing
[19:53] <manjo> maxb, you saved me !
[19:53] <manjo> thanks
[19:54] <manjo> maxb, I guess header-generic is not installed by default anymore .. but that makes sense
[20:51]  * cwillu pokes smb with a sysctl.conf entry
[20:51] <cwillu> "kernel.sched_autogroup_enabled = 0" in /etc/sysctl.conf is what makes my machine different; should have thought of that when you said "noautogroup"
[21:12]  * rtg -> EOD