[05:33] <pitti> Good morning
[06:31] <DanChapman> good morning
[07:22] <pitti> jibel: FYI, slew of failures was due to a bad amd64 VM on wazn; I rebuilt it (tested now, works), and re-enabled wazn, and I retried all failures
[07:43] <jibel> pitti, Good morning and thanks for taking care of this.
[07:43] <pitti> jibel: bonjour, ça va ?
[07:43] <jibel> pitti, ça va et toi?
[07:43] <pitti> ça va bien
[07:44] <pitti> although I feel a bit sore from first Taekwondo yesterday for this year :)
[09:26] <zyga-phone> hi
[09:42] <elfy> morning all
[10:03] <slickymaster> morning all
[10:58] <davmor2> Morning all
[11:00] <slickymaster> hey davmor2, good morning
[14:51] <elfy> balloons: once you've drunk the n'th coffee - https://code.launchpad.net/~elfy/ubuntu-manual-tests/fix1301/+merge/201564
[15:21] <balloons> oO elfy
[15:47] <elfy> balloons: does that fit the bill then?
[15:48] <balloons> elfy, yes, looks quite fine
[15:49] <balloons> should we explain no autoresize will be offered if sufficent space isn't left?
[15:51] <elfy> I guess so - makes it more explicit - personally I'd read "sufficient disk space is available" to mean that - but then I've not only ever done 1 resize :)
[16:07] <elfy> balloons: If insufficient disk space is available - the resize option will not be available
[16:14] <balloons> elfy, approved
[16:14] <elfy> oh - ok - was fiddling - shall stop now :p
[16:15] <balloons> lol
[16:16] <elfy> balloons: you going to merge etc?
[16:16] <balloons> elfy, yea I'll merge right now
[16:17] <elfy> okey doke
[16:17] <balloons> ty
[16:17] <elfy> I've been catching up today with them
[16:17] <elfy> balloons: welcome of course :)
[16:26] <elfy> balloons: I've dealt with the tracker
[16:27] <balloons> elfy, I've got a few to sync, so it's getting synced anyway, hah
[16:27] <balloons> ty
[16:27] <elfy> oh well - nvm - I fix released the bug as well
[16:28] <balloons> just want to make sure the other ones dont get missed
[16:28] <elfy> cleaning up my bug list - one left :p
[16:28] <elfy> well I don't know about others
[16:28] <balloons> i cleaned up some formatting
[16:28] <WebbyIT> ehy balloons :-) Could you help me to understand these failures? https://code.launchpad.net/~rpadovani/ubuntu-calculator-app/1267820/+merge/201313/comments/469105
[16:29] <balloons> hey WebbyIT
[16:29] <balloons> I pushed a rebuild for that.. we'll see what it says now
[16:30] <balloons> there were a few missing tags in some older stuff I found, so I commited and pushed them
[16:30] <balloons> we should be all set :-)
[16:30] <WebbyIT> balloons, thanks :-)
[16:37] <WebbyIT> balloons, passed, thanks :-)
[16:38] <balloons> WebbyIT, :-)
[17:11] <elfy> evening DalekSec
[17:11] <elfy> sorry Unit :p
[17:11] <elfy> evening DanChapman :)
[17:11] <DanChapman> evening elfy :-)
[17:13] <slickymaster> hey DanChapman, evening
[17:40] <balloons> DanChapman, slickymaster hello!
[17:40] <DanChapman> balloons, howdy o/ how's it going?
[17:41] <slickymaster> hey balloons, hello yourself :)
[17:41] <balloons> you are just in time for some earl grey tea
[17:42] <slickymaster> lol elfy addiction to tea is starting to take over every channel
[17:42] <balloons> lol.. something like that
[17:42] <knome> bah, stupid teatotalers ;)
[17:42]  * DanChapman passes balloons his cup. "I do like a cup of earl grey"
[17:43] <elopio> balloons: I owe you two things, according to my whiteboard.
[17:43] <elopio> some refactoring for the weather app, and a summary about exploratory testing.
[17:43]  * balloons tells DanChapman to be patient and wait for it to finish steeping
[17:43] <elopio> what's the status of weather app tests? is somebody working on them and I need to coordinate my changes?
[17:43] <balloons> elopio, yes, the status board ;-)
[17:44] <balloons> elopio, atm we're moving to the TWC api
[17:44] <balloons> so as part of that, it would be great to make sure we don't have network issues
[17:44] <balloons> elopio, mbo is doing the initial port. he has a branch, one sec
[17:45] <balloons> lp:~martin-borho/ubuntu-weather-app/weather-channel-client
[17:45] <knome> mbo... bit too close to mvo :P
[17:45] <balloons> elopio, on the exploratory testing thing. Let's do it during the sprint, shall we?.
[17:46] <elopio> balloons: ok, I'll wait for that branch to land. We have played a little with a fake server on the scope tests, and I think it will be useful for the apps.
[17:46] <elopio> I'll give it a try with weather.
[17:47] <elopio> and, ok to exploratory on the sprint.
[17:47] <elopio> balloons: if I owe you something else, I didn't note it down on the board so I have already forgotten.
[17:50] <balloons> elopio, if it's not on status, it's not real ;-)
[17:50] <elopio> balloons: yes, it would be your fault for not noting it down on my whiteboard, I can't be blamed :)
[17:50] <balloons> elopio, I see "make sure the SDK emulators work in python 2 and python 3."
[17:50] <balloons> http://status.ubuntu.com/ubuntu-t/u/elopio.html
[17:51] <elopio> hum, you are cheating.
[17:51] <elopio> ok, I noted it down, thank you :D
[17:51] <balloons> this is also useful: http://status.ubuntu.com/ubuntu-t/group/topic-t-community-quality.html
[17:51] <elopio> I'll get to it next week.
[17:51] <balloons> :-)
[17:51] <balloons> py3 push is coming back I think
[17:52] <elopio> balloons: yes, but I think the SDK is the only one we need to be compatible with python 2 and 3.
[17:53] <elopio> I'll ask next week though, thomi and bary will now better.
[17:53] <thomi> hmmm?
[17:53] <thomi> oh, you need to talk to barry about that I think
[17:54] <thomi> I think his [plan was to have a flag day on those...
[17:54] <elopio> thomi: I'll talk to him before I do any code.
[19:16] <balloons> DanChapman, I'm sorry.. Just realized I finished my tea a bit ago and didn't pour you a cup
[19:16]  * balloons pours DanChapman some reheated tea
[20:19] <Letozaf_> mzanetti, hello
[20:19] <mzanetti> hi Letozaf_
[20:21] <Letozaf_> mzanetti, I made the changes you were taling about yesterday, but my tests still work only on the desktop and not on the device, probably I am doing something wrong but can't figure out what,
[20:21] <Letozaf_> mzanetti, could you help ?
[20:23] <mzanetti> Letozaf_: hmm... so what exactly is the error?
[20:23] <Letozaf_> mzanetti, http://paste.ubuntu.com/6752395/
[20:24] <Letozaf_> mzanetti, if you need to see the code it's here: lp:~carla-sella/reminders-app/new-reminders-app-tests
[20:24] <mzanetti> Letozaf_: does this exist? /usr/share/applications/reminders-app.desktop
[20:24] <mzanetti> Letozaf_: this needs to point to some existing .desktop file
[20:25] <Letozaf_> mzanetti, no it's not there...
[20:25] <Letozaf_> mzanetti, after running the  run_on_ubuntu_touch.sh -c
[20:26] <mzanetti> Letozaf_: yeah, that doesn't install it
[20:26] <mzanetti> Letozaf_: replace that path to point to an existing file
[20:26] <mzanetti> ideally to a reminders-app.desktop, but I'm not sure if it has to be inside /usr/share/applications/ or not
[20:27] <Letozaf_> mzanetti, but if I install the click package again this would create that file again or not ?
[20:28] <mzanetti> Letozaf_: yeah, but right now we are trying to run the app from the build dir without installing it
[20:28] <mzanetti> to make it easy for development
[20:29] <mzanetti> to edit something and run again
[20:29] <mzanetti> otherwise you need to install a new package each time you want to test a simple change
[20:29] <Letozaf_> mzanetti, yes thats true :(
[20:29] <mzanetti> Letozaf_: so make it point to /home/phablet/reminders-app/reminders-app.desktop
[20:30] <Letozaf_> mzanetti, ok I will try now
[20:30] <mzanetti> its one of the changes I pasted yesterday
[20:30] <Letozaf_> mzanetti, :( I probably missed it , sorry
[20:30] <mzanetti> I just used camera-app's desktop file for a quick test
[20:31] <mzanetti> no, you didn't miss it, you applied the change, but just replaced camera-app with reminders-app
[20:31] <mzanetti> I can see from the debug output
[20:31] <mzanetti> :)
[20:31] <Letozaf_> mzanetti, :)
[20:33] <mzanetti> Letozaf_: so this is what's happening: in order to run an application in ubuntu touch you need to pass the parameter --desktop_file_hint=/some/file.desktop
[20:33] <mzanetti> otherwise the application manager will reject the app
[20:34] <Letozaf_> mzanetti, ok thanks
[20:35] <mzanetti> Letozaf_: and we need to call this qmlscene -testability -I /home/phablet/reminders-app/tests/builddir/src/plugin ../../src/app/qml/reminders-app.qml --desktop_file_hint=/home/phablet/reminders-app/reminders-app.desktop
[20:35] <mzanetti> Letozaf_: you can see in the debug output what autopilot is trying to start
[20:36] <mzanetti> the -testability is for autopilot to work
[20:36] <mzanetti> the -I is to let qmlscene know where the Evernote plugin is located
[20:36] <mzanetti> then there is the actual qml file to open
[20:37] <mzanetti> and then the --desktop_file_hint which is required by the ApplicationManager in Unity
[20:38] <Letozaf_> mzanetti, ok I will try to fix it with your hints, thanks
[20:54] <Letozaf_> mzanetti, yay it worked got the two tests running on the device :)
[20:54] <mzanetti> Letozaf_: cool :)
[20:54] <Letozaf_> mzanetti, now let me try if it still works on the desktop :P
[20:54] <mzanetti> hehe :)
[20:55] <Letozaf_> mzanetti, yes thanks a lot it works on both sides :D
[20:55] <mzanetti> Letozaf_: very good
[20:56] <Letozaf_> mzanetti, now I can propose a merge for these two tests
[20:56] <Letozaf_> mzanetti, and then continue writing others
[20:56] <mzanetti> ok, great
[21:00] <Letozaf_> balloons, mzanetti we have our first small autopilot tests for reminders app ready : https://code.launchpad.net/~carla-sella/reminders-app/new-reminders-app-tests/+merge/201672
[21:01] <balloons> Letozaf_, that's great news!
[21:01] <mzanetti> Letozaf_: cool
[21:01] <mzanetti> Letozaf_: but seems there is a conflict
[21:01] <balloons> looks like small conflict with trunk
[21:02] <balloons> bit silly, you should be able to fix
[21:02] <Letozaf_> balloons, thought I had fixed it, let me see
[21:02] <balloons> edit src/app/qml/reminders-app.qml to be your version :-)
[21:02] <balloons> well notebook -> notebooks
[21:03] <Letozaf_> balloons, yes I saw that and thought I had fixed it, instead i didn't :(
[21:06] <Letozaf_> balloons, that's weired if I launch bzr diff or bzr status I do not get any diffrences and bzr merge say's nothing to do...
[21:06] <Letozaf_> balloons, what am I doing wrong now ?
[21:06] <balloons> did you push everything?
[21:07] <balloons> your local copy probably is fixed
[21:07] <Letozaf_> balloons,  I will push again
[21:08] <Letozaf_> balloons, pushing says: No new revisions or tags to push.
[21:09] <balloons> lp:~carla-sella/reminders-app/new-reminders-app-tests?
[21:09] <balloons> it's rev 25
[21:09] <balloons> what's bzr revno say for you?
[21:09] <Letozaf_> balloons, if I launch bzr log I also have rev 25
[21:10] <balloons> Letozaf_, well, look in src/app/qml/reminders-app.qml and ensure it's correct
[21:10] <Letozaf_> balloons, bzr revno says 25
[21:11] <Letozaf_> balloons, aaah! I still got notebook instead of notebooks :P
[21:11] <Letozaf_> balloons, let me fix
[21:11] <balloons> lol
[21:12] <balloons> don't forget the objectname
[21:25] <balloons> Letozaf_, it's still there fyi
[21:26] <Letozaf_> balloons, yes but I do not understand why my reminders-app.qml is ok I fixed it and if I push again it says I have nothing to push :?
[21:26] <balloons> bzr merge lp:reminders-app
[21:26] <Letozaf_> balloons, bzr diff gives me nothing, so I'm quite puzzled
[21:26] <balloons> merge trunk, fix conflict, push
[21:27] <Letozaf_> balloons, ok
[21:32] <Letozaf_> balloons, yay it's ok now
[21:33] <balloons> :-)


[22:02] <nhandler> Anyone working on a team report for the Reviewers Team ?
[22:02] <nhandler> Oh wait, never mind ;)


[13:48] <psusi> bug #1365667 is caused by an incorrect dependency in the ubuntu-mate-live package... unfortunately, this package doesn't seem to exist, so where should this bug be assigned to?
[13:48] <psusi> is there an ubuntu mate spin metapackage or something?
[14:25] <hggdh> psusi: probably better toask on #ubuntu-mate
[20:52] <balloons> can someone triage to include the proper folksfor getting this updated? Should be a straightforward fix: https://bugs.launchpad.net/nvidia/+bug/1295961


[00:43] -queuebot:#ubuntu-release- Unapproved: python-oslo.config (cosmic-proposed/main) [1:6.4.0-0ubuntu1 => 1:6.4.0-0ubuntu2] (openstack, ubuntu-server)
[02:37] <smoser> hi. maybe someone can verify for me. i think the cloud-init uploads that are in queue for xenial and bionic will ultimately be rejected
[02:38] <smoser> because they have a .orig.tar.gz that is different than the one that was uploaded to cosmic
[02:38] <smoser> can someone just verify that and reject them if so ?
[03:11] -queuebot:#ubuntu-release- Unapproved: cloud-init (bionic-proposed/main) [18.3-9-g2e62cb8a-0ubuntu1~18.04.2 => 18.4-0ubuntu1~18.04.1] (edubuntu, ubuntu-cloud, ubuntu-server)
[03:12] <blackboxsw> ok pushed an update for xenial and bionic
[04:06] <vorlon> smoser: if the orig.tar.gz differs then yes, they would be rejected
[04:07] <vorlon> not checking at the moment to verify that they are in fact different
[04:14] -queuebot:#ubuntu-release- Unapproved: accepted whoopsie-preferences [source] (cosmic-proposed) [20]
[04:15] -queuebot:#ubuntu-release- Unapproved: accepted sysvinit [source] (cosmic-proposed) [2.88dsf-59.10ubuntu2]
[04:17] -queuebot:#ubuntu-release- Unapproved: accepted python-oslo.config [source] (cosmic-proposed) [1:6.4.0-0ubuntu2]
[04:17] -queuebot:#ubuntu-release- Unapproved: accepted squashfs-tools [source] (cosmic-proposed) [1:4.3-6ubuntu2]
[04:17] -queuebot:#ubuntu-release- Unapproved: accepted rootskel [source] (cosmic-proposed) [1.124ubuntu2]
[04:17] -queuebot:#ubuntu-release- Unapproved: accepted strace [source] (cosmic-proposed) [4.21-1ubuntu2]
[05:14] -queuebot:#ubuntu-release- Unapproved: twisted (cosmic-proposed/main) [18.7.0-2 => 18.7.0-3] (kubuntu, ubuntu-desktop, ubuntu-server) (sync)
[07:51] <tjaalton> please accept libinput for cosmic, it's a stable update with only fixes
[08:11] <sil2100> tjaalton: looking
[08:15] -queuebot:#ubuntu-release- Unapproved: accepted libinput [sync] (cosmic-proposed) [1.12.1-1]
[08:15] <tjaalton> thanks
[08:22] -queuebot:#ubuntu-release- Unapproved: kwin (cosmic-proposed/universe) [4:5.13.5-1ubuntu1 => 4:5.13.5-1ubuntu2] (kubuntu)
[08:45] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [ppc64el] (xenial-proposed/main) [4.15.0-37.40~16.04.1] (kernel)
[08:47] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [amd64] (xenial-proposed/main) [4.15.0-37.40~16.04.1] (kernel)
[08:52] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [amd64] (xenial-proposed) [4.15.0-37.40~16.04.1]
[08:52] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [ppc64el] (xenial-proposed) [4.15.0-37.40~16.04.1]
[09:35] -queuebot:#ubuntu-release- Unapproved: ubuntu-themes (bionic-proposed/main) [16.10+18.04.20180421.1-0ubuntu1 => 16.10+18.04.20181005-0ubuntu1] (core) (sync)
[09:35] -queuebot:#ubuntu-release- Unapproved: ubuntu-themes (cosmic-proposed/main) [16.10+18.04.20180421.1-0ubuntu1 => 16.10+18.10.20181005-0ubuntu1] (core) (sync)
[10:43] -queuebot:#ubuntu-release- Unapproved: accepted ledmon [source] (bionic-proposed) [0.90-0ubuntu1~18.04.1]
[10:46] -queuebot:#ubuntu-release- Unapproved: gdm3 (bionic-proposed/main) [3.28.3-0ubuntu18.04.1 => 3.28.3-0ubuntu18.04.2] (ubuntu-desktop)
[10:47] <Laney> OEM team are asking for that ^-, if someone has a minute
[11:16] -queuebot:#ubuntu-release- New: accepted linux-signed-oem [amd64] (bionic-proposed) [4.15.0-1022.25]
[11:16] -queuebot:#ubuntu-release- New: accepted brotli [amd64] (xenial-proposed) [1.0.3-1ubuntu1~16.04.1]
[11:16] -queuebot:#ubuntu-release- New: accepted brotli [armhf] (xenial-proposed) [1.0.3-1ubuntu1~16.04.1]
[11:16] -queuebot:#ubuntu-release- New: accepted brotli [powerpc] (xenial-proposed) [1.0.3-1ubuntu1~16.04.1]
[11:16] -queuebot:#ubuntu-release- New: accepted brotli [s390x] (xenial-proposed) [1.0.3-1ubuntu1~16.04.1]
[11:16] -queuebot:#ubuntu-release- New: accepted brotli [arm64] (xenial-proposed) [1.0.3-1ubuntu1~16.04.1]
[11:16] -queuebot:#ubuntu-release- New: accepted brotli [ppc64el] (xenial-proposed) [1.0.3-1ubuntu1~16.04.1]
[11:16] -queuebot:#ubuntu-release- New: accepted brotli [i386] (xenial-proposed) [1.0.3-1ubuntu1~16.04.1]
[11:25] -queuebot:#ubuntu-release- New sync: fonts-fork-awesome (cosmic-proposed/primary) [1.1.2+ds3-3]
[11:46] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-meta [source] (cosmic-proposed) [1.425]
[11:54] <tjaalton> Laney: yep
[11:54] <Laney> yep what?
[11:54] <tjaalton> gdm
[11:55] <Laney> nod
[12:32] -queuebot:#ubuntu-release- Unapproved: accepted gdm3 [source] (bionic-proposed) [3.28.3-0ubuntu18.04.2]
[12:37] <Laney> tjaalton: thanks!
[12:38] <tjaalton> yw
[13:09] -queuebot:#ubuntu-release- Unapproved: update-manager (xenial-proposed/main) [1:16.04.14 => 1:16.04.15] (core)
[13:14] -queuebot:#ubuntu-release- Unapproved: accepted neutron [source] (bionic-proposed) [2:12.0.4-0ubuntu1]
[13:26] <smoser> ugh. i just uploaded bionic cloud-init accidnetly. meant to send to a ppa :-(
[13:26] <smoser> please reject the very recent upload of mine to bionic-proposed.
[13:26] -queuebot:#ubuntu-release- Unapproved: cloud-init (bionic-proposed/main) [18.3-9-g2e62cb8a-0ubuntu1~18.04.2 => 18.4-0ubuntu1~18.04.1] (edubuntu, ubuntu-cloud, ubuntu-server)
[13:27] <smoser> that one
[13:36] -queuebot:#ubuntu-release- Unapproved: snapd (xenial-proposed/main) [2.35.2 => 2.35.4] (desktop-core, ubuntu-server)
[13:36] -queuebot:#ubuntu-release- Unapproved: snapd (bionic-proposed/main) [2.35.2+18.04 => 2.35.4+18.04] (desktop-core, ubuntu-server)
[13:37] -queuebot:#ubuntu-release- Unapproved: snapd (trusty-proposed/universe) [2.35.2~14.04 => 2.35.4~14.04] (no packageset)
[13:37] -queuebot:#ubuntu-release- Unapproved: snapd (cosmic-proposed/main) [2.35.2+18.10 => 2.35.4+18.10] (desktop-core, ubuntu-server)
[13:38] -queuebot:#ubuntu-release- Unapproved: nova (cosmic-proposed/main) [2:18.0.0-0ubuntu5 => 2:18.0.1-0ubuntu1] (openstack, ubuntu-server)
[13:55] <tjaalton> smoser: there are two uploads with the same version?
[13:56] <smoser> tjaalton: yes. one about 11 hours ago by blackboxsw was designed.
[13:56] <smoser> one about 1 hour or less ago was by me accidently.
[13:56] <tjaalton> correction, three
[13:57] <smoser> the one several days ago has the wrong .orig.tar.gz
[13:57] <smoser> wrong meaning != the one in archive
[13:57] <smoser> (same content different hash)
[13:57] <tjaalton> and should be rejected too?
[13:57] <smoser> yeah.
[13:57] <smoser> there is also one with the wrong hash in xenial-proposed at the moment.
[13:57] <smoser> so if you could reject that too it'd be good.
[13:58] <smoser> and blackboxsw will upload one with correct orig tarball when he comes in
[13:58] -queuebot:#ubuntu-release- Unapproved: rejected cloud-init [source] (bionic-proposed) [18.4-0ubuntu1~18.04.1]
[13:59] <tjaalton> done
[13:59] -queuebot:#ubuntu-release- Unapproved: rejected cloud-init [source] (bionic-proposed) [18.4-0ubuntu1~18.04.1]
[13:59] -queuebot:#ubuntu-release- Unapproved: rejected cloud-init [source] (xenial-proposed) [18.4-0ubuntu1~16.04.1]
[14:00] <smoser> tjaalton: thanks. it looks right now
[14:33] <xnox> infinity, vorlon - should we try to sneak in gnutls 3.6.4 from experimental? it has tlsv1.3 support
[14:40] <xnox> and nss 3.39 too =/
[15:37] -queuebot:#ubuntu-release- Unapproved: cloud-init (xenial-proposed/main) [18.3-9-g2e62cb8a-0ubuntu1~16.04.2 => 18.4-0ubuntu1~16.04.1] (edubuntu, ubuntu-cloud, ubuntu-server)
[15:40] <blackboxsw> tjaalton just fixed xenial and proposed cloud-init uploads for SRU per SRU process  bug  https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1795953
[15:41] <blackboxsw> tjaalton: so thanks for rejecting the two previous uploads
[15:41] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (cosmic-proposed) [2.35.4+18.10]
[15:46] <blackboxsw> vorlon: I'm not sure if tjaalton is EOW.  do you think there will time today to peek at the above cloud-init SRU xenial/bionic?
[15:58] -queuebot:#ubuntu-release- Unapproved: plasma-discover (cosmic-proposed/universe) [5.13.5-1ubuntu4 => 5.13.5-1ubuntu5] (kubuntu)
[16:20] -queuebot:#ubuntu-release- Unapproved: distro-info (xenial-backports/main) [0.14build1 => 0.18~ubuntu16.04.1] (core)
[16:21] -queuebot:#ubuntu-release- Unapproved: accepted distro-info [source] (xenial-backports) [0.18~ubuntu16.04.1]
[16:41] <vorlon> blackboxsw: I'm off work today
[16:42] <vorlon> blackboxsw: I might be able to look when I get a moment, but best chance is to get somebody who's actually around (despite not being SRU vanguard)
[16:46] <blackboxsw> vorlon: I just heard about the vacation day. sorry about the ping. If someone gets to it, great! If not, we will keep calm and carry on.
[16:52] <tjaalton> blackboxsw: I'm back. this is only for xenial?
[16:53] <blackboxsw> tjaalton: nice! xenial and bionic
[16:53] <blackboxsw> https://launchpad.net/ubuntu/bionic/+queue?queue_state=1&queue_text=cloud-init
[16:53] <blackboxsw> https://launchpad.net/ubuntu/xenial/+queue?queue_state=1&queue_text=cloud-init
[16:53] <tjaalton> blackboxsw: I mean bug 1795953
[16:54] <tjaalton> ah
[16:54] <blackboxsw> ahh yes that bug is for both
[16:54] <blackboxsw> I'll drop the 18.04.1 from the version in the descr
[16:54] <blackboxsw> and nominate for bionic
[16:55] <blackboxsw> done
[16:56] -queuebot:#ubuntu-release- Unapproved: gimp-help (cosmic-proposed/universe) [2.8.2-0.2 => 2.8.2-1] (no packageset) (sync)
[16:57] -queuebot:#ubuntu-release- Unapproved: accepted gimp-help [sync] (cosmic-proposed) [2.8.2-1]
[16:58] <tjaalton> blackboxsw: so I assume this sync has already been pre-approved by someone?
[16:58] -queuebot:#ubuntu-release- Unapproved: gjs (cosmic-proposed/main) [1.54.0-1 => 1.54.1-1] (desktop-extra, mozilla, ubuntu-desktop) (sync)
[16:58] -queuebot:#ubuntu-release- Unapproved: mozjs60 (cosmic-proposed/main) [60.2.1-1 => 60.2.3-1] (no packageset) (sync)
[16:59] -queuebot:#ubuntu-release- New binary: linux-signed-lts-xenial [amd64] (trusty-proposed/main) [4.4.0-138.164~14.04.1] (kernel)
[16:59] <tjaalton> reading the wikipage..
[17:00] <blackboxsw> tjaalton: I don't think this is a pre-approved exception to the SRU process. cloud-init has a sanding SRU exception though
[17:00] <blackboxsw> https://wiki.ubuntu.com/CloudinitUpdates here ... right
[17:00] <blackboxsw> *standing SRU exception*   rather
[17:01] <tjaalton> right
[17:22] -queuebot:#ubuntu-release- New: accepted linux-signed-lts-xenial [amd64] (trusty-proposed) [4.4.0-138.164~14.04.1]
[17:22] -queuebot:#ubuntu-release- Unapproved: accepted cloud-init [source] (bionic-proposed) [18.4-0ubuntu1~18.04.1]
[17:23] <tjaalton> blackboxsw: I see that xenial has more patches than bionic?
[18:24] -queuebot:#ubuntu-release- Unapproved: kubuntu-meta (cosmic-proposed/universe) [1.377 => 1.378] (kubuntu)
[18:37] <blackboxsw> tjaalton: sorry was at lunch. yes, debian/patches in xenial were to retain original behavior, we only really use the patches dir to persist original behavior in an older release if our upstream snapshot added a feature that would have changed the original behavior in the stable series.
[18:38] <blackboxsw> bionic has had less new features that involved us having to retain original behavior, so less debian/patches
[18:38] <blackboxsw> over time that will likely grow
[18:40] <blackboxsw> thx for the bionic acceptance.
[19:06] <tjaalton> blackboxsw: ok, thanks
[19:06] -queuebot:#ubuntu-release- Unapproved: accepted cloud-init [source] (xenial-proposed) [18.4-0ubuntu1~16.04.1]
[19:06] <blackboxsw> woot! happy friday happy EOW
[20:21] -queuebot:#ubuntu-release- Unapproved: cysignals (cosmic-proposed/universe) [1.6.7+ds-4 => 1.6.7+ds-4ubuntu1] (no packageset)
[20:22] -queuebot:#ubuntu-release- Unapproved: accepted cysignals [source] (cosmic-proposed) [1.6.7+ds-4ubuntu1]
[21:44] -queuebot:#ubuntu-release- Unapproved: systemd (bionic-proposed/main) [237-3ubuntu10.3 => 237-3ubuntu10.5] (core)
[21:49] -queuebot:#ubuntu-release- Unapproved: cortina (cosmic-proposed/universe) [1.1.1-1ubuntu1 => 1.1.1-1ubuntu2] (no packageset)
[21:50] -queuebot:#ubuntu-release- Unapproved: accepted cortina [source] (cosmic-proposed) [1.1.1-1ubuntu2]
[21:57] -queuebot:#ubuntu-release- Unapproved: gnome-shell-mailnag (cosmic-proposed/universe) [3.26.0-1 => 3.26.0-1ubuntu1] (no packageset)
[21:58] -queuebot:#ubuntu-release- Unapproved: accepted gnome-shell-mailnag [source] (cosmic-proposed) [3.26.0-1ubuntu1]
[22:00] -queuebot:#ubuntu-release- Unapproved: gnome-shell-pomodoro (cosmic-proposed/universe) [0.13.4-3 => 0.13.4-3ubuntu1] (no packageset)
[22:01] -queuebot:#ubuntu-release- Unapproved: accepted gnome-shell-pomodoro [source] (cosmic-proposed) [0.13.4-3ubuntu1]
[22:21] -queuebot:#ubuntu-release- Unapproved: git (cosmic-proposed/main) [1:2.19.0-1ubuntu1 => 1:2.19.1-1ubuntu1] (core)
[22:33] -queuebot:#ubuntu-release- Unapproved: gnome-sound-recorder (cosmic-proposed/universe) [3.28.1-3 => 3.28.1-3build1] (no packageset)
[22:33] -queuebot:#ubuntu-release- Unapproved: accepted gnome-sound-recorder [source] (cosmic-proposed) [3.28.1-3build1]
[22:57] -queuebot:#ubuntu-release- Unapproved: stress-ng (cosmic-proposed/universe) [0.09.41-1 => 0.09.42-1] (no packageset) (sync)
[22:57] -queuebot:#ubuntu-release- Unapproved: accepted stress-ng [sync] (cosmic-proposed) [0.09.42-1]
[23:13] -queuebot:#ubuntu-release- Unapproved: babl (cosmic-proposed/universe) [0.1.56-1 => 0.1.58-1] (edubuntu, ubuntugnome, ubuntustudio) (sync)


[22:10] <cjwatson> May have managed to work around the Launchpad mirror prober crash that's been happening for a while.  It should be gradually catching up on its backlog now.


[00:01] <dartarrow> Hey guys, My battery meter doesn't thinks my battery is not plugged in after I wake from sleep. I'd like to  debug this, any idea how I'd start?
[00:01] <dartarrow> acpi shows the battery though.
[00:04] <Micdisc> ?
[00:04] <Micdisc> Anyone here?
[00:05] <dartarrow> its quiet
[00:05] <Micdisc> Anyone know where to get a decent laptop to Ubuntu without spending a bunch? used would be fine as well
[00:07] <Micdisc> wow, this has to be the quietest room I've been in with over 250 people in it
[00:12] <artemio> Hello this is my first time in IRc Chat
[00:38] <ahoneybun> I'm here
[01:40] <zed_> o0
[02:08] <OerHeks> old bug, i have not seen since 9.04, is back, headphone and speakers work together., awesome
[02:09] <OerHeks> skype refuses to work .. ctrl + l to clear xchat is broken ...
[02:10] <OerHeks> nvidia worked previously, now nvidia 310 is loaded but not in use.
[02:10] <OerHeks> should i do a fresh install of kubuntu?
[02:16] <OerHeks> background changes.
[02:53] <fbc_> Could someone tell where I can find a link for Kubuntu amd64+mac?? Can seem to loacte them on the Kubuntu site.
[03:03] <amingv> fbc_: Try here http://cdimage.ubuntu.com/kubuntu/daily-live/current/
[03:04] <smartboyhw_> fbc_: We have Kubuntu 12.04.2 LTS amd64+mac images in http://cdimage.ubuntu.com/kubuntu/releases/12.04.2/release/
[08:11] <bigbrovar> HI guys, just setup kmail for kubuntu 13.04 (clean install) and I found out after setting by office mail (based on rackspace) nothing shows in the inbox although mails in folders under the inbox are displayed but the inbox folder is completely empty
[08:11] <bigbrovar> anyone having this issue?
[08:15] <bigbrovar> The other day I saw a blog post where the kmail devs were complaining about  kmail bad reputation among users being a best on urban legend and a myth that is different from reality.. Well its because of stuff like this that I went to thunderbird in the first place. It just works no hassle.. I should not spend my time working trying to get my mail client to do what mail client are meant to do.. display mail.. I have to just let it out before I kill someone
[08:15] <bigbrovar> for a ruined frustrating day
[09:08] <noaXess> hello
[09:08] <noaXess> does anybody use mmv for multi file copy? i need to make multi symlinks and mmv can do that.. but cant figure out the patters: source folder countains lot of files.. in the destination folger i need symlinks to the files in sourcefolder..
[09:12] <noaXess> done with this example
[09:12] <noaXess> http://paste.ubuntu.com/5628534/
[09:31] <Anubis> hi ! yesterday i installed the new version of kubuntu in a vm and when i entered in muon software center and selected sorted by rating i noticed that it doesn't work as expected. instead of ordering from greatest to lowest, for example, it mixed the results(eg.: in graphics section there was some app with 5 stars , then 4 1/2 stars and so on. instead of putting first the 5 stars app it displayed first the 4 stars app, then 5 star app, then 4 1/2 stars). i g
[09:34] <Artakha> Anubis, i dunno about that but fyi your message got cut, there's a length limit ("then 5 star app, then 4 1/2 stars). i g")
[09:35] <Anubis> ohhh
[09:35] <Anubis> the last sentence was: i guess this is a bug.
[09:36] <Anubis> sorry, i forgot there is a limit for messages
[09:37] <Artakha> it's quite an obscure limit, irc clients don't tend to be able to know what the limit is and apply it to the input field
[09:37] <noaXess> ha next.. have 500 pics, need to rename them but: orig name = 123_text_1.jpg, result shoud be 123.jpg.. so on renam remove pattern "_text_1"
[09:37] <Artakha> noaXess, pipe it to sed s/text_1//
[09:39] <Artakha> Anubis, hm. muon doesn't show ratings at all to me
[09:42] <noaXess> Artakha: hm.. do it wiht mv file file | sed s/_text_1//
[09:42] <Artakha> nono
[09:43] <Artakha> echo the file name (so that the file name goes into output), pipe it through sed and save it in a var and use that
[09:43] <noaXess> yeah.. got it. i hopw ;).. try
[09:43] <Artakha> like f2=$(echo $file |sed s/_text//)
[09:43] <Artakha> mv $file $f2
[09:45] <noaXess> Artakha: simple and easy with rename: rename s/_text_1// *.*
[09:45] <Artakha> ooh, never knew of that
[09:45] <Artakha> this is useful
[09:45] <noaXess> Artakha: found here http://stackoverflow.com/questions/2372719/using-sed-to-mass-rename-files check first answer
[09:46] <noaXess> Artakha: but anyway thanks.. you give me the right direction ;).. so..
[09:46] <Artakha> yw :)
[09:46] <noaXess> anybody hungry? .. i am.. let's do something against it.. enjoy your meal..
[09:46] <noaXess> bbs
[09:48] <bla_> hello
[09:49] <bla_> I have this problem with the "digital clock widget": it always displays time as UTC even though I set the time zone
[09:51] <Artakha> bla_, make sure you set the default time zone in the configuration dialog
[09:51] <bla_> I did that
[09:52] <bla_> is there a way to manually change it to UTC+2
[09:53] <bla_> instead of setting it to "europe/berlin"
[12:42] <n8w> hey guys
[12:42] <n8w> i have upgraded to 13.04 and for some reason in settings->monitors there is no more option to set up two monitors
[12:43] <n8w> the only settings available is a screensaver
[13:03] <BluesKaj> Howdy all
[13:34] <sebastian> Hi, I'm on kubuntu 12.10 and kdesudo -- do-release-upgrade -m desktop -f DistUpgradeViewKDE prints "No new release found". is this ok?
[13:42] <BluesKaj> sebastian, just , do-release-upgrade , why the -m desktop -f ?
[13:44] <sebastian> BluesKaj: that's the command muon is executing. do-release-upgrade without arguments also prints "No new release found"
[13:46] <BluesKaj> sebastian, don't use kdesudo for one thing , sudo do-release-upgrade in the terminal is sufficient
[13:48] <sebastian> BluesKaj: just with sudo, it still says: "No new release found"
[13:50] <Artakha> sebastian, try update software sources and upgrade everything first
[13:52] <BluesKaj> sebastian, check muon , make sure Normal Releases is enabled in software sources , updates tab
[13:53] <sebastian> BluesKaj: I've just checked. it is
[13:53] <sebastian> Artakha: everythink is up to date
[13:53] <BluesKaj> lin the Release Upgrade drop downm
[13:53] <sebastian> yep
[13:53] <BluesKaj> ok , run uname  -a
[13:54] <sebastian> Linux sebastian-RC530-RC730 3.5.0-28-generic #48-Ubuntu SMP Tue Apr 23 23:03:38 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
[13:54] <sebastian> should be the latest kernel update
[13:54] <Torch> maybe even cat /etc/issue ;-)
[13:55] <sebastian> Torch: Ubuntu 12.10 :-)
[13:56] <Authority> Kubuntu 13.04: After installing the proprietary nvidia driver, I no longer see plymouth and therefore do not see the prompt to decrypt my hard drive.  Any ideas on how to fix?
[13:56] <BluesKaj> RC530-RC730 ??   the kernel 3.5.0-28 seems right
[13:57] <BluesKaj> sebastian, ^
[13:57] <sebastian> BluesKaj: an odd computer name :-)
[13:58] <BluesKaj> I thought perhaps you had installed a newer kernel and that's why release-upgrade wasn't responding
[13:59] <sebastian> is it possible to print some more debug output to the terminal, when executing do-release-upgrade?
[13:59] <BluesKaj> sebastian, yes in pastebin , then post the url here
[14:00] <sebastian> BluesKaj: well, atm, it is just printing "No new release found".
[14:02] <BluesKaj> muonsetting must be interfering somehow , but I seldom use it or have it installed so I'm not sure what the problem is.
[14:06] <sebastian> hm
[14:06] <sebastian> strange
[14:06] <BluesKaj> sebastian, try update-manager -d
[14:07] <BluesKaj> then, sudo do-release-upgrade -d
[14:08] <sebastian> I'll need to install updata-manager. that's ok?
[14:09] <BluesKaj> yes
[14:10] <sebastian> update-manager did found something and requests a reboot
[14:10] <sebastian> seems to be ok then
[14:10] <vitimiti> o/
[14:11] <vitimiti> I came here asking how to use skype in 13.04 version and now there's been an upgrade for skype. It is working pretty fine, from there on :)
[15:48] <bd___> Hello everyone. What is the best Kubuntu release for fresh installation right now? 12.04 lts or 13.04? thanks
[15:49] <smartboyhw> bd___: You want stability or new features?
[15:49] <bd___> smartboyhw: 13.04 is not stable?
[15:50] <bd___> smartboyhw: I would like to use kde 4.10 too
[16:35] <jtate> after my upgrade to 13.04 my panel theme is messed up.  How do I reset it?
[16:36] <jtate> I'm getting black text on a transparent background, which makes the text invisible when shown over a window with a black background.
[17:19] <rosco_y> I've been noticing my CUP 1 System Load running unusually high (100%) the majority of time, while running two softwares today (Calibre and Clementine).
[17:19] <rosco_y> I've also noticed that the drive where they are getting data from is spending a lot of time in a "disk sleep" state.  Does anyone know what I should do?
[17:22] <rosco_y> well, I'm washing dishes, so I"ll be relatively unresponsive, but I'll be checking in every few minutes
[17:55] <alesan> hi, I would like to add konqueror as file manager to the quick start area
[17:55] <alesan> how do I do that? I do not see any konqueror icon in the K menu
[18:00] <rosco_y> alesan: would it help to put it in your panel?
[18:00] <rosco_y> (I don't know how to add it to the start menu either)
[18:09] <zacarias>       Hi. I've been trying to load live cd's with 13.04 on my PowerPC mac. I've tried with Kubuntu and Lubuntu lice cd's. However, after the splash screen, booting freezes on a black screen with some messages, where the last one states "Stoping mount network filesystems".      The only thing I can do is to enter a terminal prompt with Ctrl+Alt+F1.      I currently have Kubuntu 12.04 installed on the machine, and that works well. I
[18:33] <BluesKaj> alesan, you have to install konqueror
[18:35] <BluesKaj> or if installed typr it in te kmenu search then drag it to the quick start
[18:37] <alesan> thanks :)
[19:27] <Specialist> I just upgraded a Kubuntu 8.04 installation to 12.04 LTS and apparently something went wrong when creting the runlevel symlinks in /etc/rc.x. Is there an easy way to regenerate these?
[20:03] <genii-around> Specialist: Did it complete OK from 8.04 to 10.04 ?
[20:34] <Specialist> genii-around: yes, but that was some time ago. only the 10.04 -> 12.04 upgrade broke things
[20:36] <Specialist> the dist-upgrade ran out of disk space on /boot, so we completed the upgrade using apt-get dist-upgrade. atm there are no unconfigured packages left and dpkg-reconfigure -phigh -a also went through without fixing things
[20:44] <Whiskey`Wonka> hmm, some kinda bug going on with muon
[20:45] <Whiskey`Wonka> im trying to isntall virtualbox and it says 'this operation cannot continue since proper authorization was not given' but it did not ask
[20:55] <wxl> Whiskey`Wonka: you only have that problem with virtualbox or everything?
[20:56] <Whiskey`Wonka> wxl: well its the first time its happened. i will find some package to isntall and see
[20:56] <wxl> Whiskey`Wonka: try pastebinit. that's useful.
[20:56] <wxl> (and small)
[20:57] <Whiskey`Wonka> nope happens with all
[20:58] <Whiskey`Wonka> a few days ago it was working fine, dont remember when exactly
[20:58] <Whiskey`Wonka> i can see what is going wrong, its not asking for my password, why, i have no idea.
[21:01] <wxl> if you kdesudo muon do ou have the same problem? can you install from the command line, e.g. sudo apt-get update && sudo apt-get dist-upgrade?
[21:05] <wxl> you can do a quick error check with this:
[21:05] <wxl> for f in /var/log/apt/*; do grep -i error $f; done
[21:05] <wxl> if you see something, you might want to dig into the logs and see what commands caused the problem
[21:36] <Whiskey`Wonka> eh
[21:36] <Whiskey`Wonka> your for f returns fatal error: Could not open /proc/acpi/toshiba/lcd.
[21:36] <Whiskey`Wonka> and nothign else
[21:37] <onai> hi everyone
[21:37] <Whiskey`Wonka> kdesudo muon does let me install
[21:37] <onai> I am trying out the new kubuntu 13.04
[21:38] <onai> but I cannot get it to boot in secure mode
[21:40] <wxl> for f in /var/log/apt/*.log; do grep -i error $f; done
[21:41] <Whiskey`Wonka> root@Hydras:~# for f in /var/log/apt/*.log; do grep -i error $f; done fatal error: Could not open /proc/acpi/toshiba/lcd. root@Hydras:~#
[21:42] <Whiskey`Wonka> i do not get why its trying to open /proc/
[21:42] <wxl> ah, so that's your only error. somewhere in those logs an error was thrown because of acpi
[21:42] <wxl> which is straaaaaaaange
[21:42] <Whiskey`Wonka> ls /var/log/apt/ history.log  history.log.1.gz  term.log  term.log.1.gz
[21:42] <Whiskey`Wonka> yea ive got ACPI issues on this laptop
[21:43] <wxl> ah
[21:43] <wxl> well it's probably irrelevant
[21:43] <Whiskey`Wonka> damn cpu fan doesnt work in 13.10
[21:43] <wxl> grep -i exec /usr/share/applications/kde4/muon.desktop
[21:43] <wxl> does that give muon %i -caption "%c" ?
[21:44] <Whiskey`Wonka> Exec=muon %i -caption "%c"
[21:44] <wxl> strange that it doesn't call for privs right from the get go
[21:45] <Whiskey`Wonka> i know
[21:45] <wxl> but it could make sense. you don't need privs to search
[21:45] <wxl> i'm thinking about this from a command line sense
[21:45] <wxl> i never use the gui :)
[21:45] <Whiskey`Wonka> right but as soon as you try to apply, it wants them
[21:45] <wxl> apt-cache doesn't require sudo
[21:45] <wxl> now that makes sense because the update && upgrade does require privs
[21:45] <Whiskey`Wonka> i wouldnt but i was told that apt-get and muon do not work together and for some time apt-get was screwing up shit
[21:46] <wxl> harumph that sounds like **** to me
[21:47] <wxl> i'm running 13.10 and been only using apt with no probs
[21:47] <Whiskey`Wonka> wxl: i dunno, apt was deff creating issues back when 12.04 came out
[21:48] <Whiskey`Wonka> a clean isntall and never touch apt, it was ok
[21:48] <Whiskey`Wonka> touch apt, depends hells
[21:48]  * wxl shrugs
[21:48] <wxl> i've been using apt and apt only since about 11.04
[21:48] <bazhang> Whiskey`Wonka, what version of kubuntu
[21:49] <Whiskey`Wonka> bazhang: 13
[21:49] <bazhang> Whiskey`Wonka, thats not a version
[21:49] <Whiskey`Wonka> its 13.04
[21:50] <Whiskey`Wonka> Raring Ringtail
[21:50] <Whiskey`Wonka> ill reboot later tonight and see if that changes anything
[21:51] <Whiskey`Wonka> linu is slowly turning into windows, windows is slowly turning into linux
[23:11] <zacarias> Hi. I've been trying to load live cd's with 13.04 on my PowerPC mac. I've tried with Kubuntu and Lubuntu lice cd's. However, after the splash screen, booting freezes on a black screen with some messages, where the last one states "Stoping mount network filesystems". The only thing I can do is to enter a terminal prompt with Ctrl+Alt+F1. I currently have Kubuntu 12.04 installed on the machine, and that works well. I should add that the same problem has h
[23:21] <wxl> zacarias: it appears your message was truncated. have you tried burning new cds and checking the md5 of the iso AND the md5 of the cd? have you ensured you burned at slowest speed/
[23:23] <wxl> zacarias: not sure it's relevant but look at http://ubuntuforums.org/showthread.php?p=11407278
[23:31] <zacarias> wxl: Actually, I didn't try burning new cd's nor have I checked the md5 of the iso and of the cd. But the cd's appear to be working. The computer boots from them, the splash screen with the "Kubuntu" and "Lubuntu" logo appears, but it just goes to the blank screen with the messages and then, nothing more happens. As for the thread, I think it's not quite the same problem.
[23:33] <wxl> zacarias: well, one bit difference can mean something that boots right but doesn't act right
[23:33] <wxl> zacarias: as for the thread i would at least try it.


[02:01] <krandle> anyone able to help with a simple-scan memory problem?
[02:02] <krandle> tried scanning something at 2400dpi to test it out, and simple-scan crashed when i tried to save it.
[02:02] <krandle> also crashing when i try to restart
[02:02] <krandle> what to do?
[05:33] <brian4442> Hello - I am using ubuntu 15.04. It seems impossible to enable natural scrolling with synclient. Anyone know why?
[07:49] <stunatra> is there any way to disable the automatic login? i have a password but xfce doesnt seem to care about it, only asks for it after the laptop is suspended
[08:14] <nvt_> I think I enabled some magnifying glass by mistake on Xubuntu, any idea how to get it off :D
[08:16] <elfy> nvt_: alt+scroll wheel maybe
[08:17] <nvt_> thanks :D
[08:17] <elfy> :)
[08:18] <elfy> that's filed under "Yea I did that one once too"
[11:31] <xubuntu93w> Hi.  Can someone help me with UFW-firewall? After "sudo ufw enable" access to network blocks, after "sudo ufw disable" — access to network appears again. Policy is default: deny (in), allow (out), disable (forward).
[11:33] <koegs> xubuntu93w: can you nopaste the output of "sudo ufw status" while enabled?
[11:35] <koegs> xubuntu93w: sorry, it is "sudo ufw status verbose"
[11:37] <xubuntu93w> koegs: I am not now in Xubuntu. But "sudo ufw status verbose" is: active, and deny (in), allow (out), disable (forward), logging on (low).
[11:38] <xubuntu93w> I have to say that my ISP uses PPTP to shere access to Internet for clients.
[11:38] <xubuntu93w> share*
[14:44] <amari> Is there some tutorial to use Compiz with Xubuntu?
[14:45] <knome> no official one at least
[14:48] <amari> knome: And is it hard to do it by yourself?
[14:48] <amari> knome: What about compton?
[14:49] <xangua> it's hard to install compiz are you asking¿
[14:49] <xangua> sudo apt-get install compiz compton
[14:50] <xangua> you'll need metacity themes with compiz in xfce
[14:50] <knome> amari, i don't know, i don't use compiz
[14:50] <amari> xangua: How to enable one of them in place of xfwm4?
[14:50] <xangua> just put them at startup¿
[17:12] <ryan_> Hi, I'm wondering if there is a way to make the whiker menu transparent?
[17:12] <ryan_> *whisker
[17:20] <elfy> ryan_: yes - right click -properties appearance, at the bottom background opacity
[17:20] <elfy> doesn't affect menu entries though
[17:23] <ryan_> Right click on what exactly?
[17:23] <elfy> the menu button
[17:24] <ryan_> Wow ok there we go!  Thanks!
[18:56] <slee2> hello, something weird is going on, i was on xubuntu 14.04, downloaded 15.04, trying to install from stick, but when i choose the drive to install to, it tells me it can't create swap?
[19:16] <slee2> nm, solved, just cfdisk'd it, beat it like it owed me money
[19:19] <slee2> it is strange though, 1st time i've ever seen that after a gazillion installs
[21:11] <reborn> what's good apps bootable in linux?
[21:13] <knome> humm?
[22:17] <sleezio> anyone else getting the "ACPI-PCC probe failed" at boot? it doesn't seem to cause any probs after it does boot up
[22:17] <sleezio> ...on 15.04
[22:18] <sleezio> appears to be a new kernel feature looking at your motherboard
[22:31] <xubuntu696> I have a problem I don't know how to describe. Sometimes (about 20%) my screen screws up. The PC boots up then I attempt to click something, like the browser, and my screen screws up. I'm unable to do anything so I must restart the PC by holding down the power button for 5 seconds. My specs: 32bit xubuntu 14.04 eMachines EL1200-06w - Athlon 64 2650e 1.6 GHz Proc - 2 GB Mem - 160 GB HDD. I have a pic but I don't know how to attach
[22:32] <xubuntu696> How do I post a picture?
[22:33] <sleezio> take a screenshot, post to imgur.com
[22:33] <xubuntu696> ok
[22:36] <sleezio> i use an app called 'shutter', lets you take screen/select/window shots and upload to any of several image hosts then it gives you the url to the image...comes in handy
[22:38] <xubuntu696> Here is the picture: http://imgur.com/25fHcLZ
[22:38] <sleezio> yikes
[22:39] <brainwash> modern art?
[22:39] <sleezio> type this in chat: /exec -o inxi -G
[22:40] <xubuntu696> This PC had XP on it a few days ago. I convinced the owner to let me install xubuntu.
[22:40] <sleezio> xubuntu696, type that command in chat so i can see your video info
[22:41] <xubuntu696> done
[22:42] <Unit193> He's on webchat, that'll do nothing...  Terminal:  inxi -c0 -G | pastebinit
[22:43] <xubuntu696> You want me to open a terminal then then type: inxi -c0 -G | pastebinit
[22:44] <sleezio> yuh
[22:45] <sleezio> after you do, it'll give you a url, paste in chat
[22:45] <xubuntu696> Here is what I got:
[22:45] <xubuntu696> The program 'inxi' is currently not installed. You can install it by typing: sudo apt-get install inxi You are trying to send an empty document, exiting.
[22:45] <sleezio> oh, nm
[22:49] <xubuntu696> Does it help to know that under additional drivers it shows I'm using X.Org X server - Nouveau display driver
[22:50] <sleezio> have you tried using the driver for your specific videocard?
[22:50] <sleezio> youshould see it in that same list
[22:51] <xubuntu696> No I haven't tried. There are Nvidia legacy binary drivers listed I could try.
[22:51] <sleezio> use the one that ends with tested)
[22:52] <sleezio> after you do that, you'll need to reboot
[22:52] <xubuntu696> How do I choose between 304.125 and 173.14.39?
[22:53] <xubuntu696> Oh, I'll try tested.
[22:59] <farf> hi all
[23:00] <farf> i have a touchpad, i want to middle-click with two fingers, not three
[23:00] <farf> how can i do that
[23:00] <farf> iic there was a setting but it was ignored, but i might be remembering gnome
[23:00] <farf> i assume it would be some xorg setting
[23:02] <sleezio> farf, try: http://askubuntu.com/questions/306412/how-can-i-setup-my-touchpad-multi-finger-tapping-functionality
[23:59] <acro458> Using xubuntu fresh installation on latest virtualbox. Used Host+D to install virtualbox tools. Resolution was 1440x900, which is what I want.  Ubuntu says it needs to do updates. I update ubuntu. The login screen is 1440x900, but once I log in it goes to  1024x768!!! Wtf!!! I go to Displays and 1440x900 is not listed as a resolution choice. What do I do?


[00:01] <Corey>   Uploading salt_0.17.0-1lucid.dsc: [Errno 110] Connection timed out
[00:01] <Corey> Why do I wrestle and struggle with dput every time I have to shove something into a PPA, I wonder? :-)
[22:31] <mgriffin> Is there by chance a way to see a list of PPAs which exist for a given series? https://launchpad.net/ubuntu/+ppas
[22:32] <mgriffin> eg http://dl.fedoraproject.org/pub/epel/6/x86_64/repoview/
[22:32] <mgriffin> (epel is somewhat like ppa but for centos)
[22:36] <mgriffin> say i was looking for rsandbox https://launchpad.net/ubuntu/+ppas?name_filter=rsandbox and want to know which series is supported by the ppa


[07:08] <TheMue> morning
[07:35] <rogpeppe> TheMue: morning
[07:36] <TheMue> rogpeppe: hiya
[08:35] <TheMue> fwereade: heya
[08:35] <fwereade> TheMue, morning
[08:35] <fwereade> TheMue, how's it going?
[08:36] <TheMue> fwereade: fine, just waiting for Aram to discuss a mstate idea with him
[08:36] <fwereade> TheMue, cool
[08:37] <TheMue> fwereade: and how are you?
[08:37] <fwereade> TheMue, so-so :)
[08:37] <TheMue> fwereade: doesn't sound so really cool
[08:37] <fwereade> TheMue, still trying to figure out how niemeyer's upgrade plans will *actually* fit into the uniter
[08:37] <fwereade> TheMue, so finishing it feels far away agin
[08:38] <TheMue> fwereade: will be like driving on cobblestone for a while but it will fit
[08:38] <fwereade> TheMue, yeah, we'll get there :)
[08:38] <fwereade> TheMue, cheers :)
[08:39] <TheMue> fwereade: the hardest parts will be the semantic changes with lifecycle and caching/refreshing, where state using code has to be changed
[08:40] <fwereade> TheMue, I'm hoping actually the lifecycle will turn out ok, I sketched that out the other day and I *think* its impact is pretty localised from my pov
[08:40] <fwereade> TheMue, that's not to say it's easy on you ofc ;)
[08:41] <TheMue> fwereade: so far it's not too hard, only effort. but every (m)state user will have to take care that the api is changing
[09:06] <Aram> yo.
[09:07] <davecheney> sup!
[09:09] <TheMue> Aram: hi
[09:09] <TheMue> davecheney: oh, hi too ;
[09:10] <TheMue> Aram: need your help
[09:10] <Aram> I'll try my best.
[09:11] <TheMue> Aram: when building mstate I get funnily a "type *mgo.Collection has no field or method UpdateId" even with mgo v2 (with UpdateId) installed
[09:12] <TheMue> Aram: did you had the same
[09:12] <TheMue> ?
[09:12] <Aram> no.
[09:12] <davecheney> TheMue: go get -u .../mgo
[09:12] <Aram> perhaps you should reupdate mgo?
[09:12] <davecheney> err, go get -u ...mgo
[09:12] <TheMue> Aram, davecheney: will try
[09:14] <TheMue> ooops, getting a brz error now during go get
[09:14] <TheMue> oh, only temporary, now it updated
[09:15] <TheMue> and fixed, thx Aram and davecheney
[09:15] <Aram> great
[09:16] <TheMue> Aram: take a look at http://pastebin.ubuntu.com/1160449/ and http://pastebin.ubuntu.com/1160447/. a way to reuse ensureLife()
[09:16] <Aram> yeah, the only problem is that machines have integer ids
[09:16] <Aram> I wish they had string ids
[09:17] <Aram> relations also have integer ids...
[09:17] <Aram> I wish everything had string ids
[09:19] <Aram> we could use interface{} for as the id function parrameter for ensureLife in the meantime
[09:19] <Aram> mgo uses reflection and it should work.
[09:19] <TheMue> Aram: it's worth a try, yes
[09:20] <TheMue> Aram: i'll give it a try here for units
[09:33] <TheMue> Aram: in State.RemoveRelation() you check if the relation is Dead but you don't refresh before. so your life may be Dying (and so the function returns an error) while a concurrent operation already may have marked it Dead.
[09:33] <TheMue> Aram: this is no error
[09:33] <TheMue> Aram: i only think about if a refresh would make sense here
[09:34] <TheMue> Aram: at least your Dead-check in the bson selector is the most important part
[09:36] <Aram> no, it's fine the way it is.
[09:36] <Aram> you should not remove a relation before you are sure it is dead (e.g. you called r.Die() or r.Refresh())
[09:37] <rogpeppe> Aram: yeah, machine ids being integers is problematic in other places too
[09:37] <Aram> that forces the client to always call r.Die() if he wants to remove a machine, and that's fine.
[09:37] <Aram> it can be called any number of times.
[09:40] <TheMue> Aram: to me it's a bit harsh to panic on a maybe already dead entity
[09:40] <Aram> if you want to remove a relation, call r.Die() and you'll never panic :).
[09:41] <TheMue> Aram: so it's only to discipline the state user
[09:41] <Aram> yes.
[09:42] <TheMue> Aram: *lol*
[09:43] <Aram> perhaps we could add a DieAndRemove() function if it's such a common operation.
[09:43] <Aram> no
[09:43] <Aram> we should not
[09:43] <Aram> yes, I remember now
[09:44] <Aram> DieAndRemove() is harmful, usually the watcher that receives the dead event calls remove.
[09:44] <Aram> and that guy gets a machine with a dead cache and it's fine to call remove.
[09:44] <Aram> DieAndRemove will mask the dead event, and that may or may not be a bug.
[09:45] <Aram> if you really want to remove it independent of any watchers, call r.Die() and r.Remove().
[09:45] <Aram> that makes it very explicit.
[09:45] <TheMue> Aram: ic, sounds reasonable
[10:03] <Aram> TheMue: many tests use regular nodes (e.g. machine nodes) as confignodes to inject corrupt data or to inject data without calling the real setters. that's... clever. do we want to preserve this behavior?
[10:04] <Aram> because I had a plan to make tests in mstate_test pure, not to do any trickery outside the public API.
[10:04] <Aram> and move the tests that can't be pure into internal tests.
[10:04] <Aram> but many tests use this trick.
[10:05] <Aram> plus I'd need to modifcy confignodes, as now they are in a different collection, so a machine node can never be a config  node.
[10:05] <TheMue> Aram: we have to check them individually. maybe the concrete reason is only in using ZK
[10:06] <TheMue> Aram: i like the fact that they#ve got an own collection
[10:23] <Aram> TheMue: yeah, I did a check and the config node trick is only used in 4 tests.
[10:23] <TheMue> Aram: great, i think we'll find a way to get around
[10:32] <TheMue> Aram: btw, i like the speed of the mstate tests. there still several missing, but i hope it will stay so fast.
[10:32] <Aram> I hope that as well.
[10:32] <Aram> watchers will slow it somewhat, but I hope it will still e fast
[10:38] <TheMue> Aram: i just proposed https://codereview.appspot.com/6476044/
[10:39] <TheMue> Aram: we could move all lifecycle stuff in an own file and give it an own test suite
[10:41] <Aram> will take a look after lunch
[10:43] <TheMue> Aram: ok
[11:30] <Aram> TheMue: you have a review.
[11:30] <TheMue> Aram: thx
[11:31] <TheMue> Aram: oh, removed the service check, sh… ;)
[11:32] <TheMue> Aram: the rest of RemvoveUnit() is like relation and i wanted to keey it common
[11:33] <Aram> that should be changed too.
[11:34] <TheMue> Aram: then it's ok that i change it back, will do so
[11:34] <Aram> thanks
[11:38] <TheMue> Aram: what problem do you have with "if err := foo(); err != nil { … }"?
[11:38] <TheMue> Aram: IMHO is a common idiom
[11:39] <Aram> I find it hard to read, personally, I know it's common.
[11:39] <Aram> v, ok := m[something]
[11:40] <Aram> that's fine to me because it makes ok have a very local scope
[11:40] <Aram> which is great
[11:40] <Aram> but for errors I don't like it that much
[11:42] <TheMue> Aram: ok, even if i like it i will change it here ;)
[11:43] <Aram> if you feel strongly about it, keep it, it boils down to personal preference.
[11:47] <TheMue> Aram: already changed :P
[11:48] <TheMue> Aram: you've seen, i added one simple test of the state tests
[11:48] <TheMue> Aram: there it's the final one before all watcher tests
[11:48] <Aram> yes, seen it
[11:49] <Aram> I'm surprised that it works though
[11:50] <TheMue> Aram: maybe RemoveService() currently doesn't care for lifecycles?
[11:51] <Aram> ah, it marks associated units as dying
[11:52] <TheMue> Aram: *lol* ok, works by accident
[11:54] <TheMue> Aram: do you have a table of which state tests are already ported to mstate?
[11:54] <Aram> no.
[11:54] <Aram> I just picked and chosen as I saw fit
[11:54] <Aram> when I implemented a feature I searched for tests that use that feature
[11:54] <Aram> and ported those
[11:57] <Aram> TheMue: another review
[11:58] <TheMue> thx
[12:10] <TheMue> Aram: ah, thx for the explanation of the "hard death" :)
[12:11] <TheMue> Aram: i would like to move the table driven test to a lifecycle suite. because if all use the same ensureLife() there's no need for testing it multiple times
[12:13] <Aram> yes, I think it's good if we move the Life type and ensureLife to life.go, and stateChanges and the other tests to life_test.go, in a different suite.
[12:17] <TheMue> Aram: shall I do it?
[12:17] <Aram> TheMue: please do, and also convert relations to the new function.
[12:17] <TheMue> Aram: ok
[12:17] <niemeyer> Yo!
[12:17] <Aram> hi
[12:18] <TheMue> niemeyer: heya
[12:18] <niemeyer> Aram: Shall be ready for us to poke on it
[12:18] <Aram> niemeyer: what, txn?
[12:18] <niemeyer> Aram: Watches would need a small extension to have mtime on the transaction, but that's trivial.. we can convert meanwhile
[12:19] <niemeyer> Aram: Yeah
[12:19] <Aram> great.
[12:19] <Aram> show me what you got, anytime
[12:20]  * TheMue listens too
[12:21] <niemeyer> Aram: Cool, I'll just move to the main repo, as I've been mistakingly pushing it in a branch in a subdir
[12:24] <niemeyer> Aram: done
[12:24] <niemeyer> Aram: It's not tagged, so you'll need to bzr pull it
[12:25] <Aram> I can't use go.pkgdoc with it? :(
[12:26]  * Aram runs godoc
[12:26] <niemeyer> Aram: Not yet..
[12:26] <niemeyer> Aram: I'll announce it when I have a moment
[12:26] <niemeyer> Aram: and then tag it properly
[12:27] <Aram> no issue, godoc is great
[12:27]  * Aram is reading now
[12:28] <niemeyer> Aram: I'll also document it better, and write a blog post describing details
[12:28] <niemeyer> Aram: But for the moment it feels wise to just get out of your way :)
[12:34] <Aram> ok, I read the docs.
[12:34] <Aram> now I shall read the tests to get a feel for it.
[12:37] <niemeyer> Aram: sim_test.go is where the meat is
[12:38] <niemeyer> Aram: txn_test.go can see improvements
[12:38] <Aram> yes, reading it already
[12:38] <niemeyer> Aram: The API is almost boring, thankfully
[12:45] <Aram> great, thanks.
[12:45] <Aram> I'm going to play with it.
[12:49] <rogpeppe> niemeyer: ping
[12:51] <niemeyer> rogpeppe: Yo
[12:52] <rogpeppe> niemeyer: i was wondering how much the upgrade logic needs to be aware of the dev/release (odd/even) version numbers
[12:53] <rogpeppe> niemeyer: i'm thinking it perhaps doesn't, but i'm probably wrong there
[12:53] <niemeyer> Aram: I think we should start by porting the simple stuff to it
[12:53] <niemeyer> Aram: Making sure that the changes ("$set", etc) are happening in transactions
[12:53] <niemeyer> rogpeppe: IIRC, in our last conversation (in Lisbon?) we agreed it doesn't
[12:54] <Aram> yes, I'll do it after I'm done with the things I'm working on ATM.
[12:54] <rogpeppe> niemeyer: cool, i'd forgotten about that conversation.
[12:54] <niemeyer> rogpeppe: We agreed, IIRC, that all we needed was in the upgrade-juju command itself
[12:54] <niemeyer> rogpeppe: If the decision to use it has been made, then why should the agent care
[12:54] <niemeyer> rogpeppe: IIRC
[12:55] <rogpeppe> niemeyer: ah, sorry, i was talking about the logic in the upgrade-juju command itself
[12:56] <rogpeppe> niemeyer: perhaps all it needs to do is make sure it never upgrades from a release version to a dev version.
[12:57] <rogpeppe> (and vice versa?)
[12:58] <niemeyer> rogpeppe: Unless --dev is used
[12:58] <niemeyer> rogpeppe: Vice versa sounds fine
[12:58] <rogpeppe> niemeyer: i think i'll add a dev flag to environs.BestTools
[12:59] <niemeyer> rogpeppe: Sounds sane
[13:03] <rogpeppe> niemeyer: cool
[13:42] <rogpeppe> niemeyer: i'd appreciate a review of this when you have a moment BTW, as i'm stacking stuff on top of it. https://codereview.appspot.com/6485044/
[13:42] <rogpeppe> niemeyer: (it's fairly trivial stuff)
[13:44] <niemeyer> rogpeppe: Looking
[13:51] <niemeyer> rogpeppe: LGTM, with a small side-tracking peeve about the hackish storage test type
[13:52] <rogpeppe> niemeyer: yeah, i thought you might not be keen on that. i wasn't entirely sure of the best way to do it. perhaps pushing into the dummy env might be better.
[13:52] <niemeyer> rogpeppe: Why? It's just a type with methods
[13:52] <niemeyer> rogpeppe: What's wrong with just having that?
[13:53] <rogpeppe> niemeyer: quite a few methods that need to be changed every time the Environ type changes.
[13:53] <rogpeppe> niemeyer: hence i thought best to inherit them all so that piece of code is only sensitive to the methods it cares about.
[13:54] <rogpeppe> niemeyer: i agree it feels hackish tho'
[13:57] <rogpeppe> niemeyer: hmm, actually i can avoid the *most* hackish bits more easily
[13:59] <niemeyer> rogpeppe: Having that in the dummy environment sounds sane to
[13:59] <niemeyer> too
[13:59] <niemeyer> rogpeppe: A dummy.Storage we can make use of
[13:59] <niemeyer> rogpeppe: So we can do something less awkward once
[14:00] <rogpeppe> niemeyer: the dummy Storage already works actually
[14:00] <niemeyer> rogpeppe: Well, so do we have a problem? :)
[14:06] <rogpeppe> niemeyer: probably not. the FindTools tests do it already. i was doing too much of a naive translation of the tests, i think.
[14:21] <TheMue> Yeah!
[14:22] <TheMue> Aram: found a nice way to do the table driven lifecycle test for all entities in life_test.go
[14:22] <Aram> how?
[14:24] <TheMue> Aram: let me just add unit (relation is already integrated, and i'll show you).
[14:24] <Aram> please
[14:24] <TheMue> oops, bracket set too late. ;)
[14:25] <TheMue> Aram: it's a kind of "for each living do the same as aram has done for relation before".
[14:30] <TheMue> Aram: Great! Easier than thought. Will propose it now.
[14:32] <niemeyer> TheMue: Hm
[14:33] <niemeyer> TheMue: I'm not sure if I see what you mean, but FWIW, what Aram has done in relations shouldn't be *copied*
[14:33] <niemeyer> TheMue: The idea is to refactor it so that we have a single implementation that is used for all types
[14:33] <TheMue> niemeyer: yes, we are working on it. first part has been the only function ensureLife()
[14:35] <TheMue> niemeyer: but the goal shall be an embeddable type
[14:35] <niemeyer> TheMue: Superb, I imagined you'd already going in that direction, but decided to mention as it's cheaper than fixing later :-)
[14:36] <Aram> pro tip: if you are using chrome and you have pinned tabs with e-mail etc, never ever open more then one window. you'll close them in wrong order and it will forget your precious saved tabs.
[14:36] <TheMue> niemeyer: indeed :D
[14:40] <TheMue> Aram: take a look at https://codereview.appspot.com/6481045/
[14:44] <TheMue> niemeyer: btw, /me likes state on mongo. pretty clean (and fast), simply elegant
[14:44] <niemeyer> TheMue: That's great to hear!
[14:48] <Aram> TheMue: you have a review
[14:50] <TheMue> Aram: thx *click*
[14:52] <TheMue> Aram: yes, your idea sounds reasonable. will move it.
[14:52] <Aram> great
[14:52] <TheMue> Aram: you've seen the idea? when e.g. service is migrated we'll just add it to the slice of envs. ;)
[14:53] <TheMue> Aram: thanks to your idea with relation it's quite simple
[14:54] <Aram> yes, it's great
[14:57] <TheMue> 4 secs for the whole beast, pretty fast. sadly it will slow down when all watcher tests are added.
[15:05] <niemeyer> TheMue: Let's keep an eye on those
[15:05] <niemeyer> TheMue: It should be possible to keep the impact pretty low
[15:07] <TheMue> niemeyer: right time, i just wanted to ask if there's already a first proposal or impl for watchers in mstate
[15:07] <niemeyer> TheMue: No, as we were waiting to see if the txn idea would flop or not
[15:08] <niemeyer> TheMue: It seems to work, so we can now start working on it
[15:08] <niemeyer> TheMue: (in that direction, rather than the old ones)
[15:08] <TheMue> niemeyer: hey, c'mon, it's by you, so it can't flop *lol*
[15:08] <niemeyer> TheMue: Oh man, I wish that was true
[15:10] <TheMue> niemeyer: i know have to leave the keyboard for a short time. can you msg me the uri to pull it?
[15:12] <Aram> I just did a bzr pull inside the mgo dir and it was there afterwards
[15:14] <niemeyer> TheMue: ^
[15:23] <Aram> niemeyer: multiple txn runners can use the same collection, right?
[15:25] <niemeyer> Aram: Yeah, they must if they are sharing affected documents
[15:25] <Aram> ok.
[15:25] <niemeyer> Aram: We only need a single tc
[15:25] <Aram> do we need more than one runner?
[15:26] <Aram> niemeyer: ^
[15:26] <niemeyer> Aram: No, everybody can share the same one
[15:27] <Aram> great.
[15:27] <Aram> thanks
[15:27] <niemeyer> Aram: np
[16:03] <fwereade_> taking a break, back later
[16:07] <Aram> niemeyer: how can I do an UpdateAll with your txn?
[16:08] <Aram> is it possible?
[16:08] <niemeyer> Aram: It's not
[16:08] <Aram> :(
[16:08] <niemeyer> Aram: Yeah, this is a change to consider
[16:08] <niemeyer> Aram: But we can live without it for now I suppose
[16:09] <Aram> well, we do use UpdateAll
[16:09] <Aram> to update all units of a service
[16:09] <niemeyer> Aram: Sure.. where are we using it ATM?
[16:09] <Aram> in RemoveService
[16:10] <niemeyer> Aram: To begin with, we can put them all in a single transaction and run it
[16:10] <niemeyer> Aram: Won't scale to extremes, but we can address that down the road
[16:10] <Aram> but we don't know the ids
[16:11] <niemeyer> Aram: Hmm.. interesting.. let me think for a moment how we can solve this cheaply
[16:11] <niemeyer> Aram: What's the change document?
[16:12] <Aram> change = bson.D{{"$set", bson.D{{"life", Dying}}}}
[16:12] <Aram> more precisely
[16:12] <Aram> 	sel = bson.D{{"service", svc.doc.Name}}
[16:12] <Aram> 	change = bson.D{{"$set", bson.D{{"life", Dying}}}}
[16:12] <Aram> 	_, err = s.units.UpdateAll(sel, change)
[16:19] <niemeyer> Aram: Hmm
[16:21] <niemeyer> Aram: I think we can make the units themselves responsible for setting their dying state
[16:21] <niemeyer> Aram: And we can ref-count live units on the service itself
[16:22] <niemeyer> Aram: So we know when the service can transition to dead
[16:22] <niemeyer> Aram: The units then have to monitor the service to see when they're supposed to shut down
[16:22] <Aram> so each unit watches for its service, and sets itself to dying when the service is set to dying?
[16:23] <niemeyer> Aram: Yeah
[16:23] <Aram> that's potentially a lot of watches :).
[16:23] <Aram> ok.
[16:23] <niemeyer> Aram: In the same transaction that dec's the alive refcounter
[16:23] <Aram> I've put a // BUG in the code so I remember to do this after I implement watcher
[16:23] <Aram> (obviously I can't do it before).
[16:23] <niemeyer> Aram: Well, not really, sorry
[16:23] <niemeyer> Aram: Erm.. I'm correcting myself, sorry
[16:24] <niemeyer> Aram: The ref count should only be dec'd when the unit goes Dead
[16:24] <niemeyer> Aram: Regarding being a lot of watchers, not really
[16:24] <niemeyer> Aram: We already have to monitor the service from the unit for other reasons
[16:25] <niemeyer> Aram: and again, the watching logic should be implemented *client side*
[16:25] <niemeyer> Aram: There shouldn't be a significant delta in monitoring the service or not
[16:29] <niemeyer> Aram: Which code?
[16:29] <Aram> niemeyer: ?
[16:29] <niemeyer> Aram: What's the // BUG?
[16:30] <Aram> in RemoveService
[16:30] <Aram> 	// BUG(aram): units should monitor their service and set themselves
[16:30] <Aram> 	// to dead. waiting for watchers.
[16:30] <niemeyer> Aram: Why RemoveService cares?
[16:31] <Aram> niemeyer: RemoveService doesn't care, I care so i remember to do it after I implement watchers.
[16:32] <niemeyer> Aram: Okay, but we can get rid of UpdateAll already, right?
[16:32] <Aram> no?
[16:32] <niemeyer> Aram: Okay, so that's what I'm trying to talk about :)
[16:33] <niemeyer> Aram: What has to change for us to fix RemoveService in both state and mstate now?
[16:33] <niemeyer> Aram: Well, or maybe just mstate
[16:34] <Aram> first we need to implement lifecycle for services.
[16:37] <Aram> niemeyer: if I have an Assert:     txn.DocMissing, the Run() will fail if I call it twice, right?
[16:37] <Aram> (with the same ops)
[16:38] <Aram> (and if I insert something in that ops).
[16:39] <niemeyer> Aram: That's right
[16:39] <niemeyer> Aram: It'll return ErrAborted when the assertion is false
[16:39] <niemeyer> Aram: (without touching anything)
[16:39] <Aram> niemeyer: I think I found a bug in txn.
[16:39] <niemeyer> Aram: Woot
[16:39] <niemeyer> Aram: What's up?
[16:40] <Aram> basically you can add documents that have the same no-id field identical, and that field is Unique: true
[16:42] <Aram> so you can add {"_id": 0, "foo": x} and {"_id": 1, "foo": y} even if "foo" should be unique.
[16:42] <niemeyer> Aram: Well, I'm not sure I understand the problem.. you certainly can't add the document because MongoDB itself will prevent that from happening
[16:42] <Aram> maybe it doesn't end up in the database, but Run doesn't complain.
[16:42] <niemeyer> Aram: Please read the documentation of Operation in the Insert and Assert fields
[16:44] <Aram> I did, not sure your point.
[16:45] <Aram> my assert is txn.DocMissing whoch is not strong enough.
[16:45] <niemeyer> Aram: My point is that what you're complaining about is precisely described there
[16:46] <niemeyer> Aram: Of course.. DocMissing means the id isn't there.. it certainly won't dig in the database to see what are all the unique fields that the document may have and which ones are satisfied or not
[16:46] <niemeyer> Aram: The way to stop the transaction is via Assert
[16:47] <Aram> what should I write in the Assert in this scenario?
[16:47] <Aram> stuff in Assert can only refer to that on object with DocId
[16:47] <Aram> s/on/one/
[16:47] <niemeyer> Aram: Right
[16:48] <niemeyer> Aram: There's basically no way to prevent non-existence of something else that could potentially conflict with the document in any unique field
[16:48] <niemeyer> Aram: We may somewhat easily workaround it, though
[16:48] <Aram> how?
[16:49] <niemeyer> Aram: Can you describe the case in more detail?
[16:50] <Aram> niemeyer: this is called many times with a different id: http://paste.ubuntu.com/1161111/ it should fail if the key is unique, but it doesn't. concrete case is in relations, they also have an index on key, not only on _id.
[16:52] <niemeyer> Aram: By "case" I mean the real problem we have.. I understand the basic issue you're talking about, and we can easily workaround it
[16:52] <niemeyer> Aram: With relations, we could use key as _id
[16:53] <Aram> that's the real problem we have. we can't fail adding same relation twice.
[16:53] <niemeyer> Aram: Which sounds realistic
[16:53] <niemeyer> Aram: And have an auxiliar field for the numeric id
[16:53] <Aram> yes, we can use key as _id
[16:53] <Aram> that was the original design :)).
[16:53] <niemeyer> Aram: Sorry, my time machine had a bug on it and I couldn't use it
[16:54] <niemeyer> Aram: I'll step out for lunch.. happy to continue in a bit
[16:54] <Aram> enjoy
[16:54] <niemeyer> Cheers
[17:52] <niemeyer> For the record, I'll take the chance we're low on reviews right now and I'm taking the  the afternoon off to relax a bit after the intense day+night+no weekend of the last few weeks. I'll be around for a moment still to finish the blog post, so feel free to poke