[03:19] <Guest57842> so how does evryone like the RC
[03:20] <Guest57842> anyone know when the Ubuntu gnome logo will be picked ?
[03:21] <Guest57842> wow its dead here lol
[05:44] <asdf__> I downloaded the RC release, bootet and can't find gnome 3.8 classic mode. Is it because ubuntu gnome uses gnome 3.6?
[05:52] <gob> hi all
[05:52] <gob> you'r look me&
[05:53] <gob> ?
[05:57] <asdf__> I reasked it here https://lists.ubuntu.com/archives/ubuntu-gnome/2013-April/000218.html
[09:22] <hadim_> hi
[09:22] <hadim_> got a bug with ubuntu gnome (staging ppa)
[09:22] <hadim_> can you confirm that gnome terminal settings are not applied
[09:22] <hadim_> ?
[09:23] <hadim_> for example when i set terminal colors, it doesnt do anything and use default black on with colors settings
[09:29] <darkxst> hadim_, file a bug
[09:30] <hadim_> yep
[09:30] <hadim_> but where since i use staging ppa ?
[09:30] <darkxst> ubuntu-bug still works!
[09:30] <hadim_> oh ok
[09:31] <hadim_> did you notice this bug ?
[09:34] <darkxst> no, I just use the standard white on black
[09:35] <hadim_> ok
[09:35] <hadim_> https://bugs.launchpad.net/ubuntu-gnome/+bug/1172209
[09:35] <hadim_> wow
[09:36] <hadim_> fun robots :-D
[10:04] <LoverBuntu> hi folks
[10:05] <LoverBuntu> can anyone tell me what's the main advantages of using ubuntu gnome 13.04 over Ubuntu 13.04 ?
[10:07] <LoverBuntu> no idea?
[10:33] <ricotz> darkxst, hi ;)
[10:33] <darkxst> hi
[10:33] <ricotz> don't you build the packages locally?
[10:34] <darkxst> ricotz, yes I do, systemd had been a nightmare though ;(
[10:34] <ricotz> just saying, might be better to built them in another ppa intead of pushing that much uploads ;)
[10:35] <darkxst> well if I had known, I would have!
[10:35] <ricotz> (and testing it from there then)
[10:35] <ricotz> darkxst, alright
[10:36] <darkxst> but really wierd issues like Soyuz falling over because there is a ddeb with no corresponding deb
[10:36] <darkxst> and tests that apparently fail in kvm, but not the archive builds
[10:37] <ricotz> darkxst, yeah, the builders are sometime weird
[10:37] <darkxst> indeed
[10:37] <ricotz> darkxst, mostly just retrying the builds works since it will probably use another builder
[10:38] <darkxst> hmm right
[10:38] <darkxst> anyway made a few hacks to packaging as suggested by pitti, so hopefully will work now
[10:39] <ricotz> darkxst, if that one fails too, built in another ppa first ;)
[10:39] <darkxst> ricotz, sure
[10:39] <ricotz> yeah i noticed
[10:39] <ricotz> uploading systemd made be curious "why"
[10:40] <darkxst> lol, poweroff fix probably wont make raring
[10:41] <ricotz> hmm, i see
[10:43] <ricotz> looks like you got lucky
[10:45] <darkxst> anyway think I cleaned up most of the logind fallout now
[10:47] <darkxst> although suspend on lid close, might be a bit flaky until we up gsd to 3.8.1
[10:48] <ricotz> darkxst, yeah, the lid-close suspend is what i want back :)
[10:48] <darkxst> ricotz, I pushed a patch, but while I was debugging, sometime suspend was inhibited for no apparent reason
[10:49] <darkxst> it works perfectly on 3.8.1, but I not entirely sure what needs to be fixed before we can upload that
[10:49] <ricotz> darkxst, i am still running the older systemd/gsd so i guess i will notice it soon
[10:51] <darkxst> I guess the OSD's are one issue, if fallback actually still works (can't say I have tested that)
[12:24] <thepreacher> In quite a few applications eg disks, the system is still referred to as Ubuntu 13.04, I'm just curious, will these be eventually changed to Ubuntu Gnome or not?
[12:33] <camelinahat> thepreacher, what area of disks? I'm suspecting however it probably has to do with bug 1171867
[12:35] <thepreacher> camelinahat: sorry my bad, its actually the details application. The overview shows the system as Ubuntu 13.04. I was expecting it to be Ubuntu Gnome 13.04
[12:37] <thepreacher> And it show the original Ubuntu logo as well. I suspect there's too much to do at the moment for devs to bother with something like that, besides its only cosmetic.
[12:38] <camelinahat> Hmm I believe it's the same reason: "All ubuntu-flavours install as "ubuntu", there is no way to detect if unity,gnome-shell,kde are installed uniquiely or if multiple sessions are available. Thus all official flavours, once installed report that they are "Ubuntu"."
[12:38] <camelinahat> (from that bug)
[12:38] <thepreacher> Well I can happily live with that :)
[14:55] <tyrog> Hi. Why does the Gnome Staging ppa have systemd ?
[15:07] <slinnky> BOOOOOOOOO YEAH
[15:12] <jbicha> tyrog: it's just logind; other pieces of systemd (hostnamed, localed, & timedated) are already running by default in 13.04
[15:12] <jbicha> Ubuntu still uses upstart underneath so this is a bit of a hybrid
[15:13] <tyrog> jbicha: So no problem regarding compatibility with the ubuntu toolchain?
[15:15] <jbicha> logind is a 13.10 feature so it's not been fully tested on Ubuntu yet but the gnome3 staging ppa in general includes experimental stuff
[15:20] <tyrog> jbicha: but it is the only one with some components of gnome 3.8 like control center and evolution
[15:23] <jbicha> yes but there's no promises that gnome-control-center 3.8 works well on Ubuntu yet
[15:24] <bersace_nss> last update gave wifi back (no more dbus error)
[15:24] <bersace_nss> thanks !
[15:24] <bersace_nss> does anyone get nm bridging working ?
[15:24] <bersace_nss> once i configured a bridge in nm, it fails to activate it with "Device not managed by NetworkManager or unavailable"
[15:25] <bersace_nss> any clue ?
[15:26] <bersace_nss> the bridge iface is actually created, but no slave in it
[17:49] <jbicha> new images were just posted
[17:54] <user5123546> Hi. I may not be on the right channel, but does anyone know of a way I could easily set the middle mouse button to initiate the activities overview?
[17:56] <camelinahat> jbicha, Yeah I just noticed that myself.
[18:38] <camelinahat> jbicha, Looks like install alongside is still broken :(
[18:56] <jbicha> camelinahat: I wonder if that affects other flavors too?
[19:01] <camelinahat> I have a kubuntu download here I'll give a try in a little bit. Unfortunately I'm almost done with an LVM/Encytped test so I'll need to re-install the base before I can test kubuntu's resize
[19:04] <jbicha> kubuntu's ubiquity is a bit different; I'm more curious about whether the bug affects the Ubuntu image
[19:05] <camelinahat> Yeah I can try that one instead, won't take me a minute to pull down that image anyways.
[19:06] <jbicha> ok, it sounds like balloons is also checking... I asked around in #ubuntu-quality
[20:29] <darkxst> jbicha, what needed fixing in g-s-d again?
[20:30] <jbicha> everything ;)
[20:31] <jbicha> I think we need to take a closer look at the media-keys changes, possibly reverting them
[20:32] <jbicha> it's multiple commits so it might be easier to diff the directory with an older version
[20:36] <Toasty27> Is there any major difference between installing UbuntuGnome and installing Gnome 3 on the standard version of Ubuntu 13.04?
[20:36] <darkxst> jbicha, you mean the removal of the OSD stuff?
[20:38] <jbicha> yeah we have to watch out for regressing Unity so we should test whether the volume/brightness/etc. keys still work
[20:39] <darkxst> unity doesnt use the OSD's, but I suppose fallback would (if that is still working?)
[20:40] <jbicha> I thought it was more than just OSD but as long as Unity still works, go ahead and upload
[20:41] <jbicha> I think Fallback should be using notify-osd too but it might be missing the Recommends for it
[20:46] <darkxst> jbicha, I do not even have a fallback session in my test VM
[20:48] <jbicha> don't worry about fallback for now
[20:54] <darkxst> ok
[21:48] <darkxst> jbicha, oh, I am getting black text on black background in gnome-terminal under unity when 'use system colors'
[21:51] <jbicha> something in our g-s-d 3.8 breaks theming pretty bad in Unity, it doesn't affect Fallback though...
[21:52] <darkxst> hmm seems mostly ok when switching to ambiance however
[22:28] <darkxst> jbicha, did media keys actually work in 3.7.91?
[22:30] <darkxst> I am guess not?
[22:33] <jbicha> I don't know, maybe we need to revert that directory to the 3.6 version?
[22:42] <darkxst> I will try and revert the keygrabber stuff, for unity only


[12:44] <alan_g> anpok: another question about SurfaceInputDispatcher. In drag&drop was expecting a leave event when the cursor drags out of the source target. But AFAICS that only gets sent if no buttons are pressed. Is there a valid reason for that behaviour?
[12:44] <alan_g> (I know you didn't write this code but racarr isn't about to ask.)
[13:07] <anpok> alan_g: hm do we keep sending input events if there are buttons pressed?
[13:07] <anpok> to the window
[13:41] <alan_g> anpok: SurfaceInputDispatcher.gestures_persist_over_button_down says "yes"
[13:43] <alan_g> But I don't get why.
[13:44] <anpok> alan_g: so afaiu when you press a button the window owns the guesture until release.. hence the leave is only sent when all buttons are released
[13:44] <anpok> so it keeps receiving the motion events even when you leave the window..
[13:45] <anpok> when there is no owner because the button was not pressed it should sent the leave event the instant you leave the window..
[13:46] <anpok> the why is probably about menues.. and existing x11 behavior..
[13:47] <anpok> you dont want mouse interactions to directly end when you accidently leave the window .. the accidently here is identified through button state..
[13:48] <alan_g> That makes sense. But so does "drag" leaving.
[13:49] <alan_g> Hmm... I guess I need to introduce another case.
[13:50] <anpok> hm so a different state from in-guesture to in-drag  with different rules for pointer dispatch
[13:52] <alan_g> yeah. Feels messy but what choice is there.
[16:20] <attente> alan_g: hi, i'm looking at https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1669524 (and https://bugs.launchpad.net/mir/+bug/1420334 by extension). sorry i didn't reply to your original question, but can we still get the necessary client api to help implement those functions (always on top, client-side move/resize)?
[16:25] <alan_g> attente: the move API is on the "wishlist" (i.e. not yet moved to "backlog"). You want an "always on top" and "init resize" too?
[16:29] <attente> alan_g: yes please to "always/keep on top". by "init resize", do you mean initial resize event? i've worked around that so it's not as important now, just requested the size on window creation instead
[16:31] <alan_g> I mean initiate a resize gesture
[16:32] <attente> alan_g: oh. ok, yes please to that too :)
[16:56] <anpok> just another drag state
[16:57] <anpok> *states


[08:52] <xnox> slyon:  i don't think there is a way to disable that apart from exporting new DEB_BUILD_OPTIONS in the top of debian/rules. But check with rbalint. When I added implied noudeb, i added support to pass '!noudeb' to negate that. But i don't think there is '!nocheck' (aka if nocheck is in place, drop it).
[09:16] <slyon> xnox: thanks!
[10:33] <tumbleweed> slyon: RE https://launchpad.net/ubuntu/+source/pycparser/2.20-3ubuntu1 what about pypy/pypy3?
[10:36] <slyon> tumbleweed: IMO pypy is supposed to go away together with python2, no? And I'm looking into pypy3 currently to see if it can be built using python3..
[10:37] <tumbleweed> it can't
[10:37] <tumbleweed> so no, pypy sticks around for the moment, to build pypy3
[10:38] <tumbleweed> upstream is working on this, but I don't think they've got very far
[10:39] <tumbleweed> we can live without python-pycparser, if we stop building pypy with cpython. Which does leave us with a bootstrapping problem
[10:43] <tumbleweed> FWIW the relevant upstream porting work is here https://foss.heptapod.net/pypy/pypy/-/tree/branch/rpython3
[10:59] <slyon> thank you for the heads-up! I need to check that upstream work..
[11:21] <tumbleweed> of course pypy also carries a bundled pycparser, we could hack the build to get that on PATH for translation
[11:22] <tumbleweed> and we could carry a cpython2.7 source in the pypy source if the python2.7 source packgae has to go...
[11:24] <slyon> that sounds like a good approach, to keep pypy/3 as self-contained as possible. That way we can move on with the python2-rm transition, keeping pypy isolated so it can easily be remove as soon as pypy3 is ready for Python3.
[11:26] <slyon> I'm not sure about python2.7... but my understanding was that it is supposed to die, especially as python2 has been deprecated since Jan 2020.
[11:27] <tumbleweed> yes, it does need to die, somehow
[11:28] <tumbleweed> I just haven't gone down those rabbit holes because I haven't needed to, yet
[11:38] <toabctl> bdmurray, any reason why bionic was not uploaded to proposed for https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1926732 ?
[13:56] <rbalint> slyon, re: nocheck vs riscv see dpkg changelog entry for 1.20.9ubuntu1
[13:56] <rbalint> DEB_BUILD_OPTIONS := $(filter-out nocheck,$(DEB_BUILD_OPTIONS))
[13:58] <slyon> rbalint: thanks! That's a very good hint, exactly what I was looking for :)
[13:59] <xnox> slyon:  no cpython2.7 and pypy will remain.
[13:59] <xnox> slyon:  even if we remove python2-defaults, we will keep python2.7
[13:59] <xnox> a otherwise there is no way to rebootstrap pypy, to rebootstrap pypy3
[13:59] <xnox> *as
[14:00] <xnox> slyon: tumbleweed: the death of python2.7 is a lot harder than simply death of python2-defaults.
[14:01] <slyon> xnox: ack. we might still want to make use of the already bundled pycparser, to avoid keeping python-pycparser + depends (cc tumbleweed)
[14:01] <tumbleweed> yeah, it's worth a try
[14:02] <tumbleweed> from a quick look at the imports, it should be doable, I try it
[14:04] <xnox> +1
[14:53] <tumbleweed> it'd help if I tested with --profile=stage1. Doh.
[14:57] <Laney> slyon: any idea on https://autopkgtest.ubuntu.com/packages/n/netplan.io/hirsute/armhf btw? do you think I really did break it? :(
[14:59] <slyon> Laney: argh.. that test is flaky and disabled in all other series... I think it would be best to hint netplan.io/armhf/0.102-0ubuntu3 ... I don't think its worth doing a full SRU just for the autopkgtest fix
[14:59] <Laney> ahhhh
[15:00] <slyon> could you do that or do you want me to create an MP?
[15:00] <Laney> I got suspicious by the pattern going from all green to red
[15:00] <Laney> well, maybe I technically could, but I'm a bit wary of touching the SRU hints
[15:00]  * Laney picks on some SRU team members
[15:00] <Laney> apw: rbasak: sil2100: mind if I commit the above ^- ?
[15:01] <slyon> yeah it was working previously... I'm not exactly sure what changed in the build environment
[15:01] <slyon> it is most probably container related, as it only happens in the armhf/LXD test
[15:01] <Laney> I think we moved to focal meanwhile, so updated kernel
[15:03] <Laney> I could do the hint for this exact version only, if the skipping will be included in any future SRU?
[15:05] <slyon> Yes. I will include with the next hirsute SRU
[15:06] <Laney> 👍
[15:06] <Laney> ok, waiting for feedback then
[15:14] <slyon> I staged the fix here, so it can go into the next hirsute upload: https://git.launchpad.net/~ubuntu-core-dev/netplan/+git/ubuntu/log/?h=ubuntu/hirsute
[15:25] <Laney> doko: do you have any idea about automake-1.16/armhf? I see 6 retries from you against bison ;-)
[16:13] <doko> Laney: yeah, retried too often. no, didn't look at it yet, and unlikely before mid next week
[16:14] <Laney> alright
[18:15] <realtime-neil> What is the preseedable `partman-base partman/installation_medium_mounted`, why is it forcing an interactive prompt on my preseeded https://cdimage.ubuntu.com/ubuntu-legacy-server/releases/focal/release/ubuntu-20.04.1-legacy-server-amd64.iso , and how do I quiesce this prompt?
[18:51] <TJ-> realtime-neil: is it this? Bug #1491963
[18:53] <realtime-neil> TJ-: yep, that's probably the one blocking me
[19:08] <bryce> if I have a package with a debian version 5.1.20+4.0.11-0+deb11u1 that I want to do a no-change rebuild for, what should the new version be?  5.1.20+4.0.11-0+deb11u1-0build1 ?
[19:09] <bryce> or 5.1.20+4.0.11-0+deb11u1build1?
[19:18] <RzR> bryce, dpkg --compare-versions will tell you which one if it will trigger rebuild
[19:20] <RzR> \dpkg --compare-versions  5.1.20+4.0.11-0+deb11u1 lt  5.1.20+4.0.11-0+deb11u1-0build1 && echo lower
[19:20] <bryce> Rzr thanks for the reminder of that.  They both appear to work
[19:20] <RzR> so this will work
[20:32] <cjwatson> bryce: I think just appending build1 rather than appending -0build1 is more conventional
[20:32] <cjwatson> Partly because there are cases where appending -0build1 does Very Confusing Things (due to converting a native version into a non-native version), which isn't the case for just appending build1
[20:35] <bryce> cjwatson, thanks, I did end up going with just build1.  More than one '-' in a version string feels wrong.
[21:13] <cjwatson> bryce: And in fact now that I think about it there's good reason for it to feel that way; the upstream vs. packaging split in the version takes place on the *last* '-'
[21:13] <cjwatson> bryce: So 5.1.20+4.0.11-0+deb11u1-0build1 means upstream version 5.1.20+4.0.11-0+deb11u1, packaging revision 0build1
[21:13] <cjwatson> bryce: And that can have some very surprising effects
[21:23] <bryce> cjwatson, aha, thanks again!
[22:55] <mwhudson> bryce: i'm on +1 maintenance next week, so please let me know of any turn-the-handle type stuff i can do to keep the php transition moving
[22:55] <bryce> mwhudson, noted thanks.


[00:00] <ochosi> anyway, really off now ->
[00:00] <bluesabre> have a good night ochosi
[00:11] -SwissBot:#xubuntu-devel- ::xfce4-announce:: ANNOUNCE: xfce4-indicator-plugin 2.3.4 released @ http://xfce.10915.n7.nabble.com/ANNOUNCE-xfce4-indicator-plugin-2-3-4-released-tp50777.html (by Simon Steinbeiss)
[00:59] <donofrio> so what am I doing wrong https://apaste.info/8x5P
[00:59] <donofrio> any "service" needed for repo adds?
[01:01] <Unit193> donofrio: I'd say 'dirmngr' is missing, right?
[01:04] <donofrio> version 2.2.4 is already installed
[01:04] <donofrio> -1ubuntu1
[01:08] <donofrio> now I get this https://apaste.info/dl9H
[01:13] <Unit193> Odd.  Well you could just get the key and add it in /etc/apt/trusted.gpg.d/
[01:59] <donofrio> where would the gpg file be , the path is not there once you run the add-apt
[02:00] <donofrio> dirmngt_ldapservers.conf is missing ;(
[08:26] <Used2BTracker5> runnuing 18.04; installed dropbox. The icon shows up in the top bar (unlike in 16.04). But when i click with my mouse on the dropbox icon no menu is opened (I expect a menu with "open dropbox folder" etc). Is that by design or should I report that as an issue? And would that then be a dropbox issue or an issue in the status notifier?
[08:42] <flocculant> Used2BTracker5: it's not by design - but it's also not a Xubuntu issue - there were ways to get the icon working that I used a while back. try https://askubuntu.com/questions/732967/how-to-fix-non-working-dropbox-icon-on-xubuntu-14-04-lts-64
[08:44] <flocculant> ali1234: thanks - I got sidetracked yesterday when I got back - totally forgot about the blueman thing
[08:44] <flocculant> bluesabre: did you see the last bit from ali yesterday?
[09:24] <Unit193> Used2BTracker5: Do you use thunar-dropbox-plugin too?  I personally patched /usr/bin/dropbox, one can patch it to get the indicator fully working or just fully switch to a tray icon.
[09:56] <ochosi> bluesabre: we should set the new "square" option in indicator, sn-plugin and systray
[10:36] <Used2BTracker5> flocculant, thanks, will have a look
[10:40] <Used2BTracker5> flocculant, BTW, it's not the problem " black with a red slashed zero" as described on the site you kindly pointed me to. The right dropbox icon is showing, with the right animation when syncing; and when i hover over it it tells me what it is doing. But the only thing is, that when I click on it it does not open the dropboxmenu. So, would you advice me that this is still the same problem ?
[11:14] <flocculant> Used2BTracker5: not sure tbh - not something I use
[11:14] <Used2BTracker5> ok. will look into it more.
[11:14] <flocculant> :)
[11:15] <Used2BTracker5> just experienced a crash of bluetooth. When I chose to report the problem, the error report functionality told me the error was already reported, and that the browser would be opened so that I could add extra information. The browser opened, but then showed "Error: page not found".
[11:15] <Used2BTracker5> https://bugs.launchpad.net/bugs/1542829
[11:16] <Used2BTracker5> Any advice on what to do?
[11:16] <Used2BTracker5> ubottu, indeed
[11:18] <bluesabre> ochosi: systray has that option?
[11:25] <flocculant> Used2BTracker5: that generally meens that the bug is a Private one - only the reporter and bug squad people can see it
[11:25] <flocculant> hi bluesabre
[11:25] <bluesabre> hey flocculant
[11:26] <bluesabre> saw the conversation with ali, blueman is to blame then?
[11:26] <flocculant> bluesabre: looks like
[11:26] <flocculant> don't know the best way to test it other than with a hammer - have an iso without and see what happens then :D
[11:28] <bluesabre> did we create a bug report with the info we found? I might be able to dig in this weekend, fixed blueman once before
[11:28] <flocculant> didn't do a report as had no idea what to report against
[11:29] <flocculant> I can from the vanilla install - probably best - then if it goes private I'll change it
[11:29]  * flocculant toddles off to do that now while I think about it :p
[11:29] <flocculant> brb
[11:30] <Used2BTracker5> flocculant, I didn't know about "private" errors, so I was confused...
[11:33] <bluesabre> thanks flocculant
[11:33] <bluesabre> Used2BTracker5: yes, if the bug reported may contain sensitive information or exposes a security risk, it gets marked as private unless the reporter marks it as not or somebody in the bugs team marks it as not
[11:37] <flocculant> bluesabre: bug 1754836
[11:37] <flocculant> just going to try and get xsession errors from live session
[11:43] <flocculant> bluesabre: live doesn't seem to show the same thing for bluez - but added anyway
[11:44] <bluesabre> thanks flocculant
[11:44] <bluesabre> ochosi: ind looks good, packaged and tested, time to upload :)
[11:44] <flocculant> bluesabre: np
[11:45] <flocculant> I perhaps should have been a lot noiser about this 3 months ago lol
[11:45] <bluesabre> :D
[11:45] <bluesabre> flocculant: something else would have broken with it in that time
[11:45] <flocculant> ha ha ha
[11:46] <bluesabre> https://launchpad.net/ubuntu/+source/xfce4-indicator-plugin/2.3.4-0ubuntu1
[11:49] <flocculant> bluesabre: I assume you caught all the new people on tracker - and now have met the new person in here :)
[11:49] <bluesabre> flocculant: indeed, seen some new nicks
[11:49] <bluesabre> very nice :)
[11:56] <flocculant> yup :)
[12:17] <bluesabre> tested and packaged this too, https://launchpad.net/ubuntu/+source/thunar/1.6.14-1ubuntu1
[12:18] <flocculant> awesome
[12:44] <ochosi> bluesabre: at least in 4.13 it has it. not sure whether we backported it (could ask ninetls to look into it ;))
[12:45] <bluesabre> ochosi: seems not, at least with the current stable 4.12.x
[12:45] <ninetls> ochosi: only 4.13 has it, we haven't backported it
[12:45] <ochosi> bluesabre: not sure we want another FFe for that
[12:46] <bluesabre> I consider that more UI than feature
[13:00] <ochosi> bluesabre: true that. so depends if anyone (ninetls?) feels like backporting
[13:01] <ochosi> should be doable though
[13:01] <ochosi> question is whether theres anything else panel-wise we want
[13:03] <flocculant> ochosi: re panel - next cycle I will revisit the 'flocculant to look at panel changes'
[13:06] <bluesabre> knome, slickymaster, Unit193... is this an issue?
[13:06] <bluesabre> warning: failed to load external entity "C/translator-credits.xml"
[13:06] <bluesabre> warning: failed to load external entity "C/translators.xml"
[13:08] <bluesabre> other than that, docs are ready to upload
[13:13] <ochosi> flocculant: cool, i think next cycle we shpuld target the 4.13 panrl
[13:13] <ochosi> crap. phone.
[13:13] <flocculant> :D
[13:13] <flocculant> I assume you mean 4.13 panel abnd not 4.13 phone
[13:14] <flocculant> crap. fat fingers.
[13:14] <bluesabre> pretty sure he's talbfing about the 3.14 phone
[13:14] <flocculant> lmao
[13:15]  * flocculant is trying to get photo's from daughter's iphone :(
[13:15] <flocculant> next time perhaps she'll listen and not do the whole iHype thing
[13:17] <ochosi> thanks for all the typos :D
[13:18] <flocculant> :p
[13:27] <knome> bluesabre, is what an issue?
[13:28] <bluesabre> knome: when building the docs, I see
[13:28] <bluesabre> warning: failed to load external entity "C/translator-credits.xml"
[13:28] <bluesabre> warning: failed to load external entity "C/translators.xml"
[13:29] <bluesabre> also this, but that doesn't sound like a significant issue
[13:29] <bluesabre> [WARN] FOUserAgent - The contents of fo:region-before on page 46 exceed the available area in the block-progression direction by 1450 millipoints. (See position 2:583354)
[13:44] <knome> bluesabre, i think that's always happened
[13:44] <knome> yes, don't worry about it
[13:44] <knome> the first warning is, i imagine, for the english build
[13:44] <knome> as there should be no translators.xml file
[13:45] <knome> the other is related to creating the PDF files, but i've checked them numerous times and nothing overlaps any page or other area in a meaningful (or even visible) way, so *shrug*
[13:56] <bluesabre> knome, thanks!
[13:59] <bluesabre> https://launchpad.net/ubuntu/+source/xubuntu-docs/18.04
[13:59] <knome> np
[14:02] -SwissBot:#xubuntu-devel- ::xubuntu-docs:: [bionic] r645 Strip whitespace from d/changelog and d/rules, update Standa... (by Sean Davis)
[14:02] -SwissBot:#xubuntu-devel- ::xubuntu-docs:: [bionic] r646 Release 18.04 (by Sean Davis)
[14:19] <flocculant> ochosi: tiny little icon in sn-plugin? https://i.imgur.com/w2PVIVv.png
[14:19] <flocculant> panel is 26px
[14:25] <bluesabre> flocculant: try enabling the square icons config option in sn-plug and see if that helps
[14:26] <flocculant> bluesabre: just moves it a tiny little bit to the right :p
[14:26] <bluesabre> lol
[14:26] <flocculant> bug report it?
[14:26] <bluesabre> go for it
[14:28] <flocculant> at least it showed something - not had anything show up in there previously :p
[14:29] <flocculant> I've never really got which things should show up in these types of plugins
[14:30] <flocculant> actually when I think about it - the net one I hid was small too
[14:31] <bluesabre> flocculant: panel version?
[14:32] <flocculant> 4.12.2
[14:32] <flocculant> bug 1754854
[14:37] <ninetls> ochosi: I can try. most likely, it won't be hard
[14:43] <ninetls> flocculant: is it gtk or qt version of transmission?
[14:44] <flocculant> ninetls: gtk I assume - ubuntu version
[14:51] <bluesabre> guessing it's a bug in the panel height calculation if it's not full width
[14:52] <ninetls> works on my machine!
[14:52] <ninetls> but I have xfce4-panel 4.13
[14:52] <ninetls> I can try to test on 4.12
[15:18] <ninetls> tried on 4.12 and still couldn't reproduce :/
[16:38] <slickymaster> bluesabre, I think that error always happens
[18:15] <Used2BTracker5> I'd like some more directions for testing please. I have been using 18.04 for two days now. I'm using all my normal programmes: firefox, vmware-view-client, dropbox, libreoffice. All's well. Only had a crash in bluetooth, which is already being worked on (if I understand correctly).
[18:15] <Used2BTracker5> So, as to directions:
[18:16] <Used2BTracker5> Is there anything I can do? A testcase for an up to date 18.04, which you would like to see?
[18:17] <Used2BTracker5> Is there an Xubuntu program which I perhaps don't normally use, but which has been misbehaving, and since been updated, which needs a testrun?
[19:13] <flocculant> Used2BTracker5: it's often quieter here at times on the weekend :p
[19:14] <flocculant> doing what you've been doing is more or less what I do
[19:14] <flocculant> what you could do is this:
[19:14] <flocculant> go to the release note for 18.04 ( https://wiki.xubuntu.org/releases/18.04/release-notes )
[19:15] <flocculant> check the issues we've noted - make sure they are still issues
[19:15] <slickymaster> hmm flocculant what ever happened to the packages tracker?
[19:16] <flocculant> then further down in the Major Updates section - check out all of the new or updated applications we've noted there - and try them out too
[19:16] <flocculant> also - have a think about usability issues - does the application you're using make life hard? could a change make things easier?
[19:17] <flocculant> slickymaster: we don't often use it now as it seemed better to try and get people to actually use things in real life
[19:18] <flocculant> I could enable it for 18.04 but a bit late in the game now as likely changes needed to many testcases
[19:18] <slickymaster> thought of it in the sequence of Used2BTracker5 request
[19:18] <slickymaster> nooooo
[19:18] <flocculant> yea - I did exactly the same thinking :p
[19:18] <slickymaster> only 7 corrected so far
[19:18] <flocculant> anyway - with that - I'm off again for a while
[19:18] <slickymaster> hf
[19:19] <flocculant> :)
[19:29] <Used2BTracker5> Explored my 18.04 a bit for things I wouldn't normally use. Came across something which seems "wrong": http://i.imgur.com/Jqdge9z.png. If I click on details I see this: http://i.imgur.com/Najzu0J.png
[19:30] <Used2BTracker5> It's not something that's bothering me, but, well, I thought I report it here. :-)
[19:31] <Used2BTracker5> ((Thank you all for your patience. I'm learning as I go along; only just found out how to use print screen in conjunction with imgur... :-) ))
[19:33] <Used2BTracker5> https://wiki.xubuntu.org/releases/18.04/release-notes is very helpful, thanks
[19:41] <flocculant> that is a new thing for menulibre - it's telling you it has found issues with menu files
[19:41] <flocculant> funny how the second shot isn't translated
[19:42] <flocculant> off again - back early tomorrow - then back in the afternoon
[19:42] <flocculant> Used2BTracker5: thanks for working with us :)
[19:44] <Used2BTracker5> Well, the warning message isn't translated either. Luckily I understand english ;-)
[19:48] <Used2BTracker5> The menu files, which menulibre has found issues with, were not added by me; they apparently are part of the initial installation. As a simple end user I would not know what to do to rectify these menu files.
[19:49] <Used2BTracker5> Anyway: thank you for your time.
[20:08] <bluesabre> flocculant: added a work item to fix the issues menulibre finds with launchers to https://blueprints.launchpad.net/ubuntu/+spec/xubuntu-b-development
[20:15] <Used2BTracker5> bluesabre, I reported the issue on launchpad (https://bugs.launchpad.net/menulibre/+bug/1754888); should I delete that bug report?
[20:16] <bluesabre> thanks Used2BTracker5, you can keep the bug report, we'll mark it fixed once we've taken care of the issues :)
[20:19] <Used2BTracker5> you're welcome. Glad to be able to help.
[20:33] <Used2BTracker5> On 18.04 played around with mate-calc. It crashed without a message. I do have a crash report. I want to report this on launchpad, but need advice; is such a crash report likely to contain private information in any way/ (passwords, ip-adresses, and such)
[23:18] <Unit193> bluesabre: Any reason not to sync parole?


[11:03] <insanekane> !tell _jonas about repos
[11:03] <djk_> _jonas: read the links ubotu just sent you..
[11:04] <_jonas> Thanks for your help guys...I feel so lost=)
[11:05] <jesusfish> crimsun: k, building over now
[11:06] <jesusfish> crimsun: no good
[11:06] <jesusfish> ...no wonder I usually avoid building these things...
[11:06] <sioux> :))  now I have digikam with universe repo :)) thank you!
[11:07] <gast> hello
[11:07] <gast> is there a way to run multiple instances of kopete?
[11:07] <gast> (on the same desktop ^^)
[11:08] <insanekane> sioux: :)
[11:08] <insanekane> gast: why do you want multiple instances ?
[11:09] <gast> to run my friend's icq as well
[11:09] <[Relic] > where's the master list of things torun at start up?
[11:09] <djk_> gast: can't you just add 2 icq accounts?
[11:10] <gast> i want two seperated lists
[11:10] <[Relic] > gaim handle the other one?
[11:10] <insanekane> gast: why don't you run another session ?
[11:11] <[Relic] > cannot find what is writing to the HD every 5 seconds :(
[11:11] <jesusfish> crimsun: is there a way to like force the version magic?
[11:11] <gast> i considered your workarounds yet
[11:12] <insanekane> gast: K->switch user->start new session
[11:12] <gast> i know, thank you
[11:12] <insanekane> k
[11:12] <gast> so there is no way to run multiple instances of kopete?
[11:12] <insanekane> gast: heck, why don't you try kdesu ?
[11:12] <gast> aah
[11:12] <gast> mom, googling
[11:13] <jesusfish> crimsun: aha!
[11:14] <gast> ok, that's not a clean solution but thank you for the tip
[11:19] <jesusfish> crimsun: I have a feeling the headers are screwed
[11:20] <[Relic] > what is bluez-utils?  I am trying to figure out what I can shut down in hopes of getting the HD to stop running every 5 seconds
[11:28] <sioux> people thanks for now... talk you soon :)
[11:28] <sioux> I go
[11:29] <jesusfish> crimsun: got it
[11:32] <jesusfish> crimsun: headers are messed...2.6.12-8-k7 worked
[11:33] <sorush20> is there any ofline free storage
[11:34] <CVirus> guys when I start a new session of KDE .. the sound server cant be initialized in it as it is used by the first session .. is there a work round for this ?!
[11:35] <insanekane> CVirus: probably set the idle time ?
[11:35] <CVirus> insanekane, nice idea
[11:43] <sorush20> how can I cut up a compressed package into smaller pieces and then email them to my gmail account?
[11:43] <sorush20> is there a program that I can use to email my files for backup to my gmail account?
[11:44] <QMario> How do I use my Linksys WUSB11 on KUbuntu?
[11:45] <Hobbsee> !wireless
[11:46] <Hobbsee> hmmm, wonder why the bot is not responding
[11:46] <QMario> !wireless
[11:46] <QMario> Ubotu
[11:46] <Hobbsee> sorush20: maybe uncompress it, split the files, then compress them again, then send?  there may be a quicker way to do it, i'm not sure
[11:46] <Hobbsee> !ubotu
[11:47] <ubotu> [wireless]  https://wiki.ubuntu.com/HardwareSupportComponentsWirelessNetworkCards
[11:47] <QMario> Hobbsee, so what should I do?
[11:47] <ubotu> Yep, that's me! I'm a bot alright. Read http://wiki.ubuntu.com/UbotuUsage to find out how to use me. Do NOT play with me in any channel.
[11:47] <Hobbsee> ah, there we go!
[11:48] <Hobbsee> visit that page?
[11:48] <_jonas> This is the message I get when using Ktorrent and downloading files. What does it mean and how can I get it to work? "Spraren http:// http//tracker.prq.to/announce r nerkopplad. Stoppar nerladdning"
[11:49] <th3l4sts4mur41> qualche italiano :)
[11:49] <QMario> !wireless
[11:49] <ubotu> wireless is, like, https://wiki.ubuntu.com/HardwareSupportComponentsWirelessNetworkCards
[11:49] <th3l4sts4mur41> !ati
[11:49] <ubotu> rumour has it, ati is at https://wiki.ubuntu.com/BinaryDriverHowto/ATI or http://www.ubuntuforums.org/showthread.php?t=24557&page=1&pp=10
[11:54] <Nakkel> Im having a small problem with video thumbnails on Breezy and KDE 3.5, seems like Im missing /usr/lib/kde3/videothumbnail.so file? Where can I fix that?
[11:54] <Knowerrors> Anyone hear when kde 3.5 will be "ready" for usage, ie get the dependancies and bugs worked out?
[11:54] <gast> hopefully before 6.04
[11:54] <hugelmopf> Knowerrors: I did not have any problems upgrading to 3.5. But I am sure there are bugs, as in every software.
[11:54] <th3l4sts4mur41> se c' qualche italiano [quary me]  :)
[11:55] <hugelmopf> Knowerrors: anything specific that you can use help with?
[11:55] <Knowerrors> hugelmopf: Im using kde 3.5 now, you prob just haven't run into the problems, but theyre not minor things
[11:56] <hugelmopf> only problem so far is that konqueror takes forever to load webpages, while firefox works fine. seems like i have messed up some network setting.
[11:56] <Knowerrors> for example, ivman and kde storage notifications conflicting, I had to uninstall ivman
[11:56] <hugelmopf> i have been wondering what ivman is there for. what are the symptoms of the conflict?
[11:57] <djk_> hugelmopf: ivman handles the automounting..
[11:57] <Knowerrors> first window for kde comes up asking what you want to do, then ivman makes the default action happen as well
[11:57] <Knowerrors> so I had to uninstall ivman to stop this
[11:57] <QMario> !Botsnack
[11:58] <hugelmopf> Knowerrors: kde doesn't need ivman at all? i guess i'll uninstall it as well then
[11:58] <Knowerrors> right
[11:58] <Knowerrors> but the main problem now is kde doesn't automount removable media...
[11:58] <Knowerrors> for example, put in a usb flash drive, a window pops up asking what you want to do
[11:59] <Knowerrors> if you click on open in new window, it mounts it only, and does not browse to the folder for the media device
[11:59] <Knowerrors> you have to manually browse to /media/usbstorage
[12:00] <djk_> Which ati drivers are recommended? The ones from the repo or the ones directly from ati?
[12:00] <Knowerrors> the folder it takes you to first is :/media , which only handles mounting... its really weird
[12:00] <Mardle> What is this Dapper Flight 1?
[12:00] <Mardle> djk_ I use them from ATI
[12:01] <Knowerrors> test bed for next k/ubuntu
[12:01] <Knowerrors> djk_: are you using kde 3.5?
[12:01] <hugelmopf> Knowerrors: sounds indeed buggy. good they are not in the official kubuntu yet :-)
[12:01] <djk_> Knowerrors: no
[12:01] <Mardle> Knowerrors: Is there gonna be a way to upgrade when its released so i dont have to reinstall it once more?
[12:01] <djk_> Mardle: well, did you compare them to the repo ones? are they the same? what's the difference?
[12:02] <Knowerrors> Mardle: yes
[12:02] <Mardle> djk_: I just know when i tried the fglrxinfo i got the mesa respons to it and not the radeon 9800 respons i wanted to run cedega


[00:00] <alex-abreu> robru, retired yes ... they still seem stuck
[01:02] -queuebot:#ubuntu-ci-eng- alex-abreu, https://requests.ci-train.ubuntu.com/#/ticket/1640 Cancelled build (xenial/content-hub, yakkety/content-hub). Successfully built (vivid/content-hub)
[01:04] -queuebot:#ubuntu-ci-eng- ssweeny tvoss vicamo, https://requests.ci-train.ubuntu.com/#/ticket/1922 Failed to build (vivid/location-service, yakkety/location-service). Successfully built (xenial/location-service)
[01:42] -queuebot:#ubuntu-ci-eng- alex-abreu, https://requests.ci-train.ubuntu.com/#/ticket/1640 Successfully built
[02:14] <robru> alex-abreu: ah sorry for the delay there I got distracted. looks good after a retry
[02:36] -queuebot:#ubuntu-ci-eng- ssweeny tvoss vicamo, https://requests.ci-train.ubuntu.com/#/ticket/1922 Preparing packages
[03:24] -queuebot:#ubuntu-ci-eng- ssweeny tvoss vicamo, https://requests.ci-train.ubuntu.com/#/ticket/1922 Failed to build (vivid/location-service). Successfully built (xenial/location-service, yakkety/location-service)
[04:13] <bzoltan> robru:  do you know when the OTA14 QA queue will open?
[04:13] <robru> bzoltan: no idea. Mirv or jibel ^^
[04:31] <Mirv> robru: bzoltan: it hasn't been formally announced but since OTA13 is snapshotted OTA14 would be open. but what it really depends on is what QA has time for eg this week.
[04:31] <Mirv> since they are busy among else fully testing the OTA13
[04:31] <robru> Yeah
[05:06] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://requests.ci-train.ubuntu.com/#/ticket/1884 Preparing packages
[05:26] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://requests.ci-train.ubuntu.com/#/ticket/1884 Dependency wait (yakkety/unity-scopes-shell). Failed to build (yakkety/unity-scope-click). Successfully built (vivid/unity-scope-click, vivid/unity-scopes-api, vivid/unity-scopes-shell, xenial/unity-scope-click, xenial/unity-scopes-api, xenial/unity-scopes-shell, yakkety/unity-scopes-api)
[05:41] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://requests.ci-train.ubuntu.com/#/ticket/1884 Preparing packages
[06:06] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://requests.ci-train.ubuntu.com/#/ticket/1884 Currently building (vivid/unity-scopes-shell, xenial/unity-scopes-shell). Dependency wait (yakkety/unity-scopes-shell). Failed to build (yakkety/unity-scope-click). Successfully built (vivid/unity-scope-click, vivid/unity-scopes-api, xenial/unity-scope-click, xenial/unity-scopes-api, yakkety/unity-scopes-api)
[06:26] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://requests.ci-train.ubuntu.com/#/ticket/1884 Currently building (xenial/unity-scopes-shell). Dependency wait (yakkety/unity-scopes-shell). Failed to build (yakkety/unity-scope-click). Successfully built (vivid/unity-scope-click, vivid/unity-scopes-api, vivid/unity-scopes-shell, xenial/unity-scope-click, xenial/unity-scopes-api, yakkety/unity-scopes-api)
[06:46] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://requests.ci-train.ubuntu.com/#/ticket/1884 Dependency wait (yakkety/unity-scopes-shell). Failed to build (yakkety/unity-scope-click). Successfully built (vivid/unity-scope-click, vivid/unity-scopes-api, vivid/unity-scopes-shell, xenial/unity-scope-click, xenial/unity-scopes-api, xenial/unity-scopes-shell, yakkety/unity-scopes-api)
[07:16] <Saviq> jibel, davmor2, https://requests.ci-train.ubuntu.com/#/ticket/1912 is ready (green on vivid, xenial broken due to Qt 5.6 - we're landing a fix for that soon https://code.launchpad.net/~lukas-kde/unity8/fixFailingColorTests/+merge/304632)
[07:27] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://requests.ci-train.ubuntu.com/#/ticket/1884 Preparing packages
[07:36] -queuebot:#ubuntu-ci-eng- Cimi, https://requests.ci-train.ubuntu.com/#/ticket/1636 Preparing packages
[07:46] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://requests.ci-train.ubuntu.com/#/ticket/1884 Dependency wait (yakkety/unity-scopes-shell). Failed to build (xenial/unity-scope-click). Successfully built (vivid/unity-scope-click, vivid/unity-scopes-api, vivid/unity-scopes-shell, xenial/unity-scopes-api, xenial/unity-scopes-shell, yakkety/unity-scope-click, yakkety/unity-scopes-api)
[07:55] -queuebot:#ubuntu-ci-eng- sil2100, https://requests.ci-train.ubuntu.com/#/ticket/1814 Bad merges (yakkety/unity-scopes-api). Ready to build (vivid/zeromq3, vivid/zmqpp). Successfully built (vivid/unity-scopes-api, xenial/unity-scopes-api, xenial/zeromq3, xenial/zmqpp, yakkety/zeromq3, yakkety/zmqpp)
[08:06] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://requests.ci-train.ubuntu.com/#/ticket/1884 Failed to build (xenial/unity-scope-click). Needs rebuild due to new commits (yakkety/unity-scopes-api, yakkety/unity-scopes-shell). Successfully built (vivid/unity-scope-click, vivid/unity-scopes-api, vivid/unity-scopes-shell, xenial/unity-scopes-api, xenial/unity-scopes-shell, yakkety/unity-scope-click)
[08:08] <Saviq> jibel, did you see above ↑↑↑? 1912 is ready for you guys
[08:09] <davmor2> Saviq: is this the scope loading fix?
[08:09] -queuebot:#ubuntu-ci-eng- Cimi, https://requests.ci-train.ubuntu.com/#/ticket/1636 Currently building (vivid/unity8, xenial/unity8, yakkety/unity8). Failed to build (vivid/qtmir, vivid/qtmir-gles, vivid/unity-system-compositor, yakkety/unity-system-compositor). Successfully built (vivid/ubuntu-settings-components, vivid/ubuntu-system-settings, vivid/unity-api, xenial/qtmir, xenial/qtmir-gles, xenial/ubuntu-settings-components, xenial/ubuntu-system-settings, xenial/unit
[08:13] <Saviq> davmor2, yes
[08:14] <jibel> Saviq, yes, I saw it thanks, we'll land it today
[08:14] <Saviq> ack
[08:14] <Saviq> jibel, davmor2, two things I wanted to ask if you know about: 1) for a few weeks now I've been unable to use hotspot on on my krillin (always forgetting to ask) - before it wouldn't even turn on, now I can't connect to it (wifi auth fails) 2) when flashing krillin and frieza with rc-proposed, I noticed I often need to reboot manually after flashing is complete - the device just stays black until I do
[08:16] <davmor2> Saviq: what kinda of sim contract or pay as you go?
[08:16] <Saviq> davmor2, contract
[08:17] <Saviq> was working fine before
[08:17] <davmor2> yeap just checking the obvious first :)
[08:17] <jibel> Saviq, I didn't have problem with hotspot, I used it heavily during my holidays but didn't try since I'm back
[08:18] <davmor2> just updating mine
[08:18] <jibel> I'll reflahs krillin
[08:19] <Saviq> I seem to be failing to authenticate http://pastebin.ubuntu.com/23149235/
[08:19] <Saviq> lemme change passwords as it's better now anyway
[08:20] <davmor2> Saviq: so you forgot your own password ;)
[08:20] <Saviq> nope
[08:20] <Saviq> doesn't help
[08:20] <Saviq> it's as if the hotspot's set up wrong
[08:21] <jibel> Saviq, is it a phone you upgraded, or freshly flahsed?
[08:21] <Saviq> jibel, my dogfooding one
[08:21] <Saviq> so it may very well be I have something fooked in my hotspot config
[08:22] <Saviq> after having tried xenial or something
[08:22] <Saviq> just not sure where to reset it...
[08:22] <davmor2> Saviq: you flipped between xenial and vivid on that device
[08:23] <Saviq> I might've
[08:23] <Saviq> not saying it's not my fault
[08:25] <jibel> Saviq, In /etc/NetworkManager/system-connections there is a config file for the hotspot, not sure if there is anything else
[08:26] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://requests.ci-train.ubuntu.com/#/ticket/1884 Bad merges (yakkety/unity-scopes-api). Failed to build (xenial/unity-scope-click). Needs rebuild due to new commits (yakkety/unity-scopes-shell). Successfully built (vivid/unity-scope-click, vivid/unity-scopes-api, vivid/unity-scopes-shell, xenial/unity-scopes-api, xenial/unity-scopes-shell, yakkety/unity-scope-click)
[08:27] <davmor2> Saviq: working here
[08:28] <jibel> ouch, I disabled the hotspot and the phone crashed
[08:28] <jibel> hard reboot
[08:29] <davmor2> jibel: hmmm worked fine here :(
[08:29] -queuebot:#ubuntu-ci-eng- Cimi, https://requests.ci-train.ubuntu.com/#/ticket/1636 Currently building (vivid/unity8). Failed to build (vivid/qtmir, vivid/qtmir-gles, vivid/unity-system-compositor, yakkety/unity-system-compositor). Successfully built (vivid/ubuntu-settings-components, vivid/ubuntu-system-settings, vivid/unity-api, xenial/qtmir, xenial/qtmir-gles, xenial/ubuntu-settings-components, xenial/ubuntu-system-settings, xenial/unity-api, xenial/unity-system-comp
[08:34] <Saviq> jibel, it happened to me too sometimes when I changed the details while hotspot was on
[08:34] <Saviq> anyway, will talk with network folks later
[08:35] <Saviq> how about the reboot-on-flash? was it rebooting reliably for you?
[08:46] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://requests.ci-train.ubuntu.com/#/ticket/1884 Failed to build (xenial/unity-scope-click). Needs rebuild due to new commits (yakkety/unity-scopes-api, yakkety/unity-scopes-shell). Successfully built (vivid/unity-scope-click, vivid/unity-scopes-api, vivid/unity-scopes-shell, xenial/unity-scopes-api, xenial/unity-scopes-shell, yakkety/unity-scope-click)
[08:50] -queuebot:#ubuntu-ci-eng- Cimi, https://requests.ci-train.ubuntu.com/#/ticket/1636 Failed to build (vivid/qtmir, vivid/qtmir-gles, vivid/unity-system-compositor, yakkety/unity-system-compositor). Successfully built (vivid/ubuntu-settings-components, vivid/ubuntu-system-settings, vivid/unity-api, vivid/unity8, xenial/qtmir, xenial/qtmir-gles, xenial/ubuntu-settings-components, xenial/ubuntu-system-settings, xenial/unity-api, xenial/unity-system-compositor, xenial/unity8
[08:59] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://requests.ci-train.ubuntu.com/#/ticket/1884 Preparing packages
[09:03] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://requests.ci-train.ubuntu.com/#/ticket/1884 vivid/unity-scopes-shell: Failed to download DSC file https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable-phone-overlay/+files/unity-scopes-shell_0.5.7+15.04.20160624.2-0ubuntu1.dsc
[09:18] -queuebot:#ubuntu-ci-eng- mzanetti, https://requests.ci-train.ubuntu.com/#/ticket/1675 Preparing packages
[09:26] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://requests.ci-train.ubuntu.com/#/ticket/1884 Currently building (vivid/unity-scopes-api). Dependency wait (vivid/unity-scope-click, vivid/unity-scopes-shell, xenial/unity-scope-click, xenial/unity-scopes-shell, yakkety/unity-scope-click, yakkety/unity-scopes-shell). Failed to build (xenial/unity-scopes-api). Successfully built (yakkety/unity-scopes-api)
[09:47] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://requests.ci-train.ubuntu.com/#/ticket/1884 Dependency wait (vivid/unity-scope-click, vivid/unity-scopes-shell, xenial/unity-scope-click, xenial/unity-scopes-shell, yakkety/unity-scope-click, yakkety/unity-scopes-shell). Failed to build (xenial/unity-scopes-api). Successfully built (vivid/unity-scopes-api, yakkety/unity-scopes-api)
[09:57] -queuebot:#ubuntu-ci-eng- mzanetti, https://requests.ci-train.ubuntu.com/#/ticket/1675 Failed to build (xenial/unity8). Successfully built (vivid/unity8, yakkety/unity8)
[10:37] -queuebot:#ubuntu-ci-eng- mzanetti, https://requests.ci-train.ubuntu.com/#/ticket/1675 Failed to build (xenial/unity8). Needs rebuild due to new commits (yakkety/unity8). Successfully built (vivid/unity8)
[10:47] -queuebot:#ubuntu-ci-eng- renatofilho, https://requests.ci-train.ubuntu.com/#/ticket/1875 QA Signoff: Ready
[10:52] -queuebot:#ubuntu-ci-eng- Saviq, https://requests.ci-train.ubuntu.com/#/ticket/1912 QA Signoff: Ready
[11:07] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://requests.ci-train.ubuntu.com/#/ticket/1884 Preparing packages
[11:18] -queuebot:#ubuntu-ci-eng- Cimi, https://requests.ci-train.ubuntu.com/#/ticket/1636 Preparing packages
[11:20] <Saviq> robru, it looks as if more is going wrong wrt. author https://bazaar.launchpad.net/~ci-train-bot/unity8/unity8-ubuntu-yakkety-landing-078/changes - the ones that "lost" its author don't get the merged history either
[11:20] <Saviq> except that branch will soon get overwritten... let's see how it looks then
[11:31] <jibel> ogra_, hi, can you help with this build failure? https://launchpadlibrarian.net/283238146/buildlog_ubuntu_xenial_armhf_ubuntu-touch_BUILDING.txt.gz
[11:31] <jibel> lukasz is on holidays
[11:31] <jibel> ogra_, IIRC livecd-rootfs must be updated with the password db changes
[11:31] <jibel> s/with/when/
[11:40] -queuebot:#ubuntu-ci-eng- Elleo, https://requests.ci-train.ubuntu.com/#/ticket/1826 Preparing packages
[11:41] -queuebot:#ubuntu-ci-eng- timo-jyrinki, https://requests.ci-train.ubuntu.com/#/ticket/1860 Diff missing (yakkety/qtbase-opensource-src, yakkety/qtscript-opensource-src, yakkety/qtxmlpatterns-opensource-src). Failed to build (yakkety/qtdeclarative-opensource-src). Ready to build (yakkety/qtbase-opensource-src-gles, yakkety/qtdeclarative-opensource-src-gles)
[11:49] -queuebot:#ubuntu-ci-eng- Cimi, https://requests.ci-train.ubuntu.com/#/ticket/1636 Currently building (vivid/qtmir, vivid/qtmir-gles, vivid/unity8, xenial/qtmir, xenial/qtmir-gles, xenial/unity8, yakkety/qtmir, yakkety/qtmir-gles, yakkety/unity8). Failed to build (vivid/unity-system-compositor, yakkety/unity-system-compositor). Successfully built (vivid/ubuntu-settings-components, vivid/ubuntu-system-settings, vivid/unity-api, xenial/ubuntu-settings-components, xenial/
[12:06] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://requests.ci-train.ubuntu.com/#/ticket/1884 Dependency wait (vivid/unity-scope-click, xenial/unity-scope-click, xenial/unity-scopes-shell, yakkety/unity-scope-click, yakkety/unity-scopes-shell). Successfully built (vivid/unity-scopes-api, vivid/unity-scopes-shell, xenial/unity-scopes-api, yakkety/unity-scopes-api)
[12:09] -queuebot:#ubuntu-ci-eng- Cimi, https://requests.ci-train.ubuntu.com/#/ticket/1636 Currently building (vivid/qtmir, vivid/qtmir-gles, vivid/unity8, xenial/qtmir, xenial/unity8, yakkety/unity8). Failed to build (vivid/unity-system-compositor, yakkety/unity-system-compositor). Successfully built (vivid/ubuntu-settings-components, vivid/ubuntu-system-settings, vivid/unity-api, xenial/qtmir-gles, xenial/ubuntu-settings-components, xenial/ubuntu-system-settings, xenial/unit
[12:13] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://requests.ci-train.ubuntu.com/#/ticket/1884 Preparing packages
[12:16] -queuebot:#ubuntu-ci-eng- Elleo, https://requests.ci-train.ubuntu.com/#/ticket/1677 Preparing packages
[12:28] -queuebot:#ubuntu-ci-eng- Cimi, https://requests.ci-train.ubuntu.com/#/ticket/1636 Preparing packages
[12:28] -queuebot:#ubuntu-ci-eng- Elleo, https://requests.ci-train.ubuntu.com/#/ticket/1826 Successfully built
[12:39] -queuebot:#ubuntu-ci-eng- Elleo, https://requests.ci-train.ubuntu.com/#/ticket/1677 Needs rebuild due to new commits (yakkety/ubuntu-download-manager). Successfully built (vivid/ubuntu-download-manager, xenial/ubuntu-download-manager)
[12:46] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://requests.ci-train.ubuntu.com/#/ticket/1884 Currently building (vivid/unity-scopes-api). Dependency wait (vivid/unity-scope-click, xenial/unity-scope-click, xenial/unity-scopes-shell, yakkety/unity-scope-click, yakkety/unity-scopes-shell). Failed to build (xenial/unity-scopes-api). Successfully built (vivid/unity-scopes-shell, yakkety/unity-scopes-api)
[12:47] -queuebot:#ubuntu-ci-eng- jamesh, https://requests.ci-train.ubuntu.com/#/ticket/1888 Preparing packages
[12:54] -queuebot:#ubuntu-ci-eng- Saviq, https://requests.ci-train.ubuntu.com/#/ticket/1912 QA Signoff: Approved
[13:07] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://requests.ci-train.ubuntu.com/#/ticket/1884 Dependency wait (vivid/unity-scope-click, xenial/unity-scope-click, xenial/unity-scopes-shell, yakkety/unity-scope-click, yakkety/unity-scopes-shell). Failed to build (vivid/unity-scopes-api, xenial/unity-scopes-api). Successfully built (vivid/unity-scopes-shell, yakkety/unity-scopes-api)
[13:09] -queuebot:#ubuntu-ci-eng- mardy dbarth, https://requests.ci-train.ubuntu.com/#/ticket/1924 Preparing packages
[13:10] <jibel> slangasek, hi, could someone have a look at this build failure https://launchpadlibrarian.net/283238146/buildlog_ubuntu_xenial_armhf_ubuntu-touch_BUILDING.txt.gz the password db changed
[13:10] <jibel> slangasek, and this one https://launchpadlibrarian.net/283236152/buildlog_ubuntu_xenial_arm64_ubuntu-touch_BUILDING.txt.gz
[13:11] <jibel> which is due to a new version of filemanager not built for arm64, I uploaded a new version there http://people.canonical.com/~j-lallement/arm64/com.ubuntu.filemanager_0.4.569_arm64.click for arm64
[13:11] <jibel> but I don't know where lukasz upload them
[13:12] -queuebot:#ubuntu-ci-eng- Cimi, https://requests.ci-train.ubuntu.com/#/ticket/1636 Failed to build (vivid/unity-system-compositor, yakkety/unity-system-compositor). Needs rebuild due to new commits (yakkety/unity8). Successfully built (vivid/qtmir, vivid/qtmir-gles, vivid/ubuntu-settings-components, vivid/ubuntu-system-settings, vivid/unity-api, vivid/unity8, xenial/qtmir, xenial/qtmir-gles, xenial/ubuntu-settings-components, xenial/ubuntu-system-settings, xenial/unity
[13:12] <jibel> slangasek, and finally there is no new build for rc, do you the status of the build?
[13:23] -queuebot:#ubuntu-ci-eng- tiagosh bfiller boiko, https://requests.ci-train.ubuntu.com/#/ticket/1902 Preparing packages
[13:23] -queuebot:#ubuntu-ci-eng- Saviq, https://requests.ci-train.ubuntu.com/#/ticket/1912 Publishing packages
[13:25] -queuebot:#ubuntu-ci-eng- mardy dbarth, https://requests.ci-train.ubuntu.com/#/ticket/1924 Failed to build
[13:26] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://requests.ci-train.ubuntu.com/#/ticket/1884 Currently building (xenial/unity-scopes-shell). Dependency wait (xenial/unity-scope-click, yakkety/unity-scopes-shell). Failed to build (vivid/unity-scopes-api, xenial/unity-scopes-api). Successfully built (vivid/unity-scope-click, vivid/unity-scopes-shell, yakkety/unity-scope-click, yakkety/unity-scopes-api)
[13:26] -queuebot:#ubuntu-ci-eng- tiagosh bfiller boiko, https://requests.ci-train.ubuntu.com/#/ticket/1902 /: Failed to upload diffs. Please try regenerating diffs
[13:30] -queuebot:#ubuntu-ci-eng- jamesh, https://requests.ci-train.ubuntu.com/#/ticket/1888 Failed to build
[13:30] -queuebot:#ubuntu-ci-eng- jhodapp, https://requests.ci-train.ubuntu.com/#/ticket/1921 Preparing packages
[13:34] -queuebot:#ubuntu-ci-eng- tiagosh bfiller boiko, https://requests.ci-train.ubuntu.com/#/ticket/1902 Generating diffs
[13:40] -queuebot:#ubuntu-ci-eng- Cimi, https://requests.ci-train.ubuntu.com/#/ticket/1636 Preparing packages
[13:40] -queuebot:#ubuntu-ci-eng- kenvandine, https://requests.ci-train.ubuntu.com/#/ticket/1175 Needs rebuild due to new commits (yakkety/ubuntu-system-settings). Successfully built (vivid/address-book-app, vivid/libqofono, vivid/ubuntu-system-settings, xenial/address-book-app, xenial/libqofono, xenial/ubuntu-system-settings, yakkety/address-book-app, yakkety/libqofono)
[13:41] -queuebot:#ubuntu-ci-eng- Elleo, https://requests.ci-train.ubuntu.com/#/ticket/1677 Preparing packages
[13:43] -queuebot:#ubuntu-ci-eng- mardy dbarth, https://requests.ci-train.ubuntu.com/#/ticket/1924 Preparing packages
[13:44] -queuebot:#ubuntu-ci-eng- mardy dbarth, https://requests.ci-train.ubuntu.com/#/ticket/1924 yakkety/account-polld: Failed to merge https://code.launchpad.net/~mardy/account-polld/external-plugins
[13:45] -queuebot:#ubuntu-ci-eng- Cimi, https://requests.ci-train.ubuntu.com/#/ticket/1636 yakkety/unity8: Failed to branch https://code.launchpad.net/~cimi/unity8/flick-speed-tuning
[13:46] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://requests.ci-train.ubuntu.com/#/ticket/1884 Dependency wait (xenial/unity-scope-click, yakkety/unity-scopes-shell). Failed to build (vivid/unity-scopes-api, xenial/unity-scopes-api). Successfully built (vivid/unity-scope-click, vivid/unity-scopes-shell, xenial/unity-scopes-shell, yakkety/unity-scope-click, yakkety/unity-scopes-api)
[13:51] -queuebot:#ubuntu-ci-eng- mardy dbarth, https://requests.ci-train.ubuntu.com/#/ticket/1924 Preparing packages
[13:53] -queuebot:#ubuntu-ci-eng- Saviq, https://requests.ci-train.ubuntu.com/#/ticket/1912 Proposed pocket (yakkety/qtmir, yakkety/qtmir-gles). Release pocket (vivid/qtmir, vivid/qtmir-gles, xenial/qtmir, xenial/qtmir-gles)
[14:03] -queuebot:#ubuntu-ci-eng- jhodapp, https://requests.ci-train.ubuntu.com/#/ticket/1921 Successfully built
[14:04] -queuebot:#ubuntu-ci-eng- tiagosh bfiller boiko, https://requests.ci-train.ubuntu.com/#/ticket/1902 Failed to build (yakkety/telephony-service). Successfully built (vivid/telephony-service, xenial/telephony-service)
[14:06] -queuebot:#ubuntu-ci-eng- mardy dbarth, https://requests.ci-train.ubuntu.com/#/ticket/1924 Failed to build
[14:10] -queuebot:#ubuntu-ci-eng- Cimi, https://requests.ci-train.ubuntu.com/#/ticket/1636 Destination version missing from changelog (yakkety/qtmir). Failed to build (vivid/unity-system-compositor, yakkety/unity-system-compositor). Needs rebuild due to new commits (yakkety/unity8). Successfully built (vivid/qtmir, vivid/qtmir-gles, vivid/ubuntu-settings-components, vivid/ubuntu-system-settings, vivid/unity-api, vivid/unity8, xenial/qtmir, xenial/qtmir-gles, xenial/ubuntu-sett
[14:10] <cjwatson> robru: https://help.launchpad.net/Code/Git#Linking_to_bugs should work now
[14:12] -queuebot:#ubuntu-ci-eng- Elleo, https://requests.ci-train.ubuntu.com/#/ticket/1677 Preparing packages
[14:13] -queuebot:#ubuntu-ci-eng- mardy dbarth, https://requests.ci-train.ubuntu.com/#/ticket/1924 Preparing packages
[14:17] <robru> cjwatson: what's working now? just the scanning of bugs from git commits? I already went live with the code that reads merge.bugs
[14:18] <cjwatson> robru: scanning, indeed
[14:18] <robru> Saviq: I guess you overwrote it already? looks fine to me, can you be more specific about what the issue is?
[14:19] <robru> cjwatson: cool, thanks!
[14:20] -queuebot:#ubuntu-ci-eng- oSoMoN, https://requests.ci-train.ubuntu.com/#/ticket/1925 Preparing packages
[14:26] <Saviq> robru, some commits didn't have --author again
[14:27] <Saviq> but worse than that, they didn't have the tree of commits from the merge
[14:32] <robru> Saviq: can you point to the specific commit? I'm not seeing it.
[14:33] <robru> Saviq: if a merge is already merged (eg, if all it's commits are included in another merge while you were resolving conflicts), then it would indeed have no way to identify the author or the commits from that merge because it scans unmerged commits.
[14:34] <robru> Saviq: best fix would be setting prereqs on the merges so the train can sort them
[14:34] <Saviq> robru, it's looking fine now, was probably network issues again
[14:35] <robru> Saviq: can you pull up which build log pushed the problematic branch?
[14:35] <Saviq> robru, will do in a sec
[14:36] <robru> Saviq: thanks
[14:39] -queuebot:#ubuntu-ci-eng- Elleo, https://requests.ci-train.ubuntu.com/#/ticket/1677 Successfully built
[14:42] -queuebot:#ubuntu-ci-eng- Laney, https://requests.ci-train.ubuntu.com/#/ticket/1903 Preparing packages
[14:44] -queuebot:#ubuntu-ci-eng- kenvandine, https://requests.ci-train.ubuntu.com/#/ticket/1175 Preparing packages
[14:46] -queuebot:#ubuntu-ci-eng- mardy dbarth, https://requests.ci-train.ubuntu.com/#/ticket/1924 Failed to build (vivid/account-polld, vivid/account-polld-plugins-go, xenial/account-polld-plugins-go, yakkety/account-polld). Successfully built (yakkety/account-polld-plugins-go). Uploading build (xenial/account-polld)
[14:47] -queuebot:#ubuntu-ci-eng- oSoMoN, https://requests.ci-train.ubuntu.com/#/ticket/1925 Successfully built
[14:55] -queuebot:#ubuntu-ci-eng- renatofilho, https://requests.ci-train.ubuntu.com/#/ticket/1875 QA Signoff: Failed
[15:06] -queuebot:#ubuntu-ci-eng- mardy dbarth, https://requests.ci-train.ubuntu.com/#/ticket/1924 Failed to build (vivid/account-polld, vivid/account-polld-plugins-go, xenial/account-polld-plugins-go, yakkety/account-polld). Successfully built (xenial/account-polld, yakkety/account-polld-plugins-go)
[15:09] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://requests.ci-train.ubuntu.com/#/ticket/1884 Preparing packages
[15:23] <slangasek> jibel: no new build> the one I said should have happened yesterday?
[15:24] -queuebot:#ubuntu-ci-eng- Laney, https://requests.ci-train.ubuntu.com/#/ticket/1903 Successfully built
[15:25] -queuebot:#ubuntu-ci-eng- dobey tedg, https://requests.ci-train.ubuntu.com/#/ticket/1802 Failed to build (vivid/ubuntu-app-launch). Needs rebuild due to new commits (yakkety/ubuntu-app-launch, yakkety/unity-scope-click). Successfully built (vivid/unity-scope-click, xenial/ubuntu-app-launch, xenial/unity-scope-click)
[15:26] <slangasek> jibel: so, those seem to be some pretty extensive changes to the password db... who changed them?
[15:38] -queuebot:#ubuntu-ci-eng- kenvandine, https://requests.ci-train.ubuntu.com/#/ticket/1175 Successfully built
[15:54] <robru> wheeeeeeeeee
[15:55] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://requests.ci-train.ubuntu.com/#/ticket/1884 Preparing packages
[16:07] <slangasek> jibel: do you have the link to the source of those logs that you pointed me at?  you can't reverse those to find the config of the thing that was being built...
[16:14] <robru> so britney has been broken for around 12 hours and nobody in europe noticed, eh? eeeeeeenteresting!
[16:22] -queuebot:#ubuntu-ci-eng- mterry, https://requests.ci-train.ubuntu.com/#/ticket/1679 Diff missing (yakkety/lightdm). Needs rebuild due to new commits (yakkety/unity8). Successfully built (vivid/lightdm, vivid/ubuntu-touch-session, vivid/unity8, vivid/unity8-desktop-session, xenial/lightdm, xenial/ubuntu-touch-session, xenial/unity8, xenial/unity8-desktop-session, yakkety/ubuntu-touch-session, yakkety/unity8-desktop-session)
[16:24] <mterry> We don't tell you everything!  ::slams door::
[16:24] <mterry> j/k I didn't know about britney either
[16:25] <ogra_> europeans stopped litening to her a decade ago .... you mericans are so behind
[16:25] <ogra_> *listening
[16:26] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://requests.ci-train.ubuntu.com/#/ticket/1884 Dependency wait (yakkety/unity-scopes-shell). Successfully built (vivid/unity-scope-click, vivid/unity-scopes-api, vivid/unity-scopes-shell, xenial/unity-scope-click, xenial/unity-scopes-api, xenial/unity-scopes-shell, yakkety/unity-scope-click, yakkety/unity-scopes-api)
[17:00] <robru> mterry: what are the chances you have access to snakefruit and know everything about it?
[17:03] <cjwatson> robru: there was apparently a problem earlier today that pitti fixed about an hour ago
[17:04] <robru> cjwatson: yes the creds leaked and needed to be rotated, I have the new creds but it's still not working
[17:05] <robru> cjwatson: our britney has been failing for 10 hours: https://requests.ci-train.ubuntu.com/static/britney/log_20160908_163001.txt conversation happening in #webops if you know anything
[17:10] <jibel> slangasek, sorry was OTP, last rc is from 4 days ago http://system-image.ubuntu.com/ubuntu-touch/rc/bq-aquaris.en/krillin/
[17:13] <jibel> slangasek, the logs come from https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/xenial/ubuntu-touch/
[17:13] <jibel> no idea what caused these changes, I'll review the uploads
[17:21] <slangasek> jibel: so I definitely see the new rc image on the rc/ubuntu channel, which is the base channel that the others are supposed to copy their rootfs tarball from; looking now
[17:24] <slangasek> jibel: ok, so the ubuntu-touch/rc/bq-aquaris.en is set to manual, I'll mark that 'auto' so that it picks up the tarball from rc/ubuntu.  are there any other rc channels that should be updated?
[17:35] <mterry> robru: no I don't remember snakefruite
[17:37] <jibel> slangasek, bq-aquaris-pd.en, meizu-pd.en, meizu-pd.zh, meizu.en, meizu.zh
[17:39] <slangasek> jibel: marked for import, which should start in a minute
[17:39] <jibel> slangasek, okay, thanks. I'll let you know if there is still something missing
[17:48] -queuebot:#ubuntu-ci-eng- kenvandine renato, https://requests.ci-train.ubuntu.com/#/ticket/1774 Abandoning ticket
[18:02] <kenvandine> robru, i angered bileto
[18:02] <kenvandine> https://requests.ci-train.ubuntu.com/log/1774/build/latest/
[18:02] <kenvandine> robru, i abandoned the silo so i can get a new PPA
[18:02] <kenvandine> but got that error building
[18:03] <robru> kenvandine: yeah there's a delay of about an hour to really delete a PPA. just wait an hour
[18:03] <kenvandine> oh...
[18:03] <kenvandine> that hurts
[18:04] <robru> kenvandine: I'm considering putting a sequence number on the PPAs so that you can build right away again after abandoning
[18:04] <kenvandine> yeah, i was able to do this last week :)
[18:04] <robru> kenvandine: yeah the first time it was because you abandoned landing-NNN and then the new ephemeral was landing-1774, different names
[18:05] <robru> kenvandine: yeah I'll make it catch that exception then try again with a ".1" or something, but I'm just cleaning some other stuff up fist
[18:05] <robru> first
[18:06] <kenvandine> ok
[18:12] <robru> kenvandine: so I'm thinking like landing-1774-shame... ;-)
[18:13] <robru> landing-1774-impatient
[18:16] <kenvandine> robru, that's me!
[18:18] -queuebot:#ubuntu-ci-eng- ssweeny tvoss vicamo, https://requests.ci-train.ubuntu.com/#/ticket/1922 Preparing packages
[18:21] <boiko> jibel: hi, silo 1902 is the same case as silo 98 that landed yesterday: failing to build on yakkety (fix in the works) but we need that landed sooner rather than later, could you please include that in the QA queue?
[18:23] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://requests.ci-train.ubuntu.com/#/ticket/1884 Preparing packages
[18:34] <robru> kenvandine: ok I pushed an experimental fix, should go live in 6 minutes (:40 on the clock), try again then
[18:34] <kenvandine> robru, thx
[18:35] <robru> kenvandine: you're welcome. er, try at :42 on the clock so it has a chance to restart with the new code
[18:43] -queuebot:#ubuntu-ci-eng- ssweeny tvoss vicamo, https://requests.ci-train.ubuntu.com/#/ticket/1922 Failed to build (xenial/location-service, yakkety/location-service). Successfully built (vivid/location-service)
[18:47] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://requests.ci-train.ubuntu.com/#/ticket/1884 Currently building (vivid/unity-scopes-shell). Dependency wait (yakkety/unity-scopes-shell). Failed to build (xenial/unity-scopes-shell). Successfully built (vivid/unity-scope-click, vivid/unity-scopes-api, xenial/unity-scope-click, xenial/unity-scopes-api, yakkety/unity-scope-click, yakkety/unity-scopes-api)
[18:55] -queuebot:#ubuntu-ci-eng- kenvandine renato, https://requests.ci-train.ubuntu.com/#/ticket/1774 Failed to build (vivid/libphonenumber, xenial/libphonenumber, yakkety/libphonenumber). Ready to build (vivid/address-book-service, vivid/history-service, vivid/telephony-service, xenial/address-book-service, xenial/history-service, xenial/telephony-service, yakkety/address-book-service, yakkety/history-service, yakkety/telephony-service)
[19:06] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://requests.ci-train.ubuntu.com/#/ticket/1884 Dependency wait (yakkety/unity-scopes-shell). Failed to build (xenial/unity-scopes-shell). Successfully built (vivid/unity-scope-click, vivid/unity-scopes-api, vivid/unity-scopes-shell, xenial/unity-scope-click, xenial/unity-scopes-api, yakkety/unity-scope-click, yakkety/unity-scopes-api)
[19:37] -queuebot:#ubuntu-ci-eng- ssweeny tvoss vicamo, https://requests.ci-train.ubuntu.com/#/ticket/1922 Preparing packages
[19:43] -queuebot:#ubuntu-ci-eng- jhodapp, https://requests.ci-train.ubuntu.com/#/ticket/1921 Needs rebuild due to new commits (yakkety/mediaplayer-app). Successfully built (vivid/media-hub, vivid/mediaplayer-app, xenial/media-hub, xenial/mediaplayer-app, yakkety/media-hub)
[19:47] -queuebot:#ubuntu-ci-eng- kenvandine renato, https://requests.ci-train.ubuntu.com/#/ticket/1774 Abandoning ticket
[19:48] <robru> kenvandine: https://requests.ci-train.ubuntu.com/log/1926/build/latest/ that feature looks pretty reliable
[19:48] -queuebot:#ubuntu-ci-eng- robru, https://requests.ci-train.ubuntu.com/#/ticket/1926 Preparing packages
[19:48] <robru> kenvandine: out of curiosity, why do you abandon and rebuild so much?
[19:48] <kenvandine> robru, i usually don't
[19:48] <robru> kenvandine: yeah, why this one?
[19:48] <kenvandine> but i have libphonenumber i'm working on that's a manual upload
[19:49] <kenvandine> and i don't want to keep changing the revision
[19:49] -queuebot:#ubuntu-ci-eng- robru, https://requests.ci-train.ubuntu.com/#/ticket/1926 Abandoning ticket
[19:49] <robru> kenvandine: sounds like it's time to enable it for MP landings ;-)
[19:50] <kenvandine> robru, well we are hoping to get rid of our delta... so we can just use what's in debian :)
[19:50] <kenvandine> but yeah... sure would be nice
[19:50] <robru> kenvandine: wait, you're making changes to the code and re-uploading the different contents with the same revision number?
[19:50] <kenvandine> robru, yes... that's why we need new PPAs :)
[19:51] <kenvandine> it's a sync from debian with a couple patches
[19:51] <robru> kenvandine: sounds like you should be building it locally until you get it just right then upload it :-P
[19:51] <kenvandine> i am :)
[19:51] <kenvandine> but we're having problems with some other packages that depend on it
[19:51] <kenvandine> it's more than just me :)
[19:52] <robru> kenvandine: alright well the naming is sequenced now so you can build as soon as the abandon job finishes from now on. I'm off for lunch, bbl!
[19:52] <kenvandine> great
[19:52] <kenvandine> robru, thx!
[19:52] <robru> your'e welcome!
[19:54] -queuebot:#ubuntu-ci-eng- tiagosh boiko, https://requests.ci-train.ubuntu.com/#/ticket/1319 Preparing packages
[20:09] -queuebot:#ubuntu-ci-eng- ChrisTownsend kenvandine, https://requests.ci-train.ubuntu.com/#/ticket/1927 Successfully built
[20:12] -queuebot:#ubuntu-ci-eng- jhodapp, https://requests.ci-train.ubuntu.com/#/ticket/1921 Preparing packages
[20:18] -queuebot:#ubuntu-ci-eng- Cimi, https://requests.ci-train.ubuntu.com/#/ticket/1636 Preparing packages
[20:24] -queuebot:#ubuntu-ci-eng- ssweeny tvoss vicamo, https://requests.ci-train.ubuntu.com/#/ticket/1922 Failed to build (xenial/location-service). Successfully built (vivid/location-service, yakkety/location-service)
[20:25] -queuebot:#ubuntu-ci-eng- tiagosh boiko, https://requests.ci-train.ubuntu.com/#/ticket/1319 Currently building (vivid/messaging-app). Failed to build (vivid/telepathy-ofono, vivid/telephony-service, xenial/history-service, xenial/messaging-app, xenial/telepathy-ofono, xenial/telephony-service, yakkety/history-service, yakkety/messaging-app, yakkety/telepathy-ofono). Needs rebuild due to new commits (yakkety/telephony-service). Successfully built (vivid/history-service)
[20:35] -queuebot:#ubuntu-ci-eng- kenvandine renato, https://requests.ci-train.ubuntu.com/#/ticket/1774 Diff missing (vivid/libphonenumber, xenial/libphonenumber, yakkety/libphonenumber). Ready to build (vivid/address-book-service, vivid/history-service, vivid/telephony-service, xenial/address-book-service, xenial/history-service, xenial/telephony-service, yakkety/address-book-service, yakkety/history-service, yakkety/telephony-service)
[20:45] -queuebot:#ubuntu-ci-eng- tiagosh boiko, https://requests.ci-train.ubuntu.com/#/ticket/1319 Failed to build (vivid/telepathy-ofono, vivid/telephony-service, xenial/history-service, xenial/messaging-app, xenial/telepathy-ofono, xenial/telephony-service, yakkety/history-service, yakkety/messaging-app, yakkety/telepathy-ofono). Needs rebuild due to new commits (yakkety/telephony-service). Successfully built (vivid/history-service, vivid/messaging-app)
[20:51] -queuebot:#ubuntu-ci-eng- Cimi, https://requests.ci-train.ubuntu.com/#/ticket/1636 Currently building (vivid/unity8, xenial/unity8, yakkety/unity8). Destination version missing from changelog (yakkety/qtmir). Failed to build (vivid/unity-system-compositor, yakkety/unity-system-compositor). Successfully built (vivid/qtmir, vivid/qtmir-gles, vivid/ubuntu-settings-components, vivid/ubuntu-system-settings, vivid/unity-api, xenial/qtmir, xenial/qtmir-gles, xenial/ubuntu-set
[20:53] -queuebot:#ubuntu-ci-eng- Saviq, https://requests.ci-train.ubuntu.com/#/ticket/1912 Release pocket
[21:03] -queuebot:#ubuntu-ci-eng- jhodapp, https://requests.ci-train.ubuntu.com/#/ticket/1921 Needs rebuild due to new commits (yakkety/mediaplayer-app). Successfully built (vivid/media-hub, vivid/mediaplayer-app, xenial/media-hub, xenial/mediaplayer-app, yakkety/media-hub)
[21:10] -queuebot:#ubuntu-ci-eng- Cimi, https://requests.ci-train.ubuntu.com/#/ticket/1636 Currently building (vivid/unity8, xenial/unity8). Failed to build (vivid/unity-system-compositor, yakkety/unity-system-compositor). Needs rebuild due to new commits (yakkety/qtmir). Successfully built (vivid/qtmir, vivid/qtmir-gles, vivid/ubuntu-settings-components, vivid/ubuntu-system-settings, vivid/unity-api, xenial/qtmir, xenial/qtmir-gles, xenial/ubuntu-settings-components, xenial/u
[21:29] -queuebot:#ubuntu-ci-eng- Cimi, https://requests.ci-train.ubuntu.com/#/ticket/1636 Failed to build (vivid/unity-system-compositor, yakkety/unity-system-compositor). Needs rebuild due to new commits (yakkety/qtmir). Successfully built (vivid/qtmir, vivid/qtmir-gles, vivid/ubuntu-settings-components, vivid/ubuntu-system-settings, vivid/unity-api, vivid/unity8, xenial/qtmir, xenial/qtmir-gles, xenial/ubuntu-settings-components, xenial/ubuntu-system-settings, xenial/unity-
[21:34] -queuebot:#ubuntu-ci-eng- kenvandine renato, https://requests.ci-train.ubuntu.com/#/ticket/1774 Preparing packages
[21:38] -queuebot:#ubuntu-ci-eng- Laney, https://requests.ci-train.ubuntu.com/#/ticket/1903 Publishing packages
[21:38] -queuebot:#ubuntu-ci-eng- Laney, https://requests.ci-train.ubuntu.com/#/ticket/1903 Publish failed: Bad merges
[21:39] -queuebot:#ubuntu-ci-eng- Laney, https://requests.ci-train.ubuntu.com/#/ticket/1903 Publishing packages
[21:56] -queuebot:#ubuntu-ci-eng- kenvandine renato, https://requests.ci-train.ubuntu.com/#/ticket/1774 Currently building (vivid/address-book-service, vivid/history-service, xenial/address-book-service, xenial/telephony-service, yakkety/address-book-service, yakkety/telephony-service). Failed to build (vivid/telephony-service, xenial/history-service, yakkety/history-service). Successfully built (vivid/libphonenumber, xenial/libphonenumber, yakkety/libphonenumber)
[22:04] -queuebot:#ubuntu-ci-eng- Cimi, https://requests.ci-train.ubuntu.com/#/ticket/1636 Preparing packages
[22:05] -queuebot:#ubuntu-ci-eng- Laney, https://requests.ci-train.ubuntu.com/#/ticket/1903 Proposed pocket
[22:06] -queuebot:#ubuntu-ci-eng- Cimi, https://requests.ci-train.ubuntu.com/#/ticket/1636 yakkety/qtmir: Failed to merge https://code.launchpad.net/~unity-team/qtmir/mouseMovement
[22:16] -queuebot:#ubuntu-ci-eng- kenvandine renato, https://requests.ci-train.ubuntu.com/#/ticket/1774 Failed to build (vivid/telephony-service, xenial/history-service, yakkety/history-service). Successfully built (vivid/address-book-service, vivid/history-service, vivid/libphonenumber, xenial/address-book-service, xenial/libphonenumber, xenial/telephony-service, yakkety/address-book-service, yakkety/libphonenumber, yakkety/telephony-service)
[22:27] <Saviq> robru, sorry, didn't get to it before, but the new run seems to have generated the same problem https://bazaar.launchpad.net/~ci-train-bot/unity8/unity8-ubuntu-yakkety-landing-078/changes
[22:27] <Saviq> or is this an ordering issue maybe?
[22:29] -queuebot:#ubuntu-ci-eng- Cimi, https://requests.ci-train.ubuntu.com/#/ticket/1636 Failed to build (vivid/unity-system-compositor, yakkety/unity-system-compositor). Needs rebuild due to new commits (yakkety/qtmir, yakkety/unity8). Successfully built (vivid/qtmir, vivid/qtmir-gles, vivid/ubuntu-settings-components, vivid/ubuntu-system-settings, vivid/unity-api, vivid/unity8, xenial/qtmir, xenial/qtmir-gles, xenial/ubuntu-settings-components, xenial/ubuntu-system-setting
[22:35] <Saviq> robru, yeah it is an ordering problem - see in https://requests.ci-train.ubuntu.com/log/1636/build/latest/ - lp:~dandrader/unity8/cursorConfinement gets merged before its prerequisite
[22:39] <Saviq> robru, there's a lot of prereqs in that silo, might be triggering a bug in bileto
[22:49] <robru> Yikes
[22:51] <robru> Saviq: the debug log shows which MPs are being inserted out of the specified order, I'll dive in in a bit
[22:52] <Saviq> tx
[22:53] -queuebot:#ubuntu-ci-eng- Cimi, https://requests.ci-train.ubuntu.com/#/ticket/1636 Preparing packages
[23:20] <robru> Saviq: ok I see what's happening. There's a chain of prereqs, c>b>a. Your input has them as c, a, b. It sees c first then notes that b should precede it. It sees a next and leaves it in place because it isn't aware of the prereq yet. Then it sees b and says "this goes before c!" and so you end up with b, c, a
[23:22] <Saviq> robru, shall I just reorder input for now, or do you like it like that? (you can have a play, we won't be doing anything with that silo before tomorrow EU)
[23:23] <robru> Saviq: as a workaround for right now you should just move cursorconfinement before edgemaximize and it should work. No worries on my end, I'll devise a failing test then work on a solution
[23:23] <Saviq> ack, tx
[23:25] -queuebot:#ubuntu-ci-eng- Laney, https://requests.ci-train.ubuntu.com/#/ticket/1903 Release pocket
[23:49] -queuebot:#ubuntu-ci-eng- Cimi, https://requests.ci-train.ubuntu.com/#/ticket/1636 Failed to build (vivid/unity-system-compositor, yakkety/unity-system-compositor). Needs rebuild due to new commits (yakkety/unity8). Successfully built (vivid/qtmir, vivid/qtmir-gles, vivid/ubuntu-settings-components, vivid/ubuntu-system-settings, vivid/unity-api, vivid/unity8, xenial/qtmir, xenial/qtmir-gles, xenial/ubuntu-settings-components, xenial/ubuntu-system-settings, xenial/unity


[02:01] <Rocket2DMn> mdke, some other bugs have been filed and patched tonight that should probably be string freeze exceptions
[02:01] <Rocket2DMn> I'd send out an email, but I'm sure there will be more before the night is up
[11:00] <mdke> morning all
[11:00] <mdke> hi adiroiban
[11:01] <adiroiban> hi
[14:22] <slacker_nl> hello, could someone proof read the following: https://help.ubuntu.com/community/NetworkConfigurationCommandLine/Automatic I want to replace https://help.ubuntu.com/community/NetworkConfigurationCommandLine with the new document
[16:03] <Rocket2DMn> mdke, in Karmic's Applications->Accessories menu, it displays "gedit Text Editor" which doesn't match our documentation
[16:03] <Rocket2DMn> I see bug 421221 for the initial issue, but it is marked as Fix Released since they changed it from "gedit" to "gedit Text Editor"
[16:03] <ubot4> Launchpad bug 421221 in gedit "menu entry says 'gedit' should say 'Text Editor'" [Low,Fix released] https://launchpad.net/bugs/421221
[16:04] <Rocket2DMn> However, there still seems to be some discussion upstream about how to properly handle it.  Should I open a new bug against ubuntu-docs, or should I open the task on that previous bug for ubuntu-docs?
[16:04] <Rocket2DMn> I'm hesitant to open an entirely new bug against gedit for it
[16:06] <Rocket2DMn> I guess I can ask in ubuntu-devel if they plan on fixing it
[16:43] <slacker_nl> hello, could someone proof read the following: https://help.ubuntu.com/community/NetworkConfigurationCommandLine/Automatic I want to replace https://help.ubuntu.com/community/NetworkConfigurationCommandLine with the new document
[16:48] <mdke> Rocket2DMn: that sounds like a bug in gedit to me as the menu entry doesn't follow the HIG, I'd suggest asking ubuntu-desktop
[16:52] <Rocket2DMn> ok mdke , i'll ping them
[16:52] <Rocket2DMn> thanks
[16:55] <Rocket2DMn> mdke, another thing that occurred to me last night - do we currently format our xml files for consistency?  In the past I've seen files that varied from doc to doc
[16:56] <mdke> Rocket2DMn: no we don't - they definitely vary
[16:57] <Rocket2DMn> It would be really nice to get something like that, it shouldn't be all that difficult I think
[16:59] <Rocket2DMn> mdke, I'm not sure I really understand how the translations work when we do freeze exceptions or SRUs
[16:59] <mdke> yeah, I agree. Do you fancy looking into a tool that could do it reliably? I guess 'tidy' should do it, it has an xml function
[16:59] <Rocket2DMn> if a diff doesn't include text that needs to be retranslated, how does that still affect translators?
[16:59] <mdke> Rocket2DMn: but it *does* include text that needs to be retranslated
[17:00] <mdke> the original has changed, so the translators need to translate the new string
[17:00] <Rocket2DMn> but you said "The translators should leave them as they are, but changing the string
[17:00] <Rocket2DMn> will still require the translator to retranslate the string."
[17:00] <mdke> right, let me give you an example
[17:00] <Rocket2DMn> if they leave them as they are, what changes?
[17:01] <mdke> the string "ubuntu-restricted-extras includes flashplugin-nonfree" gets translated
[17:01] <mdke> in Italian that might be: "ubuntu-restricted-extra include flashplugin-nonfree"
[17:01] <mdke> then it changes to "ubuntu-restricted-extras includes flashplugin-installer"
[17:02] <mdke> that's a new string that doesn't yet have a translation, so it will appear as a new string to be translated
[17:02] <mdke> you can't use the existing translation, because it's different
[17:02] <mdke> not as clear as I'd hoped it would be :(
[17:03] <mdke> anyway, any change to a translateable string results in a new translation to be done
[17:03] <Rocket2DMn> you mean it just appears as a task for them?
[17:03] <mdke> it appears as an untranslated string
[17:03] <mdke> and if they don't translate it, it will appear in English
[17:03] <Rocket2DMn> ok, but what if no translation is ever required.  For example, here is part of the patch:

[17:04] <Rocket2DMn> tags are kept, so that leaves just "flashplugin-installer" which doesn't require translation
[17:04] <mdke> it may not require translation, but it is translatable
[17:05] <Rocket2DMn> ok, but if that were to appear "in english" in their translated docs, there is no visible effect
[17:05] <mdke> yes, that's true
[17:05] <Rocket2DMn> ok, so in Rosetta when a change is made to the branch, the adjusted lines appear as "needs translating" or something?
[17:06] <mdke> yes (although it's not the branch, it's the package that counts in our case)
[17:06] <mdke> in Rosetta it will show up as "1 string not translated" or something like that
[17:06] <mdke> you're right that it's not the end of the world, but the translators will have it on their task list and will do the work
[17:07] <Rocket2DMn> ok, i can see how we may not want to bother them with new tasks apearing like that after string freeze, but effectively it doesn't matter if they see it or not
[17:07] <mdke> you're quite right
[17:07] <Rocket2DMn> i don't have any strong opinion on the patch being included or not, I'm just trying to understand how it works
[17:07] <Rocket2DMn> I think I got the gist of it
[17:08] <mdke> yeah, you have
[17:08] <mdke> I think I was looking at it too rigidly, let's include the patch
[17:08] <Rocket2DMn> cool, thanks for explaining
[17:08] <mdke> I hadn't quite appreciated that the packagenames are the whole string, rather than just appearing in the middle of a string
[17:09] <Rocket2DMn> yeah, in this case they are just ina list
[17:10] <mdke> committed :)
[17:10] <Rocket2DMn> k
[17:10] <Rocket2DMn> As I predicted, more bugs appeared during the night :)
[17:11] <Rocket2DMn> I think we sorta dropped the ball on Grub2 documentation
[17:11] <mdke> yeah, these guys are good proof readers
[17:12] <mdke> ok, gtg to the gym, back later
[17:12] <Rocket2DMn> k, see ya
[18:21] <slacker_nl> stupic question perhaps, but how do i open .omf files?
[18:58] <mdke> slacker_nl: in a text editor
[18:59] <slacker_nl> mdke: yeah.. and then there is a pointer to some .xml file
[18:59] <mdke> slacker_nl: right.
[19:00] <slacker_nl> so how can i read somehlpfile.omf and read the actual helpfile?
[19:02] <mdke> slacker_nl: you just read the xml file
[19:14] <mdke> Rocket2DMn: I read the gedit upstream bug you referred to - it looks pretty much like upstream is determined to have the menu entries inconsistent and unpleasant to look at... so I guess we should apply your patch to ubuntu-docs
[19:40] <Rocket2DMn> mdke, it would be nice if the desktop team could confirm that they aren't going to override the change
[20:28] <mdke> Rocket2DMn: yeah, worth asking them
[21:12] <mdke> Rocket2DMn: will upload shortly - any bugs I've missed out committing that you can see?
[21:15] <Rocket2DMn> mdke, ill have a look
[21:17] <Rocket2DMn> mdke, i think that's all for now in the dev branch
[21:17] <Rocket2DMn> there are some SRUs laying around still though
[21:21] <mdke> Rocket2DMn: yeah :(