[04:56] <jibel> good morning
[05:57] <duflu> Morning jibel
[06:24] <didrocks> good morning
[06:25] <duflu> Morning didrocks
[06:26] <didrocks> hey duflu
[06:30] <didrocks> Trevinho: I didn't test it, but from the video, +1 for me if you ensured the disabled state is really looking like disabled :)
[06:31] <jamesh> looks like the new whoopsie-preferences alone is enough to fix the gnome-control-center problem
[06:31] <Trevinho> didrocks: yeah, it's like it used to be in your branch
[06:32] <Trevinho> didrocks: what's the app you used for disable?
[06:32] <Trevinho> I can do with the inspector otherwise, just lazy in finding the button :D
[07:03] <seb128> good morning desktopers
[07:04] <flexiondotorg> Morning
[07:10] <andyrock> morning
[07:10] <seb128> hey flexiondotorg andyrock
[07:10] <andyrock> hey seb128
[07:10] <andyrock> how are you?
[07:10] <Trevinho> hi seb128
[07:11] <seb128> hey Trevinho, how is it going in south america?
[07:11] <andyrock> I guess he's drinking Corona
[07:11] <Trevinho> no, never drank one yet :o
[07:11] <Trevinho> I tried others
[07:12] <duflu> Ha. Trevinho do you have a home?
[07:12] <andyrock> closer to water?
[07:12] <Trevinho> seb128: really good, good place for being focused :)
[07:12] <Trevinho> duflu: you mean back in italy?
[07:12] <Trevinho> :-D
[07:12] <duflu> Trevinho, well, I mean you spend so much of the year elswhere
[07:13] <Trevinho> as the answer would be "too many", but the problem is that... I don't want to stay there for now, when the World is quite big and it deserves my eyes who look at it :)
[07:14]  * duflu remembers now andyrock suggested a sprint at your family home a while back ;)  ... Trevinho
[07:15] <Trevinho> duflu: I'm also suggesting it all the times... The Sun sprint. It will happen  :)
[07:15] <andyrock> treviño has too many houses. andyrock none :'(
[07:19] <Trevinho> You also have, you just don't have it where you want. Like I do :)
[07:21] <seb128> Trevinho, andyrock, what are you working on atm?
[07:22] <didrocks> Trevinho: gnome-boxes, create a new machine
[07:22] <didrocks> Trevinho: all good from your perspective on the theme? Like, built in a ppa so that I can give a quick try & sponsor?
[07:22] <didrocks> hey seb128
[07:22] <Trevinho> didrocks: yeah it's in the ppa
[07:23] <didrocks> Trevinho: let me give it a try
[07:23] <seb128> lut didrocks
[07:23] <Trevinho> didrocks:  not sure it's fully built yet
[07:23] <didrocks> Trevinho: is there a bug summarizing all changes that you can reference ?
[07:23] <didrocks> Trevinho: for the release team
[07:23] <Trevinho> seb128: so.. that one ^, plus https://bugzilla.gnome.org/show_bug.cgi?id=788860
[07:23] <seb128> Trevinho, did you manage to reproduce? getting anywhere debugging?
[07:24] <Trevinho> seb128: and other fixes to indicators, as missing menus in qt again.. it seems there's an issue in dbusmenu, but still checjing
[07:24] <Trevinho> seb128: yeaah, see the ubuntu bug
[07:24] <seb128> k
[07:24] <seb128> good
[07:24] <Trevinho> I can't reproduce, but I've the coredumps... wich tells me what you see in the bug report (gnome one)
[07:24] <seb128> andyrock said he could reproduce
[07:25] <Trevinho> but while I can mute the crash (maybe enough for us), I'm still struggling to find the root cause
[07:25] <Trevinho> andyrock: can you?
[07:25] <andyrock>  yep
[07:25] <didrocks> I agree with duflu that hovering being darker is weird, but as it's the same on other parts of the theme…
[07:25] <Trevinho> yeah, i've just follwed what it was happening
[07:25] <andyrock> but I can't work on it today
[07:26] <Trevinho> andyrock: i can
[07:26] <duflu> didrocks, I mean in general it should increase contrast (see also Chrome where it is darker because the background is light)
[07:26] <Trevinho> andyrock: just check the bug
[07:26] <Trevinho> andyrock: I mean, it's something weird happening
[07:26] <andyrock> I've stuff todo for the livepatch
[07:26] <andyrock> I can't open that bug
[07:26] <didrocks> Trevinho: I find the new green really glaring, I wonder if I'm not going to change it a little bit
[07:27] <didrocks> Trevinho: otherwise, even if I'm not a fan of the titlebar, I think it's an overall improvment
[07:27] <didrocks> so, let's try to get that landed (with a small green changes IMHO)
[07:27] <duflu> But since Ambiance grey is dark, the right hover contrast should be lighter
[07:27] <Trevinho> didrocks: do what you want with green :)
[07:27] <Trevinho> just change it in the gtk-main.css
[07:27] <seb128> Trevinho, didrocks, it's getting late for look changes, gnome-shell segfaults should probably get higher priority at this point (that comment is rather for Trevinho)
[07:27] <duflu> Maybe that's where purple could be used
[07:28] <didrocks> Trevinho: yep, did you see my question about a bug report? how can I change your branches?
[07:28] <duflu> seb128, surely cards will be moved into 18.04 soon? :)
[07:28] <didrocks> seb128: yeah, that's why I told I'm going to change it myself
[07:28] <Trevinho> seb128: in fact I'm all force on that, just few tweaks on the theme recently
[07:28] <Trevinho> but it took just few minutes
[07:28] <seb128> duflu, yes
[07:28] <seb128> Trevinho, k, good
[07:28] <seb128> andyrock, how did you reproduce the segfault?
[07:28] <didrocks> Trevinho: I'm unsure how I can alter your bileto ticket
[07:28] <didrocks> otherwise, I'll change download the .dsc and modify
[07:29] <Trevinho> didrocks: maybe just land that and then build a new src package on top of it and push it too?
[07:29] <didrocks> Trevinho: don't really have time IMHO, today is final freeze
[07:29] <didrocks> let me merge your branches manually
[07:29] <didrocks> and add a change on top
[07:29] <Trevinho> didrocks:  ok
[07:29] <Trevinho> didrocks: otherwise it's just about adding a new branch based on the bileto branch, MP it and add to the ticket
[07:29] <Trevinho> didrocks: but as you prefer..
[07:30] <Trevinho> you do the change, you choose how
[07:30] <didrocks> yeah, let me do the manual way and focus on the crash :)
[07:30] <didrocks> good work on the theme :)
[07:36] <seb128> didrocks, did you keep up with the fallback session discussion? Olivier is off today, he tried to end up as many options/explanations as possible yesterday evening so we have something we can act on today
[07:37] <didrocks> seb128: no, I only did from the edge, his proposal sounds reasonable to me, but anyway, that could be a SRU, correct?
[07:37] <didrocks> it needs testing IMHO with the various edge cases
[07:39] <seb128> didrocks, I guess, it just means we are going to get some confused upgraders until the SRU is validated/moved to -updates, but that's not the end of the world
[07:40] <andyrock> seb128: just changing scaling from 2x to 1x
[07:40] <didrocks> seb128: well, it's not in the list :p
[07:40] <andyrock> you need to apply the change
[07:41] <andyrock> maybe it's triggered just if you have hidpi screen
[07:41] <seb128> didrocks, I see what you are doing there :p
[07:41] <didrocks> seb128: :p more honestly, I would like it to be battle tested
[07:41] <didrocks> seb128: what olivier wrote makes sense
[07:41] <didrocks> but there are many use case, wayland enabled, wayland disabled and reenabled
[07:41] <didrocks> and vice-versa
[07:42] <seb128> right
[07:42] <seb128> well SRU wfm
[07:42] <didrocks> that's why I'm a little bit vary rushing it right now
[07:42] <didrocks> is olivier back tomorrow?
[07:42] <seb128> yes
[07:42] <didrocks> ok, maybe we can iterate with him on this tomorrow
[07:42] <seb128> today is just an holiday in Spain
[07:42] <didrocks> and prepare it for day 0
[07:42] <seb128> right
[07:50] <jibel> Trevinho, hi, I just filed bug 1723025
[07:50] <Trevinho> no stacktrace?
[07:50] <jibel> Trevinho, is there a tag for multimonitor bugs?
[07:51] <jibel> Trevinho, no
[07:51] <seb128> jibel, hey
[07:51] <seb128> jibel, how do you set your laptop to disable the internal panel at boot?
[07:52] <jibel> seb128, in g-c-c then reboot and it uses only the external monitor
[07:52] <jibel> i'll try with another laptop
[07:52] <jibel> there is a udisk crash not sure it's related
[07:52] <seb128> probably not, do you have the bug number or e.u.c bucket?
[07:53] <jibel> not uploaded yet
[07:53] <seb128> jibel, user config changes screen changes don't apply to the greeter do they?
[07:54] <jibel> seb128, https://errors.ubuntu.com/oops/7e4d40ca-af22-11e7-9f83-fa163eec78fa
[07:54] <jibel> seb128, they should not. That's what I want to check on another latop
[07:54] <jibel> laptop*
[07:55] <seb128> I don't see that problem here btw
[07:55] <jibel> meh, problem failed to retrace
[07:55] <seb128> both screens are enabled in gdm despite me turning the laptop one off in my session
[07:55] <seb128> jibel, can you share the .crash maybe?
[07:56] <andyrock> jibel:  you need to manually start apport to get the crash
[07:57] <seb128> andyrock, apport fix got uploaded btw
[07:57] <andyrock> nice
[07:57] <jibel> seb128, http://people.canonical.com/~j-lallement/junk/_usr_lib_udisks2_udisksd.0.crash
[07:57] <alexarnaud> good morning seb128 didrocks jbicha and all
[07:57] <seb128> hey alexarnaud
[07:57] <didrocks> hey alexarnaud
[07:57] <jibel> andyrock, I usually use whoopsie-upload all so they go to errors.u.c
[07:58] <jibel> whoopsie-upload-all*
[07:58] <andyrock> I can ask my guys to debug the crash I was working on
[07:59] <seb128> andyrock, you have a team working for you now? ;-)
[08:00] <didrocks> that was the trick!
[08:01] <andyrock> seb128: 😎
[08:01] <andyrock> not sure you can get the emoticons
[08:01] <didrocks> this offending one? :p
[08:02] <seb128> I                                                                                                                                                         see one
[08:02] <jibel> seb128, it could be machine specific. On another machine it boots from the internal display then switches to the external
[08:03] <seb128> still weird, I would expect both to be on when on the login screen
[08:11] <jibel> on another machine the login screen is on the internal display and the external is all purple. And the boot messages are on the internal while the go to the external display on the other one.
[08:11] <jibel> Still when the graphical session starts it should turn the internal display on
[08:12] <didrocks> the login screen is on the primary display only IIRC
[08:13] <didrocks> then, I'm unsure how this is defined for the gdm user
[08:13] <andyrock> yeah unity-greeter was smarter
[08:13] <andyrock> following the pointer
[08:13] <didrocks> that, same with notifications and osd…
[08:13] <didrocks> I guess we'll need to look at that next cycle
[08:14] <jibel> yeah but i've a machine that decides that if an external display is connected it's the primary display and disable the internal display. Then in gdm the internal display stays off
[08:14] <seb128> jibel, your udisks crash matches bug #1707451 ... can you reproduce? do you know what you did to trigger it?
[08:15] <jibel> seb128, I really don't know, i noticed the crash file when I was looking for something else
[08:15] <seb128> k
[08:15] <seb128> well the bt is not very informative
[08:15] <seb128> I upstreamed it a few days ago anyway
[08:16] <seb128> but they didn't comment on the issue yet
[08:24] <doko> please could you walk over the list of ftbfs (main) for the last test rebuild and see what can to be fixed?  http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20170922-artful.html and http://qa.ubuntuwire.org/ftbfs/
[08:36] <seb128> doko, we can have a look
[09:44] <andyrock> a random guy just told me than Linux Mint is better than Ubuntu
[10:48] <ricotz> chrisccoulson, hi, any chance for some responses?
[11:03] <ricotz> chrisccoulson, so once more, please take a look at binutils and llvm-5.0 packages here: https://launchpad.net/~ricotz/+archive/ubuntu/mozilla/+packages which would be appropriate to use for rustc 1.20.0
[11:10] <seb128> ricotz, hey, what responses are you waiting for?
[11:10] <seb128> ricotz, you might want to ask questions on the channel to increase the chances that somebody replies?
[11:12] <ricotz> seb128, any kind of response
[11:12] <seb128> to what question?
[11:12] <ricotz> already pinged do_ko about the binutils fixes for llvm-5.0 backports
[11:13] <ricotz> seb128, sorry, what do you expect me say?
[11:14] <ricotz> seb128, aleady mentioned it to  t_jaalton who needs it for mesa backports but only for xenial
[11:26] <seb128> ricotz, I'm trying to understand what you are asking for to see if I can help you
[11:26] <seb128> ricotz, it might help if you opened bugs describing the things you need/are trying to push
[11:27] <seb128> so we can assign/track them properly and give you feedback
[11:27]  * didrocks goes for a late run
[11:28] <ricotz> seb128, this is how providing bug reports work out: https://bugs.launchpad.net/ubuntu/+source/rustc/+bug/1701556
[11:28] <seb128> didrocks, enjoy!
[11:29] <ricotz> seb128, there is nothing tracking rust/llvm backports, just chris pushing packages without notice to ppas
[11:29] <didrocks> seb128: thx :)
[11:30] <seb128> ricotz, right, that bug didn't get much attention
[11:30] <seb128> we can try to improve things
[11:30] <ricotz> and while trying to help out with prepared backports I don't get any response for a week
[11:30] <seb128> ricotz, who/what list should be notified and stating what in your opinion?
[11:31] <seb128> ricotz, well, maybe Chris doesn't need/want help and is just getting those done
[11:31] <seb128> ricotz, if that's the case you might want to let him deal with them and focus on something else?
[11:31] <ricotz> seb128, as said already pinged do_ko (no response), chris (no response), tja_lton answer and happily to the binutils fix
[11:32] <ricotz> to/took
[11:32] <seb128> well, people are busy and do what they can usually
[11:32] <ricotz> seb128, chris is constantly saying he is short in time, and it took him weeks for rustc 1.19 while it was already required
[11:32] <seb128> they could be a bit nicer in giving status updates though agreed
[11:33] <seb128> ricotz, right, that's a problem we are trying to resolve by finding extra resources to be allocated to that stack
[11:33] <ricotz> so I guess help is needed, but without any communication from his side is a pita
[11:33] <seb128> Olivier is going to help on the firefox updates
[11:34] <seb128> well, you can't really force people
[11:34] <ricotz> I know about olivier, but rustc/cargo/llvm is unassigned afaik
[11:34] <seb128> right, we asked for resourcing for that stack
[11:34] <seb128> we didn't hear back yet afaik
[11:35] <ricotz> it is not about forcing, a simple response like "ok" would be already something
[11:35] <seb128> ricotz, if you don't get the replies you want from Chris maybe it's just that co-working with him on the same things doesn't work out well and then you should accept it and focus on something else while he's getting the things he's doing done?
[11:37] <ricotz> seb128, I am preparing the firefox-trunk and firefox beta package which require those new stacks way ealier, and chris takes those changes for the mozilla releases which works for months
[11:38] <ricotz> so the co-working is already in place, but communication is painful
[11:38] <seb128> I see that
[11:39] <seb128> maybe lower your expectation
[11:39] <seb128> do your bigs in the ppa for the trunk/beta build
[11:39] <seb128> and let him sort out what he wants to for the stable updates
[11:40] <ricotz> it is more complicated than that, and would actually result in waste of efforts
[11:40] <ricotz> (a new stack is required like 4 months ahead)
[11:41] <seb128> well seems you are ahead of him
[11:41] <seb128> who would waste efforts?
[11:41] <ricotz> regarding expectations, I seems expecting like a 10 mins talk a week is too much already
[11:42] <ricotz> seb128, I don't have access to powerpc/s390x builders which are required for proper backports which chris made clear in the past
[11:42] <seb128> if you need regular updates and ad-hock IRC pings don't work maybe a status update meeting bi-weekly with the people working on those stacks would be useful?
[11:43] <ricotz> seb128, it is basically only chris working on them
[11:44] <ricotz> the involvement of mesa's need for llvm-5.0 is special and the required fix for binutils too
[11:44] <seb128> ricotz, well sorry it's frustrating, hopefully we find soon some more resourcing and things improve
[11:46] <ricotz> seb128, basically I am advertising done-things to avoid duplicating efforts, but getting no response it hard to bear
[11:47] <chrisccoulson> ricotz, thanks for preparing llvm-5.0. I noticed you added it as a dependency for firefox nightly, but it's not required for that yet (rust-bindgen works with 3.9, and that is what upstream are using)
[11:47] <chrisccoulson> what's binutils for?
[11:48] <ricotz> chrisccoulson, it is better to switch to llvm5 since this is basically targets 58
[11:48] <chrisccoulson> note, there's a chance that we'll switch our rust package to rust's bundled fork of llvm
[11:48] <ricotz> binutils includes a arm64 patch to fix ftbfs of llvm5
[11:49] <chrisccoulson> ricotz, please don't bump the dependency unnecessarily. I have to justify everything I copy to the -security pocket, and I can't just copy a llvm package because we felt like bumping the dependency for no reason
[11:49] <chrisccoulson> upstream is using 3.9 for generating the stylo bindings, and AFAICT there's no immediate plan to change that
[11:50] <ricotz> chrisccoulson, the mesa hwe backport for xenial will already need llvm55
[11:50] <chrisccoulson> yes, but that's still not a good reason for diverging even further from upstream. They don't test this with llvm5, and if there are any problems with it then it's unlikely we'll get help to fix it
[11:51] <ricotz> chrisccoulson, ok, the servo people kind of suggested to try a newer llvm too though, while its i386 build fails on ff57/58
[11:52] <chrisccoulson> the i386 issue is nothing to do with llvm, and there's a fix for that alreadyu
[11:52] <chrisccoulson> https://bugzilla.mozilla.org/show_bug.cgi?id=1406952
[11:53] <ricotz> chrisccoulson, I see, hmm, thanks for letting me know (now)
[11:54] <chrisccoulson> basically there's an ABI mismatch between the llvm API and the rust bindings on x86 related to the differences in how integral values and structs are returned
[11:54] <ricotz> chrisccoulson, why is it not possible for you to e.g. CC me?
[11:54] <chrisccoulson> do you have a bugzilla account?
[11:54] <ricotz> yes
[11:54] <ricotz> a ping on IRC would have suffice too
[11:55] <chrisccoulson> so, about llvm...
[11:55] <chrisccoulson> we discussed at the rally about using the bundled llvm in our rust package, if it reduces the amount of work required to update it. I'm not sure about that yet
[11:56] <ricotz> please PM to avoid hijacking the channel, I need to go for a moment
[11:56] <chrisccoulson> but the update to 1.20 is suggesting it probably would be less work (all of the issues I'm hitting so far are because of patches missing in our llvm package that are in upstream's fork)
[11:56] <chrisccoulson> I'd prefer to talk in the channel, particularly because oSoMoN will care about this stuff too :)
[11:57] <chrisccoulson> although he doesn't appear to be around atm
[11:58] <seb128> he's off today indeed
[11:59] <chrisccoulson> ricotz, who upstream suggested upgrading llvm for the i386 issue btw?
[11:59] <seb128> but other might be interested (I am slightly)
[11:59] <chrisccoulson> seb128, congratulations, you just volunteered to maintain rust!
[12:01] <ricotz> chrisccoulson, emilio suggested they had problems in servo with older llvm which are suppose to be fixed in later versions
[12:02] <chrisccoulson> ricotz, oh, it was emilio that helped with this. I'm a bit surprised about that, considering this was an issue they were aware of (another rust module had the same bug) :(
[12:04] <ricotz> chrisccoulson, I mentioned https://github.com/servo/servo/issues/17869#issuecomment-318136585
[12:06] <chrisccoulson> so, the other issue was https://github.com/rust-lang-nursery/rust-bindgen/issues/439 (our bug is in the clang-sys crate)
[12:07] <chrisccoulson> anyway, https://github.com/KyleMayes/clang-sys/commit/773c5468811b1a2c13dfd777ef25a13a616a3b9d.patch will fix it (I verified against a mozilla-beta checkout locally)
[12:08] <ricotz> alright
[12:08] <chrisccoulson> ricotz, do you subscribe to https://lists.mozilla.org/listinfo/dev-platform ?
[12:08] <ricotz> no
[12:09] <chrisccoulson> ah, so, about language packs - https://groups.google.com/forum/#!topic/mozilla.dev.platform/xLaNdk7fPgI
[12:09] <chrisccoulson> (please don't switch until upstream do that though)
[12:09] <chrisccoulson> oh, it suggests this week actually
[12:10] <ricotz> chrisccoulson, I talked to gandalf about its state some weeks ago
[12:10] <chrisccoulson> cool
[12:10] <chrisccoulson> anyway, I need to grab some lunch
[12:10] <ricotz> and I guess you noticed the patch in firefox branch
[12:16] <willcooke> hi all
[13:09] <willcooke> jibel, around?
[13:10] <willcooke> kirkland is upgrading his machine from x to a, and getting gconf2 errors - anyone know what's causing that
[13:15] <seb128> willcooke, what sort of errors?
[13:16] <seb128> did that stop the upgrade? or just warnings?
[13:16] <jibel> willcooke, yes
[13:20] <willcooke> laney is here to save the day :)
[13:20] <willcooke> doesn't look like it was too bad actually
[13:20] <jibel> willcooke, also the content of /var/log/dist-ugprade once the upgrade is done (successful or not) would be useful
[13:21] <willcooke> jibel, ack
[13:21] <seb128> willcooke, what was it? I'm curious now :p
[13:22] <jibel> willcooke, and a bug report too please
[13:24] <jibel> willcooke, BTW how did he upgrade? s/xenial/artful/ in sources.list?
[13:25] <willcooke> yeah
[13:31] <willcooke> laney fixed it.  Wasn't very broken after all
[13:31] <Guest96778> didn't see the initial error
[13:31] <Guest96778> WHAT
[13:31] <Guest96778> ISTHIS
[13:31] <Guest96778> FFS
[13:32] <willcooke> Hi LANEY!!!
[13:32] <seb128> is that something we need to SRU/which is making upgrades fail?
[13:33] <Laney> we'll find out
[13:33] <Laney> xenial to artful upgrades aren't going to be offered until zesty goes out of support
[13:33] <Laney> so no fire imho
[13:34] <seb128> right
[13:34] <jibel> yeah, we'll enable lts to lts tests when bb opens and we'll see
[13:34] <seb128> hey Laney btw :)
[13:34] <Laney> what up
[13:35] <seb128> it's freeze day and still fixing bugs!
[13:40] <seb128> brb changing location
[13:41] <Laney> bugs buggy bugs bugs
[13:43] <willcooke> didrocks, kirkland has a problem with byobu, when you click it on it on the launcher icon for it, it opens gnome terminal and adds a new icon to the launcher with a "broken" icon
[13:43] <willcooke> is there some .desktop file magic required?
[13:44] <kenvandine> bb == buggy bug?  let's hope not :)
[13:45] <Laney> hey kenvandine
[13:45] <kenvandine> hey Laney
[13:46] <Laney> what's going on
[13:46] <kenvandine> snaps snap snapcraft!
[13:47]  * kenvandine tries to remember what that shirt says
[13:47] <ogra_> schnaps!
[13:47] <kenvandine> and failed
[13:47] <kenvandine> lol
[13:48] <Laney> ich bin schnappi
[13:57] <chrisccoulson> yay, my rust PPA is out of space
[13:59] <seb128> :-/
[14:04] <didrocks> willcooke: I think GNOME-shell doesn't have the same WMClass magic as we had with Unity
[14:05] <didrocks> willcooke: I think he can wrap byobu to something similar than I've done for my weechat icon
[14:05] <didrocks> http://paste.ubuntu.com/25726481/
[14:06] <didrocks> willcooke: the --profile= isn't mandatory, it's just me using this to have different background color and such
[14:06] <didrocks> here, the machine works
[14:06] <willcooke> nice one, thanks didrocks
[14:06] <didrocks> matching*
[14:06] <didrocks> keep me posted
[14:24]  * didrocks doesn't follow, asking on https://twitter.com/hergertme/status/918239692729880576
[14:25] <seb128> no bug report on launchpad either
[14:27] <seb128> jbicha, we should probably remove those gnome-screenshot actions, I just noticed that one is not displayed translated due to meson and dh_translations not working...also even if you disable it launchpad is going to have the translations since those are sharing between series so the day we add it back we get the translations from xenial without having to redo the work
[14:29] <jbicha> GunnarHj: it's a bit confusing but I don't think we are supposed to ship gnome-user-docs 3.26.1 but wait for 3.26.1.1 https://wiki.gnome.org/DocumentationProject/Tasks/ReleaseSchedule
[14:30] <jbicha> https://mail.gnome.org/archives/gnome-doc-list/2017-October/msg00009.html
[14:31] <jbicha> seb128: so you want me to disable the 2 of 3 broken Actions for now?
[14:31] <seb128> jbicha, I would +1 that yes
[14:34] <didrocks> +1 as well on this
[14:43] <jbicha> GunnarHj: it's been accepted now so see LP: #1723138
[14:48] <GunnarHj> jbicha: Waiting till 3.26.1.1 was my first thought, but then I noticed that the content changes in 3.26.1 are minimal and that it includes some translation updates, so I assumed that it's not a worsening wrt translations. Do you think otherwise?
[14:49] <jbicha> GunnarHj: I leave that decision to you, remove the tag if you want it to migrate :)
[14:49] <GunnarHj> jbicha: How do I do that?
[14:50] <GunnarHj> jbicha: Or is it just the tag on the bug report?
[14:50] <jbicha> just remove the block-proposed tag on the bug report
[14:50] <GunnarHj> jbicha: Ok, thanks.
[15:03] <jbicha> seb128: could you push your NM packaging to https://code.launchpad.net/~network-manager/network-manager/+git/ubuntu/+ref/artful
[15:10] <GunnarHj> jbicha: Since we have detached the docs packages from the langpacks, it's easy to update as SRUs if and when we find it motivated.
[15:52] <seb128> jbicha, is there documentation on how to do that?
[21:05] <Gorian> question: how many people here would be interested in a script that automatically installs Ubuntu on top of a root ZFS pool for you?
[21:06] <sarnold> I know there'd be some interest in such a thing, but the long-term consequences of doing so seem less clear to me -- what will future do-release-upgrades do and so on? so I'd rather see zfs on root support 'natively', where future package upgrades take that configuration in mind
[21:14] <Gorian> Oh, definitely
[21:14] <Gorian> just wondering, as it's my current project. I have a number of servers that are using Ubuntu + ZFS NOW and i'm automating it
[21:14] <Gorian> The beginning of my refactor: https://pastebin.com/uuNUtgpC
[21:15] <sarnold> oo pretty colours ;)
[21:15] <Gorian> quick and dirty, but works for systems with BIOS https://pastebin.com/rxgSGFj3
[21:15] <Gorian> refactor is much cleaner code, better argument parsing, will support BIOS AND UEFI, etc.
[21:15] <Gorian> only works for 16.04+ so I can code for a high bash minimum version
[21:16] <Gorian> old scripts ONLY work with a ZFS mirror, new code will let you specify what RAID level you want, etc.
[21:16] <sarnold> root on raidz??
[21:16] <Gorian> if you want *shrugs*
[21:16] <Gorian> my servers are doing a mirrored root, and my desktop is doing RAID1 0
[21:16] <Gorian> *10
[21:16] <sarnold> wow :) I didn't know tha was even an option, hehe
[21:17] <sarnold> i'm mirrors all around but there's folks who'd love the raidz options
[21:17] <Gorian> yeah
[21:17] <Gorian> taking forever to do it all the "right" way though, and it's hard to test the code atm
[21:17] <Gorian> in the building of rebuilding the box I can virtualize on :p
[21:18] <Gorian> feel free to critique the code though, it's never perfect
[21:18] <Gorian> also, I know about my horrible habit of printing or catting everything into pipes them grepping, comes from lots of years of catting things, then doing something like pressing up and adding a new pipe rather than rewriting :p