[21:15] <AndrewMcC> Well, in the latest Raring packages, my resume-from-suspend is now working.
[21:16] <AndrewMcC> And I've got IPv6 working properly, but only by changing from wl to brcmsmac as my wireless card driver.
[21:23] <AndrewMcC> And dabs have some Samsung SSDs on the (slightly) cheap and I'mawfully tempted. Still not happy with SSD reliability in general though. Anybody here any experience?


[00:41] <Mike_Feravolo> Maybe some one can tell me how to find out what email address that i signed up for the marketing list is
[00:41] <Mike_Feravolo> i keep getting my messages bounced back
[14:26] <smallfoot-> hey can you make a page that teaches users how to market ubuntu
[14:26] <smallfoot-> if i say "hey get ubuntu", people say "why?" and im like shit, i dont know
[14:27] <smallfoot-> sometimes people say untrue thing like "ubuntu is faster than window" then i try it, and its slower than windows
[14:27] <smallfoot-> they say "ubuntu is more easy than windows", i try, and its difficult to use and crash and many things dont works
[14:27] <smallfoot-> they say "ubuntu is more stable than window" and it crash
[14:28] <smallfoot-> they say "ubuntu is more secure than windows", but it doesnt have disk encryption like Vista has
[14:29] <smallfoot-> they say "ubuntu dont get virus", but its because nothing works in ubuntu, so virus cant work too
[14:30] <pep> [15:28] <smallfoot-> th?ey say "ubuntu is more secure than windows", but it doesnt have disk encryption like Vista has
[14:30] <pep> [15:29] <smallfoot-> they say "ubuntu dont get virus", but its because nothing works in ubuntu, so virus cant work too
[14:30] <pep> I don't want to hurt your feelings
[14:30] <pep> but learn a little more about the funciotning of an operating system... inform yourself before saying wrong things
[14:31] <pep> ever heard of truecrypt?
[14:31] <smallfoot-> yes, and ubuntu dont have truecrypt
[14:31] <smallfoot-> go look in repository, it dont have it
[14:31] <smallfoot-> and Vista has BitLocker Drive Encryption, you can encrypt WHOLE disk, in Ubuntu you cant even protect your home directory
[14:31] <pep> it does
[14:32] <pep> sudo apt-get isntall truecrypt
[14:32] <pep> oh my god
[14:32] <pep> don't say things like that
[14:32] <pep> you know what an alternate cd is?
[14:32] <pep> take a look at how "bad" ubuntu is: http://news.softpedia.com/news/Encrypted-Ubuntu-7-10-68383.shtml
[14:33] <smallfoot-> Package truecrypt is not available, but is referred to by another package.
[14:33] <smallfoot-> This may mean that the package is missing, has been obsoleted, or
[14:33] <smallfoot-> is only available from another source
[14:33] <smallfoot-> E: Package truecrypt has no installation candidate
[14:33] <smallfoot-> apt-get say no truecrypt
[14:33] <smallfoot-> $ dpkg -l "*truecrypt*"
[14:33] <smallfoot-> No packages found matching *truecrypt*.
[14:33] <pep> which version of ubuntu do you have?
[14:33] <smallfoot-> 8.04
[14:34] <pep> ok
[14:34] <pep> I just checked
[14:34] <pep> it used to be there
[14:34] <pep> we took it out
[14:34] <smallfoot-> yeah but its not
[14:34] <pep> http://www.truecrypt.org/downloads.php
[14:34] <smallfoot-> install from outside repository is difficult
[14:34] <smallfoot-> and i want full disk encryption, not just a little encrypted file or volume, i want ALL encrypted
[14:34] <pep> it is what you have been doing all the time on windows... we're not talking about compiling here...
[14:35] <smallfoot-> and i want use normal cd, not have to use a alternative cd that i dont have, which has text install instead of graphics
[14:35] <pep> it is a precompiled .deb
[14:35] <pep> well you can, then use truecrypt
[14:35] <smallfoot-> oh good
[14:35] <pep> now listen
[14:36] <pep> if you're here to troll and say how bad it is and how you're too lazy to figure out how a new OS works, you may as well leave. We're not here to satisfy your need of complaining about Ubuntu.
[14:37] <smallfoot-> oh ok
[14:37] <pep> needless to say that it was not at all constructive what you said
[14:38] <smallfoot-> but can you make a webpage that teaches ubuntu users how promote ubuntu to other people, i say "get ubuntu its free!!!! FREEDOM!!!" and they get scared of me, or they say widnows came free with their computer
[14:38] <pep> ^^
[14:38] <smallfoot-> and if say "get ubuntu its open source!!", they say "open sauce?? what is this, i dont care"
[14:38] <pep> hang on I'll look, I think this existed... there is a "marketing-guide" or similar prepared or already out...
[14:39] <pep> smallfoot-: well then you have to explain why they should care... just take soem time to explain it all... like we all do :)
[14:39] <pep> I wouldn't care too if I had never heard of it :)
[14:39] <smallfoot-> and sometimes i see other people post in forum "Ubuntu is the absolutely best operating system ever, its much faster and stable than Windows and much easier, and its 100% secure, its impossibel get virus, and you get more FSP in CS!"
[14:40] <smallfoot-> the ubuntu marketing guys need to make a marketing-guide webpage maybe on ubuntu wiki that teaches users how to correctly promote it
[14:40] <pep> and? id you explain to them that it was a community based project also? that if their wifi bugs, they should try and get help, nd if it is a real bug they can report and we'll fix it?
[14:40] <pep> yeah I'll check on that page.. hang on
[14:42] <pep> smallfoot-: https://launchpad.net/spreadubuntu
[14:42] <pep> smallfoot-: http://doc.ubuntu.com/~marketing/spreadubuntu/
[14:43] <pep> the best is still to read an re-read the official descriptions why Ubuntu is good. and most of all: understand them thouroughly!
[14:46] <pep> the more you use ubuntu yourself, the more you will be able to talk about it and convince people.
[14:50] <smallfoot-> yeah maybe someone have different need, like if i promote to susy14 who likes to chat on msn or to csboy16 who like play game, or if i promote to Mr. John Applegate 43 who is the CEO of Applegate Solutions Inc, or if i promote to school or library
[14:51] <pep> yes, got to think about that when you talk to soemone about ubuntu
[14:52] <smallfoot-> yeah should be a guide
[14:54] <smallfoot-> why is no spreadubuntu.com?
[15:00] <pep> it is planned
[15:01] <pep> you can participate if you want to see it standing :)
[15:01] <smallfoot-> i dont knows how
[15:05] <pep> learn website making... html/css/php... or easier... just participate to the wiki, no great skills neede for that...
[15:06] <pep> it wil be done when somebody takes the time to do it.
[15:06] <smallfoot-> well i can download Drupal, it is what spreadfirefox.com uses
[15:06] <smallfoot-> then install that
[15:07] <pep> if you want to make  a standalone .com site maybe use drupal, yes... see https://launchpad.net/spreadubuntu for info...
[15:29] <smallfoot-> i dont want make standalone .com, i want put on spreadubuntu.com
[15:30] <pep> spreadubuntu.com is a domain name... and it doesn't exist...
[15:30] <pep> I was talking about a standalonde website, as in "not in the ubuntu wiki"
[15:31] <smallfoot-> spreadubuntu.com does exist
[15:31] <smallfoot-> but it redirect to ubuntu.com
[15:31] <pep> ah
[15:31] <pep> cool
[15:32] <smallfoot-> yeah so we must put drupal on it, and make it same like spreadfirefox.com
[15:32] <smallfoot-> cuz that is what they use
[15:32] <smallfoot-> and their site is successful
[15:33] <pep> yes... actually a site needs tobe made, then the domain name will be linked to it....
[15:34] <pep> but if you're serious to participate in this, mail the list...
[15:34] <smallfoot-> there is a mailing lists?
[15:34] <pep> yes
[15:34] <pep> this is ubuntu-markting :)
[15:34] <pep> http://ubuntuforums.org/showthread.php?t=213606 there has already been a lot of talk about this project..
[15:35] <pep> and the list is in the topic
[15:35] <pep>  /topic
[15:36] <smallfoot-> oh


[02:19] <mup> PR snapd#9235 opened: tests: new tests for nested and external <Run nested> <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/9235>
[05:00] <mup> PR snapd#9233 closed: vendor: run ./get-deps.sh to update the secboot hash <Skip spread> <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/9233>
[05:23] <mborzecki> morning
[05:30] <mup> PR snapd#9232 closed: run-checks: check for dirty build tree too <Skip spread> <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/9232>
[05:39] <zyga> o/
[05:39] <zyga> mvo you're up early
[05:43]  * zyga leaves the macbook to charge and goes upstairs to do reviews from the imac
[05:52] <mborzecki> mvo: zyga: hey
[05:53] <mvo> hey zyga and mborzecki
[06:05] <mup> PR snapd#9236 opened: kernel: remove "edition" from kernel.yaml and add "update" <Created by mvo5> <https://github.com/snapcore/snapd/pull/9236>
[06:07] <mborzecki> heh, in the 15.2 images we have there's no daemon user/group
[06:11] <mborzecki> zyga: i think we need to fix the rpm spec on openssue and add a dependency on system-user-daemon (as daemon is needed for system usernames)
[06:12] <mborzecki> zyga: idk why but installing lsb release does not seem to pull in that package (even though daemon user is required by lsb?)
[06:14] <mvo> thanks for this
[06:14] <mvo> I mean, thanks for looking/fixing this
[06:16] <mvo> mborzecki: quick question - gadget updates are already smart in the sense that there is no file update if the hash is the same, correct?
[06:16] <mborzecki> mvo: yes
[06:16] <mvo> ta
[06:17]  * mvo still scratches head over how to best apply the kernel-dtb refs
[06:18] <mborzecki> mvo: this is the bit that does that https://github.com/snapcore/snapd/blob/master/gadget/mountedfilesystem.go#L763
[06:18] <mvo> mborzecki: ta
[06:26] <jamesh> zyga: thanks for the review comments.  Since you're the expert on process tracking, my spread test is failing on Ubuntu 14.04, where it doesn't seem to be able to identify a process from a classic confined snap.  Is that a known limitation?
[06:45] <zyga> jamesh, yes, 14.04 has no tracking
[06:45] <zyga> jamesh we could fake it I mean
[06:45] <zyga> we can expand tracking to use apparmor labels
[06:46] <zyga> that would cover 14.04
[06:46] <zyga> by fake it, I mean we could be better while not being really equal to 16.04+
[06:46] <zyga> mborzecki sounds good (dependency change) - I have some changes I didn't merge into master, related to suse packaging
[06:46] <jamesh> zyga: weird that the rest of the test using strict confinement passed then.
[06:47] <zyga> jamesh, hmmm, but even with classic confinement, we should be setting an apparmor label
[06:47] <mborzecki> zyga: i have a fix to push to #9218
[06:47] <mup> PR #9218: tests: running tests on opensuse leap 15.2 <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/9218>
[06:47] <jamesh> zyga: I could probably just skip the test on 14.04
[06:47] <zyga> jamesh which exact test is that?
[06:47] <zyga> jamesh I honestly think that's best
[06:47] <zyga> 14.04 is not a fully supported release
[06:49] <jamesh> zyga: the spread test in https://github.com/snapcore/snapd/pull/9132: the "exit_staus 11 ..." test at the end to check against a classic process returns 10 (which is "not snap confined")
[06:49] <mup> PR #9132: o/hookstate/ctlcmd: add optional --pid argument to "snapctl is-connected" <Created by jhenstridge> <https://github.com/snapcore/snapd/pull/9132>
[06:49] <zyga> jamesh I'll look
[07:04] <pstolowski> morning
[07:07]  * zyga small errand
[07:07] <zyga> hey Pawel
[07:18] <mvo> good morning pstolowski
[07:26] <mborzecki> zyga: can you take a look at?
[07:26] <mborzecki> zyga: pff, forgot to paste the link ;P https://github.com/snapcore/snapd/pull/9218
[07:26] <mup> PR #9218: tests: running tests on opensuse leap 15.2 <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/9218>
[07:33] <pstolowski> eh, snap-logs test failures seem related to my services changes but i don't understand how
[07:34] <pstolowski> did anyone see this test failing on master recently?
[07:46] <zyga> mborzecki looks sensible
[07:46] <mborzecki> pstolowski: snap logs?
[07:47] <mborzecki> pstolowski: there's a PR from ijohnson with a bug fix, do you have a log?
[07:47] <pstolowski> mborzecki: yes sna logs
[07:47] <mborzecki> pstolowski: this PR from ian: https://github.com/snapcore/snapd/pull/9234
[07:47] <mup> PR #9234: systemd/systemd.go: support journald JSON messages with arrays for values <Bug> <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/9234>
[07:48] <mborzecki> related?
[07:49] <pstolowski> mborzecki: ah, interesting! thanks, could be
[07:49] <pstolowski> going to test with my branch
[07:51] <pstolowski> this test often fails on snap logs -f ... check (no match for the expected log message), but snap logs -n=all does include it
[08:37] <mborzecki> quick errand, back in 30
[09:04] <pedronis> pstolowski: now the service PR is ready for re-review, right? (not sure I'll get to it today though)
[09:05] <pstolowski> pedronis: i'm testing ijohnson's fix for log parsing to see if it fixes snap-logs test failures in my PR, i'll know shortly
[09:15] <mborzecki> re
[09:16] <pedronis> mborzecki: hi, is #9201 still a draft or should I re-review it?
[09:16] <mup> PR #9201: boot: observe update & rollback of trusted assets <UC20> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9201>
[09:16] <mborzecki> pedronis: i converted it to non-draft
[09:17] <mborzecki> pedronis: would appreciate if you could take a look, and maybe we can discuss things if needed
[09:17] <pedronis> ok
[09:21] <mborzecki> mvo: can you force merge https://github.com/snapcore/snapd/pull/9218 ? the failure on 18.04 is unrelated
[09:21] <mup> PR #9218: tests: running tests on opensuse leap 15.2 <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/9218>
[09:25] <mvo> mborzecki: sure
[09:25] <mvo> mborzecki: also reviewed/approved the other pr
[09:26] <mborzecki> mvo: thanks!
[09:26] <mup> PR snapd#9218 closed: tests: running tests on opensuse leap 15.2 <Created by sergiocazzolato> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/9218>
[09:44] <pstolowski> pedronis: Ian's fix didn't help with my issue with snap-logs, probably makes sense if you wait till i figure out what's going on
[09:55] <pedronis> pstolowski: ok, it wasn't yet at the top of my queue anyway
[10:00] <pstolowski> ha https://pastebin.ubuntu.com/p/v9G8ZMsw2c/
[10:01] <pstolowski> journalctl seems to be skipping messages if we ask for multiple units
[10:28] <mborzecki> macos github job failing?
[10:34] <mborzecki> huh https://github.com/snapcore/snapd/runs/1041031007
[10:35] <mborzecki> go get golang.org/x/sys/unix apparently fails there
[10:39] <ijohnson> morning folks
[10:40] <ijohnson> anybody have any ideas why I would be getting `cannot install "generic-classic" fallback model assertion: no matching public key "Lcw4MOHeD6yUabUqD_Gd5BwBGuJBB6t8jDV42wg02jv5XikFZoe6CBMJAo5pTbrW" for signature by "generic"` for unit tests I didn't change in o/devicestate ?
[10:40] <ijohnson> pedronis: maybe ^ ?
[10:56] <pstolowski> hi ijohnson
[10:57] <ijohnson> hey pstolowski
[10:57] <ijohnson> more fun with journald I see ?
[10:57] <pstolowski> ijohnson: yes
[10:58] <ijohnson> the fun never ends!
[11:01] <pedronis> ijohnson: where is that?  it seems an assertion db not configured right
[11:01] <ijohnson> pedronis: it comes from the firstBoot16Suite.TestPopulateFromSeedOnClassicNoop unit test
[11:02] <ijohnson> this only happens when I enable my 2nd suite in devicestate_cloudinit_test.go for uc20 variants
[11:02] <ijohnson> where my uc20 suite inherits from the devicemgrbasesuite
[11:02] <pedronis> ijohnson: ok, something is not cleaning up correctly I suppose
[11:03] <ijohnson> pedronis: what's most confusing is that I have tried even deleting all of the setup code from my uc20 suite, and simply calling the device mgr base suite setup is enough to trigger this other unit tests to fail
[11:03] <ijohnson> pedronis: do you want me to push a wip branch to look at the tests ?
[11:04] <pedronis> ijohnson: I suppose
[11:04] <ijohnson> one moment
[11:10] <ijohnson> pedronis: sorry still a wip commit, but here is my current branch: https://github.com/anonymouse64/snapd/commit/8c17373ac055a1d0ef90f99f3bc8a566ed594b95
[11:10] <ijohnson> pedronis: if you just run all the tests in o/devicestate you should see the issue with all of my various print statements
[11:10]  * ijohnson afk for quick breakfast
[11:15] <mborzecki> 2020-08-28T10:15:41.3077042Z - Fetch and check assertions for snap "test-snapd-content-plug" (5) (cannot fetch assertion: got unexpected HTTP status code 408 via GET to "https://api.snapcraft.io/api/v1/snaps/assertions/snap-revision/UzfhJIDc1A04xUNzbAEwvu2_aCeT3FxOvo5tsKFG2V9ZzssK_ZIaEiRAFh8RdNus?max-format=0")
[11:15] <mborzecki> pedronis: still getting 408 from time time apparently ^^
[11:15] <pedronis> yea
[11:27] <ijohnson> ok I'm back
[11:30] <mvo> pstolowski: 9211 looks good, please let me know if you need a force-merge or if the spread issues are real
[11:39] <ijohnson> mvo: could I ask for your super powers on https://github.com/snapcore/snapd/pull/9225#issuecomment-682478359 ?
[11:39] <mup> PR #9225: many: cloud-init cleanups from previous PR's <Cleanup :broom:> <Run nested> <Simple 😃> <Test Robustness> <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/9225>
[11:39] <ijohnson> the comment I just linked to explains the various spread failures, some of which are already fixed in master
[11:39] <ijohnson> none of which are related to the PR in question
[11:44] <ijohnson> huh I think the issue I was having is that my cloudInitUC20Suite embedded the cloudInitBaseSuite struct, which embeds the deviceMgrBaseSuite, and so it inherited a SetUpTest from that, but then I also called setup on deviceMgrBaseSuite again separately, so setting my test up twice caused a different test to fail
[11:45] <ijohnson> pedronis: ^
[11:46] <pstolowski> mvo: yes i think you can merge
[11:46] <pedronis> ijohnson: yes, I see some setup being run twice, is that the problem though?
[11:47] <ijohnson> pedronis: I am not 100% sure, but I am going to try with a small patch on master to see if I can reproduce with just calling deviceMgrBaseSuite's setup twice on a single test
[11:47] <pedronis> ijohnson: anyway fwiw the line that is causing trouble is 	s.AddCleanup(sysdb.MockGenericClassicModel(s.storeSigning.GenericClassicModel))
[11:47] <ijohnson> yes
[11:48] <ijohnson> sorry I meant interesting
[11:48] <pedronis> it seems is not undone properly ?
[11:48] <ijohnson> hmm
[11:49] <pedronis> ah
[11:49] <pedronis> it's funny probably
[11:49] <pedronis> in a terrible sort of funny way
[11:49] <pedronis> let me see if I'm right
[11:58] <pedronis> ijohnson: yes, the issue is the double setup, the problem with that is among other things that the first setup is never undone, because the 2nd setup will simply reset the cleanup function list
[11:59] <ijohnson> pedronis: hmm that's weird, should we fix that ?
[12:01] <pedronis> ijohnson: I don't know if it's weird or not, it's one way to implement this, you need to stare at testutils/base.go
[12:02] <ijohnson> uhh
[12:02] <ijohnson> AddCleanup just appends the handlers, so the handler should just get called even if it's appended twice ?
[12:02] <ijohnson> oh I wonder if it's called in the wrong order
[12:02] <ijohnson> maybe AddCleanup should be a stack
[12:02] <pedronis> well, the order is weird as well
[12:02] <pedronis> but that's the problem
[12:02] <ijohnson> *use
[12:02] <pedronis> your second setup
[12:02] <pedronis> calls the BaseTest.Setup
[12:03] <pedronis> that's just forgets everything
[12:03] <ijohnson> ahhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh
[12:03] <ijohnson> yes you're right
[12:03] <ijohnson> I see it now
[12:03] <pedronis> SetUpTest is not really intended to be called twice
[12:03] <pedronis> in general I mean
[12:03] <ijohnson> yes, I'm not sure how I accidentally got to that point
[12:04] <ijohnson> but I think it's clear to me that as long as we don't use BaseTest.SetUpTest twice things are fine
[12:04] <ijohnson> so that was my original problem
[12:04] <pedronis> yes
[12:04] <ijohnson> ok, good to know
[12:04] <pedronis> but I agree that the order we call the cleanup is weird
[12:04] <pedronis> it should be a stack
[12:04] <ijohnson> I will fix up this commit and open the PR shortly
[12:04] <pedronis> I don't know why is like that
[12:04] <ijohnson> probably just because it was easy
[12:04] <ijohnson> last change to that file was 4 years ago
[12:05] <pedronis> anyway I don't think SetUpTest should need to cleanup the handlers, is not a map, otoh maybe it should panic if the handlers are not empty already
[12:06] <ijohnson> I like that change a lot actually
[12:06] <ijohnson> would have made it super obvious my error very quickly
[12:06] <pedronis> maybe I should try to do that in a separate PR and fix the order, and see if anything breaks
[12:06] <ijohnson> I will propose that in a separate PR I think
[12:06] <pedronis> or you can
[12:06] <ijohnson> well I will work on that after opening the cloud-init PR
[12:06] <ijohnson> so if you want to do it first go for it
[12:08] <pedronis> ok, I'll try to do that just now
[12:12] <pedronis> ijohnson: we have some tests that fail interestingly
[12:12] <cachio> zyga, hi
[12:12] <zyga> hi
[12:12] <ijohnson> oooh fun
[12:12] <ijohnson> morning cachio and zyga
[12:12] <zyga> nice find on non-stack cleanup for base test
[12:12] <cachio> ijohnson, good morning
[12:12] <zyga> and the related issues
[12:13] <zyga> maybe base test should panic if invoked incorrectly
[12:13] <pedronis> ijohnson: one is cloud init, was the problem already on master?
[12:13] <cachio> zyga, yesterday implented what you sent and that works, the session is created
[12:13] <ijohnson> pedronis: no, there shouldn't any problems on master
[12:13] <ijohnson> well I don't think so
[12:13] <cachio> zyga, during the test the sesions is there
[12:13] <ijohnson> pedronis: what test failed ?
[12:13] <pedronis> ijohnson: well it's panicing
[12:13] <ijohnson> err how did it fail
[12:14] <cachio> zyga, but still fails when we do "systemctl --user daemon-reload"
[12:14] <pedronis> well I added code to panic if cleanup handlers are not empty in setup
[12:14] <pedronis> what I said before
[12:14] <ijohnson> :-(
[12:14] <ijohnson> ok, I will have a look
[12:14] <zyga> cachio what do you mean "fails", what fails when you do this?
[12:15] <cachio> zyga, 1 sec
[12:15] <pedronis> ijohnson: I see issues with repair, something in cmd/snap (just one test, that is weird)
[12:15] <pedronis> and then quite a few in devicestate
[12:15] <pedronis> the rest is fine
[12:17] <cachio> zyga, https://paste.ubuntu.com/p/PPYFgSQy69/
[12:17] <cachio> fail like this
[12:17] <zyga> cachio before the failure, do we still have the seesion?
[12:17] <cachio> zyga, yes
[12:17] <zyga> are you absolutely sure?
[12:18] <cachio> when it fails we have the session in the debug session
[12:18] <zyga> the root session?
[12:18] <cachio> yes
[12:18] <zyga> can you check the status of<EMAIL_ADDRESS>[12:18] <cachio> zyga, sure
[12:19] <ijohnson> pedronis: I don't understand how, but if I make cloudInitSuite embed a pointer to deviceMgrBaseSuite and initialize that pointer in cloudInitSuite.SetUpTest, then the panic goes away
[12:19] <ijohnson> pedronis: I have seen other test suites that inherit base suites do that too, so perhaps that's the thing to do
[12:20] <ijohnson> otoh, I have seen the pattern of not defining SetUpTest for the base suite, and instead having something like setup() for the base suite which needs to be called from the final suite's SetUpTest
[12:21] <pedronis> ijohnson: so some tests call SetUpTest on their own, fun
[12:21] <pedronis> without TearDown
[12:21] <ijohnson> ugh what
[12:22] <ijohnson> I'm still confused how this happens for i.e. the cloudInitSuite since we aren't manually calling SetUpTest there
[12:22] <pedronis> well, I'll have to stare it myself in a bit
[12:23] <ijohnson> ok, well we know how to make the panic's go away
[12:23]  * ijohnson returns to prepping the cloud-init PR
[12:24] <cachio> zyga, https://paste.ubuntu.com/p/vvxJCWCr67/
[12:24] <zyga> cachio and systemctl --user status
[12:25] <zyga> (note: assuming this is invoked by root)
[12:25] <zyga> not by the external user
[12:25] <cachio> Failed to connect to bus: No such file or directory
[12:25] <zyga> strace -f systemctl --user status
[12:25] <zyga> and check which connect fails
[12:27] <cachio> I am in core16
[12:27] <cachio> dont have strace
[12:27] <cachio> is there an y snap instead?
[12:27] <zyga> we have strace static
[12:27] <zyga> try that
[12:29] <cachio> this is hte output https://paste.ubuntu.com/p/KjKMz6s5g9/
[12:30] <zyga> cachio run strace-static directly, not as a snap please
[12:31] <cachio> https://paste.ubuntu.com/p/w5krDr87Np/
[12:32] <cachio> like that?
[12:34] <zyga> no
[12:34] <zyga> that's not any different
[12:34] <zyga> directly without snap run pipeline
[12:38] <cachio> zyga, https://paste.ubuntu.com/p/VGQYZKsXP5/
[12:39] <zyga> open("/sys/fs/kdbus/1001-user/bus", O_RDWR|O_NOCTTY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
[12:39] <zyga> this is not running as root for real
[12:39] <zyga> are you logged in as the external user?
[12:39] <cachio> https://paste.ubuntu.com/p/t3sHWqj9CC/
[12:40] <cachio> we login as external
[12:40] <zyga> using sudo / su will again bring back the same issues
[12:40] <zyga> it's not the same
[12:40] <zyga> as logging in as root
[12:40] <cachio> through ssh
[12:40] <cachio> then we make sudo to run the test script
[12:40] <zyga> hmm?
[12:40] <zyga> we cannot do that
[12:40] <cachio> so we should run with runuser?
[12:40] <zyga> we must use what I provided to run the script
[12:40] <zyga> runuser won't work directly
[12:41] <zyga> do you understand what the problem is?
[12:41] <cachio> partially
[12:41] <zyga> the script cannot run in the session of the external user which just happens to elevate to root
[12:41] <zyga> our tests do not cope with that
[12:42] <zyga> my suggestion was to run the whole test this way
[12:42] <zyga> "this way" is the way we talked about yesterday, with the service and pam name
[12:42] <zyga> this then runs in an environment very similar to root ssh-ing into the system
[12:43] <zyga> cachio perhaps we can log in as external
[12:43] <zyga> install a ssh key for root
[12:43] <zyga> and then go back to running as root
[12:43] <cachio> is it possible to do that in core syste?
[12:43] <cachio> to add a ssh key for root?
[12:44] <zyga> can you write to /root/.ssh/?
[12:44] <zyga> if so then yes
[12:44] <zyga> I mean...
[12:44] <zyga> root is not read only :D
[12:45] <cachio> zyga, but to connect to the system  using spread a password we need for root
[12:46] <cachio> because spread just connects using password
[12:46] <zyga> something has to change
[12:46] <zyga> what we have doesn't work
[12:46] <zyga> we just need to pick the most sensible thing to alter
[12:47] <cachio> zyga, so
[12:47] <cachio> some time ago I did a change
[12:47] <cachio> in sporead to support connecting using ssh keys
[12:47] <cachio> if we could add that to spread we could connect using root
[12:47] <cachio> and the problem is solved
[12:48] <cachio> right?
[12:48] <zyga> if we can connect as root over ssh then yes
[12:48] <zyga> however that is done
[12:48] <zyga> cachio could we hack it like this?
[12:48] <zyga> add an extrauser
[12:48] <zyga> root-with-password
[12:48] <zyga> have it have uid 0
[12:48] <zyga> and home /root
[12:49] <zyga> but have a password?
[12:49] <cachio> we need password for spread
[12:50] <zyga> right, but isn't that what I just said?
[12:52] <cachio> I though it was a question
[12:52] <zyga> cachio?
[12:53] <cachio> 1 sec
[12:55] <cachio> can do that
[12:55] <cachio> Warning: The home dir /root you specified already exists.
[12:55] <cachio> adduser: The UID 0 is already in use.
[12:57] <zyga> cachio you can add it as another uid
[12:57] <zyga> and just sed it to zero
[12:57] <zyga> it's just the tool that complains
[12:58] <cachio> zyga, cant create the home /root
[12:58] <cachio> because it already exists
[12:58] <zyga> use whatever directory and edit the created user
[12:58] <zyga> you can just edit the text file
[12:59] <zyga> you can even just append to
[13:02] <mup> PR snapd#9237 opened: [RFC] many: enable cloud-init on uc20 for grade signed and secured <Complex> <Run nested> <UC20> <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/9237>
[13:03]  * zyga will go AFK in about 10 minutes
[14:04] <mborzecki> errands, bbl
[14:23] <pedronis> ijohnson: so on master things are clean for me now
[14:23] <pedronis> devicestate was in a very messy state though
[14:32] <mup> PR snapd#9225 closed: many: cloud-init cleanups from previous PR's <Cleanup :broom:> <Run nested> <Simple 😃> <Test Robustness> <Created by anonymouse64> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/9225>
[14:39] <cachio> ijohnson, is this the same error you fixed a time ago for uc20-recovery test? https://paste.ubuntu.com/p/C94XTPBTWG/
[14:40] <ijohnson> cachio: could be, will look in little bit
[14:55]  * cachio lunch
[14:55] <ijohnson> pedronis: so are you going to prepare a PR to make the panic change ?
[14:55] <pedronis> ijohnson: yes, about to propose it actually
[14:55] <ijohnson> pedronis: also if you could give a quick review to #9237 on the general direction and options names and such I can split it up
[14:55] <mup> PR #9237: [RFC] many: enable cloud-init on uc20 for grade signed and secured <Complex> <Run nested> <UC20> <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/9237>
[14:55] <ijohnson> thanks
[14:56] <ijohnson> I guess names of things can be separate PR's but the overall interaction between devicestate and sysconfig.ConfigureRunSystem via the options is more what I'm curious about
[14:56] <pedronis> ijohnson: I have a meeting now but I'll try to look after
[14:57] <ijohnson> k, thanks
[14:57] <pedronis> ijohnson: https://github.com/snapcore/snapd/pull/9238 is the PR, likely it might conflict with yours
[14:57] <mup> PR #9238: many: check that users of BaseTest don't forget to consume cleanups <Created by pedronis> <https://github.com/snapcore/snapd/pull/9238>
[14:57] <mup> PR snapd#9238 opened: many: check that users of BaseTest don't forget to consume cleanups <Created by pedronis> <https://github.com/snapcore/snapd/pull/9238>
[14:57] <ijohnson> pedronis: sure no problem, the RFC one won't be mergable right away unless one big PR review is easiest
[15:07] <mup> PR snapd#9239 opened: many: misc doc-comment changes and typo fixes <Simple 😃> <Skip spread> <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/9239>
[15:11] <pstolowski> pedronis: your hunch about systemd & my --root change was good... this is peculiar: https://pastebin.ubuntu.com/p/yMXYd93ZQZ/
[15:14] <pstolowski> also funny how the message is slightly different
[15:16] <ijohnson> pedronis: I de-conflicted things so that #9237 doesn't need your PR and doesn't conflict with it afaict and updated the PR description to reflect this
[15:16] <mup> PR #9237: [RFC] many: enable cloud-init on uc20 for grade signed and secured <Complex> <Run nested> <UC20> <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/9237>
[15:16] <pstolowski> the basic problem is we set rsyslog in gagdet defaults (which makes no sense on core18 but because of emulation mode), but then we fail on normal "snap set.. ", but that was masked with --root=.. as my pastebin demonstrates, because it prints error but gives exit 0
[15:17] <ijohnson> pstolowski: bash exit codes strike again?
[15:17] <pstolowski> ijohnson: what about bash exit codes?
[15:17] <mup> PR snapd#9240 opened: o/devicestate/devicestate_cloudinit_test.go: test cleanup for uc20 cloud-init tests <Simple 😃> <Skip spread> <Test Robustness> <UC20> <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/9240>
[15:17] <ijohnson> pstolowski: you said "because it prints error but gives exit 0"
[15:18] <pstolowski> ijohnson: see https://pastebin.ubuntu.com/p/yMXYd93ZQZ/
[15:18] <ijohnson> just curious if that was related to all the random bash issues that zyga has discovered recently
[15:18] <pstolowski> ijohnson: ah got you. no it's not bash, it' ssytemctl behavior
[15:18] <ijohnson> ah great
[15:18] <ijohnson> that's so silly
[15:18] <pstolowski> ijohnson: note the slightly different spelling of the error message...
[15:18] <ijohnson> --root=/ makes it exit with code 0 and not that option makes it exit with code 1
[15:19] <pstolowski> yet it means the same
[15:19] <ijohnson> oh ffs
[15:19] <ijohnson> that's ridiculous
[15:21] <pstolowski> "error but not really"
[15:26] <pstolowski> it's also the case on 20.04
[15:40] <ijohnson> mmm how do we do tests for grade signed images in spread with custom snapd snaps
[15:40] <ijohnson> because grade signed model assertions don't allow unasserted snaps
[15:40] <ijohnson> pedronis: thoughts ?
[15:43] <ijohnson> cachio: do you have more logs from that uc20-recovery failure? it seems that it should have gone back to run mode but it didn't so that seems like a real test failure
[15:47] <mup> PR snapd#9241 opened: tests: do not set rsyslog.disable in core18 config defaults test <Test Robustness> <Created by stolowski> <https://github.com/snapcore/snapd/pull/9241>
[15:47] <pstolowski> i see no other option than ^
[15:53] <pedronis> ijohnson: there is nothing easy we can do, what kind of modifications do you need?
[15:53] <pedronis> ijohnson: also I did a pass on #9237
[15:53] <mup> PR #9237: [RFC] many: enable cloud-init on uc20 for grade signed and secured <Complex> <Run nested> <UC20> <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/9237>
[15:54] <pstolowski> hmm i wonder if we should maybe ignore error on disable in configcore
[15:56] <pedronis> pstolowski: well, if I understand the issue is that we trying to disable a service that doesn't exist?
[15:57] <pedronis> and in that case --root makes a difference
[15:58] <pstolowski> pedronis: yes, we do that because test setup is wrong, but it is masked because with --root systemctl returns 0
[16:02] <ijohnson> pedronis: I'm trying to write a spread test of the grade signed cloud-init changes
[16:02] <ijohnson> pedronis: but how do I test grade signed with an unasserted custom snapd snap
[16:06] <pedronis> pstolowski: systemd seems to be using a special exit code to mean no unit
[16:07] <pedronis> but is not consistent
[16:07] <pstolowski> pedronis: yes
[16:08] <zyga> back from PT
[16:08] <zyga> I need to catch up and cover this time, I'll be here for a few hours at least
[16:09] <pedronis> ijohnson: we can only write a test using store snaps , so I'm asking what changes do we need?  otherwise we can have a chat but the solutions are slightly horrible
[16:10] <ijohnson> pedronis: well if we accept that we can only write cloud-init spread tests for grade signed, then we don't need any changes
[16:10] <ijohnson> pedronis: it just means that getting all the bits correct for uc20 cloud-init will take more time as I can't verify anything with an integration test
[16:10] <pedronis> I can't parse that sentence
[16:11] <ijohnson> pedronis: sorry let me rephrase
[16:11] <ijohnson> pedronis: I would like to write a spread test like we have for uc16/uc18 cloud-init but for grade==signed uc20
[16:11] <ijohnson> pedronis: but I can't write this spread test today because there is no snapd snap in the store with my changes I made
[16:11] <zyga> cachio any luck?
[16:11] <pedronis> ijohnson: can we have a quick chat?
[16:11] <ijohnson> pedronis: sure
[16:12] <ijohnson> pedronis: I'm in SU HO
[16:12] <pedronis> pstolowski: it seems that systemctl status foo uses exit code 4 when the unit is not there, maybe we should teach systemd.Status to detect that and then use Status in the loop to know if a service exits at all
[16:13] <pedronis> ans just skip doing anything with it
[16:13] <pedronis> if it doesn't
[16:13] <pstolowski> pedronis: to be clear about systemctl issue, this is not about emulation mode (we use it when we should); this is about running for real, per man page the mere presence of --root bypasses systemd (and apparently changes semantics of error code)
[16:14] <pstolowski> pedronis: yeah, probably
[16:14] <pedronis> yes, that's why I'm suggesting something slightly complicated
[16:14] <pedronis> I don't think we want to just ignore errors without understanding them
[16:14] <pstolowski> fair point
[16:18] <pstolowski> i'll address this on monday, thanks
[16:18] <pstolowski> have a great weekend everyone!
[16:54] <cachio> ijohnson, hey, do you know if there was any change that could produce this cd: /home/gopath/src/github.com/snapcore/snapd/tests/core/uc20-recovery: No such file or directory
[16:54] <cachio> I think it is the first thing you fixed
[16:54] <cachio> for this test
[16:58] <ijohnson> cachio: I asked earlier before you disconnected
[16:58] <ijohnson> cachio: do you have more logs from that run ?
[16:59] <cachio> no, but I can reproduce it
[16:59] <ijohnson> cachio: what seems to have happened is a real test failure, where we went to reboot and should have gone back to run mode, but we didn't and went back to recover mode
[16:59] <ijohnson> cachio: if you could get me the full system journal that would be great
[16:59] <cachio> and give you a shell there
[16:59] <ijohnson> I need to go break for lunch now, but will be back in a little bit to debug this further with you
[16:59] <cachio> ijohnson|lunch, sure
[17:07] <pedronis> #9201 needs 2nd reviews
[17:07] <mup> PR #9201: boot: observe update & rollback of trusted assets <UC20> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9201>
[17:17]  * zyga grabs coffee
[17:51] <ijohnson> pedronis: yes I can take a look, also should I look at the cups PR again today ?
[17:54] <pedronis> ijohnson: if you can (abou cups)
[17:54] <ijohnson> pedronis: sure
[17:57] <cachio> ijohnson, I have an instance ready
[17:57] <cachio> ijohnson, which already failed
[17:58] <cachio> you need to be connected to the vpn
[18:52] <pedronis> cmatsuoka: ijohnson: do you need anything more from me today?
[18:52] <ijohnson> pedronis: no I'm good
[18:52]  * ijohnson is staring at fakestore
[18:52]  * ijohnson to some useful effect however
[19:10] <cmatsuoka> pedronis: I'm trying the bootloader chain composition but found some problems
[19:11] <cmatsuoka> pedronis: mainly related to being unable to, after composing the run mode chain, map entries to the asset cache
[19:11] <cmatsuoka> (because we don't know from the final chain which parts came from each bootloader)
[19:12] <cmatsuoka> in my previous implementation I was doing this mapping before composing the run mode chain
[19:13] <cmatsuoka> I could do the same thing but it seems to me that the bootloader shouldn't be cache-aware
[19:14] <cmatsuoka> anyway, I'll think a bit about the in-between degraded upgrade states before returning to the boot chains
[19:24] <pedronis> cmatsuoka: I see two approaches to that we include the root path in the assets names then you can find which partition/bootloader they belong to from that, or we return just names (that is what we need) and have a separate flag/marker to know which role/partition they are on
[19:25] <cmatsuoka> pedronis: just the name with an origin mark should solve it
[19:25] <cmatsuoka> pedronis: thanks
[21:04]  * cachio afk


[10:42] <jbailey> doko: around?
[10:42] <doko> jbailey: yes
[10:43] <jbailey> doko: I think you told me you had gcc-4.1 binaries hanging out somewhere.
[10:43] <jbailey> I'm wondering if I can have them. =)
[10:45] <doko> jbailey: I told you that in February ;-P
[10:46] <jbailey> That's probably why I'm not finding it in my grep, I usually only look in recent dates.
[10:46] <doko> jbailey: apt-get install gcj-4.1
[10:46] <jbailey> And that'll bring in gcc silently? =)
[10:46] <doko> yes
[10:46] <jbailey> luvly, thanks
[10:48] <jbailey> Oh right.
[10:48] <jbailey> I even had it installed already.
[10:48] <jbailey> *sigh*
[10:56] <doko> jbailey: you don't need g++, correct?
[10:56] <jbailey> Correct.  g++ is only used for ABI testing.
[10:56] <jbailey> 4.0 will do.
[10:57] <jbailey> Thinking of which, libstdc++-v7 is on the LSB agenda.
[10:57] <jbailey> Have they announced that this is going to show up eventually?
[10:57] <doko> no, not on the libstdc++ list. do you have pointers?
[10:58] <jbailey> http://www.freestandards.org/en/LSB_Summit
[10:58] <jbailey> Just there.
[10:58] <jbailey> It's a call I've been on all day and will be on tomorrow.
[10:58] <jbailey> They didn't really go into it, but I was wondering if it was based on some announcement that I had missed.
[11:03] <doko> ahh, you participated?
[11:03] <doko> so tell me about libstdc++-v7 ...
[11:04] <doko> are there streams available from the call?
[11:07] <jbailey> There are supposed to be.
[11:07] <jbailey> But they didn't say anything about it specifically.
[11:07] <jbailey> They just ranted a bit about ABI changes and said that they were goign to keep the C++ interfaces out of the ISO standard.
[11:09] <doko> anyway, as long as ISV's still ship libstdc++5 based stuff ...


[16:40] <wildmanne39> hi elfy what do you think of this thread for conversion http://ubuntuforums.org/showthread.php?t=1132821 is it on bordering against forum policy?
[16:40] <elfy> we should ask ibuclaw to do it perhaps - but PM him :)
[16:41] <elfy> doubt it is against forum policy - I remeber bodhi getting ibuclaw to write it :)
[16:42] <wildmanne39> so I should add it then pm him?
[16:42] <wildmanne39> to the import page
[16:43] <elfy> yea - I almost have a couple if times and then forgotten
[16:43] <wildmanne39> I will do it now thanks
[16:43] <elfy> hang on
[16:43] <elfy> https://help.ubuntu.com/community/Sudoers
[16:44] <elfy> no need - add and edit perhaps if you can
[16:45] <elfy> I wonder if a - "There's this tute and this wiki already - should the tute be closed" page in our armoury
[16:47] <wildmanne39> I think they are 2 different guides, and I was going to link to the wiki that you posted when I converted it
[16:48] <elfy> mmm - should they be different?
[16:49] <wildmanne39> not sure that is what makes picking threads so hard
[16:49] <elfy> lol
[16:50] <elfy> I tend to look every couple of days and see what's been moving
[16:50] <elfy> I also get to see the ones that are still in the moderation queue
[16:51] <wildmanne39> I am trying to compare the two line by line right noe
[16:52] <wildmanne39> now
[16:55] <elfy> perhaps talk to ibuclaw about it - think of a name - advancedsudoers or something and do as you thought
[16:55] <wildmanne39> it is very close to the same
[16:56] <elfy> perhaps then we just need to add the extra
[16:56] <wildmanne39> I think I will pm him and ask his opinion
[16:57] <elfy> k - makes sense
[16:57] <wildmanne39> should I wait to add it to the import page?
[16:57] <elfy> yea
[16:58] <wildmanne39> do you find that it is harder to find pages to convert then it is to convert them?
[16:58] <elfy> yep
[16:58] <elfy> lots of old stuff and less than wiki worthy
[16:58] <wildmanne39> we need to start adding he rejected ones to the rejected page
[16:59] <elfy> I think that issue needs to be talked about - what to do with things that should be wikified - but don't need a whole page
[16:59] <elfy> wildmanne39: +1
[17:00] <wildmanne39> I agree and it is hard to know what needs to be when only small bits of information needs to be added
[17:01] <elfy> yea
[17:01] <wildmanne39> thank you
[17:01] <elfy> it is nice to see the import page filling with new wiki's :)
[17:04] <wildmanne39> yes it is, one of the pages that I had put on the import page to be wikified I looked at it yesterday because someone had created a wiki out of it while I was out of town but they left it as the script imported it and it was a mess or it may have been the author of the thread not sure but I fixed it
[17:05] <elfy> thank you :)
[17:06] <elfy> I've got to go again - cya over weekend perhaps
[22:41] <wildmanne39> when considering threads for conversion should we consider threads that are aimed at one particular laptop?
[23:56] <bodhi_zazen> how old wildmanne39 ?
[23:57] <wildmanne39> bodhi_zazen, 6 months covers 11.10
[23:57] <wildmanne39> pretty sure works with 12.04 too
[23:57] <bodhi_zazen> link please
[23:57] <bodhi_zazen> I will look
[23:57] <bodhi_zazen> There is a hardware tag for the wiki
[23:57] <wildmanne39> http://ubuntuforums.org/showthread.php?t=1867367
[23:59] <wildmanne39> I am not sure that laptop only uses one wireless card though
[23:59] <bodhi_zazen> Looks reasonably up to date and complete


[00:07] <mparillo> Is this still the case? System Tray Icons cannot be re-ordered? https://www.reddit.com/r/kde/comments/4rolzw/customize_the_order_of_system_tray_icons/
[05:39] <naruu> Hi. Is this a known bug: I login, then logout, login again. Then the kwallet is unable to open and asking endless for the password.
[05:50] <valorie> naruu: I've not heard anyone else mention this
[05:54] <naruu> I'm trying to switch back to KDE since Kubuntu 15.10. Every release had this bug.
[05:57] <naruu> How can I debug this bug?
[06:01] <naruu> So now I've done this again. Login, logout, login again and the problem is showing up again: Error message is: The program "akonadi_googlecontacts_resource_0" has requested opening kdewallet.
[06:01] <naruu> Now when I enter the password I get error code -9.
[06:05] <valorie> def. sounds like a bug, naruu
[06:06] <naruu> Yes. This bug is in all versions of KDE plasma I've tested.
[06:06] <naruu> It drives me crazy
[06:06] <naruu> How can I debug this?
[06:07] <naruu> Because I have to reboot the system to get rid of this endless password questioning
[09:45] <auie> Helle everybody :-)
[09:45] <auie> I mean "Hello"
[09:47] <acheronUK> auie: hi
[09:48] <auie> Please, would you suggest something against blank screen after booting Kubuntu 14.04? I've been searching in the Internet and only found solutions which change the modeset of the grub. This works. I no longer have blank screen BUT I can no longer hibernate. Please would you have a suggestion ? :-)
[09:59] <oquidave> Hello how it is possible that I can ping a host, but when I traceroute, I only see stars?!! https://dpaste.de/VbFY what does mean exactly? Thanks
[10:42] <BluesKaj> Hey folks
[10:44] <Guest34377> oquidave: try sudo traceroute -I <IP_ADDRESS>
[10:45] <Guest34377> BluesKaj: hi! how are you?
[10:45] <oquidave> Guest34377: same story. could some ISPs block traceroute probes on their network? Bse I can do a traceroute on another link
[10:46] <BluesKaj> hi Guest34377 , ...do I know you by a different nick?
[10:46] <Guest34377> oquidave: i'm not an expert here, sorry
[10:48] <Guest34377> BluesKaj: no. i just wanted to greet a Kubuntu maintainer, because i use Kubuntu. so, thank you
[10:50] <BluesKaj> Guest34377,  well thanks , but I'm a Kubuntu tester , not a maintainer, but i appreciate the thought
[10:52] <Guest34377> BluesKaj: well, that's a part of maintaining, isn't it?
[10:52] <BluesKaj> oquidave,  some sites have more security against IP probes than others, basically
[13:46] <user|39806> Can i upgrade from 16.04 ubuntu to kubuntu 17.04 directly
[13:46] <user|39806> help please
[13:55] <acheronUK> user|39806: no, that sort of upgrade is not supported
[13:56] <acheronUK> you need to go 16.04 -> 16.10 - 17.04, or just do a fresh install from a 17.04 iso
[14:16] <user|39806> sure. Thank you so much for the prompt reply.
[14:16] <user|39806> cheers.
[14:20] <Irateroey> hello all
[14:20] <IrateRoey> BluesKaj, hey good morning!
[14:21] <IrateRoey> BluesKaj, so I rebooted with a livecd and tried to reinstall... I would like to remove the entire partition table from the m.2 drive on this desktop, but the crypto keeps on partition in use... how do I kill it?
[14:33] <lordievader[m]> IrateRoey: The crypto? What crypto? Luks?
[14:37] <bodhi> test kubuntu 17
[14:38] <bodhi> hello guys and girls
[14:38] <acheronUK> hi
[14:40] <bodhi> anyone of us had problems with nvidia driver?i have dual microsoft and nvidia
[14:40] <bodhi> when i change to nvidia the system crash
[14:41] <bodhi> to restart i kill t with the power buttonhe system
[14:41] <bodhi> button
[14:49] <BluesKaj> bodhi,  run, lspci | grep VGA in the konsole, then paste the out put here
[14:51] <BluesKaj> microsoft doesn't make graphics chips, it's most likely an intel /nvidia hybrid called optimus if this is a laptop
[14:52] <BluesKaj> bodhi, ^
[15:44] <viewer|15741> Hi.
[15:44] <viewer|15741> a quick help please
[15:44] <viewer|15741> i just installed kubuntu 17.04
[15:44] <BluesKaj> ask your question
[15:44] <viewer|15741> internet is not working
[15:44] <viewer|15741> though status showing as connected
[15:45] <BluesKaj> ethernet or wifi?
[15:45] <viewer|15741> tried both
[15:45] <viewer|15741> now connected to eathernet
[15:46] <BluesKaj> run sudo dhclient ,then try your bowser
[15:47] <BluesKaj> browser
[15:47] <viewer|15741> ok. let me try that out
[15:49] <viewer|15741> sorry that din worked
[15:49] <viewer|15741> any other solutions please
[15:50] <lordievader[m]> viewer|15741: Could you pastebin the output of 'ip a s' and 'ip r' please?
[15:51] <BluesKaj> can you ping google.com?
[18:26] <viewer|9787> KUbuntu wifi or eathernet has connected but, no internet
[18:26] <viewer|9787> can anyone help me to fix
[18:27] <lordievader[m]> viewer|9787: Could you provide the info I asked for?
[18:28] <viewer|9787> can u post the query again. Am sorry, current tab got refershed
[18:30] <lordievader[m]> viewer|15741: Could you pastebin the output of 'ip a s' and 'ip r' please?
[18:31] <viewer|9787> sure.
[18:47] <viewer|9787> its in the different system
[18:47] <viewer|9787> i wont be able to pate those directly
[18:47] <viewer|9787> can u help me out, what exactly you need from that output
[18:47] <viewer|9787> ?
[18:49] <lordievader[m]> If you have an ip and if you have a default gateway.
[18:50] <viewer|9787> ok
[18:50] <viewer|9787> ?
[18:50] <lordievader[m]> Do you?
[18:53] <viewer|9787> https://thepasteb.in/p/WnhzoyoPmPJcV
[18:54] <viewer|9787> https://thepasteb.in/p/pghQ6x6yv2osR
[18:54] <viewer|9787> please have a look into these output
[18:55] <lordievader[m]> You have two different gateways for ethernet and wifi?
[18:55] <lordievader[m]> While you have no ip attached to your wifi nic.
[18:55] <viewer|9787> yes
[18:55] <viewer|9787> strange, one wifi is started working now
[18:56] <viewer|9787> and ethernet is still not working
[18:56] <viewer|9787> i tried restarting my router, then suddenly started working
[18:56] <lordievader[m]> Both do dhcp?
[18:57] <viewer|9787> yes.
[18:57] <lordievader[m]> Can you ping <IP_ADDRESS>
[18:57] <lordievader[m]> ?
[18:59] <viewer|9787> i tried, unfortunately no response
[19:00] <lordievader[m]> Does <IP_ADDRESS> respond?
[19:00] <viewer|9787> yes
[19:00] <viewer|9787> it is
[19:02] <lordievader[m]> Do you get a different ip if you disconnect and reconnect the ethernet cable?
[19:03] <viewer|9787> i havnt't checked yet. let me do that now
[19:03] <viewer|9787> yes
[19:03] <viewer|9787> it says
[19:04] <viewer|9787> <IP_ADDRESS>
[19:04] <viewer|9787> unreachable
[19:05] <lordievader[m]> What?
[19:05] <lordievader[m]> Where do you get that ip from?
[19:13] <viewer|9787> ethernet ip <IP_ADDRESS>
[19:14] <viewer|9787> wifi <IP_ADDRESS>
[19:15] <BluesKaj> working wifi has disbled ethernet i bet
[19:15] <viewer|9787> ok.
[19:16] <lordievader[m]> viewer|9787: Yes, so how do you get a 10.104.something address?
[19:16] <lordievader[m]> Where do you see that?
[19:16] <viewer|9787> sorry, i was pasted those from terminal
[19:17] <viewer|9787> i disabled wifi, and trying to connect eathernet
[19:17] <viewer|9787> still its not working
[19:17] <lordievader[m]> Both now have an ip in the 192.168.0.x range? Can you now ping <IP_ADDRESS>?
[19:18] <viewer|9787> sure
[19:18] <viewer|9787> yes am able to ping now
[19:19] <lordievader[m]> viewer|9787: Via ethernet (alone)?
[19:19] <viewer|9787> yes.
[19:19] <viewer|9787> via eathernet
[19:19] <viewer|9787> i completely disabled the wifi device
[19:20] <BluesKaj> try a browser
[19:20] <viewer|9787> though am unable to ping
[19:20] <viewer|9787> tried
[19:21] <lordievader[m]> viewer|9787: Can you ping <IP_ADDRESS>?
[19:21] <viewer|9787> sure
[19:21] <viewer|9787> done
[19:21] <viewer|9787> sucess
[19:22] <lordievader[m]> What is the result?
[19:22] <lordievader[m]> Does it respond? Do you get an unroutable? etc/
[19:22] <lordievader[m]> Ah, good.
[19:22] <lordievader[m]> What do you get when you issue 'dig A www.google.com'?
[19:23] <viewer|9787> 62 bytes from <IP_ADDRESS> icmp_seq=124.....
[19:23] <viewer|9787> yea, whats wrong with ma browser i donno
[19:24] <lordievader[m]> viewer|9787: We are getting to that, don't rush ahead ;)
[19:24] <viewer|9787> cool.
[19:24] <BluesKaj> you browser probly cached the 404
[19:24] <viewer|9787> ok.
[19:24] <BluesKaj> so it appear on next launch
[19:25] <BluesKaj> appears
[19:25] <lordievader[m]> viewer|9787: Did you run the dig command?
[19:25] <lordievader[m]> BluesKaj: I suspect the dns resolution fails.
[19:26] <viewer|9787> its says
[19:26] <viewer|9787> connection timedout
[19:26] <BluesKaj> users should setup dns IPs in their router , so many don't ...even thsir ISP IP DNS will do
[19:27] <lordievader[m]> viewer|9787: As I figured, your dns setup is broken.
[19:27] <viewer|9787> ohh i see
[19:27] <lordievader[m]> viewer|9787: Does 'dig @<IP_ADDRESS> A www.google.com' work?
[19:29] <viewer|9787> yea it worked
[19:30] <lordievader[m]> viewer|9787: Do you have access to your router administrative panel?
[19:30] <viewer|9787> no
[19:30] <viewer|9787> :(
[19:31] <viewer|9787> please give suggestions, so that i can inform these to my network admin
[19:31] <lordievader[m]> Hmm, oh well. Open NetworkManager, edit your ethernet (and/or wifi) connection, under the IPv4 tab set address to 'automatic (address only)'.
[19:32] <lordievader[m]> Add under DNS Servers '<IP_ADDRESS>' and hit ok.
[19:32] <viewer|9787> ok.
[19:32] <lordievader[m]> Reconnect the nic and you should be good to go.
[19:32] <viewer|9787> from ma pc?
[19:33] <viewer|9787> great
[19:33] <lordievader[m]> The one with issues.
[19:33] <viewer|9787> it worked
[19:34] <viewer|9787> thanks a ton
[19:34] <viewer|9787> may i know, what went wrong
[19:34] <viewer|9787> ?
[19:35] <lordievader[m]> Most likely the ISP dns server is down or something.
[19:35] <lordievader[m]> <IP_ADDRESS> is Google's open DNS resolver.
[19:35] <lordievader[m]> It is pretty much allways online.
[19:35] <viewer|9787> oh,,,
[19:36] <viewer|9787> i see
[19:36] <viewer|9787> thanks a ton, and all working fine
[19:36] <viewer|9787> :)
[19:37] <BluesKaj> adding the dns nameserver to /etc/network/interfaces file works too
[19:37] <lordievader[m]> No problem.
[19:37] <viewer|9787> great!
[19:38] <BluesKaj> namserver <IP_ADDRESS>
[19:38] <lordievader[m]> BluesKaj: Only if NM does not manage the interface ;)
[19:38] <viewer|9787> ok.
[19:39] <BluesKaj> nameserver even , lordievader[m] nm doesn't look at the interfaces file afaik , so it's like a backup dns
[19:39] <lordievader[m]> BluesKaj: You are talking about /etc/resolv.conf not /etc/network/interfaces ;(
[19:39] <lordievader[m]> ;)*
[19:40] <lordievader[m]> BluesKaj: It does, if a device is mentioned there NM does not manage it anymore.
[19:40] <BluesKaj> resolv.conf used to have that role, but that changed a few yrs ago
[19:41] <BluesKaj> anyway i get by without NM ,
[19:42] <viewer|9787> any idea, whenever i use wireless mouse and keyboard, it get stucks in between and evenytime i need to re-insert it again
[19:43] <viewer|9787> and system is also hanged ?
[19:45] <lordievader[m]> System is also hanged? As in freezes?
[19:45] <viewer|9787> yes
[19:47] <lordievader[m]> Could be a out-of-memory/swapping situation, hard to tell without any measurements.
[19:47] <viewer|9787> ok.
[19:47] <viewer|9787> i have done a fresh install
[19:48] <viewer|9787> and alloted good number for swap space while installing
[19:49] <lordievader[m]> Lots of swap space does not mean the system does not slow down if the kernel decides to swap out pages.
[19:50] <viewer|9787> yea got your point
[19:50] <viewer|9787> agree with it
[19:51] <lordievader[m]> So, grab a (h)top and check the memory usage around those times.
[19:51] <viewer|9787> ok i will do that
[19:52] <BluesKaj> debian still uses /etc/resolv.conf for dns entries, but kubuntu overwrites them to <IP_ADDRESS> in my case
[19:56] <lordievader[m]> NM usually starts a dnsmasq listening to that ip. I.m.o. dnsmasq is quite nice.
[20:06] <Bob99> Hi guys, I have Kubuntu 5.8.4 installed and backports added to ppa but it will not update to 5.8.6....  any suggestion?
[20:08] <angelkde1604lts> Bob99: http://www.kubuntu.org/news/plasma-bugfix-releases-frameworks-selected-app-updates-now-available-in-backports-ppa-for-zesty-and-xenial/
[20:11] <Bob99> thanks, did that and nothing is updated...
[20:15] <lordievader[m]> What version of Kubuntu are you running?
[20:16] <lordievader[m]> Bob99: ^
[20:17] <acheronUK> what is in the file? /etc/apt/sources.list.d/kubuntu-ppa-backports-xenial.list
[20:17] <acheronUK> assuming it exists
[20:18] <acheronUK> or are you on zesty and meant 5.9.4?
[20:38] <Bob99> 16.04
[20:39] <Bob99> stby I'll check
[20:46] <Bob99> https://thepasteb.in/p/3lh7NRzr6Lyu1
[20:57] <acheronUK> Bob99: and the result of 'sudo apt-get update && sudo apt-get dist-upgrade' ?
[20:58] <Bob99> Nothing...
[20:59] <Bob99> I'm thinking about reinstalling....
[21:01] <acheronUK> Bob99: just tested in a VM, and the package upgrades are there for me. odd
[21:01] <Bob99> it's weird...
[21:02] <acheronUK> no key errors when updating the sources with apt-get update?
[21:03] <acheronUK> does it show that ppa in the fetched urls?
[21:06] <Bob99> when I add the ppa, I get this: gpg: no ultimately trusted keys found
[21:07] <Bob99> https://thepasteb.in/p/r0hwJDZN059UK
[21:08] <acheronUK> that's not a problem
[21:09] <Bob99> https://thepasteb.in/p/KOh8prW36jlCJ
[21:09] <acheronUK> Bob99: 'plamsashell -v' give what?
[21:10] <acheronUK> Bob99: eek!
[21:10] <Bob99> command not found
[21:10] <acheronUK> that would make it not be able to update things!
[21:11] <acheronUK> I mistyped :P
[21:11] <acheronUK> but not the issue by the looks of that
[21:11] <Bob99> when I do plasmashell --version I get 5.8.4
[21:14] <acheronUK> what ownerships and permissions are on /var/lib/apt/lists/partial/ ?
[21:16] <Bob99> I just tried 'SU' and had "su: Authentication failure".... that's weird.... the sudo works....
[21:17] <acheronUK> very odd
[21:20] <Bob99> I really think I should reinstall...
[21:21] <Bob99> with the SU command, it's the same password as SUDO?
[21:22] <valorie> please don't use SU
[21:22] <valorie> that's root, rather than sudo
[21:22] <valorie> !sudo
[21:23] <valorie> SU can be very dangerous, and wreck permissions in the $HOME if used wrongly
[21:25] <Bob99> But it should be the same password?
[21:25] <acheronUK> should not be able to su by default in ubuntu anyway
[21:25] <acheronUK> nope. it's not
[21:27] <valorie> I would try that fixsudo page instructions before re-installing, Bob99
[21:27] <valorie> but that's just me
[21:29] <acheronUK> Bob99: maybe 'sudo rm -f /var/lib/apt/lists/partial/*'
[21:29] <acheronUK> if the content of that folder have got borked
[21:29] <Bob99> just remove the file....
[21:31] <acheronUK> also, although it should not make a difference, remove the multiple disabled line from your kubuntu-ppa-backports-xenial.list
[21:32] <Bob99> ok stby
[21:34] <acheronUK> remove the content of that folder, but not the folder, yes
[21:43] <Bob99> Ok, done but I do not know if it work or not.
[21:45] <Bob99> Thanks guys, I have to go, I'll figure it out later on.  Thank you for all the good advices.
[21:46] <Bob99> thx acheronUK
[21:46] <acheronUK> okaaaaaaay
[22:59] <metabolic> hi


[12:25] <ryanakca> how do you remove a remote bug watch thingy? ex: https://launchpad.net/products/amarok/+bug/64573 is watching the same remote bug twice
[12:25] <Ubugtu> Malone bug 64573 in amarok "Amarok crashes on iPod connection" [Unknown,Unknown]
[12:31] <mpt> Goooooooooooooooooooood morning Launchpadders!
[03:28] <jamesh> mpt: I did a bit of work on the new FormLayout stuff
[03:29] <jamesh> mpt: a few screenshots are here: https://devpad.canonical.com/~jamesh/images/
[03:30] <jamesh> the positioning of the textarea on formlayout-productseries-edit.png one looks a bit weird to me
[03:31] <jamesh> but maybe left aligning all the labels would fix that
[03:31] <jamesh> also, I am not sure where the "required" markers should go with this layout
[04:04] <mpt> jamesh, that looks very cool
[04:04] <mpt> well done!
[04:05] <mpt> You're right about the textarea
[04:05] <mpt> but I don't think there's any better solution
[04:06] <mpt> The usual solution should be to make the textarea either the first or the last field in the form.
[04:06] <mpt> So all the aligned elements are together, and all the textareas are together.
[04:09] <jamesh> The alignment of formlayout-new-distro-task.png also comes out a bit weird since the fields are laid out in two groups
[04:09] <jamesh> not sure how much of a problem that is though
[04:09] <jamesh> what do you think about placement of the "(required)" text though?
[04:12] <mpt> I think it should be removed, in favor of "Foo (optional):" labels for optional fields
[04:13] <mpt> see bug 39142
[04:13] <Ubugtu> Malone bug 39142 in launchpad "Checkboxes should not be flagged as 'required'" [Medium,Confirmed]  http://launchpad.net/bugs/39142
[04:14] <jamesh> alright.  Same question then: where do you think the "(optional)" labels should be placed?
[04:15] <mpt> "Foo (optional):"
[05:05] <Ubugtu> New bug: #66344 in blueprint "Dependency chart becomes unreadable with >12 dependencies" [Undecided,Unconfirmed]  http://launchpad.net/bugs/66344
[05:21] <Ubugtu> New bug: #66345 in blueprint "alt="" in dependency charts makes them poorly accessible" [Undecided,Unconfirmed]  http://launchpad.net/bugs/66345
[07:54] <stub> I think I'm going to do a full rollout - r4153
[07:54] <stub> (as long as malcc or cprov agrees - soyuz is running with local patches)
[08:29] <SteveA> morning
[08:30] <stub> Morning
[08:43] <stub> SteveA: Where are the navigation menus generated from now? I need to change the URLs they all point too
[08:57] <SteveA> which navigation menus?
[08:57] <SteveA> there are several
[08:57] <SteveA> ah, okay
[08:57] <SteveA> you'll need to also grep for absolute URLs starting with the paths you're changing
[08:58] <stub> There seem way to many places to change :-(
[09:01] <stub>  $ grep -R /malone/ .  | wc -l
[09:01] <stub> 131
[09:01] <SteveA> redirects should handle it if you miss any
[09:02] <SteveA> particularly if the redirects have logging
[09:04] <stub> There won't be a redirect for /malone, because that is a perfectly valid URL to the malone product under the new system
[09:07] <stub> So LaunchpadRootFacet handles the top level menu, bug URLs in the navigation and actions portlets in /+bugs still point to /malone/
[09:08] <stub> And I don't know what generates that popup menu at the top of the page either
[09:10] <lifeless> stub: have you just done an update ?
[09:10] <stub> of what?
[09:11] <lifeless> never mind
[09:11] <lifeless> (got a weirdness in malone)
[09:16] <mpt> stub, are you going to break URLs of the form https://launchpad.net/bugs/nnn?
[09:18] <SteveA> I think we should blacklist "bugs" to keep that working
[09:18] <stub> mpt: yup
[09:19] <mpt> SteveA, agreed
[09:19] <stub> The amazing mutating spec
[09:19] <mpt> There was a spec???
[09:19] <stub> Yup
[09:19] <stub> Although it didn't have URL changes at all on it originally ;)
[09:20] <mpt> That's something wrong with the spec process, perhaps
[09:20] <stub> Ok. So no tacking on UI changes to non UI specs after the non-UI spec has been implemented
[09:22] <mpt> Specs *should* mutate, otherwise for someone starting as a Launchpadder in five years, there will be no useful information outside of the code
[09:23] <mpt> unless that's an ok thing
[09:24] <stub> Nah - specs should be obsoleted, possibly by other specs being implemented (IMO)
[09:24] <mpt> Well, specs can (a) describe how a feature should behave, or (b) describe how something should be changed
[09:25] <mpt> Currently we have (b), so our specifications are glorified bug reports
[09:25] <stub> Specs describe work to be done (except for specs flags as informational), and are not documentation that needs to be maintained.
[09:25] <mpt> But without (a), it's harder to do QA, or to decide whether something is a bug.
[09:27] <lifeless> the best specs I've seen describe a state to reach
[09:27] <lifeless> *and*
[09:27] <lifeless> how to reach it
[09:27] <stub> You are talking about a Launchpadder in 5 years time. Unless the specs are treated as documentation and maintained in lockstep with code, QA using the spec is just silly. And specs should not be documentation, they should be a description of a task that was discussed, approved and implemented at a particular point in time.
[09:28] <mpt> I see only assertions in that paragraph :-)
[09:30] <stub> Specs should not be mutated, as then they stop being specs and become moving targets. You have no idea what is implemented, what will be implemented, what might be implemented, what was implemented.
[09:31] <stub> If you have one spec, you might have an answer to one of those. Or a very confusing spec that attempts to address two or more.
[09:31] <mpt> I don't think any of those particularly matter. What matters is whether there's a difference between what the spec says and what the code does.
[09:31] <mpt> Because that can be regarded as a bug in one or the other.
[09:32] <mpt> Otherwise you can't tell whether the divergence was because of design decisions made since the spec was approved, or because the developer was sloppy.
[09:33] <stub> We need a different term then. In most usage, a spec represents an agreed chunk of work generally in the context of someone implementing a spec. Changes to specs during implementation involve negotiation. And changes post signoff are irrelevant as the chunk of work is done.
[09:34] <mpt> So, I'm not a wizened software engineer, but I'm thinking of functional specifications
[09:34] <mpt> Are you thinking of a different kind?
[09:34] <stub> Same I think. But I don't see how a spec being implemented today can possibly be relevant in 5 years unless no work was done on that feature over that time.
[09:35] <stub> Once a spec is implemented, its only use is historical information and possibly finger pointing.
[09:35] <stub> If the feature needs to change, write a new spec.
[09:39] <mpt> Okay, that's great
[09:40] <mpt> because it greatly reduces the rationale for having a separate bug tracker and feature tracker :-)
[09:44] <stub> Use case would be a bounty on implementing a particular spec. The spec at the time the bounty was accepted is what counts, with changes a possibility through negotiation. And changes after signoff just represent destruction of historical record.
[11:07] <SteveA> mpt: ping
[11:07] <mpt> SteveA, pong
[11:08] <SteveA> skype call?
[11:08] <mpt> sure
[11:10] <mpt> Well, I could hear you...
[11:10] <Ubugtu> New bug: #66367 in launchpad "Number of translations to do" [Undecided,Unconfirmed]  http://launchpad.net/bugs/66367
[11:11] <mpt> that's a dupe
[11:11] <SteveA> i could not hear you
[11:11] <SteveA> lets try echo test, both of us
[11:12] <mpt> works fine for me
[11:12] <SteveA> try again pleae
[11:13] <SteveA> I'm having intermittent issues hearing voices
[11:13] <mpt> ok
[11:13] <SteveA> poo
[11:13] <SteveA> silence
[11:14] <mpt> ?
[11:15] <jamesh> do you have your microphone muted?
[11:15] <mpt> If I did, the echo test wouldn't work...
[11:15] <SteveA> no, it's a bluetooth issue I think
[11:16] <mpt> complete silence from you now
[11:16] <SteveA> I'll adjust alsa setting
[11:16] <SteveA> don't just hang up!
[11:16] <mpt> Shall I sing?
[11:16] <SteveA> no
[11:18] <SteveA> hmm
[11:18] <SteveA> also spracht
[11:20] <jamesh> mpt: I don't think it has any caching
[11:24] <jamesh> mpt: the output of the test suite would be buffered, so the web front end wouldn't see each new line as it is generated
[11:25] <jamesh> stdio only uses the line buffered mode (flush on new line) when outputting to the terminal
[11:26] <mpt> It doesnt't send any Expires header, or anything else
[11:26] <mpt> http://www.ircache.net/cgi-bin/cacheability.py?query=http%3A%2F%2Fpqm.launchpad.net%2F
[11:26] <jamesh> ... so it isn't using caching
[11:28] <jamesh> that URL site says that it will be considered stale
[11:28] <jamesh> how can you less agressively cache the result than not caching it at all?
[11:34] <mpt> Maybe Epiphany is looser with caching
[12:12] <stub> danilos: Do you remember what I was supposed to be runnng against the production database today? I can't find the details in my IRC log and Carlos never emailed me (assuming it was actually Carlos who asked).
[12:13] <danilos> stub: copy-translations
[12:13] <stub> dapper -> edgy?
[12:13] <danilos> stub: let me check the proper syntax, I think it's "copy-translations-from-parent.py dapper edgy"
[12:13] <danilos> stub: that's right
[12:14] <stub> ok - that's all I need. I'll wait until malcc or cprov get online to see if I can combine the downtime with a rollout.
[12:19] <lifeless> lp review teem meeting in 41 minutes
[12:27] <mpt> A 6.8 MB PQM failure message? That has to be some kind of record
[12:28] <spiv> mpt: lucky you!
[12:28] <mpt> I must have caused every single pagetest to fail voluminously
[12:31] <stub> jamesh: Are you aware of any limits to the size of a regexp?
[12:31] <jamesh> stub: not off hand
[12:32] <stub> I'm wondering how safe it is to use a single |'d regexp when the list grows to be a few hundred items long
[12:32] <jamesh> stub: I can't see it being worse than maintaining all those regexps separately
[12:34] <stub> I'll probably leave it the way it is though, as it will allow the UI to report the id of the regexp matched if we want
[12:34] <stub> (yagni?)
[12:35] <jamesh> stub: fair enough.  If that feature is really needed, it can also be done with named groups
[12:35] <spiv> stub: If you used named groups (like Moin's markup parser), you could have one regexp but still report an id.
[12:35] <jamesh> stub: but if you'd prefer to go with multiple regexps for now, go for it.
[12:35] <jamesh> (just make sure they don't get recompiled every run)
[12:38] <stub> spiv: As in r'(?P<1>exp_1)|(?P<2>exp_2)|...|(?P<n>exp_n)' ?
[12:40] <stub> Means people can't use (?i) syntax but that might be good
[12:40] <spiv> >>> re.compile(r'(?P<a>a+)|(?P<b>b+)|(?P<c>c+)').match('aaaaa').groupdict()
[12:40] <spiv> {'a': 'aaaaa', 'c': None, 'b': None}
[12:44] <SteveA> stub: ask gustavo
[12:44] <SteveA> he maintains regex libs in python
[01:01] <SteveA> lifeless: review meeting?
[01:04] <stub> Tests show only 100 named groups
[01:04] <SteveA> python library tests?
[01:05] <SteveA> named groups, so that you can say which pattern a particular name falls foul of
[01:05] <stub> Me playing with a command line tests.
[01:05] <stub> Non named groups have a similar limit
[01:05] <SteveA> oh, a limit in python?
[01:06] <SteveA> I was confused by your use of the word "Tests"
[01:07] <SteveA> lifeless: ping
[01:07] <lifeless> review meeting
[01:07] <lifeless> sorry, had a phone call from mum right at the start
[01:08] <lifeless> getting organised give me 5
[01:10] <SteveA> ok
[01:12] <lifeless> ok
[01:13] <lifeless> == Agenda ==
[01:13] <lifeless>  * Roll call
[01:13] <lifeless>  * Queue status.
[01:13] <lifeless> who art here ?
[01:13] <BjornT> me
[01:13] <spiv> me
[01:13] <SteveA> me
[01:13] <jamesh> me
[01:14] <lifeless> queue status...
[01:14] <SteveA> actually... grammar nazi...
[01:14] <SteveA> I
[01:14] <lifeless> :)
[01:15] <lifeless> 11 items in the queue
[01:15] <lifeless> longest is the tt-workflow mega branhc
[01:15] <lifeless> BjornT: how is that co,ing ?
[01:16] <BjornT> lifeless: i think i can finish it tomorrow. but it's taking some time since it's big, and i've also done other reviews in parallel, since it don't want it to block my queue completely.
[01:16] <lifeless> BjornT: I've been trying not to allocate anything to you
[01:16] <SteveA> tt-workflow?
[01:16] <lifeless> BjornT: how many hours so far reviewing it ?
[01:16] <SteveA> I can't quite place this
[01:17] <SteveA> who is the author?
[01:17] <spiv> tt == "ticket tracker", I believe.
[01:17] <lifeless> https://launchpad.canonical.com/SupportTrackerWorkflowSpec
[01:17] <lifeless> flacoste
[01:17] <lifeless> see https://launchpad.canonical.com/PendingReviews for details
[01:18] <SteveA> ok, thanks.  does francis know that large branches are not welcome in the future, and that he can get support from the review team in working out how to make landings in smaller units?
[01:18] <BjornT> lifeless: i haven't checked yet, but i'd say it's almost two full working days. in short, several smaller patches would have been much faster to review.
[01:18] <lifeless> SteveA: I think we need to do a general announcement about this
[01:18] <SteveA> it's difficult to reverse-engineer a suitable staged landing plan from the whole blob
[01:18] <lifeless> SteveA: as I mentioned on the phone to you
[01:18] <SteveA> lifeless: I announced it last week in the meeting, btw
[01:18] <BjornT> SteveA: i will at least inform him about it in my review.
[01:19] <lifeless> SteveA: thank you
[01:19] <SteveA> but I think this will take several announcements
[01:19] <SteveA> it was met with general support iirc
[01:19] <SteveA> or, my ego is being overactive again
[01:19] <lifeless> ok, so jamesh - you have two branches over the 2 day goal period - whats up there ?
[01:19] <Keybuk> sabdfl: ping
[01:19] <lifeless> (4 and 7 respectively)
[01:19] <Keybuk> I still get "Not allowed here" for https://launchpad.net/sprints/uds-mtv/+settopics
[01:19] <jamesh> lifeless: just posted a review of matsubara's one.  Will get on to Bjorn's one
[01:20] <SteveA> we may need to go to a policy of rejecting large landings unless they've been agreed with a reviewer in advance, sometime over the coming weeks
[01:20] <lifeless> SteveA: :) I was proposing something like this to you, and you suggested we wait and talk in allhands
[01:20] <lifeless> SteveA: so lets wait, and talk in allhands about it
[01:21] <lifeless> everything else is within our target review period of 2 days
[01:22] <lifeless> though there are a number of branches - BjornT spiv SteveA are the reviewers - that need to be done tomorrow at latest.
[01:22] <lifeless> jamesh: you were bringing up white space cleanups at the lp meeting last week. How did that go ?
[01:22] <spiv> I'm not sure that flacoste's 3402 line diff will be reviewed be reviewed tomorrow.
[01:22] <jamesh> lifeless: I forgot to add it to the agenda.  Will do so for this meeting
[01:23] <BjornT> lifeless: i plan to spend all of today and tomorrow reviewing, hopefully i'll finish all my reviews then.
[01:23] <SteveA> lifeless: I have some review time today
[01:24] <lifeless> SteveA: you already have jamesh/launchpad/death-to-tabindex allocated to you
[01:24] <lifeless> SteveA: if you have time to do flacostes flacoste/launchpad/tt-views instead, you and spiv can swap :)
[01:24] <lifeless> (death to tabindex is 1K lines, largely mechanical
[01:25] <lifeless> tt-views is 3.4K lines, and not so mechanical, but seemed probably ok when spiv and I glanced at it
[01:25] <BjornT> SteveA: if you have time for some more reviews, you could take salgado's shipit branch from my queue. i think it's fairly small, but i won't get by reviewing it today.
[01:25] <lifeless> loo
[01:25] <lifeless> lol, its pile on stevea day
[01:26] <SteveA> stick them in my queue, and we'll see what I can do today
[01:26] <lifeless> SteveA: fyi salgado is too busy with 1.0 to review at the moment, so there is some extra pressure on the review team; and the lp coding team has grown recently too
[01:26] <SteveA> after that, I want no more reviews this week
[01:26] <lifeless> SteveA: ok
[01:26] <SteveA> as I have UI 1.0 stuff to do
[01:26] <spiv> SteveA: thanks
[01:27] <lifeless> jamesh: can you trigger a reviews run please
[01:27] <lifeless> ok, any other business?
[01:28] <jamesh> lifeless: finished
[01:28] <lifeless> wicked
[01:28] <lifeless> SteveA: your reviews are ready
[01:28] <lifeless> https://devpad.canonical.com/~jamesh/pending-reviews/
[01:28] <lifeless> SteveA: the biggest ones first please!
[01:29] <lifeless> any other business 5
[01:29] <lifeless> any other business 4
[01:29] <lifeless> any other business 3
[01:29] <lifeless> any other business 2
[01:29] <lifeless> any other business 1
[01:29] <lifeless> thanks for attending!
[01:30] <SteveA> thanks lifeless
[01:30] <ctrlsoft> jamesh: hi
[01:30] <ctrlsoft> jamesh: Is there any easy way to import bugs from trac into lp?
[01:32] <ctrlsoft> (not just remote watch, but really migrate)
[01:32] <jamesh> ctrlsoft: not at present.  We have an importer from the XML dump effbot's SourceForge tools generate, but that is not really that user friendly to generate
[01:32] <jamesh> getting a better interchange format is a todo
[01:32] <lifeless> poolie: btw, dotted decimal has landed
[01:34] <ctrlsoft> jamesh: ok, thanks
[01:35] <poolie> lifeless: sweet
[01:35] <jamesh> ctrlsoft: we have an XML export format for a product's bugs, so it would be useful to be able to import something in a similar format
[01:35] <jamesh> but that code isn't yet ready.
[01:36] <ctrlsoft> jamesh: Any spec/bug about it?
[01:37] <jamesh> ctrlsoft: no
[01:39] <jamesh> ctrlsoft: I've already written importers for Ubuntu Bugzilla and SourceForge, so I'd really like to have a sane XML format I could tell people to give me
[01:39] <ctrlsoft> jamesh: Yeah, that makes sense. I'm happy to write a generator for trac once there's a format
[02:36] <lifeless> gnight all
[02:48] <stub> cprov: I would like to roll out r4153 either tonight or (preferably) tomorrow morning my time.
[02:50] <stub> cprov: That will add db patches 67-21, 22, 23, 24 and 26
[02:53] <stub> cprov: I don't think any of those affect soyuz but thought I should confirm
[03:10] <Ubugtu> New bug: #66408 in malone "URL of bugs does not understand rejected bugtask status" [Undecided,Unconfirmed]  http://launchpad.net/bugs/66408
[03:18] <cprov> stub: yes, looks ok, but we need 4155 cherrypick
[03:19] <cprov> stub: or we can do it ourself only in drescher
[03:19] <stub> cprov: So you don't need those local patches listed on the wiki page?
[03:20] <malcc> stub: Let me check, I think they were mostly turning something off then back on again and things which are in rf, I'll confirm in a moment
[03:23] <malcc> stub: Yes, confirmed. Two local fixes undo each other, the third is r4136.
[03:25] <cprov> stub: the db patches should be fine too
[03:26] <stub> cprov: I will roll out 4155 tomorrow everywhere, including drescer then.
[03:26] <cprov> stub: perfect, thank you
[04:26] <salgado> SteveA, do you have some time to review my latest shipit changes today, so that I can ask stub to include them in tomorrow's roll out?
[04:26] <stub> Shouldn't we sit on the changes a few days before pushing out brand new code, or is it really urgent?
[04:28] <salgado> stub, it is /really/ urgent, and it's quite low risk --just changes the front page
[04:29] <stub> ok
[04:37] <PSUSI> how would one go about getting spam removed from bugs on launchpad?
[04:40] <seb128> is there a way to mail all the member of a team on launchpad?
[04:43] <gjc> hmm.. lucky me, no nick registration needed here :)
[04:58] <PSUSI> anyone know what to do when someone starts spamming bugs on launchpad?  can it be cleaned up and the offending email unsubscribed?
[05:02] <salgado> PSUSI, although there's no automated way to do so, we can sort it out for you. what's the bug that's beeing spammed?
[05:03] <PSUSI> I have a list of about 10 bugs that some silly person is also subscribed to and he seems to have recently installed a very broken email blocking probram that has ignored the Errors-to: header and replied with a confirm request to each bug
[05:04] <PSUSI> so now this silly confirm request is posted to all of these bugs... standby for list
[05:04] <jamesh> distributed spam blocking: get the rest of the world to filter your email
[05:05] <PSUSI> 35934, 38649, 64174, 44370, 64585, 28925, 45768, 30284
[05:05] <PSUSI> hehehe
[05:05] <Ubugtu> New bug: #66422 in malone "How to deal with spam" [Undecided,Unconfirmed]  http://launchpad.net/bugs/66422
[05:06] <PSUSI> I just wish the retarded developers of these things would at least respect the damn Errors-to: header
[05:06] <PSUSI> I also found a half a dozen of these confirm requests in my mailbox this morning as a result of a few posts to a public mailing list
[05:06] <jamesh> It is an argument for requiring that replies maintain some token in the subject line (e.g. the bug number)
[05:07] <PSUSI> the list sets Errors-to: specifically to be able to deal with ( read: unsubscribe ) email addresses that are undeliverable instead of bothering subscribers with that
[05:08] <PSUSI> I think just setting the From: filed to an undeliverable address would fix it actually
[05:08] <PSUSI> normal mail clients will use the Reply-to: anyhow
[05:08] <ddaa> some do
[05:09] <ddaa> it's an ongoing flamewar topic
[05:09] <salgado> seb128, no, we don't have a way to do that yet. (bug 44545)
[05:09] <Ubugtu> Malone bug 44545 in launchpad "FOAF Request: make all Teams into email-aliases/mailing-lists" [Medium,Unconfirmed]  http://launchpad.net/bugs/44545
[05:09] <PSUSI> non broken mail clients will respect it ;)
[05:09] <seb128> gjc: ^^
[05:09] <seb128> salgado: thank you
[05:10] <PSUSI> jamesh: so you are manually cleaning the spam from the bugs and unsubscribing the guy?
[05:10] <PSUSI> err, salgado  even
[05:11] <gjc> seb128, salgado: thanks
[05:12] <salgado> seb128, gjc, np.
[05:14] <salgado> PSUSI, I can't do that myself, but I just noticed that he's only subscribed to bug 28925
[05:14] <Ubugtu> Malone bug 28925 in xserver-xorg-driver-ati "X fails to start in dapper flight3 & 4 with ati X600, onward all the way through dapper 6.06 LTS" [Unknown,Unknown]  http://launchpad.net/bugs/28925
[05:15] <salgado> the problem is that he's notified every time a bug is marked as a duplicate of that one, and that one has lots of dupes
[05:15] <PSUSI> salgado: do you know who can?  and if he isn't subscribed then why did he get notifications from the bug?
[05:15] <PSUSI> ahhhh
[05:15] <PSUSI> yes
[05:16] <salgado> actually, he's subscribed to 47083 which is a dupe of 28925
[05:16] <salgado> oh, he reported that one. :/
[05:20] <salgado> stub, is there anything we can do to avoid glen-stewart's spam killer to spam bug 47083 and the dupes of 28925?
[05:20] <Ubugtu> Malone bug 47083 in xserver-xorg-video-ati "installer CD fails to start X on Radeon X800 GTO" [Medium,Unconfirmed]  http://launchpad.net/bugs/47083
[05:22] <elmo> salgado: how about a rubber duck deactivates his email, would that work?
[05:24] <stub> eh?
[05:25] <salgado> elmo, that may cause OOPSes because we assume that somebody who reported a bug has a preferred email
[05:26] <elmo> salgado: sweet
[05:28] <salgado> stub, on 47083 we can see an automated reply from the reporter's spam killer asking for a confirmation of the message. a similar message is sent every time a bug is marked as a dupe of 47083 or 28925.
[05:28] <stub> Bg 47083
[05:28] <stub> Bug 47083
[05:28] <Ubugtu> Malone bug 47083 in xserver-xorg-video-ati "installer CD fails to start X on Radeon X800 GTO" [Medium,Unconfirmed]  http://launchpad.net/bugs/47083
[05:29] <stub> I'll unsubscribe glen-stewart for a start
[05:30] <stub> I wonder if elmo's suggestion would blow anything up? It should work, but unlikely to be tested.
[05:31] <stub> Hmm... should, because they would become an invalid user.
[05:31] <salgado> I think it'd blow if the guy was the only person subscribed to that bug
[05:31] <salgado> might blow in other cases too
[05:33] <stub> Not much we can do anyway - it isn't as if Launchpad will ever be able to communicate with them.
[05:45] <salgado> stub, btw, I think we had enough testing of the mirror prober on staging. there's no need to keep it running there
[05:45] <stub> ok
[06:40] <carlos> hi
[06:43] <kiko-fud> bonjour mes amies
[06:43] <kiko-fud> err amis
[06:43] <kiko-fud> how's it going?
[06:45] <SteveA> hello world
[06:45] <SteveA> salgado-lunch: still need that review done?
[06:50] <kiko-fud> sabdfl, around?
[07:08] <kiko-fud> hey cprov-lunch
[07:08] <salgado-lunch> SteveA, yeah, I do
[07:08] <cprov-lunch> kiko-fud: hey
[07:13] <kiko-fud> how's it going cprov-lunch
[07:13] <kiko-fud> just saw your update to n-m-a-f
[07:14] <cprov-lunch> kiko-fud: yes, very good so far, updating specs & plans, testing new i-f-p (w/o translations) in mawson.
[07:15] <kiko-fud> cprov-lunch, the funny part is that mdz doesn't think that changing the RFC address would be a big deal
[07:15] <kiko-fud> cprov-lunch, and malcc?
[07:16] <malcc> Changing my rfc address probably wouldn't be a big deal either
[07:16] <cprov-lunch> kiko-fud: well, it's precisely what is in the DSC, it will only change if we modify the SPR
[07:17] <kiko-fud> malcc, so you arrived in one piece?
[07:17] <kiko-fud> cprov-lunch, no, mdz was saying that it wouldn't be strictly necessary to store that exact line
[07:17] <kiko-fud> as long as we never regenerated old indices files, I guess
[07:17] <malcc> kiko-fud: Yup, the journey was suspiciously smooth. I think the universe must have a nightmare in store for me on the way home
[07:18] <kiko-fud> malcc, you firm believer in karma?
[07:18] <cprov-lunch> kiko-fud: yes, I understood, but better keep it constant, following the DSC, not the Person.displayname, IMHO.
[07:19] <kiko-fud> cprov-lunch, yeah, I'm okay too
[07:56] <SteveA> salgado: I'm reviewing your shipit branch now
[08:05] <ddaa> SteveA: my hands are falling off, and I'll be going for dinner soon
[08:05] <ddaa> I'll reply to poolie about the debian svn issue tomorrow
[08:05] <ddaa> some clarifications seem to be needed
[08:08] <malcc> Hmm, looks like the date created patch went into rocketfuel without the matching sampledata changes, anyone regenerating sampledata at the moment gets a bonus 1000 lines for their patch
[08:08] <malcc> Any objection if I do nothing but make newsampledata in a branch and trivial it?
[08:09] <kiko-fud> malcc, no objection, d it.
[08:11] <SteveA> salgado: reviewed. well done.
[09:22] <sivang> hi all
[09:22] <sivang> is there a way to list package karms joined by maintainers, over a specific team? (ubuntu-dev)
[09:57] <lamont> currently there are 3 or so releases worth of build logs in people.u.c/~lamont/buildLogs - does it make sense to import those into launchpad to go with the binaries that are there?
[10:28] <kiko-fud> lamont, good question, check with cprov if it's doable
[10:30] <lamont> kiko-fud: you will, or I should?
[10:30] <kiko-fud> lamont, if you can, that'd be best
[10:30] <lamont> cprov: how about it? ^^^
[10:30] <lamont> :-)
[10:31] <malcc> So this is build logs which would have been imported by gina, if gina imported build logs, right?
[10:31] <kiko-fud> yes.
[10:31] <cprov> lamont: what buildlogs ? security ?
[10:31] <lamont> people.ubuntu.com/~lamont/buildLogs - all of warty-breezy build logs
[10:32] <lamont> no security logs
[10:32] <lamont> just thinking it might be good to prune the size of that tree on p.u.c
[10:32] <lamont> esp since someone went there today looking for an edgy build log, and had to be redirected to launchpad...
[10:33] <cprov> lamont: well, not sure if they are useful since they were not done using our buildfarm. really, dunno.
[10:34] <salgado> SteveA, around?
[10:34] <lamont> cprov: neither were the binaries... :)
[10:34] <cprov> lamont: it's feasible and you want them we can do it. if it was your question.
[10:34] <lamont> cprov: the real question was (1) does it  make sense to do it, and (2) if so, how feasable?
[10:35] <cprov> lamont: yes ;) legacy
[10:35] <lamont> exactly
[10:35] <cprov> lamont: it only make sense if you use it
[10:36] <lamont> well, not personally, but sometimes it's useful to compare the build log with the one that's not working for a security update or some such
[10:36] <cprov> lamont: it's feasible, it's just a matter of finding the correspondent build record, upload the log to librarian and update its buildlog field
[10:36] <lamont> so it really gets back to a dev-team question of "do we want them".  got it.
[10:36] <lamont> cprov: I'll ask dev-team et al, and get back with you
[10:37] <cprov> lamont: good, thank you for pointing that, I appreciate it.
[10:38] <lamont> np
[10:46] <SteveA> salgado: hi
[10:47] <salgado> hi SteveA.  about the XXX I droped from some config files on my shipit-for-edgy branch... I'd like to keep them since I'm going to remove the variable I added soon
[10:48] <salgado> do you think it'd be okay to not add that variable on the production config files and leave the XXX in them?
[10:56] <SteveA> salgado: I'd say leave the XXX, add the variable, but add a further line of comment above the variable saying
[10:56] <SteveA>  # XXX: the following config item is temporary, so the XXX above applies in the long term.
[10:59] <salgado> fair enough
[11:06] <salgado> SteveA, do you know if it's possible to check the status used by the redirect using testbrowser or if I have to use an old-style test?
[11:06] <salgado> BjornT, maybe you know ^^?
[11:11] <SteveA> I think you can't easily check from a regular "real" browser
[11:11] <SteveA> so it may not be so easy from testbrowser
[11:14] <SteveA> looking at the testbrowser code, doesn't look like there's an easy way
[11:14] <SteveA> so, write an old-style test for it
[11:14] <BjornT> salgado: i think you can do it by setting browser.handleError = True (or maybe False). but i'm not sure.
[11:14] <salgado> yeah, I couldn't find anything either
[11:33] <sabdfl> kiko: briefly now - 'sup?


[03:39] <pleia2> nice work everyone, copying over summaries now
[03:41] <jose> pleia2: did we get to add wxl's post about the mailman/launchpad script?
[03:42] <pleia2> jose: no, go in loco?
[03:42] <jose> pleia2: yeah
[03:42] <jose> lemme get the link
[03:42] <jose> http://polka.bike/blog/mailmangroupxref-markdown
[03:43] <pleia2> jose: can you write a summary real quick in the google doc while I do other wiki things?
[03:43] <jose> sure
[03:43] <pleia2> thanks :)
[03:43] <jose> np!
[03:45] <jose> all set
[03:46] <pleia2> thanks
[03:51] <pleia2> Unit193: link check? https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue394
[03:51] <pleia2> sending off to summary writers now
[03:51] <pleia2> err, editors!
[03:56]  * pleia2 goes back to offline things now
[04:15] <Unit193> Looking good.
[05:42] <pleia2> Unit193: thanks!
[17:42] <wxl> omg is it too late to add something to the news?!!?!
[17:42] <wxl> if it's not too late, pleia2, you should mention hacksummit.org. it just started but it's a free online dev conference.
[17:50] <pleia2> wxl: if there's an article about it and it's linux or open source-focused, we can link it under "Other Articles of Interest"
[17:50] <pleia2> there are too many hack events, conferences, etc to link to in every issue though
[18:05] <wxl> pleia2: ok i got a couple links for it cross referencing open source and/or linux
[18:05] <wxl> http://www.infoq.com/news/2014/11/hack-summit
[18:05] <wxl> here comes
[18:05] <pleia2> cool, that one works for me :)
[18:05] <wxl> http://java.dzone.com/articles/hacksummit-pace-be-largest
[18:05] <wxl> that one's interesting
[18:05] <wxl> i think that as a virtual conference the uos folks stand to get something from it
[18:06]  * pleia2 nods
[18:06] <pleia2> I'll go with the 2nd link
[18:06] <wxl> i'm sitting in a room with over 3000 people
[18:06] <wxl> last one had over 6000
[18:06] <pleia2> wow
[18:06] <wxl> this talks a bit about its charity focus http://www.programmableweb.com/news/hack.summit-conference-tackles-inequality-tech/2014/11/26
[18:06] <wxl> it's a charity for coding nonprofits
[18:06] <wxl> including women who code
[18:06] <wxl> black girls code
[18:07] <wxl> ladies learning code
[18:07] <pleia2> yeah, I heard about it through both those orgs
[18:07] <pleia2> just... work :)
[18:07] <wxl> etc etc
[18:07] <wxl> :)(
[18:07] <wxl> pick one if you want and i'll write a summary
[18:07] <wxl> or include them all and i can summarize
[18:07] <pleia2> it's just a bullet-pointed item
[18:07] <wxl> works for me
[18:07] <pleia2> not Ubuntu-specific enough to be a full thing :\
[18:07] <pleia2> anyway, it's in now
[18:08] <pleia2> thanks \o/
[18:08] <wxl> okie dokie
[18:09] <wxl> thank you :)
[18:09] <wxl> i'm happy to have helped with the newsletter
[18:10] <wxl> ew this guy is using windows
[18:10] <pleia2> I'm happy you did too! less work for me :)
[18:10] <pleia2> haha
[18:11] <wxl> hahahah
[18:11] <wxl> well you can count on me on into the future
[18:11] <pleia2> wonderful, thanks :)
[18:11] <wxl> maybe i can work on getting some lubuntu stuff in there
[18:12] <pleia2> we pull stuff that lands on planet.ubuntu.com, but sometimes the 3rd party articles on flavors are missed
[18:12] <pleia2> anyway, back to the work I'm actually paid for, I'll publish in a few hours
[18:12] <wxl> see ya
[21:04] <wxl> pleia2: oh man i should have looked. my blog is about crossrefercing Mailman subscriber lists and Launchpad memberships, not Launchpad mailing lists
[21:05] <pleia2> wxl: whoops, you can correct on the wiki and I can fix on forums at least
[21:05] <wxl> pleia2: ok
[21:05] <wxl> i'm going to add my name in there too ;)
[21:07] <wxl> done
[21:07] <pleia2> wxl: for LoCo news we don't add the name, just for Planet
[21:07] <pleia2> (even if LoCo news was on planet too)
[21:08] <wxl> pleia2: oops fixing
[21:08] <wxl> done
[21:09] <pleia2> thanks, updated for forum post too
[21:25] <pleia2> Welcome to the Ubuntu Weekly Newsletter, Issue 394 for the week November 24 - 30, 2014 https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue394
[21:27] <jose> thanks, pleia2! :)
[21:27] <pleia2> sure thing