[01:13] <benc> I want to use upstart for mochiweb - an erlang web server
[01:14] <benc> the server knows how to kill itself so usualy people use a script that tells erlang to stop the server and the erlang VM
[01:14] <benc> in upstart the stop event kill the process so aren't they both doing the same thing?
[08:48] <babel> hello
[08:50] <babel> I'm playing with upstart and would like to run a script before runlevel [016]. I tried several ways to express what I want but "start on starting runlevel [016]" seems to be right but my job doesn't start. I've tested the script before with initctl emit test and that was fine. any ideas?
[08:51] <babel> note: the script should shutdown any running kvm guest with virsh shutdown.
[12:33] <benc> what does this means 'stop on runlevel [!023456]'
[12:34] <benc> I'm trying to understand when I should stop my server. It's a web server
[12:37] <ion> Effectively ‘stop on runlevel 1’, as long as [0123456] are the only runlevel event parameters. ‘start on filesystem’, ‘stop on runlevel [06]’ might be appropriate for Ubuntu 9.10.
[12:39] <benc> ion: hi, you helped me yesterday. for a mochiweb app, when do I need to stop it? do I need the [!023456] or something else?
[12:40] <ion> ‘start on filesystem and net-device-up’ instead of ‘start on filesystem’ might be appropriate for a network service.
[12:40] <ion> ‘stop on runlevel [06]’ probably works.
[12:41] <benc> what about 'start on startup' and 'stop on shutdown' ?
[12:41] <benc> ok. I want to be sure that the network is up
[12:41] <benc> thanks
[12:42] <ion> ‘start on stopped rc RUNLEVEL=[2345]’ to start after the entire rc2 has been run.
[12:42] <benc> do I need to wait for the entire rc2?
[12:43] <ion> Depends. You might not even need to wait for a network device, if the service listens on all present and future interfaces. I don’t remember what mochiweb does by default.
[12:46] <benc> I don't mind waiting. startup speed is not very important as long as it's reliable. it just help me understand how stuff work
[12:49] <ion> We probably should have networking emit an event when *all* interfaces defined in /e/n/i are up. That would be reliable. In fact, waiting for the entire rc2 to finish doesn’t really guarantee all network devices are up. They just probably are. :-) ‘start on net-device-up’ only guarantees one interface is up. Currently one could do ‘start on filesystem and net-device-up ethfoo and net-device-up ethbar’ to make sure ethfoo and ethbar are up.
[12:53] <benc> are you missing couple of and in the last example?
[12:53] <ion> Nope
[12:53] <benc> what do I need to replace ethfoo and ethbar with?
[12:54] <benc> all I want is to start a web server reliably :) couldn't find nginx or apache examples
[12:54] <ion> The names of the network interfaces (‘auto ethfoo’ entries in /etc/network/interfaces)
[12:55] <benc> it should be protable. I want to use the same job on my dev machine and on vps hosting
[13:25] <benc> ion: I've created a job for my mochiweb app but the status is stop/waiting
[13:25] <benc> http://dpaste.com/122823/
[14:08] <benc1> ion: any idea?
[16:20] <ion> benc: Add ‘exec >/tmp/log 2>&1’ just after the ‘script’ line, start the job and look at the log.
[16:33] <sadmac> Keybuk: I've had some thoughts on respawn
[16:33] <sadmac> and limits thereof
[16:39] <ion> For each job, have an integer respawn_delay initialized to 1. Whenever the job dies, respawn_delay *= 2; respawn_delay -= number_of_seconds_the_job_was_running_before_it_died * 1; respawn_delay = clip (respawn_delay, 1, 300); respawn_after (respawn_delay);  // TODO tune the constants
[16:39] <sadmac> ion: something quite like that, yes.
[19:42] <sadmac> Keybuk: new bug filed. You're welcome
[19:42] <sadmac> :)
[19:45] <Keybuk> huh?
[19:46] <Keybuk> sadmac: no it doesn't
[19:47] <sadmac> Keybuk: it doesn't?
[19:47] <Keybuk> not here
[19:48] <sadmac> Keybuk: ...oops. I accidentally 0.3
[19:48] <Keybuk> huh?
[19:49] <sadmac> Keybuk: its a 0.3 bug
[19:49] <Keybuk> why?
[19:49] <Keybuk> 0.6 is no different in this regard
[19:49] <sadmac> Keybuk: apparently it is. over here init has 3 persistant connections to /dev/console
[19:50] <Keybuk> yes, stdin, stdout, stderr
[19:50] <Keybuk> wing-commander scott% sudo ls -l /proc/1/fd
[19:50] <Keybuk> total 0
[19:50] <Keybuk> lrwx------ 1 root root 64 2009-11-20 13:50 0 -> /dev/console
[19:50] <Keybuk> lrwx------ 1 root root 64 2009-11-20 13:50 1 -> /dev/console
[19:50] <Keybuk> lrwx------ 1 root root 64 2009-11-20 13:50 2 -> /dev/console
[19:50] <sadmac> Keybuk: oh, so it does have the /dev/console, but the SAK key doesn't kill it for you?
[19:50] <sadmac> Keybuk: yeah, that's because X is on tty1 here
[19:51] <Keybuk> X is on tty7
[19:51] <Keybuk> (here)
[19:51] <sadmac> that seems to be the killer
[19:52] <Keybuk> so you're probably killing X, not init
[19:52] <sadmac> Keybuk: killing X is desirable
[19:52] <sadmac> Keybuk: its also killing init
[19:53] <Keybuk> I can't see anything that indicates why it would
[19:53] <Keybuk> for a start, SAK only applies to a TTY
[19:54] <sadmac> what do you mean?
[19:57] <Keybuk> SAK is handled in the TTY code
[19:57] <Keybuk> /dev/console is not a tty
[19:58] <sadmac> Keybuk: init and X are on the same tty for us
[19:59] <Keybuk> err
[19:59] <Keybuk> init isn't on a TTY
[19:59] <sadmac> Keybuk: it has open FDs to the active tty
[20:00] <notting> sadmac: but if it's /dev/console, then it theoretically would kill it on whatever tty you did SAK on
[20:00] <notting> not just tty1
[20:00] <Keybuk> exactly
[20:01] <Keybuk> but since /dev/console is separate to the tty later
[20:01] <Keybuk> layer
[20:01] <Keybuk> (it's not /dev/tty0)
[20:01] <Keybuk> it won't
[20:01] <sadmac> Keybuk: not what the kernel docs say
[20:02] <Keybuk> which docs?
[20:02] <sadmac> Keybuk: Documentation/SAK.txt
[20:02] <sadmac> Keybuk: "On the PC keyboard, SAK kills all applications which have /dev/console opened."
[20:03] <Keybuk> see the first line
[20:03] <Keybuk> Linux 2.4.2 Secure Attention Key (SAK) handling
[20:03] <Keybuk>       ~~~~~
[20:03] <sadmac> there is that, isn't there...
[20:03] <Keybuk> the sysrq.txt docs say "given console"
[20:04] <Keybuk> besides
[20:04] <Keybuk> sysvinit holds /dev/console open too
[20:05] <Keybuk> (afaik)
[20:12] <sadmac> Keybuk: its by SID from the foreground console
[20:12] <sadmac> and nothing on fedora has SID 1 but init
[20:13] <Keybuk> SID?
[20:13] <sadmac> Keybuk: session id
[20:13] <sadmac> Keybuk: the code is 1) get foreground tty.  Its kind of a sloppy mess
[20:16] <sadmac> Keybuk: in an abstract sense, tty1 should have X's session ID.
[20:21] <Keybuk> yes
[20:21] <Keybuk> it should
[20:21] <Keybuk> in fact, X will sulk heavily (ie. crash) if something else takes it
[20:21] <Keybuk> but tty1 is in KD_GRAPHICS mode
[20:21] <Keybuk> so all bets are off
[20:22] <sadmac> Keybuk: will TIOCSCTTY fail in graphics mode?
[20:22] <Keybuk> no idea
[20:22] <sadmac> might be worth a shot
[20:22] <sadmac> notting: thoughts on all this?
[20:23] <notting> (on a conf call, not reading yet)
[20:24] <sadmac> Keybuk: If upstart does close stdin/out/err, that would get it as well, would it not?
[20:25] <Keybuk> "get it" ?
[20:26] <sadmac> Keybuk: kill the bug
[20:27] <sadmac> I don't know what the session would become in that case, but you can't be the controller for a terminal that you don't have open, can you?
[20:28] <Keybuk> no idea
[20:28] <sadmac> Keybuk: I thought you were the font of obscure tty behavior :)
[20:28] <sadmac> time to go screw around with it. /me waits for $dayjob to end/
[20:54] <wasabi> Keybuk, you guys doing dinner anywhere tonight? I'd love to meet up with ya.
[20:56] <Keybuk> there's the BBQ and AllStars event at the hotel
[20:57] <wasabi> hmm
[20:57] <wasabi> i haven't been by at all. been swamped at Real Job
[21:07] <notting> sadmac: hey, that bug has a dup
[21:15] <sadmac_home> notting: really?
[21:15] <notting> yeah, someone filed a bug against X about it
[21:43] <sadmac_home> hm
[22:00] <benc2> if I need to export HOME, do I do this at the top of the job or inside the script/end script ?


[00:00] -queuebot:#ubuntu-release- New binary: ocaml-metadata [arm64] (noble-proposed/universe) [0.2.0-1] (no packageset)
[00:00] -queuebot:#ubuntu-release- New binary: ocaml-metadata [armhf] (noble-proposed/universe) [0.2.0-1] (no packageset)
[00:15] -queuebot:#ubuntu-release- New: accepted ghdl [ppc64el] (noble-proposed) [3.0.0+dfsg2-1]
[00:15] -queuebot:#ubuntu-release- New: accepted ocaml-metadata [arm64] (noble-proposed) [0.2.0-1]
[00:15] -queuebot:#ubuntu-release- New: accepted ocaml-metadata [ppc64el] (noble-proposed) [0.2.0-1]
[00:15] -queuebot:#ubuntu-release- New: accepted ocaml-metadata [amd64] (noble-proposed) [0.2.0-1]
[00:15] -queuebot:#ubuntu-release- New: accepted ocaml-metadata [s390x] (noble-proposed) [0.2.0-1]
[00:15] -queuebot:#ubuntu-release- New: accepted ocaml-metadata [armhf] (noble-proposed) [0.2.0-1]
[00:44] -queuebot:#ubuntu-release- New binary: haskell-barbies [amd64] (noble-proposed/universe) [<IP_ADDRESS>-3] (no packageset)
[00:44] -queuebot:#ubuntu-release- New binary: haskell-barbies [arm64] (noble-proposed/universe) [<IP_ADDRESS>-3] (no packageset)
[00:50] -queuebot:#ubuntu-release- New binary: haskell-barbies [ppc64el] (noble-proposed/universe) [<IP_ADDRESS>-3] (no packageset)
[00:55] -queuebot:#ubuntu-release- New binary: haskell-barbies [s390x] (noble-proposed/universe) [<IP_ADDRESS>-3] (no packageset)
[03:22] -queuebot:#ubuntu-release- New binary: haskell-barbies [armhf] (noble-proposed/universe) [<IP_ADDRESS>-3] (no packageset)
[06:17] <LocutusOfBorg> riscv64 are stuck building archive rebuilds tasks, llvm, gcc, linux, ceph... so should we presume for a couple of days almost no risc capacity for the archive?
[06:34] -queuebot:#ubuntu-release- New: accepted haskell-barbies [amd64] (noble-proposed) [<IP_ADDRESS>-3]
[06:34] -queuebot:#ubuntu-release- New: accepted haskell-barbies [armhf] (noble-proposed) [<IP_ADDRESS>-3]
[06:34] -queuebot:#ubuntu-release- New: accepted haskell-barbies [s390x] (noble-proposed) [<IP_ADDRESS>-3]
[06:34] -queuebot:#ubuntu-release- New: accepted haskell-barbies [arm64] (noble-proposed) [<IP_ADDRESS>-3]
[06:34] -queuebot:#ubuntu-release- New: accepted haskell-barbies [ppc64el] (noble-proposed) [<IP_ADDRESS>-3]
[06:57] <LocutusOfBorg> please move libspqr4 to universe
[06:57] <LocutusOfBorg> the old suitesparse libspqr3 was in universe, it was probably auto accepted in suitesparse main pocket (default)
[11:21] -queuebot:#ubuntu-release- New binary: golang-github-bsm-go-vlq [amd64] (noble-proposed/none) [0.0~git20150828.ec6e8d4-2] (no packageset)
[11:31] -queuebot:#ubuntu-release- New binary: fenics-basix [amd64] (noble-proposed/universe) [0.7.0-2] (no packageset)
[11:38] -queuebot:#ubuntu-release- New binary: fenics-basix [ppc64el] (noble-proposed/universe) [0.7.0-2] (no packageset)
[11:39] -queuebot:#ubuntu-release- New binary: fenics-basix [arm64] (noble-proposed/universe) [0.7.0-2] (no packageset)
[11:43] -queuebot:#ubuntu-release- New binary: binutils [amd64] (noble-proposed/main) [2.41-6ubuntu1] (core, i386-whitelist)
[11:45] -queuebot:#ubuntu-release- New: accepted binutils [amd64] (noble-proposed) [2.41-6ubuntu1]
[11:45] -queuebot:#ubuntu-release- New: accepted fenics-basix [arm64] (noble-proposed) [0.7.0-2]
[11:45] -queuebot:#ubuntu-release- New: accepted golang-github-bsm-go-vlq [amd64] (noble-proposed) [0.0~git20150828.ec6e8d4-2]
[11:45] -queuebot:#ubuntu-release- New: accepted fenics-basix [amd64] (noble-proposed) [0.7.0-2]
[11:45] -queuebot:#ubuntu-release- New binary: fenics-basix [s390x] (noble-proposed/universe) [0.7.0-2] (no packageset)
[11:45] -queuebot:#ubuntu-release- New: accepted fenics-basix [ppc64el] (noble-proposed) [0.7.0-2]
[11:49] -queuebot:#ubuntu-release- New: accepted fenics-basix [s390x] (noble-proposed) [0.7.0-2]
[12:12] -queuebot:#ubuntu-release- New binary: fenics-basix [armhf] (noble-proposed/universe) [0.7.0-2] (no packageset)
[12:17] -queuebot:#ubuntu-release- New: accepted fenics-basix [armhf] (noble-proposed) [0.7.0-2]
[12:34] -queuebot:#ubuntu-release- New binary: binutils [i386] (noble-proposed/main) [2.41-6ubuntu1] (core, i386-whitelist)
[12:36] -queuebot:#ubuntu-release- New: accepted binutils [i386] (noble-proposed) [2.41-6ubuntu1]
[13:14] <adrien> can this SRU be reviewed with a high priority?  https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2033422
[13:14] -ubottu:#ubuntu-release- Launchpad bug 2033422 in openssl (Ubuntu Jammy) "openssl: backport to jammy 'clear method store / query cache confusion'" [Medium, In Progress]
[13:15] <adrien> the reason for it being high priority is that there is only so much time before there is a new openssl security issue and therefore security update and corresponding preparations and embargo
[13:16] <adrien> this kind of situation has already delayed this SRU by 10 days and with the sprints, and then end-of-year holidays, I can easily imagine this taking several more months otherwise...
[13:16] <adrien> I'm off this week but I'll do my best to answer all comments
[13:23] <sil2100> Hello everyone! Just a heads up: I switched Ubuntu's britney2 to dry-run mode for all series. Hopefully this will be temporary
[13:53] <LocutusOfBorg> hello vorlon do you think we can have python3-httpbin on i386?
[13:55] -queuebot:#ubuntu-release- Unapproved: dotnet8 (mantic-proposed/universe) [8.0.100-8.0.0~rc2-0ubuntu1 => 8.0.100-8.0.0~rc2-0ubuntu2~23.10.1] (no packageset)
[14:05] <vorlon> LocutusOfBorg: please point me at the dependency chain that requires it?
[14:11] <LocutusOfBorg> wxwidgets3.2
[14:11] <LocutusOfBorg> sorry vorlon
[14:11] <vorlon> ok, I'll have a look at it later
[14:11] <LocutusOfBorg> it was needed to avoid internet requiring during tests, but since the package is in sync...
[14:11] <LocutusOfBorg> meh :)
[14:11] <LocutusOfBorg> otherwise disable testsuite on i386 looks feasible indeed
[14:25] <utkarsh2102> \o
[14:34] -queuebot:#ubuntu-release- Unapproved: iptables-netflow (jammy-proposed/universe) [2.6-2ubuntu2 => 2.6-2ubuntu3] (kernel-dkms)
[15:08] <mitchdz> Hi, could multipath-tools L/J/F -proposed package be pushed to -updates if there's no issues?
[17:16] -queuebot:#ubuntu-release- New binary: flake8-spellcheck [amd64] (noble-proposed/none) [0.28.0-2-1] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: zix [amd64] (noble-proposed/none) [0.4.2-1] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: libfixposix [amd64] (noble-proposed/universe) [1:0.5.1-1+nmu1] (no packageset)
[17:17] -queuebot:#ubuntu-release- New binary: hintview [amd64] (noble-proposed/none) [1.3.1-1] (no packageset)
[17:17] -queuebot:#ubuntu-release- New binary: rust-relative-path [amd64] (noble-proposed/none) [1.9.0-1] (no packageset)
[17:17] -queuebot:#ubuntu-release- New binary: rust-multer [amd64] (noble-proposed/none) [2.1.0-1] (no packageset)
[17:18] -queuebot:#ubuntu-release- New binary: labwc [amd64] (noble-proposed/none) [0.6.4-1] (no packageset)
[17:18] -queuebot:#ubuntu-release- New binary: wf-shell [amd64] (noble-proposed/none) [0.7.0+ds-1] (no packageset)
[17:20] -queuebot:#ubuntu-release- New binary: libfixposix [ppc64el] (noble-proposed/universe) [1:0.5.1-1+nmu1] (no packageset)
[17:20] -queuebot:#ubuntu-release- New binary: zix [ppc64el] (noble-proposed/none) [0.4.2-1] (no packageset)
[17:21] -queuebot:#ubuntu-release- New binary: labwc [ppc64el] (noble-proposed/none) [0.6.4-1] (no packageset)
[17:21] -queuebot:#ubuntu-release- New binary: rust-multer [ppc64el] (noble-proposed/none) [2.1.0-1] (no packageset)
[17:23] -queuebot:#ubuntu-release- New binary: rust-relative-path [ppc64el] (noble-proposed/none) [1.9.0-1] (no packageset)
[17:24] -queuebot:#ubuntu-release- New binary: hintview [ppc64el] (noble-proposed/none) [1.3.1-1] (no packageset)
[17:24] -queuebot:#ubuntu-release- New binary: libfixposix [s390x] (noble-proposed/universe) [1:0.5.1-1+nmu1] (no packageset)
[17:24] -queuebot:#ubuntu-release- New binary: wf-shell [ppc64el] (noble-proposed/none) [0.7.0+ds-1] (no packageset)
[17:25] -queuebot:#ubuntu-release- New binary: hintview [s390x] (noble-proposed/none) [1.3.1-1] (no packageset)
[17:25] -queuebot:#ubuntu-release- New binary: libfixposix [armhf] (noble-proposed/universe) [1:0.5.1-1+nmu1] (no packageset)
[17:25] -queuebot:#ubuntu-release- New binary: libfixposix [arm64] (noble-proposed/universe) [1:0.5.1-1+nmu1] (no packageset)
[17:26] -queuebot:#ubuntu-release- New binary: rust-multer [s390x] (noble-proposed/none) [2.1.0-1] (no packageset)
[17:26] -queuebot:#ubuntu-release- New binary: rust-relative-path [s390x] (noble-proposed/none) [1.9.0-1] (no packageset)
[17:28] -queuebot:#ubuntu-release- New binary: labwc [s390x] (noble-proposed/none) [0.6.4-1] (no packageset)
[17:29] -queuebot:#ubuntu-release- New binary: zix [s390x] (noble-proposed/none) [0.4.2-1] (no packageset)
[17:32] -queuebot:#ubuntu-release- New binary: labwc [armhf] (noble-proposed/none) [0.6.4-1] (no packageset)
[17:32] -queuebot:#ubuntu-release- New binary: rust-multer [armhf] (noble-proposed/none) [2.1.0-1] (no packageset)
[17:32] -queuebot:#ubuntu-release- New binary: wf-shell [armhf] (noble-proposed/none) [0.7.0+ds-1] (no packageset)
[17:32] -queuebot:#ubuntu-release- New binary: rust-multer [arm64] (noble-proposed/none) [2.1.0-1] (no packageset)
[17:32] -queuebot:#ubuntu-release- New binary: wf-shell [s390x] (noble-proposed/none) [0.7.0+ds-1] (no packageset)
[17:32] -queuebot:#ubuntu-release- New binary: rust-relative-path [armhf] (noble-proposed/none) [1.9.0-1] (no packageset)
[17:32] -queuebot:#ubuntu-release- New binary: hintview [arm64] (noble-proposed/none) [1.3.1-1] (no packageset)
[17:32] -queuebot:#ubuntu-release- New binary: rust-relative-path [arm64] (noble-proposed/none) [1.9.0-1] (no packageset)
[17:32] -queuebot:#ubuntu-release- New binary: labwc [arm64] (noble-proposed/none) [0.6.4-1] (no packageset)
[17:32] -queuebot:#ubuntu-release- New binary: zix [armhf] (noble-proposed/none) [0.4.2-1] (no packageset)
[17:33] -queuebot:#ubuntu-release- New binary: zix [arm64] (noble-proposed/none) [0.4.2-1] (no packageset)
[17:35] -queuebot:#ubuntu-release- New binary: hintview [armhf] (noble-proposed/none) [1.3.1-1] (no packageset)
[17:35] -queuebot:#ubuntu-release- New binary: wf-shell [arm64] (noble-proposed/none) [0.7.0+ds-1] (no packageset)
[19:40] <liushuyu> Hi, can someone from the Release Team review and process gdb (armhf) in the SRU queue for Jammy? Thanks!
[20:09] -queuebot:#ubuntu-release- New binary: libfixposix [riscv64] (noble-proposed/universe) [1:0.5.1-1+nmu1] (no packageset)
[20:22] <vorlon> LocutusOfBorg: how do I see that wxwidgets3.2 needs python3-httpbin? currently the package FTBFS on all archs...
[20:46] <vorlon> LocutusOfBorg: mm.  was going through the release opening checklist, forgot that llvm-toolchain-16 is the package we had backed out.  Do you want to take the ubuntu name updates into Debian? https://launchpad.net/ubuntu/+source/llvm-toolchain-16/1:16.0.6-15ubuntu1
[20:55] -queuebot:#ubuntu-release- New binary: labwc [riscv64] (noble-proposed/universe) [0.6.4-1] (no packageset)
[20:55] -queuebot:#ubuntu-release- New binary: rust-relative-path [riscv64] (noble-proposed/universe) [1.9.0-1] (no packageset)
[20:56] -queuebot:#ubuntu-release- New binary: rust-multer [riscv64] (noble-proposed/universe) [2.1.0-1] (no packageset)
[21:03] -queuebot:#ubuntu-release- New binary: zix [riscv64] (noble-proposed/universe) [0.4.2-1] (no packageset)
[21:04] -queuebot:#ubuntu-release- New binary: hintview [riscv64] (noble-proposed/universe) [1.3.1-1] (no packageset)
[21:12] -queuebot:#ubuntu-release- New binary: wf-shell [riscv64] (noble-proposed/universe) [0.7.0+ds-1] (no packageset)
[21:49] <LocutusOfBorg> sure vorlon
[21:49] <LocutusOfBorg> well for wxwidgets3.2, not sure, I'm looking at https://launchpad.net/ubuntu/+source/wxwidgets3.2/3.2.3+dfsg-3
[21:49] <LocutusOfBorg> and only i386 fails
[21:50] <LocutusOfBorg> maybe you are stick with -2 upload in your page?
[21:50] <vorlon> hmm I see -3 now, I guess it wasn't yet on update_excuses when I asked
[21:51] <vorlon> so, python3-httpbin is arch: all but has arch: any deps
[21:51] <vorlon> but it's not obvious which ones
[21:51] <vorlon> if you could trace the deps and figure that out, that would be helpful
[21:55] <LocutusOfBorg> is it ok to just commit noble addition on git for now?
[21:55] <LocutusOfBorg> I plan to upload later, one week or two
[21:55] <vorlon> ommit noble addition of what?
[21:55] <vorlon> oh, for llvm-toolchain? yes
[21:56] <vorlon> and I've re-removed it from noble-proposed
[21:56] <LocutusOfBorg> ah ok
[21:56] <LocutusOfBorg> I can upload as 18~build1 right now, so we don't have to add it back
[21:56] <LocutusOfBorg> I think it's time to start ocaml transition anyway
[21:57] <LocutusOfBorg> so with llvm-toolchain-16_16.0.6-18~build1_source.changes there is no need anymore to restore 17exp1 :)
[21:58] <LocutusOfBorg> python3-greenlet and python3-pyrsistent looks needed for httpbin
[21:58] <LocutusOfBorg> not sure if they are enough
[22:17] <LocutusOfBorg> and maybe also python3-gevent
[22:27] -queuebot:#ubuntu-release- New sync: haskell-vector-stream (noble-proposed/primary) [<IP_ADDRESS>-2]
[22:27] <LocutusOfBorg> please have a look if possible ^^
[23:34] -queuebot:#ubuntu-release- New binary: ceres-solver [amd64] (noble-proposed/universe) [2.2.0+dfsg-3] (no packageset)
[23:41] -queuebot:#ubuntu-release- Unapproved: open-vm-tools (jammy-proposed/main) [2:12.1.5-3~ubuntu<IP_ADDRESS> => 2:12.3.0-1~ubuntu<IP_ADDRESS>] (ubuntu-cloud, ubuntu-desktop, ubuntu-server)
[23:43] -queuebot:#ubuntu-release- Unapproved: open-vm-tools (lunar-proposed/main) [2:12.1.5-3ubuntu<IP_ADDRESS> => 2:12.3.0-1~ubuntu<IP_ADDRESS>] (ubuntu-cloud, ubuntu-desktop, ubuntu-server)
[23:54] -queuebot:#ubuntu-release- New binary: ceres-solver [s390x] (noble-proposed/universe) [2.2.0+dfsg-3] (no packageset)


[00:13] <JanC> they could have built the Shell Extension thing into Epiphany instead of waiting for Firefox/Chrome addons to work...
[05:43] <Habbie> athos, TIL resolv.conf in docker is writable :)
[12:11] <athos> Habbie: :)
[12:11] <Habbie> athos, do you know when the fixed package will hit mirrors?
[12:15] <athos> Habbie: it is in the proposed pocket ATM. It seems there are a few issues blocking migration, so it is hard to predict an exact date (could be today, could be in a few days)
[12:15] <athos> https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#systemd
[12:16] <Habbie> thanks


[03:41] <jamesh> robert_ancell: hi.  there was some discussion last night about snapd-glib's "Recommends: snapd" dependency.
[03:42] <jamesh> robert_ancell: more details in https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856054
[03:42] <jamesh> what do you think about switching it to "Suggests: snapd"?
[03:42] <robert_ancell> jamesh, I've uploaded SRUs to all supported releases.
[03:43] <jamesh> robert_ancell: ah.  Hadn't seen that it got split off into a second bug report
[03:43] <robert_ancell> See bug 1856196
[06:13] <oSoMoN> good morning desktoppers
[06:17] <duflu> Morning oSoMoN
[06:33] <oSoMoN> hey duflu
[07:05] <jibel> bonjour everyone
[07:29] <oSoMoN> salut jibel
[07:29] <duflu> Hi jibel
[08:08] <seb128> happy friday desktopers!
[08:09] <duflu> Hi seb128
[08:10] <duflu> How goes?
[08:10] <seb128> hey duflu, I'm doing well thanks! how are you?
[08:11] <duflu> seb128, almost finished diagnosing and fixing the perf regressions that happened while I was away. So very good
[08:11] <seb128> great
[08:46] <marcustomlinson> morning oSoMoN duflu jibel and seb128
[08:46] <duflu> Hi marcustomlinson
[08:46] <seb128> hey marcustomlinson, how are you today?
[08:47] <marcustomlinson> seb128: quite well thanks :)
[09:03] <Laney> hey
[09:12] <marcustomlinson> hey Laney
[09:13] <tjaalton> oSoMoN: hi, eoan sru queue still has tbird 68.2.2 while it's already in -updates?
[09:24] <duflu> hey hey Laney
[09:31] <Laney> hey marcustomlinson duflu
[09:34] <jamesh> seb128: for the Pulse Audio dependency problem, do we need to produce new versions of the package, or can we republish the version that was pulled once the new snapd-glib is in proposed?
[09:36] <marcustomlinson> hey jamesh :)
[09:36] <jamesh> hi marcustomlinson
[09:37] <oSoMoN> tjaalton, yes, it should be deleted from the queue, I initially thought it wouldn't go through the usual security updates, which is why I uploaded it to the queue
[09:37] <tjaalton> ok
[10:36] <seb128> jamesh, we can republish the same one, also we kept it in proposed
[10:36] <seb128> hey Laney, how are you? happy friday!
[10:36] <jamesh> seb128: awesome.
[10:36] <seb128> lut oSoMoN
[11:04] <seb128> shrug, canonistack is so slow, 100M of debs to install, 10 min and it has done 15% :-/
[11:05] <ogra> you should use a local raspberry pi instead :P
[11:06] <oSoMoN> salut seb128
[11:07] <seb128> it's an amd64 canonical instance
[11:07] <seb128> oSoMoN, en forme ?
[11:07] <oSoMoN> bien, et toi?
[11:07] <seb128> ça va !
[11:10] <seb128> ok, that's ridiculous, I'm going to for lunch, hopefully it will have installed those packages once I'm back...
[11:11] <oSoMoN> yeah, I/O is very slow on canonistack
[11:12] <oSoMoN> 10 mins to install 15MB of debs sounds much slower than what I'm used to, though
[11:13] <Laney> hey seb128 & oSoMoN
[11:13] <oSoMoN> hey Laney
[11:13] <oSoMoN> all good?
[11:18] <Laney> bit glum
[11:18] <Laney> but I'm ok
[11:51] <jamesh> It's almost cooled down to 30°C here.
[11:52] <marcustomlinson> don't miss that kind of heat :/
[11:52] <jamesh> the heat wave should break on monday
[11:53] <jamesh> it'll only be 34 max then
[11:59] <marcustomlinson> yeah, much better, don't forget a coat
[14:53] <kenvandine> seb128: that's on the new bos01 region right?
[15:04] <seb128> kenvandine, yes
[15:16] <hellsworth> good morning everyone!
[15:18] <seb128> hey hellsworth, happy friday! how are you?
[15:20] <hellsworth> hi seb128 . i'm ok and you :)
[15:20] <hellsworth> seems like quite some heat in the southern hemisphere
[15:20] <seb128> I'm pretty good, it's friday :)
[15:20] <hellsworth> the temps jamesh has in C is our temp here in F
[15:20] <hellsworth> lol
[15:20] <hellsworth> friday the 13th no less
[15:21] <hellsworth> are you going to watch any scary movies?
[15:21] <hellsworth> actually, is that a thing in europe?
[15:23] <seb128> that's not a think in Europe afaik
[15:23] <hellsworth> ah ok
[15:23] <seb128> it's a luck/unlucky day, depending to what you believe
[15:23] <hellsworth> see our country is so young we have to come up with things to celebrate since there aren't too many holiday s:)
[15:24] <seb128> it's rather a "play the lotterie" day in France if anything
[15:24] <hellsworth> normally i would watch some really bad scary movie. like evil dead or something.
[15:24] <hellsworth> but tonight i need to bake to get ready for my daughter's birthday party tomorrow
[15:25] <seb128> oh, happy birthday to her! big milestone for you as well I guess :)
[15:26] <hellsworth> indeed. i'll post a picture tomorrow
[15:26] <seb128> great :)
[15:26] <hellsworth> we also will be opening a very nice bottle of scotch to celebrate :)
[15:26] <hellsworth> i'm very excited
[15:26] <seb128> that's the spirit!
[15:26] <hellsworth> lol yes it is!
[15:26] <seb128> :-)
[15:48] <Saviq> is there a known bug about /indicator|notification|tray/ icons going away in GNOME on eoan? I lost my Remmina icon altogether, and the KeepassXC one plays hide'n'seek
[16:43] <kenvandine> marcustomlinson: desktop-launch sees some nice improvements with my PR
[16:43] <kenvandine> cold start goes from 0.846 down to 0.184
[16:43] <hellsworth> is github super slow for anyone else?
[16:43] <marcustomlinson> kenvandine: holy moly
[16:43] <kenvandine> 2nd start goes from 0.115 down to 0.089
[16:44] <marcustomlinson> kenvandine: how did you get it even better than the version in snapcraft?
[16:44] <kenvandine> those fixes haven't been released in snapcraft!
[16:44] <marcustomlinson> oh wow
[16:44] <marcustomlinson> very nice!
[16:44] <kenvandine> they were merged right after 3.9 was released
[16:45] <kenvandine> marcustomlinson: mind reviewing https://github.com/ubuntu/snapcraft-desktop-helpers/pull/200
[16:45] <gitbot> ubuntu issue (Pull request) 200 in snapcraft-desktop-helpers "Performance improvements backported from snapcraft extension" [Open]
[16:45] <marcustomlinson> kenvandine: sure will do
[16:45] <kenvandine> hellsworth: github doesn't seem slow to me
[16:45] <hellsworth> nice changes to desktop helpers kenvandine!
[16:45] <hellsworth> i wouldn't have thought that a simple check before mkdir -p would make that much difference
[16:45] <kenvandine> they were really from galagash :)
[16:46] <kenvandine> yeah, seriously!
[16:46] <kenvandine> turns out mkdir is expensive
[16:46] <hellsworth> i guess so
[16:47] <hellsworth> yeah humm only github.com/snapcore/snapcraft is slow
[16:47] <hellsworth> must be the friday 13th voodoo :)
[16:54] <marcustomlinson> kenvandine: just one small comment. sorry ocd
[16:55] <Saviq> marcustomlinson: they're actually <TAB> I think ;)
[16:58] <marcustomlinson> hmm
[17:00] <marcustomlinson> I'm am really confused. github diff shows the lines indented differently but pulling the branch looks fine locally. all spaces, no tabs either
[17:04] <marcustomlinson> github is super slow
[17:05] <marcustomlinson> and now I can't comment anymore. anyways looks good kenvandine, approved
[17:09] <hellsworth> yeah i'm having troubles commenting too
[17:09] <hellsworth> rebooted and didn't help
[17:10] <marcustomlinson> definitely screwy
[17:13] <kenvandine> marcustomlinson: did you just say you prefer 3 space indentation?
[17:13]  * kenvandine is confused...
[17:13] <marcustomlinson> kenvandine: no the spacing is fine, github is doing something odd there
[17:14] <marcustomlinson> kenvandine: but I'm actually confused about this PR now that I think more about it
[17:14] <kenvandine> oh... looks fine to me
[17:14] <marcustomlinson> how are we getting gains from ensure_dir_exists
[17:14] <marcustomlinson> nothing should exist at all on first run
[17:14] <marcustomlinson> so mkdir should be called for every one right?
[17:14] <kenvandine> no gains on first run from that specific change
[17:14] <kenvandine> just the icon cache fix
[17:15] <kenvandine> which is pretty significant on first run
[17:15] <marcustomlinson> ok ok I get it
[17:15] <marcustomlinson> big gain on just that wow
[17:15] <kenvandine> the mkdir fix helps on the second run
[17:15] <marcustomlinson> indeed
[17:17] <marcustomlinson> kenvandine: so you don't see this indent discrepancy: https://imgur.com/a/IZdPUxc
[17:18] <marcustomlinson> line 396 is good, then the next 4 lines are one space too short
[17:18] <marcustomlinson> but not in the actual file if I download it
[17:18] <marcustomlinson> anyway, ignore the comment
[17:19] <kenvandine> wow... that is weird
[17:19] <kenvandine> https://usercontent.irccloud-cdn.com/file/68R3Zprg/Screenshot%20from%202019-12-13%2012-19-33.png
[17:20] <kenvandine> why would that render differently
[17:20] <marcustomlinson> just the sort of thing that happens on a friday
[17:20] <kenvandine> friday the 13th :)
[17:21] <marcustomlinson> /o\
[17:22] <marcustomlinson> well the election results certainly feel cursed
[17:22] <hellsworth> but maybe scotland will be safe. maybe.
[17:23] <marcustomlinson> aye
[18:01] <Laney> happy weekend all
[18:01] <hellsworth> you too Laney!
[18:01] <marcustomlinson> cheers Laney
[18:02] <marcustomlinson> kenvandine: for completeness, added a note to my post about why chromium and irccloud-desktop showed slower desktop-launch times
[18:03] <marcustomlinson> and with that I'm out, have a good weekend all
[18:04] <marcustomlinson> oh one last thing
[18:05] <marcustomlinson> oSoMoN: you may want to rebuild the chromium snap as soon as kenvandine get's his PR merged into desktop-helpers :)
[18:07] <marcustomlinson> should give the snap about half a second faster cold run (https://github.com/ubuntu/snapcraft-desktop-helpers/pull/200)
[18:07] <gitbot> ubuntu issue (Pull request) 200 in snapcraft-desktop-helpers "Performance improvements backported from snapcraft extension" [Open]
[18:10] <marcustomlinson> kenvandine: by the way, I don't have write access to snapcraft-desktop-helpers, so I can't merge your PR myself
[18:11] <kenvandine> marcustomlinson: i can fix that
[18:11] <kenvandine> but i'
[18:12] <kenvandine> but i'll merge this, just want to build another snap with it for testing
[18:12] <marcustomlinson> cool
[18:12] <marcustomlinson> kenvandine: how about chromium ;)
[18:13] <kenvandine> i was thinking something that builds a little faster
[18:13] <marcustomlinson> :D
[18:13] <marcustomlinson> alright, I'm really out now, byyyye
[18:13] <hellsworth> cheers!
[18:14] <hellsworth> hey kenvandine what are your thoughts on https://github.com/snapcore/snapcraft/pull/2794/files/1a00748ba0b3c6362582c4170df62244940f7470#r357421762
[18:14] <gitbot> snapcore issue (Pull request) 2794 in snapcraft "Add gnome 3 34 extension" [Open]
[18:14] <hellsworth> idk the thought process behind having dicts with one item
[18:25] <kenvandine> multiple bases
[18:25] <kenvandine> we'll have a core20
[18:31] <hellsworth> i know there will be a core20 base but how will this affect the extension?
[18:32] <oSoMoN> marcustomlinson, kenvandine: I'll definitely rebuild the chromium snap with the new desktop helpers
[18:32] <hellsworth> maybe we'll just have to cross that bridge when we come to it
[18:32] <oSoMoN> thanks for working on this!
[18:33] <oSoMoN> not right now though, I'm baby-sitting full time
[18:33] <oSoMoN> have a great week-end everyone!
[18:33] <hellsworth> you too oSoMoN !
[18:34] <kenvandine> marcustomlinson: merged
[18:40] <hellsworth> doesn't it feel good to merge something on a friday :)
[19:35] <hellsworth> kenvandine: i got recipes to build with the gnome-3-34 extension!
[19:40] <kenvandine> hellsworth: woot
[19:41] <hellsworth> yep. making cleanups and a coupel changes then will tuck it away for storage until the gnome-3-34 extension is merged
[19:41] <hellsworth> yay!
[19:53] <gQuigs> I now have the same but opposite problem on two different machines...
[19:54] <gQuigs> on my media system, it can never remember to use HDMI audio, and I have to enable it every time
[19:55] <gQuigs> on my desktop, if my new HDMI monitor goes to sleep, my sound settings like switching to it...  also for whatever reason, now when system sounds are played (I have them muted) - it silences my music player too....
[19:59] <gQuigs> on desktop; just opening "Sound" was doing it sometimes.. and then I just noticed  - it might be scrolling up and a selection issue..    now of course I can't reproduce :/
[20:00] <hellsworth> gQuigs: perhaps you're hitting this issue on your media system: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570
[20:00] <hellsworth> looks like there's a fix coming up in 20.04
[20:01] <gQuigs> hellsworth: awesome! thanks.. I'm going to get right on testing that
[20:01] <hellsworth> sorry i meant desktop. the one where the hdmi audio is auto switching
[20:03] <gQuigs> hellsworth: honestly, that might fix both
[20:03] <hellsworth> worth a try
[20:03] <gQuigs> and it's much easier for me to upgrade my media box to 20.04, cause that's what it's already running...
[20:05] <hellsworth> a quick glance through the pulseaudio issues didn't have anything else that sticks out :
[20:05] <hellsworth> https://bugs.launchpad.net/ubuntu/+source/pulseaudio?field.searchtext=hdmi&search=Search&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.assignee=&field.bug_reporter=&field.omit_dupes=on&field.has
[20:05] <hellsworth> _patch=&field.has_no_package=
[20:05] <hellsworth> that's a ridiculous link
[20:06] <hellsworth> https://bugs.launchpad.net/ubuntu/+source/pulseaudio and search for hdmi
[20:06] <hellsworth> if that bug 1847570 doesn't fix your issue, consider opening a new pulseaudio bug in launchpad
[21:24] <gQuigs> thanks, oh well.. it didn't work.. (for media center)  although I did find snd_hda_codec_hdmi hdaudioC0D0: HDMI ATI/AMD: no speaker allocation for ELD.  I think I just have to figure out how to tell it, that it is a TV...
[21:24] <gQuigs> (that has it's own speakers..)
[21:32]  * gQuigs found a bug to read through - https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1371919


[00:52] <ahoneybun> how did I get put at the top of the UWNL?
[03:28] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_libkscreen build #31: FAILURE in 41 sec: https://kci.pangea.pub/job/artful_unstable_libkscreen/31/
[03:28] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkscreen build #404: FAILURE in 58 sec: https://kci.pangea.pub/job/xenial_unstable_libkscreen/404/
[03:28] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_libkscreen build #180: FAILURE in 1 min 9 sec: https://kci.pangea.pub/job/zesty_unstable_libkscreen/180/
[03:34] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_libkscreen build #181: STILL FAILING in 29 sec: https://kci.pangea.pub/job/zesty_unstable_libkscreen/181/
[03:34] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_libkscreen build #32: STILL FAILING in 1 min 3 sec: https://kci.pangea.pub/job/artful_unstable_libkscreen/32/
[03:34] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkscreen build #405: STILL FAILING in 46 sec: https://kci.pangea.pub/job/xenial_unstable_libkscreen/405/
[04:16] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #474: STILL FAILING in 58 sec: https://kci.pangea.pub/job/xenial_unstable_kstars/474/
[04:16] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kstars build #44: STILL FAILING in 1 min 3 sec: https://kci.pangea.pub/job/artful_unstable_kstars/44/
[04:16] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kstars build #213: STILL FAILING in 1 min 8 sec: https://kci.pangea.pub/job/zesty_unstable_kstars/213/
[04:19] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_kstars build #26: STILL FAILING in 3 min 35 sec: https://kci.pangea.pub/job/zesty_stable_kstars/26/
[04:20] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kstars build #24: STILL FAILING in 4 min 24 sec: https://kci.pangea.pub/job/artful_stable_kstars/24/
[04:22] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kstars build #214: STILL FAILING in 58 sec: https://kci.pangea.pub/job/zesty_unstable_kstars/214/
[04:22] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kstars build #45: STILL FAILING in 1 min 12 sec: https://kci.pangea.pub/job/artful_unstable_kstars/45/
[04:23] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #475: STILL FAILING in 1 min 50 sec: https://kci.pangea.pub/job/xenial_unstable_kstars/475/
[04:29] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_kstars build #27: STILL FAILING in 5 min 27 sec: https://kci.pangea.pub/job/zesty_stable_kstars/27/
[04:29] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kstars build #25: STILL FAILING in 4 min 45 sec: https://kci.pangea.pub/job/artful_stable_kstars/25/
[04:48] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_kstars build #32: STILL UNSTABLE in 32 min: https://kci.pangea.pub/job/xenial_stable_kstars/32/
[04:48] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kwave build #21: UNSTABLE in 14 min: https://kci.pangea.pub/job/artful_stable_kwave/21/
[04:50] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kwave build #22: UNSTABLE in 15 min: https://kci.pangea.pub/job/artful_unstable_kwave/22/
[05:00] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_kwave build #35: UNSTABLE in 26 min: https://kci.pangea.pub/job/zesty_stable_kwave/35/
[05:01] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_kwave build #33: UNSTABLE in 26 min: https://kci.pangea.pub/job/xenial_stable_kwave/33/
[05:02] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwave build #124: UNSTABLE in 28 min: https://kci.pangea.pub/job/xenial_unstable_kwave/124/
[05:02] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kwave build #100: UNSTABLE in 28 min: https://kci.pangea.pub/job/zesty_unstable_kwave/100/
[05:05] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_umbrello build #19: STILL FAILING in 6 min 37 sec: https://kci.pangea.pub/job/artful_unstable_umbrello/19/
[05:05] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_umbrello build #171: STILL FAILING in 6 min 51 sec: https://kci.pangea.pub/job/zesty_unstable_umbrello/171/
[05:05] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_umbrello build #259: STILL FAILING in 7 min 16 sec: https://kci.pangea.pub/job/xenial_unstable_umbrello/259/
[05:11] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_umbrello build #172: STILL FAILING in 5 min 48 sec: https://kci.pangea.pub/job/zesty_unstable_umbrello/172/
[05:11] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_umbrello build #260: STILL FAILING in 5 min 40 sec: https://kci.pangea.pub/job/xenial_unstable_umbrello/260/
[05:12] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_umbrello build #20: STILL FAILING in 6 min 49 sec: https://kci.pangea.pub/job/artful_unstable_umbrello/20/
[05:20] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_umbrello build #29: STILL UNSTABLE in 22 min: https://kci.pangea.pub/job/zesty_stable_umbrello/29/
[05:20] -kubuntu-ci:#kubuntu-devel- Project artful_stable_umbrello build #23: STILL UNSTABLE in 22 min: https://kci.pangea.pub/job/artful_stable_umbrello/23/
[05:23] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_umbrello build #261: STILL FAILING in 7 min 12 sec: https://kci.pangea.pub/job/xenial_unstable_umbrello/261/
[05:24] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_umbrello build #173: STILL FAILING in 8 min 27 sec: https://kci.pangea.pub/job/zesty_unstable_umbrello/173/
[05:24] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_umbrello build #41: STILL UNSTABLE in 26 min: https://kci.pangea.pub/job/xenial_stable_umbrello/41/
[05:25] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_umbrello build #21: STILL FAILING in 8 min 43 sec: https://kci.pangea.pub/job/artful_unstable_umbrello/21/
[05:36] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[05:36] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_kwin build #48: FIXED in 30 min: https://kci.pangea.pub/job/xenial_stable_kwin/48/
[05:41] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_umbrello build #42: STILL UNSTABLE in 16 min: https://kci.pangea.pub/job/xenial_stable_umbrello/42/
[05:41] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_umbrello build #30: STILL UNSTABLE in 20 min: https://kci.pangea.pub/job/zesty_stable_umbrello/30/
[05:41] -kubuntu-ci:#kubuntu-devel- Project artful_stable_umbrello build #24: STILL UNSTABLE in 20 min: https://kci.pangea.pub/job/artful_stable_umbrello/24/
[05:41] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[05:41] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kwave build #22: FIXED in 14 min: https://kci.pangea.pub/job/artful_stable_kwave/22/
[05:43] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[05:43] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kwave build #23: FIXED in 16 min: https://kci.pangea.pub/job/artful_unstable_kwave/23/
[05:44] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[05:44] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwave build #125: FIXED in 16 min: https://kci.pangea.pub/job/xenial_unstable_kwave/125/
[05:44] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[05:44] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kwave build #101: FIXED in 16 min: https://kci.pangea.pub/job/zesty_unstable_kwave/101/
[05:50] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[05:50] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_kwave build #36: FIXED in 23 min: https://kci.pangea.pub/job/zesty_stable_kwave/36/
[05:51] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[05:51] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_kwave build #34: FIXED in 23 min: https://kci.pangea.pub/job/xenial_stable_kwave/34/
[08:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1533: SUCCESS in 1 min 1 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/1533/
[08:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #1533: SUCCESS in 1 min 9 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/1533/
[08:48] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1533: SUCCESS in 3 min 52 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/1533/
[08:49] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-02 build #1533: SUCCESS in 4 min 19 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-02/1533/
[08:49] <lordievader[m]> Good morning
[10:04] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_babe build #24: STILL FAILING in 4 min 38 sec: https://kci.pangea.pub/job/artful_unstable_babe/24/
[10:05] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_babe build #45: STILL FAILING in 5 min 50 sec: https://kci.pangea.pub/job/zesty_unstable_babe/45/
[10:06] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_babe build #41: STILL FAILING in 7 min 15 sec: https://kci.pangea.pub/job/xenial_unstable_babe/41/
[10:15] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_babe build #25: STILL FAILING in 6 min 36 sec: https://kci.pangea.pub/job/artful_unstable_babe/25/
[10:17] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_babe build #46: STILL FAILING in 6 min 44 sec: https://kci.pangea.pub/job/zesty_unstable_babe/46/
[10:17] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_babe build #42: STILL FAILING in 6 min 6 sec: https://kci.pangea.pub/job/xenial_unstable_babe/42/
[10:32] <BluesKaj> 'Morning folks
[14:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1534: SUCCESS in 1 min 5 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/1534/
[14:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #1534: SUCCESS in 1 min 13 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/1534/
[14:48] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1534: SUCCESS in 3 min 52 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/1534/
[14:49] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-02 build #1534: SUCCESS in 4 min 22 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-02/1534/
[15:23] <mparillo> It looks as if KDE Frameworks 5.34 is in the AA Archive: http://gpul.grupos.udc.es/ka-iron-hand_reports/frameworks_archive/5.34_artful_proposed_migration.pdf
[15:25] <ahoneybun> !info frameworkintegration
[15:25] <ahoneybun> yepp
 (Photo, 917x637) https://irc-attachments.kde.org/0DQ3FJ0v/file_2646.jpg
[16:01] <mparillo> ahoneybun: Thanks, but I was getting that yesterday from kinfocenter. Then santa pointed me to the PDF he generates, and there were some blue and orange items yesterday, but all green today.
[16:02] <ahoneybun> ahhh ok
[16:02] <ahoneybun> I wonder with the new MP3 news does that mean Ubuntu will install MP3 support by default?
[16:05] <mparillo> Think of how many wiki pages, AskUbuntu, and Ubuntu Forum articles become obsolete?
[16:06] <mparillo> Updated Status for KF 5.34: https://phabricator.kde.org/w/kubuntu/packaging/status/
[16:06] <ahoneybun> damnn
[16:10] <mparillo> I just tested the 64-bit daily AA ISO on real HW. I picked the auto re-size option, pretty much all the defaults, and it installed smoothly.
[16:10] <ahoneybun> mparillo: if you ever try that again let me know if the sidebar color changes
[16:12] <mparillo> Will do. I did not exactly stare at the screen for 10 minutes straight. When you say changes, do you mean like a flickering, with a subtle color change, as the slideshow advances? Or just a different sidebar color than we are sued to.
[16:13] <ahoneybun> last one
[16:13] <mparillo> I certainly did not notice anything spectacularly ugly.
[16:13] <ahoneybun> damnn
[16:14] <ahoneybun> I just got todays ISO and it did not change yet
[16:14] <mparillo> I zsynced maybe two hours ago.
 (Photo, 912x621) https://irc-attachments.kde.org/EwNmTtLC/file_2647.jpg
[16:15] <ahoneybun> meant like that
[16:15] <mparillo> Your jpeg looks dark gray to me. IIRC (and do NOT trust me), it was more of a steel blue.
[16:15] <ahoneybun> yea I know
 (Document) https://irc-attachments.kde.org/ZjVGkqzu/Slideshow-sidebarold.png
[16:16] <ahoneybun> default old looks like that
[16:19] <mparillo> Yes, that is what I recall. Re-booting with the thumb drive to confirm.
[16:19] <mparillo> Yup. sidebarold. Steel blue
[16:20] <mparillo> Or whatever color you want to call it.
[17:02] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_pim-sieve-editor build #43: FAILURE in 28 sec: https://kci.pangea.pub/job/zesty_stable_pim-sieve-editor/43/
[17:02] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_pim-sieve-editor build #53: FAILURE in 30 sec: https://kci.pangea.pub/job/xenial_stable_pim-sieve-editor/53/
[17:02] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_pim-sieve-editor build #155: FAILURE in 32 sec: https://kci.pangea.pub/job/zesty_unstable_pim-sieve-editor/155/
[17:03] -kubuntu-ci:#kubuntu-devel- Project artful_stable_pim-sieve-editor build #17: FAILURE in 35 sec: https://kci.pangea.pub/job/artful_stable_pim-sieve-editor/17/
[17:03] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_pim-sieve-editor build #138: FAILURE in 1 min 1 sec: https://kci.pangea.pub/job/xenial_unstable_pim-sieve-editor/138/
[17:03] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_pim-sieve-editor build #22: FAILURE in 1 min 6 sec: https://kci.pangea.pub/job/artful_unstable_pim-sieve-editor/22/
[17:27] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[17:27] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_pim-sieve-editor build #44: FIXED in 24 min: https://kci.pangea.pub/job/zesty_stable_pim-sieve-editor/44/
[17:28] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[17:28] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_pim-sieve-editor build #54: FIXED in 24 min: https://kci.pangea.pub/job/xenial_stable_pim-sieve-editor/54/
[17:28] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[17:28] -kubuntu-ci:#kubuntu-devel- Project artful_stable_pim-sieve-editor build #18: FIXED in 24 min: https://kci.pangea.pub/job/artful_stable_pim-sieve-editor/18/
[17:29] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[17:29] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_pim-sieve-editor build #23: FIXED in 26 min: https://kci.pangea.pub/job/artful_unstable_pim-sieve-editor/23/
[17:30] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[17:30] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_pim-sieve-editor build #156: FIXED in 26 min: https://kci.pangea.pub/job/zesty_unstable_pim-sieve-editor/156/
[17:30] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[17:30] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_pim-sieve-editor build #139: FIXED in 26 min: https://kci.pangea.pub/job/xenial_unstable_pim-sieve-editor/139/
 ahoneybun: no ubiquity uploads since your MP
 santa_: thx for the continued works on apps. can see you are being busy there :)
 @acheronuk I've been checking the daily isos for changes
 how do you see uploads?
 @ahoneybun, I'mm subbed to: https://lists.ubuntu.com/mailman/listinfo/Artful-changes
 and filter those emails into their own folder
 right
 subed
[19:45] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_babe build #43: STILL FAILING in 7 min 48 sec: https://kci.pangea.pub/job/xenial_unstable_babe/43/
[19:46] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_babe build #47: STILL FAILING in 8 min 37 sec: https://kci.pangea.pub/job/zesty_unstable_babe/47/
[19:49] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_babe build #26: STILL FAILING in 12 min: https://kci.pangea.pub/job/artful_unstable_babe/26/
[19:52] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_plasma-pa build #22: STILL UNSTABLE in 16 min: https://kci.pangea.pub/job/xenial_stable_plasma-pa/22/
[19:55] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-pa build #426: STILL UNSTABLE in 19 min: https://kci.pangea.pub/job/xenial_unstable_plasma-pa/426/
[19:56] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_babe build #48: STILL FAILING in 4 min 36 sec: https://kci.pangea.pub/job/zesty_unstable_babe/48/
[19:56] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_babe build #44: STILL FAILING in 5 min 32 sec: https://kci.pangea.pub/job/xenial_unstable_babe/44/
[20:00] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_babe build #27: STILL FAILING in 5 min 39 sec: https://kci.pangea.pub/job/artful_unstable_babe/27/
[20:10]  * acheronuk wonders what happened with X that I now get the 'try kubuntu' option booting the iso in a VM now
[20:11] <acheronuk> instead of that crashing and going straight to the desktop
[20:11] <ahoneybun> it gives you the "try kubuntu and install kubuntu riight?>
[20:12] <acheronuk> yep. for a looooooooooooooong time in Virtualbox, that never worked
[20:13] <acheronuk> tried to load. saw a fleeting glimpse. then it seemed to crash and load the live session instead
[20:13] <acheronuk> now it seems stable
[20:13] <acheronuk> odd. but good :)
[20:14] <ahoneybun> you get that big window about try vs install?
 http://i.imgur.com/EMZYhao.png
[20:16] <ahoneybun> I like that tho
[20:17] <ahoneybun> work went into those icons
[20:17] <acheronuk> so do I. just long time since I've seen it in a VM
[20:17] <ahoneybun> yea I know
[20:17] <ahoneybun> it usually is a black screen with install option
[20:18] <acheronuk> in my VMs it's not even been that, but going straight to the live session.
[20:18] <ahoneybun> right
[20:18] <ahoneybun> this is great to see
[20:19] <acheronuk> oh well. something changed in X stack somewhere I guess to make it happier :)
[20:19] <ahoneybun> nice
[20:39] <acheronuk> ahoneybun: http://i.imgur.com/x6IBq6k.png
[20:39] <ahoneybun> the new settings!
[20:40] <acheronuk> getting there
[20:40] <ahoneybun> how did you?
[20:40] <acheronuk> KCI VM
[20:40] <ahoneybun> ahhh
[20:41] <acheronuk> it was crashing on startup until today
[20:42] <acheronuk> certainly looks more modern and fitting with the rest of newer plasma
[20:43] <ahoneybun> yep
[20:43] <ahoneybun> sick of that Mac OS X look
[20:44] <ahoneybun> http://thesmithfam.org/images/mac-snapshot1.png
[20:45] <ahoneybun> http://thesmithfam.org/images/fedora-11-snapshot6.png
[20:47] <acheronuk> lol. when you look at them one after the other, you really see it!
[20:47] <ahoneybun> yeppp lol
[20:48] <ahoneybun> I wonder how to change my LP picture
[20:49] <acheronuk> ahoneybun: hmmm... they still have that look. just not the default
[20:49] <ahoneybun> loook?
[20:51] <acheronuk> ahoneybun: http://i.imgur.com/pZUNkTl.png
[20:51] <acheronuk> 3 options now
[20:51] <acheronuk> new being the sidebar one
[20:51] <ahoneybun> right thought so
[20:54] <blaze> that's mine https://i.imgur.com/kWgyCVz.png macos indeed :\
[20:55] <ahoneybun> odd
[21:00] <blaze> also guys your nicknames are really indistinguishable https://i.imgur.com/Ow04Js2.png
[21:01] <ahoneybun> xD
[21:04] <acheronuk> blaze: ahhhh. oops!
[21:04] <acheronuk> I don't get that so much: http://i.imgur.com/8WPtqKX.png
[21:04]  * acheronuk thanks coloured nicks
 (Photo, 865x326) https://irc-attachments.kde.org/MUKsTgpZ/file_2650.jpg
[21:07] <ahoneybun> I don't get it at all
[21:10] <acheronuk> using a monospace font doesn't help.
[21:25] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_babe build #28: STILL FAILING in 5 min 40 sec: https://kci.pangea.pub/job/artful_unstable_babe/28/
[21:35] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_babe build #29: STILL FAILING in 5 min 40 sec: https://kci.pangea.pub/job/artful_unstable_babe/29/
 @acheronuk, Hey, thanks for the compliment. It would be nice if you could check if they are still any libs needing a revert of the abi bumps
 ok. I have an un-updated clone of apps from before the merging I can hopefully use to check that
[23:19] <acheronuk> santa_: http://paste.ubuntu.com/24614079/
[23:19] <acheronuk> from diffing the unstable vs stable PIM branches in my clone
[23:20] <ahoneybun> found Simon's source code: https://download.kde.org/unstable/simon/0.4.90/simon-0.4.90.tar.xz.mirrorlist
[23:20] <ahoneybun> time to make some MR's to fix bugs lol
[23:20] <acheronuk> so just the bumps in those 3 packages in what would become 17.08 vs what was 17.04 in the stable branch
[23:25] <acheronuk> santa_: say in akonadi, did you deliberately leave the abi1 install/symbols/overides files there? https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/akonadi/tree/debian?h=kubuntu_artful_archive
[23:26] <acheronuk> ahoneybun: lol
[23:26] <ahoneybun> xD
[23:29] <acheronuk> ahoneybun: https://cgit.kde.org/simon.git/commit/?h=0.5&id=78f289332e5abbde8e41aa9ac36a7042f9460c4f
[23:29] <acheronuk> adding Ignore=true :P
[23:29] <ahoneybun> xDDD


[00:46] <diddledan> popey: did you find the secret surprise in the corebird snap yet?
[00:47] <daftykins> it's not a secret NOW!
[00:47] <diddledan> :-p
[01:08] <diddledan> epic young ladies are epic: https://twitter.com/zellieimani/status/924821383330361346
[01:10] <daftykins> i have no idea what that's about - and now it's bed time! \o
[01:11] <diddledan> it's about the hidden story of a group of black ladies who were the secret source of the moon landing - they were mathmaticians
[01:11] <daftykins> ah that one
[01:11] <diddledan> sauce**
[01:11] <daftykins> and their office was in a VHS tape?
[01:12] <diddledan> I've not actually had the chance to watch the movie yet, to my shame :-(
[01:12] <daftykins> shame on you!
[01:12] <daftykins> g'night sir
[01:13] <diddledan> nn
[08:23] <brobostigon> morning boys and girls.
[09:08] <zmoylan-samj3> let the shops be decked with holly fa-la-la-la la-la la-la la-la
[09:09] <zmoylan-samj3> fill the air with christmas muzak....
[09:12] <foobarry> forgot to do my trick with a baby wipe on the windscreens wipers :(
[09:12] <foobarry> MOT place want to replace them instead
[17:53] <ali1234> directhex: i don't use this, but someone might. what suite should it be now? https://github.com/ali1234/rpi-ramdisk/blob/master/raspbian/multistrap.conf#L59
[17:54] <ali1234> raspbianstretch?
[17:54] <directhex> yes, that repo exists & is maintained
[17:54] <ali1234> cool, i will update it
[17:54] <ali1234> is there a keyring package and if so what is it called?
[17:54] <directhex> http://www.mono-project.com/download/alpha/#download-lin-raspbian
[17:55] <ali1234> heh, that still says alpha
[17:55] <directhex> keyring is not available as a package, you can have a .asc via https?
[17:55] <directhex> ali1234: stable then: http://www.mono-project.com/download/#download-lin-raspbian
[17:56] <ali1234> i don't think multistrap knows how to get keys on https
[17:58] <directhex> manpage suggests not - set that repo to unsecure i guess
[17:59] <ali1234> i think noauth is all or nothing. not sure
[18:15] <ali1234> random question: you know when you log in to a board over serial and the terminal is all messed up - wrong size, arrow keys don't work etc - how do you fix that?
[19:03] <zmoy-pixi> terminal emulation?
[19:07] <ali1234> yes, it has something to do with terminal emulation :)
[19:07] <ali1234> specifically SIGWINCH and escape codes etc


[12:53] <bac> hi frankban, you around today?
[12:53] <frankban> bac: yes
[12:56] <bac> cool.  might just be us.
[13:01] <frankban> bac: yeah. do you have any idea of how bundle annotations are supposed to work in a real env?
[13:01] <bac> frankban: i'm not sure what you're asking
[13:02] <bac> you talking about x,y annotations or something else?
[13:02] <frankban> bac: yeah sorry, x,y annotations
[13:03] <bac> frankban: the positioning seems to work.  gary fixed a bug on friday and i tested by deploying four really huge bundles and they were laid out correctly.
[13:03] <frankban> bac: in a real env?
[13:04] <bac> ah, sorry, no it was sandbox.
[13:04] <frankban> bac:  when you drag a bundle file and drop it in the gui canvas, the GUI seems to just pass the YAML contents to the server, and the server uses the deployer to start the import process. Looking at the deployer code ISTM that annotations are just ignored
[13:04] <frankban> :-/
[13:04] <bac> oh, not good
[13:13] <rick_h_> ugh, that sucks
[13:13] <rick_h_> and explains a lot
[13:18] <bac> rick_h_, frankban: have you seen the annotations ignored in a real env in practice?  i haven't done an actual bundle deploy against ec2 or other real envs.
[13:18] <bac> rick_h_: are you working today?
[13:18] <rick_h_> bac: yea, I did QA on release day in a real env and never got positioning to work
[13:18] <bac> darn
[13:19] <rick_h_> bac: no, just peeking in. I'm staying away today as I got sucked in on friday
[13:19] <bac> rick_h_: then go away!  didn't you read robbie's email?  :)
[13:19] <bac> rick_h_: i'm about to do the mjc deploy
[13:19] <rick_h_> bac: hah, yes I did. I think I did that on a sunday :P
[13:19] <rick_h_> bac: awesome!
[13:20] <rick_h_> bac: as a follow up, should we move comingsoon back to mjc at that point (and the new bundles ingest) or leave it at staging do you think?
[13:20] <rick_h_> I guess since it was moved to staging for the demo it should stay put until those are done from maaten and jcastro
[13:20] <bac> yeah, i'd wait until an all clear.
[13:21]  * rick_h_ gets twitchy with comingsoon pointing at staging. Too many times of canonistack blowing things up on us
[13:21] <rick_h_> ok, running away. Thanks for the production update bac. /me will be so happy when all the moving parts setting back down a bit.
[13:23]  * bac stuck waiting for fusion to download update
[14:14] <bac> adeuring: the new heartbeat information looks good!
[14:15] <bac> i may augment it to show when the bzr branch was updated.
[14:27] <bac> hi abentley, jenkins for charmworld is not seeing a recently landed change.  if i select 'build now' it asks for manual input of several items, which i'm uncomfortable setting, assuming it would just trigger the next one.  the trigger log shows that it has run after the landing of r456 but is not seeing changes.
[14:28] <abentley> bac: Looking, but standup about to start.
[14:28] <bac> ok
[14:29] <abentley> bac: What do you mean, not seeing changes?
[14:30] <adeuring> bac: thanks :)
[14:30] <bac> abentley: i mean the ScriptTrigger log ends with "Polling complete. Took 4 sec.
[14:30] <bac> No changes." and no build is triggered
[14:31] <bac> abentley: last build was 455 but 456 is available.
[14:31] <abentley> bac: The last thing it landed was 456: http://<IP_ADDRESS>:8080/job/charmworld-autoland-lxc/78/console
[14:32] <bac> abentley: i was looking at http://<IP_ADDRESS>:8080/job/charmworld-autoland-lxc/78/ for build #78 which says 455
[14:40] <luca___> Can anyone tell me what cloud credentials look like? I've asked rick_h_ but he's ignoring me!
[14:45] <abentley> bac: It says "The new revision is 456" and "juju set charmworld revno=456", so that means it committed r456 and instructed charmworld to deploy 456.
[14:45] <abentley> bac: That's at the bottom of the log.
[14:46] <bac> abentley: yes, i see that in the console log.  i do find it confusing that the main page i pasted above indicates it is processing r455.  i know you're not a jenkins apologist i'm just explaining the reason for my confusion.  thanks for clearing it up.
[14:49] <abentley> bac: That refers to the initial state of trunk, before it commits.
[14:52] <bac> ty abentley
[14:58] <abentley> bac: Jenkins is behaving as if we are doing test-after-commit, so it is saying "Oh, this is the new revision since my last test, and here are the changes".  It is somewhat my fault because of the way I set the build up.
[15:00] <abentley> bac: We could change it so that the pull is done as part of the script, rather than using the Jenkins Bazaar plugin.  I believe that would remove the "changes" info from that page, which would be less misleading.
[16:07] <frankban> bac: have you received my email to juju-gui-peeps? (testing if my smtp configuration work)
[16:08]  * bac looks
[16:09] <bac> frankban: i received Re: [Juju-gui-peeps] Visual placement of services in bundle deployment on real environment
[16:12] <frankban> bac: ok, with my listing of two bugs, right?
[16:12] <bac> yes
[17:03] <frankban> hazmat: ping
[17:03] <hazmat> frankban, pong
[17:03] <frankban> hazmat: the deployer does not support annotations, correct?
[17:03] <hazmat> frankban, not yet, this is just for gui positions?
[17:04] <frankban> hazmat: yes
[17:04] <hazmat> frankban, k, i can add some support in today
[17:05] <frankban> hazmat: that would be great! it is critical for us now that we support bundles
[17:08] <frankban> hazmat: in the next days I will work on a deployer branch (fixes for our import calls from the guiserver) and on a jujuclient branch (make EnvError pickable + optional ToMachineSpec support in deploy()). How does it sound?
[17:08] <hazmat> frankban, also fwiw re placement in bundles. http://pythonhosted.org/juju-deployer/config.html#placement
[17:08] <frankban> hazmat: cool
[17:09] <hazmat> frankban, afaik that covers the tomachinespec support for deploy
[17:09] <hazmat> there's a new release of jujuclient coming as well to catch up with core's recent api work
[17:10] <hazmat> frankban, re enverror pickable.. you mean json serialization support?
[17:10] <hazmat> frankban, there's a longer discussion  with rick_h_ about changing deployer to be more library based instead of cli (ie no more ErrorExit exceptions).
[17:10] <hazmat> fwiw
[17:12] <frankban> hazmat: re jujuclient I mean this diff -> http://pastebin.ubuntu.com/6377430/
[17:14] <hazmat> frankban, gotcha, okay
[17:15] <frankban> hazmat: long story short, the guiserver calls the deployer in a separate process, any exception should be propagated using futures, but to do that, the ProcessPoolExecutor pickles exceptions. That python bug prevents the exception to be correctly deserialized, an the diff is a quick workaround. do you want me to propose that, do you want to just include the fix in your next release?
[17:15] <hazmat> frankban, i'll just include it
[17:16] <frankban> hazmat: the branch is in https://code.launchpad.net/~frankban/python-jujuclient/pickable-enverror
[17:16] <frankban> hazmat: great thanks
[17:18] <frankban> hazmat: ok so I'll work tomorrow just on the deployer fixes for the guiserver, ok?
[17:18] <hazmat> frankban, sounds good
[17:20] <hazmat> frankban, 0.15 jujuclient uploaded has the exc fix and deploy() machine_spec support
[17:20] <hazmat> to pypi that is
[17:21] <frankban> hazmat: awesome! :-)
[17:26] <frankban> hazmat: so, thanks a lot. so tomorrow I'll grab the deployer with annotations support if it is ready and work on the guiserver code there.
[17:26] <hazmat> frankban, sounds good
[17:26] <hazmat> frankban, does gui charm get deployer from pypi or cloud archive
[17:27] <frankban> hazmat: the gui charm includes the deployer tarball.
[17:28] <hazmat> frankban, ic, thanks
[18:20] <frankban> bac: when you have a minute later, could you please review and qa https://codereview.appspot.com/24600043 ?
[18:20] <bac> frankban: sure
[18:20] <frankban> bac: thanks, have a nice evening
[18:20] <bac> you too
[18:46] <hatch> rick_h_,  hey I don't suppose you're kickin around?
[18:46] <rick_h_> hatch: around, what's up?
[18:47] <hatch> just working on huw's branch now and implementing your changes
[18:47] <hatch> but I'm wondering why onboarding is handled by the browser.js and not app.js?
[18:47] <rick_h_> hatch: couple reasons. One, it's only in the build viewstate, it's part of the browser experience in that way
[18:48] <rick_h_> hatch: and getting that viewstate info up out to the app was a pita and bad code smell
[18:49] <hatch> oh, I was under the impression that it was done over top of whatever would be there
[18:49] <rick_h_> hatch: no, it's only in build mode
[18:49] <hatch> but I guess it makes sense
[18:49] <rick_h_> hatch: so originally there was all this url hacky crap to check if it should show when it was in app.js
[18:49] <rick_h_> hatch: which got convoluted when you considered default view mode and such
[18:49] <hatch> cool, so that is another thing that can be simplified post fullscreen removal :)
[18:49] <rick_h_> hatch: so it was a MUCH simpler thing to move to browser.js and check viewmode directly
[18:49] <hatch> right
[18:49] <hatch> I knew there had to be a reason for it :)
[18:50] <rick_h_> hatch: what doesn't get simpler (once you get past removing everything and fixing all the state machinery bits)
[18:52] <rick_h_> hatch: that and I HATE app.js doing more work. It's a lot easier to test as it is now.
[18:53] <hatch> :)
[18:57] <hatch> only 4 more hours to go, should be able to get this done before then :)


[00:40] <dandrader__> racarr, you're still adding two entries to debian/changelog in https://code.launchpad.net/~mir-team/platform-api/support-state-changing/+merge/235545
[00:44] <racarr> dandrader__: Whoops...sorry...total misparse..
[00:44] <racarr> rev 276 :)
[00:47] <dandrader__> racarr, nitpick: version can be simply 2.5.0 instead of 2.5.0+14.10.20140929-0ubuntu1. CI will append all the rest upon release. just like with the symbols version
[00:48] <dandrader__> approving anywas
[00:48] <dandrader__> anyway
[07:46] <tsdgeos> Cimi: CI finished on https://code.launchpad.net/~aacid/unity8/clip_settings_list/+merge/236537 and is as good as it gets, top approve
[07:46] <tsdgeos> ?
[07:59] <tsdgeos> Cimi: what do we need for https://code.launchpad.net/~unity-team/unity8/scopes_more_things_on_memory/+merge/235588 top approval?
[08:22] <Cimi> tsdgeos, we need me to remember :)
[08:23] <Cimi> tsdgeos, top approved both
[13:03] <tsdgeos> dandrader: can you merge trunk should kill some of the CI failures
[13:16] <tsdgeos> dandrader: there's still a few 2013 in there
[13:17] <dandrader> tsdgeos, done the merge
[13:22] <dandrader> tsdgeos, all done and flattened the branch
[13:30] <tsdgeos> / TODO Consider using qCDebug() when available (Qt 5.2)
[13:30] <tsdgeos> that's available already
[13:31] <dandrader> tsdgeos, not worth the trouble. and not available when I started writing that code
[13:32] <dandrader> tsdgeos, I'm more comfortable with compile time enable/disable
[13:32] <tsdgeos> dandrader: then remove the todo :)
[13:33] <tsdgeos> dandrader: is it worth having a break; on  allGood = false; in the DDA?
[13:33] <dandrader> tsdgeos, filename and line number please
[13:34] <tsdgeos> there's just 2 allgood
[13:34] <tsdgeos> ./plugins/Ubuntu/Gestures/DirectionalDragArea.cpp:401:        allGood = false;
[13:34] <tsdgeos> ./plugins/Ubuntu/Gestures/DirectionalDragArea.cpp:412:                allGood = false;
[13:34] <tsdgeos> second one
[13:36] <dandrader> tsdgeos, micro optimization that would make the code more complex, I think
[13:36] <tsdgeos> dandrader: make it part of the for?
[13:36] <tsdgeos> for (int i = 0; i < touchPoints.count() && allGood; ++i) {
[13:36] <tsdgeos> ?
[13:36] <dandrader> tsdgeos, we actually should never reach this line with mir as android-input never starts more than one touch in a single event
[13:37] <dandrader> tsdgeos, yeah, that could be done
[13:40] <dandrader> tsdgeos, done
[14:20] <dandrader> mzanetti, gonna start reviewing https://code.launchpad.net/~mzanetti/unity8/launcher-update-on-dconf-change/+merge/236561
[14:21] <mzanetti> dandrader: ah cool, thanks
[14:21] <dandrader> it's all new code to me, so it might take a while
[14:22] <mzanetti> dandrader: no worries... I'll be busy until saviq comes back
[16:04] <tsdgeos> mterry: please have a look at trunk and fix the failing test in xvfbtestShell
[16:05] <tsdgeos> seems it was introduced by "Make it easier to use the Lockscreen component from the welcome wizard. "
[16:05] <mterry> tsdgeos, sigh ok
[16:05] <tsdgeos> sorry i did not catch it in review :/
[16:05] <mterry> sorry I let it through  :/
[16:06] <tsdgeos> it's consequence of having too many broken ones
[16:06] <tsdgeos> testShell was totally failing to even start when we did this branch
[16:06] <tsdgeos> so couldn't catch it
[16:06]  * mterry goes afk
[16:06]  * tsdgeos goes eod
[16:54] <tsdgeos> dandrader|lunch: there's a few tests that fail with your branch, plz have a look
[18:51] <yecril71pl> Why does gedit insert a new line when I replace text with \n?
[18:52] <davmor2> yecril71pl: because that is the notation for a newline
[18:53] <yecril71pl> What other notations should I expect gedit to support?
[18:53] <davmor2> yecril71pl: pass
[18:54] <yecril71pl> pass what?
[18:54] <davmor2> yecril71pl: you can try the website for gedit and see what it supports and doesn't
[18:55] <yecril71pl> The manual does not say what it supports
[18:56] <yecril71pl> and it does not say what the Web site is
[18:56] <yecril71pl> Oh I see, it is in the About dialogue box
[18:58] <yecril71pl> The manual on the Web site is quite similar to the manual in Ubuntu.
[18:58] <yecril71pl> However, the manual in Ubuntu does not contain the section "Using escape sequences".
[18:59] <yecril71pl> Why is that?
[19:12] <yecril71pl> <URL: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1376403 >
[19:24] <yecril71pl> How can I find differences between files in Unity?
[19:26] <yecril71pl> I guess the answer is Meld.