[06:27] <lazyPower> stub: http://bazaar.launchpad.net/~lazypower/charms/bundles/sentiment-analysis/bundle/view/head:/bundles.yaml
[06:35] <jcastro_> tvansteenburgh, can we kick off tests for this? http://review.juju.solutions/review/1087
[06:36] <jcastro_> I tried to click the button but it didn't do anything for me
[06:36] <jcastro_> robert would like to test his latest pushes
[06:37] <tvansteenburgh> jcastro: kicked
[07:38] <jcastro_> bcsaller, https://askubuntu.com/questions/611564/how-does-juju-get-the-private-address-of-a-node
[07:59] <mbruzek> jamespage Please send me a link to the actions document.
[08:15] <Bardhi> Hello everyone. I am new with juju and maas and im trying to get that installed and running in our company. I managed to get installed maas and juju, but when i want to deploy a service with juju it gets stucked in "allocating units" and it doesnt advance from there. It remains yellow it doesnt become green. If someone could help me how to solve this i wold appreciate it. Thank you
[09:15] <mwak> hi
[09:20] <ludvigx> anyone got a sec to help me out ? Trying to deploy the latests trusty/ceph-36 via juju, and it returns a agent-state-info: 'hook failed: "mon-relation-changed"' every single time.
[09:21] <ludvigx> or is this more just a ceph related question ? not sure :)
[09:34] <lazyPower> cory_fu: another fyi re: sync-watch - i'm getting consistent errors when watching subordinates
[09:47] <lazyPower> https://github.com/juju/plugins/issues/56
[09:53] <Bardhi|2> ello i am trying to deploy some services with juju but it gets stucked on allocating units and services are not deployed. i just started using juju and i am not an expert in using it and i dont know very well how it all works but i
[09:58] <g3naro> hello! is anyone here able to help noob
[09:59] <g3naro> root@falcon:~/.juju# juju deploy apache
[09:59] <g3naro> ERROR environment is not bootstrapped
[10:04] <hazmat> lazyPower: any presentation deck you recommend for giving a presentation on juju?
[10:07] <lazyPower> hazmat: i do, 1 sec
[10:07] <lazyPower> do you want the raw deck, pdf, or speakerdeck link?
[10:07] <lazyPower> hazmat: https://speakerdeck.com/chuckbutler/service-orchestration-with-juju
[10:08] <hazmat> lazyPower: looking, thanks
[10:10] <hazmat> lazyPower: that looks solid, thanks
[10:10] <hazmat> i'm giving a presentation on juju in a few hrs, and my decks are moldy ;-)
[10:12] <lazyPower> :) want the .odp file to make tweaks?
[10:12] <hazmat> lazyPower: that would be great
[10:12] <lazyPower> hazmat: the biggest change is juju is the modelling language, and not "the orchestrator" - we're enabling orchestration through the language model
[10:13] <lazyPower> https://www.dropbox.com/s/cvh31c2vrjbsrgm/service-orchestration.odp?dl=0
[10:13] <lazyPower> hazmat: ^
[10:13] <hazmat> g3naro: you have to bootstrap an environment before deploying
[10:14] <hazmat> lazyPower: that distinction seems subtle, so juju is not an orchestrator but a language runtime for orchestrator?
[10:14] <lazyPower> yeah, basically its a universal language to describe your infra as SOA
[10:24] <cory_fu> lazyPower: You and your damned subordinates.  ;)  Thanks for opening the issue
[10:25] <lazyPower> :3
[10:25] <cory_fu> marcoceppi: Where was that tool you showed for rendering a bundle svg?
[10:25] <marcoceppi> cory_fu: svg.juju.solutions
[10:26] <cory_fu> Hrm.  No form?  How do you post the bundle?
[10:26] <lazyPower> (۶ૈ ᵒ̌ Дᵒ̌)۶ૈ=͟͟͞͞ ⌨  GIVE US THE KNOWLEDGE MARCO
[10:27] <marcoceppi> cory_fu: read the instructions?
[10:27] <cory_fu> It says post, but there's no form to post
[10:27] <cory_fu> What am I, a wizard?
[10:27] <marcoceppi> yes, use HTTP to post to it
[10:27] <marcoceppi> or http://svg.juju.solutions/?bundle-file=http://bazaar.launchpad.net/~bigdata-dev/charms/trusty/apache-analytics-sql-hue/trunk/download/head:/bundles.yaml-20150420030716-vycsb0pcenhst8wt-1/bundles.yaml
[10:27] <marcoceppi> cory_fu: I thought you knew kung fu
[10:27] <marcoceppi> cory_fu: or http://svg.juju.solutions/?bundle=cs:bundle/openstack-telemetry-31
[10:28] <marcoceppi> https://github.com/marcoceppi/svg.juju.solutions
[10:28] <marcoceppi> no instructions, sorry, forgot I didn't write them yet
[10:28] <marcoceppi> still a WIP
[10:28] <cory_fu> Fair enough
[10:29] <marcoceppi> cory_fu: I'll be adding caching and faster processing (plus embedding SVG so it downloads more cleanly) soon
[10:31] <rogpeppe> jam: hiya
[10:31] <jam> rogpeppe: /wave
[10:32] <rogpeppe> jam: just wanted to give you a head's up regarding some changes we intend to make to the juju/charm repo
[10:32] <jam> sure, what's up?
[10:32] <rogpeppe> jam: we've had some cyclic dependency issues between the charm repo and charmstore
[10:32] <rogpeppe> jam: i made a little doc to explain things to ourselves: https://docs.google.com/document/d/10Ol5g2T688fih2wBTDk6ZO5h2I8dXjVI3hWTSpMaUew/edit
[10:33] <rogpeppe> jam: after some discussion, we've decided that solution 3 is the best way forward
[10:34] <rogpeppe> jam: YMMV so any feedback would be good
[10:35] <rogpeppe> jam: essentially this means moving the charmrepo package into a new repository. for juju-core, the implication should just be a simple import path rewrite with no other code changes required
[10:36] <jam> rogpeppe: what is "publicly depends on" vs "depends on" ?
[10:36] <jam> (it has a public API that uses a type defined in the other repo?)
[10:36] <rogpeppe> jam: yes
[10:36] <rogpeppe> jam: you said it much more neatly than i was trying to :)
[10:38] <rogpeppe> jam: this is also a possible precedent for a pattern that we might use more generally and eventually something that might be worthwhile for juju-core to use (so that juju Go clients don't have to incur all juju-core's dependencies)
[10:39] <jam> rogpeppe: so I'd like to understand why cycles in tests is ok
[10:39] <jam> because you have to set up the underlying objects to test against?
[10:40] <rogpeppe> jam: because it's possible to make forward progress even when there are cycles in tests
[10:40] <rogpeppe> jam: in the worst case, you might need to temporarily disable some tests
[10:41] <rogpeppe> jam: whereas in the situation we were in (with cycles in exported APIs) we literally couldn't make forward progress without some really nasty hackery (including charm.v6 needing to import charm.v5 in tests)
[10:41] <jam> rogpeppe: so its not *actually* possible to upgrade a version and have all the tests pass
[10:42] <rogpeppe> jam: it should be in most cases
[10:42] <rogpeppe> jam: you'll end up with the tests importing two versions of the package, but that is usually ok
[10:43] <jam> So charmstore is the actual server internals code, csclient is a consumer of the public API, what is charmrepo ?
[10:43] <jam> "charm" is the core data structure, right?
[10:44] <rogpeppe> jam: charmrepo is the API that juju uses, that layers onto csclient
[10:44] <rogpeppe> jam: yeah
[10:44] <rogpeppe> jam: charmrepo implements local repository handling too
[10:45] <jam> and params is shared implementation of types exported and imported between the server and clients?
[10:45] <rogpeppe> jam: charmrepo already exists, BTW: http://godoc.org/gopkg.in/juju/charm.v5/charmrepo
[10:45] <rogpeppe> jam: yes
[10:45] <rogpeppe> jam: similar to juju-core's params package
[10:49] <rogpeppe> jam: ha, this probably isn't the right channel for this discussion - i had intended #juju-dev
[10:55] <philip_stoev> Hello, how does one deploy a charm using uncommitted changes in a local bzr repository?
[10:55] <philip_stoev> I am using this command:
[10:55] <philip_stoev>  juju deploy --repository=. --config galera.yaml local:trusty/galera-cluster
[10:55] <philip_stoev> and the charm being deployed does not contain the local uncommitted changes
[11:08] <rogpeppe> philip_stoev: AFAIK the juju deploy command doesn't know about the bzr repo at all
[11:08] <rogpeppe> philip_stoev: so it should just see all the files as they are (including uncommitted changes)
[11:09] <rogpeppe> philip_stoev: what does it do if you try to deploy the charm when there's no .bzr directory at all (for instance, move it out of the way or make a copy of the charm dir without it) ?
[11:09] <rogpeppe> philip_stoev: it's possible that this is an existing bug with juju deploy with respect to local charms actually
[11:10] <rogpeppe> philip_stoev: have you already previously deployed that charm to the environment?
[11:10] <philip_stoev> I found out that it is safer to destroy the environment every time. Otherwise it seems I am always getting a cached version of the charm
[11:11] <philip_stoev> Actually committing to the local repository did not help
[11:12] <philip_stoev> so, with a fresh environment
[11:12] <philip_stoev> I am still getting files from the Charm Store
[11:12] <philip_stoev> Even though I provided  --repository=. local:trusty/galera-cluster to juju deploy
[11:13] <philip_stoev> Does juju have some local cache that I need to purge?
[11:14] <philip_stoev> I have no ~/.juju/charmcache on the local machine
[11:17] <philip_stoev> --upgrade has been deprecated
[11:17] <philip_stoev> so what is left apart from committing every revision to the charm store?
[11:22] <rogpeppe> philip_stoev: i think the problem is the revision number of the local charm
[11:23] <rogpeppe> philip_stoev: i encountered this problem with gocharm, and worked around it
[11:23] <philip_stoev> I think I got what the problem is, for some reason I had multiple copies of the charm locally, so --repository=. was picking the wrong directory
[11:23] <rogpeppe> philip_stoev: if you create a "revision" file and increase the revision number in it each time, it may fix your issue
[11:23] <philip_stoev> thanks
[11:24] <rogpeppe> philip_stoev: ah, that can also be a problem
[11:24] <rogpeppe> philip_stoev: the local repository logic is weird
[11:24] <rogpeppe> philip_stoev: it ignores the name of the directory and just looks at the charm name in the metadata.yaml
[11:25] <rogpeppe> philip_stoev: and then takes the one with the highest revision, or the last alphabetically by directory name
[11:25] <philip_stoev> I was able to make it pick up the right files ...
[11:25] <philip_stoev> so I am good
[11:25] <rogpeppe> philip_stoev: cool
[11:25] <philip_stoev> thanks for the help
[11:26] <philip_stoev> I have a more conceptual question regarding Juju
[11:27] <philip_stoev> Assuming I have started a service, e.g. MySQL , is it a strict juju requirement for other services to connect to it only through juju relations and interfaces?
[11:28] <philip_stoev> If not, then it seems it is difficult for the user to simply obtain the IP of the service and then use that IP as needed
[11:28] <philip_stoev> juju status seems to be the easiest way
[11:28] <philip_stoev> as it is difficult to have juju create a database and spit out the complete connection URL
[11:28] <philip_stoev> unlesss relations are used
[13:18] <lukasa_work> Is there any way I can force Juju to run a hook?
[13:18] <lukasa_work> neutron-api seems to have rendered an incorrect neutron.conf, and I'd like it to re-render
[13:25] <cory_fu> lukasa_work: Easiest way would be to change and reset a config value.  If you don't want to do that, you *might* be able to manually run the config-changed hook using `juju run`
[13:26] <cory_fu> But I'm not at all certain that won't cause you more issues
[13:26] <cory_fu> It depends heavily on how the charm is implemented.
[13:47] <plars> So I got python-jujuclient upgraded and now juju-deployer tries to run at least, but I'm hitting this now. Any ideas?
[13:47] <plars> https://www.irccloud.com/pastebin/VUvzEJIo
[14:55] <g3naro> juju deploy apache
[14:55] <g3naro> ERROR cannot resolve charm URL: "cs:apache"
[14:55] <g3naro> any ideas?
[14:55] <lukasa_work> The charm is called apache2. =)
[14:55] <g3naro> ohhh
[14:55] <g3naro> :D
[14:56] <g3naro> what what!! first lxc-local deployed
[14:58] <jcastro_> g3naro, \o/
[15:18] <g3naro> but what is the defualt user/pass :(
[15:22] <roadmr> g3naro: use juju authorised-keys to add an ssh key to your containers, then you can ssh into them, no need to use user/password
[15:22] <roadmr> g3naro: https://jujucharms.com/docs/stable/howto-authorised-keys
[15:33] <g3naro> roadmr, thanks! looking now
[15:34] <g3naro> i found in .juju/environments/local.jenv
[15:34] <g3naro> it has correct ssh key but still giving me denied
[15:35] <roadmr> g3naro: how are you doing ssh into the container?
[15:40] <g3naro> ssh -i ssh -i juju_id_rsa.pub<EMAIL_ADDRESS>[15:40] <g3naro> also without the juju@
[15:40] <g3naro> anhd without .pub of course
[15:41] <g3naro> ssh -i juju_id_rsa <IP_ADDRESS>
[15:41] <g3naro> ohh its ubuntu@
[15:41] <g3naro> what hwat :D
[15:42] <jrwren> juju ssh is your friend :)
[15:42] <g3naro> juju ssh ?
[15:43] <g3naro> oh leet
[15:43] <g3naro> is anyone running juju for prod
[15:43] <stub> tvansteenburgh: I will need to add Adam's actions in a separate branch, as it needs to be taught how to connect to a cluster with authentication enabled.
[16:32] <tvansteenburgh> stub: ack
[17:32] <Aligner> Hi, if I upgrade charms with juju upgrade-charm, do I need to redeploy everything for the upgraded version to take affect?  I am trying to upgrade some charms but I can't tell if the applications are newer version


[01:00] <callmepk> good morning
[01:29] <duflu> Morning callmepk
[01:30] <callmepk> morning duflu
[03:18] <handsome_feng> Oh,  I think I missed something
[05:50] <didrocks> good morning
[05:50] <Maik> good morning all
[06:01] <oSoMoN> good morning desktoppers
[06:04] <Maik> good morning oSoMoN
[06:05] <handsome_feng> oSoMoN: Good morning, and sorry for the delay, there are some internet problems here lately and the email server is down, so I didn't login ircclound and no emails were received.
[06:07] <didrocks> hey oSoMoN
[06:21] <handsome_feng> I used heroku to keep my account online, but I can only see these messages if I'm actually logged in.
[06:25] <oSoMoN> handsome_feng, no worries, and thanks for merging!
[06:25] <oSoMoN> hey Maik, didrocks
[06:25] <Maik> o/
[06:25] <Maik> :)
[06:27] <handsome_feng> :)
[07:01] <marcustomlinson> morning callmepk duflu didrocks oSoMoN Maik
[07:02] <Maik> marcustomlinson: hey :)
[07:07] <didrocks> hey marcustomlinson
[07:16] <callmepk> hey marcustomlinson didrocks oSoMoN Maik
[07:16] <Maik> heya callmepk
[07:17] <didrocks> hey callmepk
[07:43] <seb128> goood morning desktopers
[07:44] <oSoMoN> good morning marcustomlinson, callmepk, seb128
[07:45] <seb128> lut oSoMoN , comment ça va ?
[07:45] <marcustomlinson> hey seb128
[07:45] <seb128> hey marcustomlinson, how are you?
[07:46] <marcustomlinson> seb128: well thanks, you?
[07:47] <oSoMoN> seb128, bien, et toi?
[08:04] <Laney> yo
[08:06] <jibel> hi all
[08:08] <Laney> moin jibel
[08:08] <Laney> how's it going?
[08:16] <marcustomlinson> hey Laney
[08:18] <KGB-0> gnome-shell-extensions pristine-tar 0fc1f2f Simon McVittie gnome-shell-extensions_3.38.0.orig.tar.xz.delta gnome-shell-extensions_3.38.0.orig.tar.xz.id * pristine-tar data for gnome-shell-extensions_3.38.0.orig.tar.xz * https://deb.li/3HTtM
[08:18] <KGB-0> gnome-shell-extensions upstream/latest 8957c27 Simon McVittie * pushed 15 commits * https://deb.li/VG6y
[08:18] <KGB-0> gnome-shell-extensions tags b7310de Simon McVittie upstream/3.38.0 * Upstream version 3.38.0 * https://deb.li/3TkI4
[08:23] <oSoMoN> hey Laney, jibel
[08:23] <jibel> Hey Laney oSoMoN
[08:25] <didrocks> hey hey Laney, seb128 :)
[08:36] <seb128> lut diddledan
[08:36] <seb128> ups
[08:36] <seb128> lut didrocks
[08:36] <seb128> & jibel
[08:38] <seb128> oSoMoN, marcustomlinson , sorry I context switched and forgot to reply, I'm slightly better but still not great, that cold is no fun, I lost my voice during the w.e and it's still not fully back, at least I start feeling I'm the recovery path, nose is unblocked now
[08:38] <seb128> hey Laney
[08:39] <Laney> hey oSoMoN didrocks seb128!
[08:44] <jibel> salut seb128
[10:59] <KGB-0> gobject-introspection tags 48babf5 Simon McVittie upstream/1.66.0 * Upstream version 1.66.0 * https://deb.li/BaQM
[10:59] <KGB-0> gobject-introspection upstream/latest faab8d6 Simon McVittie * pushed 77 commits * https://deb.li/9EPC
[11:00] <KGB-0> gobject-introspection pristine-tar 99916dc Simon McVittie gobject-introspection_1.66.0.orig.tar.xz.delta gobject-introspection_1.66.0.orig.tar.xz.id * pristine-tar data for gobject-introspection_1.66.0.orig.tar.xz * https://deb.li/iwEpV
[13:01] <luna_> meeting now soon?
[13:06] <luna_> also good afternoon
[13:07] <Trevinho> luna_: yeah, and good afternoon!
[13:29] <hellsworth> good morning desktopers
[13:29] <kenvandine> hey hellsworth
[13:30] <oSoMoN> hey hellsworth, kenvandine
[13:30] <luna_> heya hellsworth Trevinho kenvandine oSoMoN
[13:30] <oSoMoN> hey luna_
[13:30] <didrocks999> hey hellsworth, luna_
[13:30] <hellsworth> hi folks
[13:30] <luna_> 1 month left until the 20.10 release
[13:31] <seb128> #startmeeting Desktop Team Weekly Meeting - 2020-09-22
[13:31] <meetingology> Meeting started Tue Sep 22 13:31:11 2020 UTC.  The chair is seb128. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[13:31] <meetingology> Available commands: action commands idea info link nick
[13:31] <seb128> Roll call:  didrocks, duflu, hellsworth, jamesh, jibel, kenvandine, Laney, marcustomlinson, oSoMoN, seb128 , tkamppeter, Trevinho, robert_ancell, callmepk
[13:31] <Trevinho> o/
[13:31] <oSoMoN> o/
[13:31] <marcustomlinson> \o
[13:31] <didrocks> o/
[13:31] <luna_> o/
[13:31] <callmepk> o/
[13:31] <hellsworth> \o
[13:32] <seb128> k, let's get started!
[13:32] <seb128> #topic rls-bb-bug
[13:32] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-incoming-bug-tasks.html
[13:32] <seb128> no desktop entry
[13:32] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-tracking-bug-tasks.html
[13:33] <seb128> bug #1801814
[13:33] <luna_> seems a fix is released in Focal? can that be backported? (just a question)
[13:34] <seb128> it could probably
[13:34] <seb128> it's a flatpak/wayland session fix on bionic
[13:35] <seb128> I think it's not a priority to target for us, since it has no assign I would suggest deleting the bionic target for now
[13:35] <seb128> it doesn't stop someone to work on it if they want
[13:35] <didrocks> agreed
[13:35] <seb128> thanks Didier, deleted
[13:35] <seb128> and that's it for bionic
[13:36] <seb128> #topic rls-ff-bug
[13:36] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ff-incoming-bug-tasks.html
[13:36] <seb128> the one bug there is assigned and targetted but just not untagged
[13:37] <seb128> remind me that I said I would try one day to filter those cases out of the reports, I will put that for my next hacking session
[13:37] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ff-tracking-bug-tasks.html
[13:38] <seb128> Trevinho, you forgot to assign the SRU bug to yourself
[13:38] <seb128> other items are assigned or incomplete
[13:38] <Trevinho> seb128: oh
[13:38] <seb128> #topic rls-gg-bug
[13:38] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-gg-incoming-bug-tasks.html
[13:38] <seb128> no desktop entry
[13:38] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-gg-tracking-bug-tasks.html
[13:39] <seb128> nothing needed there
[13:39] <seb128> #topic update_excuses_by_team.html#desktop-packages
[13:39] <seb128> https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses_by_team.html#desktop-packages
[13:40] <seb128> gstreamer is being hanlded
[13:40] <luna_> There is a new Firefox 81, and Thunderbird (some version) released today and yesterday if oSoMoN wants something new to package up btw :)
[13:40] <seb128> gnome-control-center should clear off when retries results are updated
[13:41] <seb128> luna_, thanks, such comments are better for the AOB part of the meeting that come next :-)
[13:41] <seb128> glib/gst-omx sounds like something that needs investigated
[13:41] <seb128> any taker?
[13:41] <Laney> I already handled it
[13:41] <seb128> great
[13:41] <seb128> gnoe-shell Binaries broken by the update: gnome-shell-extensions/3.37.91-1~fakesync/amd64
[13:42] <seb128> Trevinho, ^ you are handling that?
[13:42] <Laney> Handled
[13:42] <Trevinho> sync to be done
[13:42] <luna_> seb128: alright then i know that for next time
[13:42] <seb128> shell is what is blocking xdg portals, etc (I've a mp for the report script that would indicate that if someone wants to review it ;-)
[13:42] <seb128> k, then we are good
[13:42] <seb128> #topic AOB
[13:42] <seb128> any other topic?
[13:42] <Laney> It's not to be done, I fake synced it
[13:42] <Laney> yeah
[13:43] <Laney> the SRU team are asking about the scope of our micro release exception
[13:43] <Laney> looks like life is going to get harder for gnome shell updates, around extensions
[13:43] <seb128> I saw that on discourse
[13:43] <Laney> https://discourse.ubuntu.com/t/scope-of-gnome-mru/18041/
[13:44] <seb128> Trevinho was reprsenting us well there I think
[13:44] <Trevinho> yeah, doesn't make much sense imho, we need to figure out a way not to be blocked by them
[13:44] <seb128> I wonder if we should just remove any extension .deb from the ubuntu archive
[13:44] <Trevinho> it's very hard to check ALL them, not sure if we can avoid debian syncs for them at all
[13:44] <seb128> and tell users to just use the upstream facilities to install those
[13:44] <seb128> (I mean the ones we are not relying on and testing)
[13:44] <Trevinho> I'd agree, we can just support our ones, for the rest packages don't make any sense IMHO.
[13:44] <oSoMoN> I was going to suggest deleting extensions that are known offenders
[13:45] <Laney> If that's what the SRU team wants
[13:45] <Laney> then fine, let's kick all gnome-shell-extension-* out
[13:45] <seb128> that should maybe a suggestion someone (Trevinho?) should post about on discourse to have a public discussion ?
[13:45] <Trevinho> seb128: is it possible to avoid auto-syncs to apply tho those packages?
[13:45] <luna_> https://blogs.gnome.org/sri/2020/09/16/the-gnome-extensions-rebooted-initiative/ is this in anyway helpful or related?
[13:45] <seb128> it's possible to blacklist syncs yes
[13:45] <Trevinho> I feel alone in that discussion, so if someone joins me, at least I don't feel like I speak for myself only :D
[13:46] <didrocks> agreed that it’s the only sustainable way for us due to API instability IMHO
[13:46] <seb128> I don't know if you can do gnome-shell-extensions*
[13:46] <Laney> it's just code, it can be changed to do anything
[13:46] <Trevinho> ther's basically NO api either :)
[13:46] <Trevinho> we've a volounteer :D
[13:47] <seb128> Trevinho, can you post on discourse saying we want to remove those because of SRU requirement and upstream minor versions not being compatible
[13:47] <seb128> I will create a trello card
[13:47] <Trevinho> ok
[13:47] <seb128> and I will reply on the SRU team discussion, sorry for not doing earlier
[13:48] <seb128> I though you were handling that well so stayed out of it :-)
[13:48] <Trevinho> eheeh, no worries :)
[13:48] <Laney> Is this all because of one bug that happened once, or are there other cases?
[13:48] <Trevinho> thanks then
[13:49] <Trevinho> I've given my opinion on packages we still need the exceptions for, but maybe that list could be improved, so maybe it's better if you guys review it again and propose a final one (I'm sure Laney wanted something more)
[13:49] <seb128> Laney, I will let Trevinho comment on that, maybe a good question/answer for the discourse topic
[13:49] <seb128> Trevinho, right
[13:49] <Trevinho> Laney: not that I know, but for sure may be... there could be loads of cases where it's not working, just nobody checks
[13:49] <seb128> we can discuss that more after the meeting if needed
[13:49] <seb128> any other topic ?
[13:49] <Laney> The point for SRUs though ...
[13:49] <Laney> ok
[13:50] <Trevinho> well this is still something for all the team I imagine, so... fine to skip to later, but it should be interesting for most of us
[13:50] <seb128> Laney, sorry I though we addressed the SRU question enough, anything specific you think we should cover here?
[13:51] <seb128> Trevinho, 'this'?
[13:51] <Trevinho> SRU thingy
[13:51] <Laney> yes I was just going to say that SRUs don't care if something is working in the archive or not, it's more if something is broken *by* the SRU
[13:51] <seb128> if I understand the request we need to review the discourse post and see if the list makes sense and is complete
[13:51] <seb128> and agree on a course of actions for extensions
[13:51] <Laney> it's "OK" for things to be broken and stay broken
[13:51] <Trevinho> > In that case, I think this means that we cannot push microrelease updates of gnome-shell to stable releases because such updates are known to break packaged extensions. The microrelease exception was originally granted by the technical board on the basis that such updates are not expected to break things, and that situation has clearly changed in the case of gnome-shell.
[13:51] <Trevinho> just arrived a reply....
[13:52] <Laney> so I think the scope is about whether shell stable releases do actually break extensions or if this is just one
[13:53] <seb128> I've a feeling the SRU team is not going let us get away with a 'this is one'
[13:53] <seb128> reality is that it can happen
[13:53] <kenvandine> yeah, it can
[13:53] <seb128> so we either need to remove things from the archive to reduce our testing
[13:53] <seb128> or increase our testplan to cover what is in the archive
[13:53] <Trevinho> can we remove things from focal though?
[13:53] <seb128> or another option I'm not thinking of?
[13:53] <seb128> I don't think so
[13:54] <Trevinho> I've NOT a scientific way to check if we're breaking
[13:54] <seb128> but we shouldn't have more new tarballs for focal after that round
[13:54] <Trevinho> nor saying "I teated them all" i think would be professional
[13:54] <Trevinho> tested*
[13:54] <seb128> GNOME schedules stops at .6
[13:54] <Trevinho> yeah, but... we can still do cherry-picks
[13:54] <seb128> so I say we do an effort to test extensions from the archive for that round if that's what the SRU team requires...
[13:55] <Trevinho> and they may happen (like OEM things, for example I may do in the fingerprint lands)
[13:55] <seb128> well then we need to convince the SRU team on those cases that it's fine
[13:55] <seb128> either by explaining why the changes cherry picked are not risky
[13:55] <seb128> or by testing the extensions...
[13:55] <seb128> no?
[13:56] <Trevinho> 41 extensions, not easy task
[13:57] <Trevinho> sorry 42 in focal
[13:57] <Trevinho> let's remove the 3 we handle.... still 39 to check, impossible.
[13:57] <seb128> not impossible, but expensive to do yes
[13:58] <luna_> would it not be easier to let people download the extensions they want from: https://extensions.gnome.org/ ?
[13:58] <seb128> luna_, that's basically whar we suggested doing going forward
[13:58] <seb128> but we can't change past releases
[13:58] <luna_> ah true
[13:59] <seb128> anyway
[13:59] <seb128> I'm a bit lost at this point
[13:59] <seb128> Laney, Trevinho , did you want to get some conclusion out of the meeting?
[13:59] <seb128> or should we just wrap and keep that going here if needed?
[14:00] <Laney> it would have been nice to have had a unified position as the team
[14:00] <Laney> but it's ok, I guess that isn't going to come from a quick chat in the meeting
[14:00] <seb128> right, I think we need some data and time to process which is why I was suggesting Trevinho start a discourse topic about his proposal of removing extensions
[14:00] <Trevinho> yeah, not sure... I would like to have a statement to reply for sure
[14:00] <seb128> we can continue the discussion there
[14:01] <Trevinho> given the new one I mean
[14:01] <seb128> Trevinho, I'm going to reply
[14:01] <seb128> to the SRU post on discourse
[14:01] <Trevinho> seb128: new topic, not same on SRU exceptions, right?
[14:01] <seb128> yes
[14:01] <seb128> one specific about removing deb extensions for better shell maintainability
[14:02] <Laney> Robie asked for that conversation to be with the release team
[14:02] <seb128> they are on discourse?
[14:03] <Laney> Not sure, there's a category there but we only used it for like release schedules so far
[14:03] <seb128> k, I'm going to read the SRU post again there now
[14:03] <seb128> but no point keeping everyone in the meeting for that imho
[14:04] <seb128> so let's wrap and those interested can continue the discussion
[14:04] <kenvandine> ok
[14:05] <seb128> #endmeeting
[14:05] <meetingology> Meeting ended Tue Sep 22 14:05:01 2020 UTC.
[14:05] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-desktop/2020/ubuntu-desktop.2020-09-22-13.31.moin.txt
[14:05] <seb128> thanks everyone!
[14:05] <luna_> np
[14:05] <didrocks> thx!
[14:07] <seb128> so our option I think
[14:07] <seb128> 1. don't SRU gnome-shell updates
[14:07] <seb128> 2. validate every extension in the archive as part of the SRU test plan
[14:07] <seb128> 3. remove deb extensions to avoid 2.
[14:07] <seb128> 4. accept that gnome-shell updates can create issues for some universe extensions (is that ok? needs r-t convincing)
[14:07] <seb128> 5. other?
[14:08] <seb128> what do people here think?
[14:09] <seb128> I think we can rule out 1, we want updates they are beneficial to most users
[14:09] <seb128> 2. is has a non trivial resource cost and I don't think we do have the resources for that atm
[14:09] <Trevinho> 1. would just make people sad, and as I wrote, it would be silly to make ubuntu worse for 1 offending case that was fixed anyways
[14:09] <seb128> so I would suggest 3 or maybe 4...
[14:10] <oSoMoN> 3 makes the most sense to me, but the question remains of what to do for currently supported releases
[14:10] <Trevinho> I agree
[14:10] <seb128> or a mix, we could purge things are outdated, buggy, known to break and maybe keep a few popular ones if we believe there is a value in having them as a deb (is there?)
[14:10] <Trevinho> 3 is the final path, wondering for focal though
[14:10] <Trevinho> well if there's community doing the work to maintain them, fine...
[14:10] <Trevinho> not saying we ban them
[14:10] <Trevinho> but they need to be responsible for
[14:10] <seb128> it's always tricky
[14:10] <seb128> because there is, until there isn't
[14:11] <seb128> and then we are left with a LTS to maintain and no-one to fix those that had community interest
[14:11] <seb128> is there any value to have some as deb (out of default install for us and flavors)
[14:12] <Trevinho> don't think so
[14:13] <Trevinho> for sure there may be extensions (dashtodock) for example that is outdated in e.g.o
[14:13] <Trevinho> so packages help
[14:13] <Trevinho> but this is a case where users can still always just intall it from git...
[14:13] <Trevinho> not that hard
[14:13] <seb128> right, or get the e.g.o situation sorted out
[14:13] <seb128> which is the real problem
[14:13] <Trevinho> exactly
[14:14] <Trevinho> we can't do the role of the maintainer for everything, if we're not
[14:15] <oSoMoN> I'd argue that if upstreams are not updating their extensions on e.g.o, packaging them as debs to work around the problem is not a good fix
[14:21] <seb128> Trevinho, marcustomlinson , what happened to the vte/g-t updates?
[14:22] <Trevinho> seb128: marcustomlinson was busy so I took it, but I've not finished yet
[14:22] <Trevinho> seb128: if you want to take it, feel free :)
[14:23] <seb128> Trevinho, no, maybe you should have it to marcus if you are already busy was my point :)
[14:23] <seb128> also it's done in Debian so just a merge, shouldn't be too difficult
[14:25] <Trevinho> seb128: yeah, yeah... shouldn't be long indeed
[14:25] <Trevinho> seb128: just didn't had time yet, but will do it later
[14:26] <Trevinho> I actually took it when it wasn't in debian yet so it involved a few more work
[14:27] <Laney> I was leaving that one because marcustomlinson was signed up on Trello
[14:27] <Laney> but I see that he left the card, so ...
[14:29] <Beret> quick poll - for those of you that have both - do you disable the integrated graphics in your systems for Ubuntu?
[14:29] <seb128> Trevinho, that's not true, the update was uploaded to Debian on monday and you discussed it with marcus and the card changed on thursday
[14:29] <Beret> and just use the discreet cards?
[14:29] <Trevinho> Beret: I only use integrated :)
[14:30] <Trevinho> (unless I've to test stuff on nvidia)
[14:30] <seb128> Beret, hey, I've an XPS with only intel so I'm out of that poll
[14:30] <Trevinho> seb128: I mean, I looked at that before it was in debian... then I noticed was just a merge
[14:31] <Trevinho> but I had it into my radar even before
[14:31] <seb128> Trevinho, you should have left it to marcus who said would do it on friday
[14:31] <seb128> now we are tuesday and it's still not done
[14:31] <jibel> Beret, I disable the discret card for longer battery life.
[14:32] <Beret> I'm looking to buy a new desktop/machine and I do google hangouts like ... too much... so I need hardware acceleration of that
[14:32] <Beret> so I'm thinking of getting a discrete  graphics capable NUC
[14:32] <Beret> my existing NUC is integrated only and I can't get hangouts accelerated
[14:33] <Beret> which renders the machine not really useful while in a google meet
[14:33] <Trevinho> seb128: I just wanted to help as he was busy, but I can handle quickly, nw
[14:34] <Trevinho> Beret: mh, well recent integrated card should be quite good at that, and for sure intel ones have better and earlier support for video acceleration
[14:34] <jibel> I've a recent NUC with integrated only and I can stay all day long in a HO without any problem.
[14:34] <jibel> python linter in vscode is what kills the NUC
[14:34] <Trevinho> seb128: meanwhile I've also opened https://discourse.ubuntu.com/t/removal-of-gnome-shell-extension-from-universe-and-stop-auto-syncs/18437
[14:35] <Trevinho> jibel: don't tell me that about clangd :D
[14:35] <Beret> jibel, I have i915
[14:35] <Beret> it's awful
[14:35] <jibel> I don't know what is on this machine
[14:36] <jibel> lspci says VGA compatible controller: Intel Corporation Device 9bca
[14:37] <Laney> Trevinho: Thanks for posting that, but I think that it should been on the ubuntu-release list, since I don't believe most release team members read the desktop group on discourse - or even read discourse at all most of the time. Maybe email the list to point to the thread?
[14:37] <Beret> what does lspci | grep VGA say?
[14:37] <Beret> 00:02.0 VGA compatible controller: Intel Corporation Iris Pro Graphics 580 (rev 09)
[14:37] <Trevinho> Laney: I don't have powers to write them, can you maybe move it?
[14:37] <Beret> that's me
[14:37] <Laney> Trevinho: email list
[14:37] <Laney><EMAIL_ADDRESS>[14:38] <Laney> you have the power, for sure
[14:43] <Trevinho> Laney: I meant that I've not the powers to create a topic in the Release team section
[14:43] <Trevinho> of discourse
[14:44] <Laney> yeah, I'm not sure it should be there, we didn't use that section for discussions yet
[14:44] <Laney> it's got restricted access
[14:44] <Laney> I'd have just started a thread on the email list, but if you want to have it on discourse then I'm just suggesting sending an email saying "please see this thread" to the release team list
[14:47] <Laney> so that release team members actually have a chance of seeing it :>
[14:48] <Trevinho> Laney: well can be both, I wrote there as that's what seb told me :)
[14:55] <Laney> it's fine if you prefer that, I'm just suggesting echo "I started a Discourse thread about removing gnome-shell extensions from the Ubuntu archive, would appreciate your feedback: <discourse link>" | mail -s "Thread about removing gnome-shell extensions from Ubuntu"<EMAIL_ADDRESS>[14:55] <Laney> :>
[14:55] <marcustomlinson> Trevinho: sorry :/
[14:55] <marcustomlinson> looks like I got you in trouble
[14:56] <Trevinho> marcustomlinson: no, no worries :)
[14:56] <seb128> bah, why does my client tend to drop from IRC on idle now :-/
[14:57] <seb128> Laney, Trevinho , I suggested to post on discourse to have a team + community discussion about our suggested course of actions, that's a bit orthogonal to the r-t discussion (which is taking the result of the post to them)
[14:58]  * Trevinho writes to ML to notify as well
[14:58] <seb128> thx
[14:58] <Laney> merci
[14:58] <Laney> I think it's OK / nice / good to involve that team early
[14:59] <seb128> right
[15:07] <kenvandine> seb128: which client are you using?
[15:07] <kenvandine> IRCCloud has been disconnecting me pretty often lately
[15:08] <kenvandine> used to stay connected, but that was when i was paying
[15:08] <kenvandine> i stopped paying and it would stay connected at least throughout the work day
[15:08] <kenvandine> but now i get disconnected every 3-4 hours it seems
[15:11] <Laney> Nice IRC connection you've got there...
[15:12] <Laney> ...shame if anything were to happen to it...
[15:24] <seb128> lol
[15:24] <seb128> kenvandine, no, just hexchat here but I think it's rather nm status changes
[16:48] <ricotz> Laney, hi :), is there an ETA of gtk+3.0 3.24.23 for focal?
[16:50] <Laney> ricotz: no ETA, it's somewhere on the list though
[16:51] <Laney> You Can Help™
[16:53] <ricotz> I would not expect it to more than a rebuild of the groovy package
[17:02] <Laney> the upload probably will indeed be that, also needs SRU bug and build/runtime testing
[17:03] <Laney> see you tomorrow


[01:58] <thafreak> grr...i hate having to reboot servers just because processes get stuck
[01:59] <thafreak> especially when you have over 1 year uptime :(
[01:59] <thafreak> well i guess it's worse when it's *almost* 1 year uptime...
[02:01] <yano> ouchie
[02:14] <thafreak> yeah, especially when it's your VM host...and all the stuff you depend on runs as vms on it
[02:31] <canthus13> VMS?
[02:31] <Unit193> RMS*
[02:31] <canthus13> they still use VMS?
[02:31] <canthus13> Unit193: that's a dirty word.
[02:32] <Unit193> :D
[02:32] <canthus13> or a word with poor hygeine, at least.
[02:32] <Unit193> You can at least install vrms - Virtual RMS. :D
[02:34] <canthus13> The only reason I'd install that is to see how low of a score I can get.
[02:37] <yano> RMS is really a VMS
[02:41] <Unit193>   9 non-free packages, 0.4% of 2292 installed packages.
[02:41] <Unit193>   2 contrib packages, 0.1% of 2292 installed packages.
[02:41] <Unit193> :D
[14:40] <thafreak> Morning Ohio
[14:40] <yano> good morning :-)
[14:50] <thafreak> what's so good about it
[14:50] <thafreak> j/k
[14:50] <thafreak> i know i started it
[14:50] <yano> this, http://radar.weather.gov/radar.php?rid=ILN&product=NCR&overlay=11101111&loop=yes
[14:51] <thafreak> because you're going to get rain?
[14:51] <yano> yes \o/
[14:51] <yano> and lightning
[14:51] <yano> rain, thunder, and lightning: oh my!
[14:51] <thafreak> i could use some rain I guess...no lightning though...have enough misbehaving electronics as it is
[14:52] <thafreak> speaking of lightning...anyone have any tips for lightning-proofing phone lines?
[14:52] <thafreak> had an analog phone system card fry on me a few months back
[14:53] <thafreak> and I'm finally replacing it...don't want it to happen again...waste of $500
[14:53] <thafreak> do the surge protectors with phone line plugs work?
[14:54] <yano> i believe so, though i haven't been in a situation to test it though
[14:54] <thafreak> probably should do some research
[14:55] <thafreak> i think I saw some one talking about coiling copper or something, but don't know if that would be useful in my situation
[14:58] <thafreak> what do you guys think about mozilla axing thunderbird???
[14:58] <thafreak> http://news.cnet.com/8301-1023_3-57467973-93/mozilla-calling-it-quits-on-thunderbird-report-says/?goback=%2Egde_77477_member_135739306
[15:00] <thafreak> ok so they're not axing it, but moving resources away and only focusing on security/maintanence fixes
[15:00] <thafreak> and hoping the "comminity" will drive innovation
[15:16] <canthus13> mail clients are becoming a niche market.
[22:03] <thafreak> So, I found an old disk image I created, and I think I used a really old version of ghost
[22:04] <thafreak> found a trial version of ghost 6, and it said the image was created with a version older than 3 so it couldn't do anything
[22:04] <thafreak> any ideas on either where to find an ancient version of ghost, or does anyone know of something that can read old ghost images?
[22:07] <canthus13> call norton?
[22:07] <thafreak> it appears that new versions should be able to open it, and they have trial versions...
[22:08] <thafreak> my luck, i didn't even use ghost and this is a wild goose chase
[22:15] <canthus13> http://www.linuxquestions.org/questions/linux-newbie-8/ghost-software-linux-ghost-server-204119/
[22:15] <canthus13> might be able to mount it...
[22:20] <canthus13> Oh. have you checked the magic number to see if you can find the actual file type?
[22:23] <thafreak> yah, file just spits out weird escape chars...
[22:25] <thafreak>  \0 "\376\357\001"
[22:25] <thafreak> That
[22:25] <thafreak> that's the file type of the image :)
[22:40] <toddc> I thought Norton made motorcycles!!! :)
[22:53]  * canthus13 mounts a motorcycle.
[23:05] <dzho> Nortons and Indians and Greeves won't do . . .
[23:39] <toddc> is still trying to get the image of canthus13  mounting a motorcycle out of my head. shivers and walks away shacking his head!!!! :)
[23:39] <canthus13> Heh.
[23:40] <toddc> I ride my motorcycle not mount it on a wall


[00:40] <Wild_Man> tsimonq2, I have published the letter to the forum, I did try the mailing list but it failed, I figure I do not have the proper access
[00:45] <Wild_Man> pleia2, when you have time would you please give us access to the social media and the m/l? I assume that is why the m/l with the letter was rejected
[00:46] <krytarik> (..I already have got access to the first, but I didn't want to do social media.)
[00:46] <pleia2> krytarik already has access to all the social media stuff
[00:47] <pleia2> are you subscribed to the mailing list? I don't see anything in the queue
[00:47] <krytarik> I know for a fact that Wild_Man is used to doing this for the forums, so.. :)
[00:48] <krytarik> Yes, because it got rejected outright - I suspect content filter.
[00:48] <Wild_Man> I subscribed about 15 minutes ago then I sent the letter to the mailing list and it came back as rejected
[00:48] <pleia2> what email address did you send from?
[00:48] <Wild_Man><EMAIL_ADDRESS>[00:48] <Wild_Man> it may be an issue with that
[00:48] <pleia2> you're not a member of the mailing list
[00:49] <Wild_Man> I guess it is not showing up yet, I did not receive a reply after I signed up
[00:49] <Wild_Man> should I have received a reply?
[00:49] <pleia2> yeah, you have confirm membership
[00:50] <pleia2> so random people can't just sign you up
[00:50] <Wild_Man> maybe it is just taking its time then
[00:50] <pleia2> check spam filter too? it shouldn't take long
[00:50] <Wild_Man> ok
[00:53] <Wild_Man> Okay I am a member now
[00:56] <pleia2> ok, try to send now
[00:58] <Wild_Man> still rejected
[00:59] <pleia2> can you forward me the rejection notice<EMAIL_ADDRESS>[00:59] <Wild_Man> yes
[01:00] <pleia2> the mailing list is configured to hold messages from members for moderation, so I'm not sure what's happening :\
[01:01] <krytarik> I already thought earlier the size or the sheer amount of links today might matter..
[01:01] <Wild_Man> the message I doubt is helpful
[01:01] <pleia2> Wild_Man: can you forward me the entire email? not just the text, I know what the text is :)
[01:01] <Wild_Man> ok
[01:04] <Wild_Man> brb
[01:05] <pleia2> Wild_Man: sorry, not the UWN text, I'm asking for you to forward me the exact rejection notice that you got from the ubuntu news mailing list
[01:05] <pleia2> not just copying the rejection text into an email, forward the full rejection email
[01:09] <pleia2> I'm still not seeing your address as subscribed to the mailing list :\
[01:09] <Wild_Man> I just sent the full rejection there is not much there but when it came back the letter is as an attachment but that is not how I sent it
[01:09] <Wild_Man> does it take time for the servers to catch up?
[01:09] <pleia2> you subscribed to ubuntu-news-team, but not ubuntu-news
[01:10] <Wild_Man> okay
[01:10] <krytarik> ..Funny, at logging in to the Fridge's WP, I can't continue if the ubuntu-fridge team membership box isn't ticked - but it won't give me any access other than to my profile settings then anyway. :P
[01:10] <pleia2> Wild_Man: so you need to subscribe to ubuntu-news and then I can click the box to let your messages through automatically
[01:10] <pleia2> I can't do this until you subscribe though
[01:10] <Wild_Man> doing now
[01:11] <pleia2> krytarik: are you able to update social media? or share whatever is needed with others?
[01:12] <pleia2> I need to step out to run some errands before everything closes ;)
[01:13] <krytarik> Tbh, I didn't think of the latter option yet.. :P
[01:13] <krytarik> And yes, goo!
[01:15] <Wild_Man> I am signed up!
[01:16] <pleia2> still not showing up :( https://lists.ubuntu.com/mailman/listinfo/ubuntu-news this one?
[01:17] <pleia2> you're definitely on ubuntu-news-team, but that's just for discussion, ubuntu-news is the one you need to be on in order to send/receive the newsletter itself
[01:17] <Wild_Man> pleia2, yes I signed yp but it may take a minute to show up, do what you need to and it will be here when you get back
[01:18] <pleia2> ah, you signed up with your gmail account
[01:18] <pleia2> you need to sign up with the ubuntu.com address if that's the one you want to send the newsletter from
[01:18] <Wild_Man> on my end it shows with the ubuntu one
[01:18] <Wild_Man> it does not matter
[01:18] <pleia2> ubuntu-news-team has the ubuntu address, ubuntu-news has the gmail account
[01:19] <pleia2> you want to send the newsletter from your gmail account?
[01:19] <Wild_Man> I sent them from both from thunderbird with the same settings
[01:19] <Wild_Man> yes that is okay
[01:19] <pleia2> I don't love it, but if you must
[01:20] <Wild_Man> I do not know why it did that but I do not have tome to figure it out this second
[01:20] <Wild_Man> I will work on it
[01:20] <pleia2> your gmail account can send to the list now
[01:21] <Wild_Man> Thanks
[01:23] <pleia2> any luck?
[01:24] <pleia2> ok, I actually do need to go out now ;) I'll check back upon my return if you're still having trouble with anything
[01:25] <Wild_Man> it has not been rejected yet
[01:30] <krytarik> Fwiw, I can't seem to log in to Facebook at all due to what seems to be an issue with it and Firefox currently - keeps on saying 'cookies required'...
[01:30] <tsimonq2> krytarik: Give it what it wants!
[01:30] <tsimonq2> Cookies are good.
[01:31] <tsimonq2> Especially chocolate chip.
[01:31] <tsimonq2> :P
[01:31] <krytarik> Well, they are enabled though.. :P
[01:31] <Bashing-om> Uuummmmm Chocolate Chip Cookies :D
[01:31] <Unit193> Oatmeal Raisin*
[01:32] <tsimonq2> Sugar cookies?
[01:33] <Wild_Man> tsimonq2, we have made progress with posting to the forum and I think the mailing list went through this time
[01:37] <tsimonq2> ok
[01:38] <Wild_Man> if you want me to do twitter in the future since krytarik does not have a twitter account let me know and we can set it up\
[01:39] <tsimonq2> krytarik has the ability to do Twitter.
[01:40] <Wild_Man> ok
[01:54] <pleia2> Wild_Man: you can always check the mailing list archives to check if it's been posted :) it has https://lists.ubuntu.com/archives/ubuntu-news/
[01:55] <Wild_Man> pleia2, thanks
[02:02] <krytarik> Nobody has thought of or decided for 'claiming' the custom URL on Google+ yet..? :P
[02:03] <pleia2> you can't until you have a certain number of followers
[02:03] <pleia2> but look at that, we do now!
[02:03] <krytarik> Yes!
[02:03] <pleia2> done :)
[02:03] <krytarik> And here I thought 178 was little.. :P
[02:04] <pleia2> https://plus.google.com/+UbuntuWeeklyNewsletter
[02:04] <krytarik> Yeep! \o/
[02:04] <pleia2> could be they loosened the restrictions on it, when I claimed +Xubuntu we for sure had over 1000
[02:04] <krytarik> Oh yeah, that could be too.
[02:09] <Wild_Man> pleia2, do I have to join this list to send them email<EMAIL_ADDRESS>[02:09] <pleia2> yes
[02:09] <Wild_Man> thanks
[02:10] <pleia2> if you don't want to receive emails from the list, there's a setting for that after you subscribe
[02:10] <Wild_Man> ok
[02:14] <Wild_Man> pleia2, is this the one I need https://lists.ubuntu.com/mailman/listinfo/loco-contacts
[02:14] <pleia2> yes
[02:14] <Wild_Man> thanks
[02:16] <krytarik> Google+ certainly does an amount of caching there too..  :P
[02:21] <tsimonq2> I can do the Fridge.
[02:21] <pleia2> krytarik: would you like me to do facebook?
[02:22] <krytarik> pleia2: Well yes, since it doesn't appear to work with Firefox currently, and I can't technically use Chrome/ium either. :P
[02:23] <pleia2> ok, done
[02:24] <krytarik> Btw, since I'm just looking at the Fridge's front page again - was it used to be all monospace for the forwarded release announcements and such?
[02:25] <pleia2> no, I think guiverc uses the WYSIWYG editor to paste in the announcements from the mailing lists, so they don't have the native formatting that old posts have
[02:28] <guiverc> from lists.ubuntu & yeah I don't worry much about formatting
[02:35] <Wild_Man> pleia2, I posted to twitter, I think the format is right
[02:38] <Wild_Man> All M/L are done
[02:41] <guiverc> is there a wiki on formatting for fridge that anyone knows?  or is it markdown/wiki-like?
[02:41] <Bashing-om> Wild_Man: Publishing complete ?
[02:41] <Wild_Man> I think so
[02:42] <Bashing-om> Then we can all get a good nights sleep :P
[02:42] <Wild_Man> I am going to relax, I have not even turned the tv on today
[02:43] <krytarik> I haven't watched TV for like 4 days now - but I'm pretty sure I didn't miss much either.. :P
[02:43] <pleia2> guiverc: it's HTML
[02:44] <Bashing-om> Somebody break out the champaign ( Chocolate Chip Cookies goes well ) :P
[02:45] <pleia2> congrats everyone :)
[02:45] <Wild_Man> when I sent out the emails for the summary writers there was an email in there that said something like reply to this email address if you need to contact us, is it possible some writers have been replying to that address and no one has looked?
[02:46] <Wild_Man> \o/
[02:48] <Wild_Man> Bashing-om, to put the stuff from gdoc into the wiki you just need to copy and paste it into the proper section and it should be formatted correctly
[02:49] <Wild_Man> pleia2, when do we start a new gdoc?
[02:49] <pleia2> you just delete the stuff from the existing gdoc and start over
[02:49] <pleia2> don't delete the headings ;) just the articles
[02:50] <Wild_Man> okay that is what I wonder as well, I for sure was going to leave the headings or I would be lost
[02:50] <pleia2> Wild_Man: the ubuntu news gmail account?
[02:50] <pleia2> I don't remember what email address is referenced in the email
[02:51] <Bashing-om> Wild_Man: copy paste for the most part . only bit of formnatting I recall is the summary heading inclosed between 3 dashes. na ofcourse spacing between entries .
[02:52] <Wild_Man> pleia2, says editors email account
[02:52] <pleia2> I'll look at the doc
[02:53] <Wild_Man> it is the one with the summary writers email addresses
[02:53] <pleia2> ah<EMAIL_ADDRESS>[02:53] <pleia2> no one has emailed that account, I do check it
[02:54] <Wild_Man> okay thanks, I had three yeses and one new person is going to start the first of next month
[02:54] <pleia2> that's good to hear :)
[02:54] <Wild_Man> indeed!
[02:54] <Bashing-om> Wild_Man: What browser are you running ?? I am presently using chromium and had to install 2 plugins for c/p to gdoc .
[02:54] <Wild_Man> I am using FF
[02:55] <pleia2> I'm using Chrome and never had a problem c/p to/from gdocs
[02:55] <Wild_Man> you copy and paste the heading and all the contest under that heading and it should be formatted perfectly
[02:55] <Wild_Man> it was all the other stuff that took me a while last night
[02:55] <Bashing-om> pleia2: After I got the plugins installed both gdoc and chromiun were happy to cooperate .
[02:56] <Wild_Man> I need to take some meds
[02:57] <pleia2> Wild_Man: sometimes that's how I feel after publishing UWN too ;)
[02:57] <krytarik> Wild_Man: Speaking of all the other stuff, please "git pull" again on the script repo.
[02:57] <Wild_Man> ok
[02:58] <krytarik> ..Pahaha. :D
[03:02] <Wild_Man> krytarik, we did not miss publishing anywhere did we?
[03:05] <Wild_Man> happy days, I just received another reply yes from a summary writer
[03:09] <krytarik> Wild_Man: tsimonq2 is gonna do the Fridge he said, but otherwise nah.
[03:10] <Wild_Man> That is what I thought but I wanted to make sure there is a lot of details to check when publishing as I learned today
[03:10] <krytarik> Which fwiw, is the source I personally get the UWN from.. :P
[03:11] <krytarik> Well, at least you subscribed to all the mailing lists today..  And I didn't have to yet! \o/
[03:12] <krytarik> So next time it'll be much less time-consuming.
[03:12] <Wild_Man> very true
[03:12] <tsimonq2> krytarik: Wanna take Fridge?
[03:14] <krytarik> tsimonq2: ...Unless you magically made my account there anything more than dumb, I can't still. :P
[03:15] <tsimonq2> krytarik: Have you cleared your cache?
[03:16] <krytarik> Well, it was like this right from the start - and as I noticed just earlier, one can't even log in without being in and ticking the appropriate team.
[03:19] <krytarik> To be clear, I can log in but I only get the profile settings then.
[03:20] <krytarik> (And yes, I just also cleared the cache.)
[03:20] <guiverc> krytarik: i have to add a /wpmin something to get more options (note: i'm no expert - i just follow notes)
[03:21] <krytarik> Yes, of course one has to append "wp-admin/" to get there in the first place.
[03:22] <krytarik> I'm currently looking at the dashboard, that is. :)
[03:33] <pleia2> krytarik: did you submit a ticket?
[03:33] <krytarik> Not in the last 1.5 days yet, no.
[03:34] <pleia2> ok
[03:34] <krytarik> I seem to have been busy enough as is already. :P
[03:34] <pleia2> no worries, just wanted to make sure you weren't stuck or anything
[03:35] <tsimonq2> pleia2: Could I please get a peer review? http://ubuntu-news.org/2018/04/17/ubuntu-weekly-newsletter-issue-523/
[03:35] <tsimonq2> I haven't done this in months, ya know. ;)
[03:36] <pleia2> hehe
[03:36]  * pleia2 has a look
[03:37] <pleia2> ltgm, all links check out
[03:37] <tsimonq2> \o/
[03:38] <Wild_Man> sounds like we passed?
[03:38] <tsimonq2> Looks like it. :)
[03:38] <pleia2> yes, gold stars all around!
[03:38] <Wild_Man> :)
[03:40] <Bashing-om> :)
[03:51] <krytarik> pleia2: https://rt.ubuntu.com/Ticket/Display.html?id=28954 - this is the one about the previous occasion I mentioned btw.
[03:55] <pleia2> interesting, 2016 is after they revoked our access and told us they wouldn't give it back x_x
[03:56] <krytarik> Yes, that's what I was particularly thinking of here.
[03:58] <pleia2> but now that I look at it, we do have admin on xubuntu.org
[03:58] <pleia2> curious
[03:59] <krytarik> Yes. :D
[04:02] <Bashing-om> pleia2: krytarik :; Sharpening our tools are we ?
[04:03] <krytarik> More like looking for the lost marbles..
[04:04] <Bashing-om> LOL ...
[04:05] <Bashing-om> I jave little marbles to loose .. so I sure got to find some .
[04:05] <tsimonq2> C[M
[04:05] <tsimonq2> C[M
[04:05] <tsimonq2> C[M
[04:05] <tsimonq2> C[M
[04:05] <tsimonq2> C[M
[04:05] <tsimonq2> I *suck* at this.
[04:05] <tsimonq2> Argh.
[04:05] <tsimonq2> Bear with me, lol.
[04:05] <Wild_Man> takes practice
[04:05] <Wild_Man> I do not use op's often
[04:06] <pleia2> tsimonq2: pro tip: use the chanserv topic command and then no one knows who is doing it, or messing up ;)
[04:06] <tsimonq2> That double space has been annoying me. :P
[04:06] <pleia2> lol
[04:06] <tsimonq2> pleia2: chanserv> But that's no fun. :P
[04:07] <tsimonq2> Also, first topic update in 3.5 years \o/
[04:08]  * Bashing-om likey \o/
[04:08] <krytarik> You just wanted to have your name on it! :(
[04:08] <tsimonq2> krytarik: No, I just despise double spaces.
[04:08] <tsimonq2> And, the lack of Oxford commas.
[04:08] <tsimonq2> ::P
[04:08] <tsimonq2> *:P
[04:09] <krytarik> Yeah, true me too, and I know another one too. :P
[04:09] <tsimonq2> Although, I know how much pleia2 *loves* the Oxford comma. ;)
[04:10] <pleia2> they should only be used when necessary for clarity :P
[04:10] <krytarik> Yes!  Same! \o/
[04:10] <tsimonq2> No, they should be used *always*. :P
[04:10] <Bashing-om> and the krytarik periods :)
[04:11] <krytarik> You mean more like spurious spaces.. :P
[04:11] <tsimonq2> Oh, and ".." instead of "..."
[04:11] <tsimonq2> >_>
[04:12] <krytarik> Yes, I variate there!
[04:14] <tsimonq2> (Only in #ubuntu-news do we argume about grammar. :P)
[04:14] <tsimonq2> *argue
[04:15] <pleia2> hehe
[04:16] <Bashing-om> And style, content, and, presentation :)
[04:16] <krytarik> Period!
[04:16] <Bashing-om> LOL
[04:19] <tsimonq2> That extra comma...
[04:19] <tsimonq2> :P
[04:19] <krytarik> Yes.. :(
[04:44] <Bashing-om> Late for the date for some rack time .. we do this more tomorrow :)
[13:30] <krytarik> Cool, managed to log in to Facebook now - somehow..
[18:42] <krytarik> So, given what we now know about the admin on Canonical-hosted WordPress thing, it just occurred to me that it might yield a better outcome if, rather than having them fix the role level (to anything other than blank options) for a single team member (me), we request the role level be raised to admin for everybody on the ubuntu-fridge team. :)
[21:11] <Wild_Man> krytarik, howefield fixed it where the whole news letter can be posted on the forum, so I added the updates for 17.10
[21:14] <krytarik> Oh cool - I shouldn't ask what did it.. :P
[21:18] <Wild_Man> pleia2, tsimonq2 I received two emails today one of them with profanity in it about wanting to be removed from the newsletter mailing list, I figure I should reply with the message go to the mailing list page and include the link to unsubscribe but I just want to make sure that is the protocol?
[21:19] <Wild_Man> krytarik, he has not told me yet, he fixed it and went off line but no I would not post it here in the open channel anyway
[21:19] <tsimonq2> Wild_Man: Please forward me the email, and I can take care of it.
[21:19] <pleia2> Wild_Man: PM me their email addresses and I'll remove them, you can reply by saying something like "In the future, be aware that you can unsubscribe yourself by going logging in to the mailing list page"
[21:19] <tsimonq2> Er
[21:19]  * tsimonq2 tags pleia2
[21:20] <tsimonq2> pleia2: Thanks. :)
[21:20] <pleia2> no sense in making them jump through hoops to unsubscribe if they're already unhappy
[21:20] <krytarik> Wild_Man: I mean that's probably technicalities I wouldn't be particularly interested in knowing. :P
[21:20] <Wild_Man> true
[21:21] <Wild_Man> I am going to see if I can find some links, I have been at the VA almost all day
[21:21] <Wild_Man> I did clear out the gdoc last night so it is ready
[21:22] <Wild_Man> I also need to pm Rick with links to this channel and the wiki page before I forget
[21:41] <Wild_Man> krytarik, has bashing-om been here today?
[21:42] <krytarik> Not yet.
[21:42] <Wild_Man> ok
[22:23] <Wild_Man> will pleia2 and thanks tsimonq2
[22:41] <Wild_Man> krytarik, are you thinking about trying to make a script to pull from the hub? or does that fall into the same category as the forum?
[22:44] <krytarik> Well, I already gave a statement about this some days ago - please see the public logs of this channel.
[22:47] <Wild_Man> ok
[22:48] <Wild_Man> tsimonq2, what exactly is the purpose of this page http://fridge.ubuntu.com/2018/04/17/ubuntu-weekly-newsletter-issue-523/
[22:49] <tsimonq2> Wild_Man: What about it?
[22:49] <krytarik> I'm just writing a script however, that creates the 'in this issue' list automatically. :P
[22:51] <Wild_Man> what is its purpose since it is just a short version of the letter, I am just wondering why have it at all?
[22:51] <Wild_Man> krytarik, that is awesome!
[22:52] <pleia2> Wild_Man: the fridge is the community news blog, some people subscribe to it to get news, including UWN
[22:52] <pleia2> this is also how the newsletter gets to planet.ubuntu.com
[22:53] <pleia2> so just like we post it to the mailing list, forums, social media... fridge is just another place where people get to see it
[22:54] <Wild_Man> pleia2, so the planet gets the shortened version with the link to see the full version?
[22:54] <pleia2> yes
[22:54] <pleia2> the full version is too long for a blog :)
[22:55] <Wild_Man> Thanks for clearing that up
[22:57] <Wild_Man> hello Bashing-om
[22:59] <Wild_Man> krytarik, for most sections we really only need about 3 stories correct?
[22:59] <Wild_Man> I added 3 to the planet section
[22:59] <krytarik> Well, I'd say no more than 5 or such.
[22:59] <Bashing-om> Wild_Man: Here we go again .. I see the gdoc has begun for next issue :)
[23:00] <Wild_Man> okay we are thnking along the same lines
[23:00] <krytarik> Depends on what you find the week, of course.
[23:00] <Wild_Man> of course
[23:00] <Wild_Man> Bashing-om, I cleared it out last night so it would be easy to start today
[23:01] <Bashing-om> Wild_Man: Gonna add 2 links to general ..
[23:02] <Wild_Man> good deal Bashing-om, howefield fixed the forum issue for us so now the whole news letter is on the forum
[23:03] <Bashing-om> Wild_Man: Hreat news about the forum .. lemme check the rss feed .. see what I can find for gdoc .
[23:04] <Bashing-om> Great*
[23:12] <Wild_Man> what other sources can we use under canonical it says most come from insights.ubuntu.com so that implies we may get some from other sources?
[23:19] <Bashing-om> Wild_Man: This one: http://www.roaksoax.com/2018/04/maas-2-4-0-beta-2-released . Put it under conical or cloud or blog ???
[23:23] <wildmanne39> never mind about the question above I found the answer
[23:26] <Bashing-om> wildmanne39: Ehat are your thouhgts on MAAS . The AP is cloud directed .. and Cononical is the driver but the source is from a blog .
[23:26] <Bashing-om> What*
[23:27] <wildmanne39> It could go under cloud, we have three other ones in the Planet already Bashing-om
[23:28] <wildmanne39> it may be a question to asked the experienced people on there thoughts, either way is okay with me
[23:29] <wildmanne39> I am going to log out and see if I can get back on now as Wild Man
[23:33] <Bashing-om> Wild_Man: Yepper I too think cloud for MAAS :)
[23:34] <Wild_Man> Bashing-om, it is more appropriate
[23:37] <Bashing-om> Wild_Man: Nope, no can do ,, as the source is a blog .. and no blogs in the Cloud and no summaries . .. I Put the MAAS source in the blog section .
[23:43] <Wild_Man> Bashing-om, any idea how to undo an edit we were working in the same section and it blew up
[23:43] <Wild_Man> Bashing-om, never mind I found the undo button and fixed it
[23:43] <Wild_Man> Bashing-om, if it can not go in the cloud then it is more appropriate in the Planet section where I found it
[23:44] <Wild_Man> Bashing-om, I guess this falls out side of what we should publish but it is interesting https://www.omgubuntu.co.uk/2018/04/microsoft-linux-custom-kernel-azure-sphere?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+d0od+%28OMG%21+Ubuntu%21%29
[23:47] <Wild_Man> biab I need to do a few things
[23:48] <Bashing-om> Wild_Man: Lemme sign oot of gdoc .. and back in .. see what the state is ..  as to kernel-azure . I was going to look at that one in length and then see if we could make it relevant .
[23:51] <Bashing-om> Wild_Man: gdoc looks all right to me at this time .
[23:52] <Wild_Man> I fixed Bashing-om
[23:54] <Bashing-om> Wild_Man: K .. ack to "looking for sources"
[23:55] <Bashing-om> back*
[23:58] <Wild_Man> eating Bashing-om


[06:19] <didrocks> good morning
[06:23] <duflu> Hi didrocks. First as usual :)
[06:23] <didrocks> heh not sure what I win \o/
[06:23] <didrocks> how goes duflu?
[06:24] <duflu> didrocks, goes well. Somehow I am managing to get good sleep on Monday nights lately but never weekends
[06:24] <duflu> You didrocks?
[06:24] <didrocks> I'm mostly ok, thanks! :)
[06:45] <duflu> Hi seb128. I just deleted the BT meeting, based on Will's suggestion
[06:45] <seb128> good morning desktopers
[06:45] <seb128> hey duflu, that makes sense, thanks
[06:45] <seb128> how are you today?
[06:47] <duflu> seb128, going well, you?
[06:47] <seb128> I'm good, thanks!
[06:48] <didrocks> hey seb128
[06:48] <seb128> hey didrocks
[07:32] <oSoMoN> good morning desktoppers
[07:34] <duflu> Morning oSoMoN
[07:36] <oSoMoN> hey duflu
[07:41]  * tsimonq2 waves to everyone :)
[07:47] <duflu> Everyone waves to tsimonq2
[07:47] <seb128> lut oSoMoN, en forme ?
[07:47] <seb128> hey tsimonq2
[07:48] <oSoMoN> salut seb128
[07:49] <oSoMoN> peu dormi, mais bien
[07:49] <oSoMoN> et toi?
[07:49] <seb128> levé un peu tôt mais j'ai pas à me plaindre sinon ;)
[08:01] <Laney> boop
[08:03] <oSoMoN> hey Laney
[08:07] <Laney> morning oSoMoN!
[08:07] <Laney> all good?
[08:07] <oSoMoN> I'm good! you?
[08:14] <seb128> hey Laney, how are you?
[08:14] <Laney> hej hej seb128
[08:14] <Laney> seb128: oSoMoN: GOOD!
[08:15] <Laney> the rain that we might have had last night didn't come though
[08:15] <Laney> :'(
[08:15] <Laney> what about you?
[08:15] <seb128> it's a bit cooler here today, it has been raining somewhere during the night which is nice
[08:16] <seb128> we might have had a few drops in fact, it looked a bit like that this morning but we didn't hear anything so we are unsure :)
[08:20] <Laney> :3
[08:41] <tsimonq2> TIL being part of the DMB means receiving notifications for e.g. https://code.launchpad.net/~3v1n0/ubuntu/+source/nautilus/+git/nautilus/+merge/349670
[08:42] <tsimonq2> I've either not noticed it for the past few months for other teams or something isn't configured right. :P
[08:42] <tsimonq2> (Both of which are possible.)
[08:47] <Trevinho> Morning
[08:47] <Trevinho> And nice e emoji international day ❤🎉💐🎁🤗
[08:48] <Trevinho> Laney, aren't you celebrating it?
[08:49] <Laney> 🙌🙌🙌🙌🙌🙌🙌🙌🙌🙌🙌🙌🙌🙌🙌🙌🙌🙌
[08:49] <Laney> tsimonq2: you might have had that through the ubuntu-desktop list
[08:50] <Laney> use the X-Launchpad-* headers to filter it
[08:50] <Laney> if you don't want to see those
[08:53] <seb128> hey Trevinho, how are you?
[08:54] <andyrock> he all
[08:55] <andyrock> *hey 😅
[08:56] <tsimonq2> Laney: I don't particularly care, just wondering why :)
[08:56] <tsimonq2> Laney: 🦒 :P
[08:59] <Laney> TIL there's a giraffe emoji
[08:59] <Laney> hey andyrock
[08:59] <Laney> what up
[09:00] <tsimonq2> >:D
[09:00] <Trevinho> seb128: hey, good...
[09:01] <Trevinho> seb128: had time for that nautilus branch?  No I didn't yet but it's on my list, I just finished dealing with emails/HR things
[09:06] <ogra_> (or a llama)
[09:06] <Trevinho> Anyway this could be a good day for making Lennart happy and prepare a branch with lots of emoji
[09:07] <Trevinho> seb128: ehehe, yes... Powerful 4hrs or so
[09:08] <seb128> you crazy man
[09:09] <jamesh> how do emoji sort according to the dpkg version comparison algorithm?
[09:09] <Trevinho> jamesh: jhemoji... It's the time 😅
[09:09] <popey> didrocks: just got notified of a question that maybe you can answer :) https://askubuntu.com/questions/1055064/why-do-i-get-these-differences-on-ppa-vs-snap-communitheme-ubuntu-18-04
[09:11] <tsimonq2> jamesh: Asking the real questions :D
[09:11] <jamesh> are smiley faces considered greater or less than frowning faces?
[09:12] <Laney> the fun killers already thought of this and disallowed emoji 😭
[09:12] <tsimonq2> NOOOOO
[09:12] <tsimonq2> C'monn
[09:12] <tsimonq2> XD
[09:12] <jamesh> is yellow skin newer or older than pink skin?
[09:13] <tsimonq2> Laney: So... has anyone actually tested that? :P
[09:13] <Trevinho> jamesh: the utf encoding is used as alternative I can guess, so.... Might be based on fifo?
[09:13] <Trevinho> But.... Actually that's the debian tools situation on supporting emoji as version component?
[09:14] <tsimonq2> I'm going to do a test build to a PPA trying this out...
[09:14] <tsimonq2> Just to confirm :P
[09:16] <Trevinho> Time for a DEP-✍?
[09:17] <tsimonq2> Darn
[09:17] <tsimonq2> debuild: warning:     debian/changelog(l1): version '1.🦒' is invalid: version number contains illegal character '�'
[09:21] <Trevinho> Laney: fix that! 😝👀
[09:22] <Laney> somethings are stronger than the efforts of humans
[09:22] <Laney> debian policy is one of those things
[09:22] <Laney> 🏋
[09:22] <tsimonq2> hehe
[09:23] <tsimonq2> Laney: In other words, the giraffe broke dpkg >_>
[09:23] <tsimonq2> It doesn't like it.
[09:24] <seb128> Trevinho, those search engine provider changes, did you get a code review from someone upstream or downstream yet?
[09:24] <Trevinho> seb128: upstream...
[09:24] <seb128> why "..."?
[09:25] <seb128> was that a sarcastic reply, like "why upstream, it doesn't apply there"?
[09:25]  * seb128 is not sure how to read your reply
[09:25] <Trevinho> seb128: all the query code is ready for land upstream... It didn't since the I needed to rebase it, and I didn't do before the end of guadec. But I can ping Carlos
[09:25] <seb128> ok, let me re-ask
[09:26] <seb128> was the code in the diff from https://code.launchpad.net/~3v1n0/ubuntu/+source/nautilus/+git/nautilus/+merge/349670 reviewed by someone already?
[09:26] <seb128> sorry your answer was not clear if it was yes or no
[09:26] <Trevinho> seb128: ahaha, no. Just like (hit on thee imaginary mp link to see) 😅
[09:26]  * Trevinho screws with normal signs today
[09:27] <Trevinho> anyways the parts that apply upstream have been reviewed and acked upstream
[09:28] <seb128> k
[09:28] <seb128> why is the show-error-if-volume-is-not-mounted.patch change not needed upstream?
[09:29] <Trevinho> seb128: because it should be done in gtk, then ported to GNOME... But at the same time, I didn't see any report affecting other distros.
[09:30] <seb128> Trevinho, that's the fix for https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1764779 ?
[09:30] <Trevinho> its natural place would probably be glib, as it should return a Gerror in that case when on_mount is called, but I've no idea how to track that or reproduce
[09:31] <Trevinho> so, this is the best-effort fix for us, but upstreaming that would be done or at GTK or at GLib level
[09:31] <Trevinho> so, not needed for nautilus, that's what I meant.
[09:31] <seb128> Trevinho, see comment #9 from me on that bug, re "not seen in other distro"
[09:31] <seb128> "The issue is not Ubuntu specific, see https://retrace.fedoraproject.org/faf/reports/1743420/"
[09:32] <seb128> they don't have fc28 reports though so maybe it's fixed in some update
[09:33] <Trevinho> seb128: exactly, I found it in RH bugzilla, but not happening in recent versions
[09:34] <seb128> Trevinho, that's different from "I didn't see any report affecting other distros." :)
[09:35] <Trevinho> at least, could happen, for sure there's some systemd involved there... See the bug log, but glib doesn't give that as an error, or maybe the unmount happens while the process is happening
[09:35] <Trevinho> I skipped the "recent" :)
[09:35] <seb128> hehe
[09:35] <seb128> anyway, it feels like that there are enough code changes that we should have some code review
[09:36] <seb128> unsure what's the right place to do those/if a package update with patches diffs is a good way
[09:36] <Trevinho> also faf last night wasn't working when looking for volume_mount_ready_cb
[09:36] <Trevinho> mh
[09:36] <seb128> andyrock, Laney, would one of you have some cycles to help review the changes from Marco on https://code.launchpad.net/~3v1n0/ubuntu/+source/nautilus/+git/nautilus/+merge/349670 ? at least the bits that didn't get an upstream review
[09:37] <andyrock> 1688 lines of diff mmm
[09:37] <Trevinho> I'm anyway happy to propose the same on Gtk though, as it would make sense to be protect on that anyway, but I thought that it would have been better to do it at lower level, and I've not an idea of where that could be done, as looking at gunixfile a bit the mount operation is done as expected
[09:38] <Trevinho> well, just use gbp -> export to patches (on pre and post) -> diff against previous :)
[09:38] <andyrock> I'll take a look but it could require some time
[09:38] <Trevinho> clone, create a branch for pre, export patches, -> go to current -> export patches then compare the two branches
[09:38] <Trevinho> should be easier than reviewing patch of patches
[09:39] <Trevinho> Laney: any other smarter idea for doing the same ^? Maybe gbp could have a diff mode for helping with this :)
[09:43] <Laney> A gbp pq diff sounds like it might be nice
[09:43] <Laney> feel free to file it
[09:52] <seb128> popey, do you know if anyone has been looking in doing a snap for shotwell? sounds like it would be a good one. They are landing face detection support code upstream, I'm unsure that stack is going to be something we want to MIR or land in Ubuntu this cycle but it would be good if users could try it with a snap
[11:06] <popey> seb128: i think someone may have tried in the past and not looked again. I agree it would be a good one to have.
[11:06] <popey> All the video editors are a bit gnarly to snap though
[11:07] <popey> sorry, mistook shotwell for shotcut :)
[11:07] <popey> no, don't know that anyone has done shotwell
[11:08] <seb128> popey, is it likely that you/your team/community could be hinted to look at it? or is that not realistic and it would be better for us to have a look/help if we want it?
[11:08] <popey> tbh as it's a gnome app, I think ken would have more exprience
[11:08] <popey> I'd love him to write up what he did to snap other gnome apps, because that knowledge needs sharing
[11:08] <seb128> k
[11:08] <popey> would be useful for example to build elementary apps too
[11:09] <seb128> I think he's busy enough with core GNOME but I can talk to him (also he's in Montréal this week)
[11:09] <popey> last time I spoke to ken about that was back in New York iirc
[11:09] <seb128> thx for the reply
[11:09] <popey> np
[11:09] <popey> I'm keen for us to have good docs for snapping gnome apps. but I have no idea what's been done to make that happen.
[11:09] <seb128> yeah, I'm also unsure how much things are still changing around there
[11:10] <seb128> with themes now and new snapcraft features letting us moving some of the work around between the helper and the build
[11:11] <popey> ya
[11:11] <seb128> popey, if we get the snapcraft.yaml can you help with "selling" to upstram on how they could build from their CI or other cool things they can have/do?
[11:11] <popey> totes
[11:11] <seb128> great
[11:11] <seb128> thx
[11:11] <popey> np :)
[11:37] <andyrock> seb128: Trevinho can I suggest that when we cherry-pick something from upstream or from a MP and we edit it applying ubuntu-specific bits, we should create two different quilt patches
[11:37] <didrocks> this is what I call a PR: https://github.com/ubuntu/gtk-communitheme/pull/628 :)
[11:37] <gitlab-bot> ubuntu issue (Pull request) 628 in gtk-communitheme "Merge all repositories into a single one" (comments: 1) [Open]
[11:38] <andyrock> one with the original commit and one with the ubuntu specific bits
[11:38] <andyrock> in this way it's easier to review
[11:38] <didrocks> +202293 −391
[11:38] <Laney> 🌞
[11:39] <didrocks> andyrock: +1, especially to know if we can match and revert it once the cherry-pick patch is in the next release
[11:39] <seb128> andyrock, that makes sense to me and common practice for most "packagers" I think
[11:39] <didrocks> Laney: you should have a funny gitg :p
[11:39] <seb128> easier to track the status of the different pieces and to update/rebease
[11:39] <Laney> didrocks: did you do the unrelated history thing?
[11:39] <Trevinho> andyrock: in that case there's not just upstream + ubuntu bits, but also some modifications because upstream is against 3-29, while that's on 3-26 and diff can't be 1:1
[11:39] <didrocks> Laney: yep!
[11:39] <Laney> sweet
[11:39] <seb128> didrocks, I trust whoever is going to approve is it going to carefully read every single line of the diff right?
[11:40] <Trevinho> andyrock: anyway I agree, in this case what was related to?
[11:40] <didrocks> seb128: ahah, I wrote mostly "please test it" on the hub: https://community.ubuntu.com/t/merging-repositories-into-a-single-one/6769/11 :)
[11:40] <seb128> Trevinho, andyrock, you could have upstream's version, tweak-to-work-on-Ubuntu-version patch over it
[11:40] <Trevinho> yeah, fine
[11:40] <didrocks> at least, the snap is working fine
[11:41] <didrocks> backward compatible with the older name
[11:41] <andyrock> Trevinho: the -eel_uri_is_desktop (uri))
[11:41] <andyrock> I know that it's a small change
[11:41] <didrocks> the deb is ready, just need renaming once we announce the new name
[11:41] <didrocks> (but the debs need more testing)
[11:41] <andyrock> but without this I could review it basically checking the sha
[11:41] <andyrock> or maybe not
[11:43] <Trevinho> let me see if I can get some more cherry-picks + an upstream relase too
[11:43] <Trevinho> it would be easier
[12:15] <kenvandine> andyrock, I backported your libgtop2 patch for filtering out the snap mounts to our gnome-3-26 backports PPA
[12:15] <kenvandine> and rebuilt the gnome-system-monitor snap with it
[12:15] <kenvandine> but they are still showing up, and i've figured out why
[12:15] <andyrock> kenvandine: the old snaps will still show up
[12:16] <kenvandine> looking at /proc/mounts on my system i see this:
[12:16] <kenvandine>  /dev/loop30 /snap/spotify/13 squashfs ro,nodev,relatime 0 0
[12:16] <kenvandine> however, from inside the snap /proc/mounts look different
[12:16] <kenvandine>  /dev/loop30 /var/lib/snapd/hostfs/snap/spotify/13 squashfs ro,nodev,relatime 0 0
[12:16] <andyrock> ah
[12:16] <kenvandine> so the mount point is different
[12:16]  * kenvandine has no idea why that is different from inside the snap
[12:17] <kenvandine> i also have others that show up inside the snap that are junk
[12:17] <andyrock> I don't know, but you could filter them using the '/var/lib/snapd/hostfs/snap'
[12:17] <kenvandine>  /dev/loop55 /var/lib/urandom squashfs ro,nodev,relatime 0 0
[12:17] <kenvandine> no, it's also files in /etc, etc
[12:18] <andyrock> mmm so that means that a major rework for libgtop is needed
[12:19] <andyrock> first we should understand why snap is doing that
[12:19] <kenvandine> yeah
[12:19] <kenvandine> http://paste.ubuntu.com/p/Rv7vy8zV7k/
[12:19] <kenvandine> andyrock, ^^
[12:20] <andyrock> kenvandine:  can you ask on #snappy ?
[12:20] <kenvandine> sure
[12:22] <ricotz> kenvandine, hi, could you update vala in gnome-3-26 backports PPA too?
[12:23] <ricotz> for reference see https://launchpad.net/~vala-team/+archive/ubuntu/ppa/+packages
[12:25] <ricotz> kenvandine, https://wiki.gnome.org/Projects/Vala
[12:25] <kenvandine> ricotz, i'll take a look
[12:25] <kenvandine> should be no problem
[12:26] <ricotz> thanks, it is highly recommended
[12:52] <andyrock> kenvandine:  how can I get your snap?
[12:53] <andyrock> otherwise can you check if /proc/filesystems is visible?
[12:53] <andyrock> libgtop is using this to filter out fs
[12:57] <kenvandine> andyrock, it's in the store
[12:59] <andyrock> Kk I'm taking coffee right now
[12:59] <andyrock> Brb
[12:59] <kenvandine> andyrock, thx!
[13:13] <andyrock> kenvandine: mmm all this fs are mounted as squashfs
[13:13] <andyrock> it's not going to be easy to filter them out
[13:13] <kenvandine> andyrock, yes...
[13:13] <kenvandine> pita... i know
[13:13] <kenvandine> but what i was saying in the other channel, i don't know if displaying squashfs in gnome-system-monitor is even useful
[13:14] <kenvandine> the point there is to see what your resources used are
[13:14] <kenvandine> so how much space you have left
[13:14] <kenvandine> etc
[13:14] <kenvandine> squashfs isn't useful there
[13:15] <andyrock> mmm upstream disagrees with you
[13:15] <andyrock> I already had the same chat with them
[13:15] <kenvandine> :/
[13:15] <andyrock> one thing that we could do is to use the x-gdu.hide option
[13:16] <andyrock> let me check if this feasible
[13:16] <kenvandine> cool
[13:18] <andyrock> kenvandine: mmm nope
[13:18] <andyrock> the file /run/mount/utab is not visible inside the snap
[13:25] <kenvandine> :(
[13:25] <kenvandine> maybe we can get that fixed :)
[13:25] <kenvandine> andyrock, ask in #snappy
[13:30] <seb128> k, it's meeting time
[13:30] <seb128> #startmeeting Desktop Team Weekly Meeting - 2018-07-17
[13:30] <meetingology> Meeting started Tue Jul 17 13:30:19 2018 UTC.  The chair is seb128. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[13:30] <meetingology> Available commands: action commands idea info link nick
[13:30] <didrocks> hey
[13:30] <oSoMoN> o/
[13:30] <seb128> andyrock, dgadomski, didrocks, duflu (out), jamesh (out), heber, kenvandine (out), laney (out), oSoMoN, seb128, tkamppeter, trevinho (out), robert_ancell (out)
[13:31] <andyrock> o/
[13:32] <seb128> k, let's get started, should be an efficient one with some people out
[13:32] <seb128> #topic andyrock
[13:32] <seb128> andyrock, hey
[13:32] <andyrock> hey all
[13:32] <andyrock> - Updated fix for https://gitlab.gnome.org/GNOME/gnome-shell/issues/372 (merged upstream)
[13:32] <andyrock> - Proposed fix for LP: #1781996 (merged upstream)
[13:32] <andyrock> - Update fixes for https://gitlab.gnome.org/GNOME/gnome-shell/issues/373 (on review)
[13:32] <andyrock> - Working on g-s-d, mutter and gnome-shell to extend the above fix for g-s-d too (wip)
[13:32] <andyrock> - Proposed fix for https://gitlab.gnome.org/GNOME/gnome-shell/issues/109 (on review)
[13:32] <andyrock> - Update MR for using g-o-a in gnome-software (https://gitlab.gnome.org/GNOME/gnome-software/merge_requests/50)
[13:32] <andyrock> - Update MR to get ubuntu-sso provider in gnome-online-accounts (this is blocking the above MR)
[13:32] <andyrock> - Proposed a MR to backport fix for LP: #1764723 in Bionic
[13:32] <andyrock> - Proposed fix to remove deprecated functions call in gnome-software snap plugin
[13:32] <andyrock> - Helping ken_vandine with the gnome-system-monitor snap (hiding all the noise)
[13:32] <gitlab-bot> GNOME issue 372 in gnome-shell "Keeping Alt+Space pressed shows the window menu and then minimizes the window" (comments: 4) [Closed]
[13:32] <andyrock> Review:
[13:32] <andyrock>  - https://gitlab.gnome.org/Community/Ubuntu/gnome-initial-setup/merge_requests/7
[13:32] <andyrock>  - https://code.launchpad.net/~3v1n0/ubuntu/+source/nautilus/+git/nautilus/+merge/349670 (WIP)
[13:32] <gitlab-bot> GNOME issue 373 in gnome-shell "Some keybindings should discard auto-repeat events" (comments: 0) [Opened]
[13:33] <andyrock> EOW
[13:33] <gitlab-bot> GNOME issue 109 in gnome-shell "Extended characters in OSK don't get entered" (comments: 16) [Opened]
[13:33] <gitlab-bot> GNOME issue (Merge request) 50 in gnome-software "auth: Use gnome-online-accounts to handle the authentication" (comments: 10) [Opened]
[13:33] <gitlab-bot> Ubuntu issue (Merge request) 7 in gnome-initial-setup "Display the ubuntu welcome wizard in Unity" (comments: 2) [Merged]
[13:33] <seb128> thanks andyrock
[13:33] <seb128> (topic was too long and cut it seems)
[13:33] <seb128> #topic dgadomski
[13:33] <dgadomski> hey
[13:33] <dgadomski> * reported and working on small reproducer for bug #1782152
[13:33] <dgadomski> * working on bug #1721988
[13:33] <dgadomski> eof
[13:34] <andyrock> https://www.irccloud.com/pastebin/wmbtk7l3/
[13:34] <seb128> thanks dgadomski
[13:34] <andyrock> seb128: ^^^
[13:34] <seb128> andyrock, no, I meant the /topic is too long and truncated, so the "current topic" is wrong
[13:35] <seb128> the bot memorized the one from the meeting start though it seems and didn't let me fix it
[13:35] <seb128> oh well, summary with 2 lettres nicknames :p
[13:35] <seb128> #topic didrocks
[13:35] <seb128> didrocks, hey
[13:35] <didrocks> * BOFs days (theme, icons, settings discussion) at GUADEC and travel back
[13:35] <didrocks> * Work on preparing communitheme renaming + move to debs: https://github.com/ubuntu/gtk-communitheme/pull/628
[13:35] <gitlab-bot> ubuntu issue (Pull request) 628 in gtk-communitheme "Merge all repositories into a single one" (comments: 6) [Open]
[13:35] <didrocks>   - merge all 5 repos: gtk, gnome-shell, icons, sounds and snap helpers into a single one, with subdirectories for each. Reorganize the whole repo
[13:35] <didrocks>   - work on the build system itself, to be parameterized to only the project name for each folder and settings set. Basically, renaming will be "change the project name" and be done!
[13:35] <didrocks>   - ensure the snap is backward compatible with the older name (sed to be back to "communitheme" + symlinks for Suru and other names)
[13:35] <didrocks>   - recheck licenses and organize them.
[13:35] <didrocks>   - ensure that there is an easy way for people doing ninja install (like communitheme members) to have a dedicated session for them. This won't be shipped in the debian packaging.
[13:35] <didrocks>   - other discussions over new names/theme icons and decisions about the ubuntu logo over the hub.
[13:35] <didrocks> * SRU apport (currently in unapproved) for Bionic with the new layout and functionality. Emailed translation team.
[13:35] <didrocks> .
[13:36] <seb128> thanks didrocks
[13:36] <seb128> did you get any feedback from the SRU team about why apport is not being reviewed?
[13:36] <didrocks> I got one this night
[13:37] <didrocks> it seems bdmurray found an issue in the "server only install"
[13:37] <didrocks> which isn't the default
[13:37] <didrocks> and isn't a new issue
[13:37] <didrocks> I answered on this, bdmurray will give another look
[13:37] <seb128> k, let's discuss it out of the meeting if needed
[13:37] <seb128> thanks
[13:37] <didrocks> yw
[13:37] <seb128> #topic duflu
[13:37] <seb128> * Video acceleration:
[13:37] <seb128>   - Intel asked if I had tried their latest driver. Turns out they were paying attention to the Ubuntu wiki and fixed the proprietary prerequisite problem (https://wiki.ubuntu.com/IntelQuickSyncVideo#Future_Approach_.232:_Media_SDK_.28.22MSDK.22.29). So we should eventually: https://launchpad.net/bugs/1781315
[13:37] <seb128> * Gnome Shell:
[13:37] <seb128>   - Performance: Steady progress on a general timing fix to avoid dropped frames and double gnome-shell's frame rate for many people (https://gitlab.gnome.org/vanvugt/mutter/commits/super-smooth)
[13:38] <seb128>     . Although it really needs to be combined with https://gitlab.gnome.org/GNOME/mutter/merge_requests/73 but that's going to take even longer to get approved.
[13:38] <seb128>   - Performance: Revised several times: More accurate & detailed CLUTTER_SHOW_FPS (https://gitlab.gnome.org/GNOME/mutter/merge_requests/154)
[13:38] <seb128>   - Added/fixed support for local non-root installations, now with multiple potential solutions (https://gitlab.gnome.org/GNOME/gnome-shell/issues/399)
[13:38] <seb128> * PulseAudio 12.0:
[13:38] <gitlab-bot> GNOME issue (Merge request) 73 in mutter "WIP: renderer-native: CRTCs now hold front buffer refs. [performance]" (comments: 44) [Opened]
[13:38] <seb128>   - Released to cosmic! (https://launchpad.net/ubuntu/+source/pulseaudio/1:12.0-1ubuntu1)
[13:38] <seb128> * BlueZ:
[13:38] <seb128>   - Released SRU for bionic! (https://launchpad.net/ubuntu/+source/bluez/5.48-0ubuntu3.1)
[13:38] <seb128> * Daily bug management across gnome-shell, mutter, gdm3, ubuntu-themes, bluez, pulseaudio, dkms, wayland, totem, mpv, libinput.
[13:38] <seb128>   - A subtle but pleasing trend at the high end
[13:38] <gitlab-bot> GNOME issue (Merge request) 154 in mutter "clutter: More accurate & detailed CLUTTER_SHOW_FPS [performance]" (comments: 8) [Opened]
[13:38] <gitlab-bot> GNOME issue 399 in gnome-shell "`ninja install` fails as non-root trying to write to an incorrect directory" (comments: 6) [Opened]
[13:38] <seb128>
[13:39] <seb128> #topic jamesh
[13:39] <seb128> guadec:
[13:39] <seb128> * I attended GUADEC last week, flying back home on the Thursday and Friday
[13:39] <seb128> * While there, I put together a patch for GEdit to use the
[13:39] <seb128> GtkFileChooserNative API:
[13:39] <seb128> https://gitlab.gnome.org/GNOME/gedit/merge_requests/2
[13:39] <seb128> * Ken rebuilt the GEdit snap and uploaded it to the beta channel,
[13:39] <gitlab-bot> GNOME issue (Merge request) 2 in gedit "gedit: port GeditFileChooserDialogGtk to GtkFileChooserNative" (comments: 2) [Opened]
[13:39] <seb128> confirming that this let it open and save files via portals
[13:39] <seb128> * I also talked with the upstream xdg-desktop-portal developers about
[13:39] <seb128> improving snap support.  We agreed on a way forward, by implementing a
[13:39] <seb128> new "snap" sub-command to return information about a particular
[13:39] <seb128> running snap application and have xdg-desktop-portal call that.
[13:39] <seb128> snapd/pulseaudio:
[13:39] <seb128> * Jamie posted to the Snapcraft forums about microphone access via
[13:39] <seb128> Pulse Audio: https://forum.snapcraft.io/t/pulseaudio-recording/6361
[13:39] <seb128> * With upstream Pulse, there is no distinction between playback and recording.
[13:39] <seb128> * We had a patch to restrict recording on Ubuntu Phone, so I am
[13:39] <seb128> looking at porting it forward and having it check with snapd to see if
[13:39] <seb128> an app has plugged a new audio-record interface
[13:40] <seb128> #topic heber
[13:40] <seb128> hum, he's not there
[13:40] <seb128> #topic kenvandine
[13:40] <seb128> kenvandine, hey, there or out?
[13:40] <seb128> I know you are travelling but you were active and didn't send your summary :p
[13:41] <seb128> (though it's probably around the lines of "GUADEC & Montreal")
[13:42] <seb128> I guess he's not
[13:42] <seb128> #topic laney
[13:42] <seb128> • was at GUADEC some more, worked on the (internal) trip report for that, public one is going to be posted by w_illcooke soon
[13:42] <seb128> • fixed a couple of glib bugs and reviewed some easy MRs, proposed one of our distro patches as MR (was a patch on bugzilla that got ignored)
[13:42] <seb128> • got some reviews on systemd things, addressed the comments raised there
[13:42] <seb128> • uploaded a partial revert of vte2.91 to bionic, it caused an API change and b_dmurray complained about that (this change remains in cosmic)
[13:42] <seb128> • getting ready to finally push T_revinho's git commits, just testing the source packages build ...
[13:42] <seb128> ⛅
[13:42] <seb128> #topic oSoMoN
[13:42] <seb128> oSoMoN, hey
[13:42] <oSoMoN> hey
[13:42] <oSoMoN> • chromium
[13:42] <oSoMoN>   ∘ updated license in the snap store and filed bug #1781013 and bug #1781014 against lp:snapstore
[13:42] <oSoMoN>   ∘ reported to Robert that custom SPDX expressions are displayed in gnome-software as a flattened list, which doesn't really convey the meaning of the expression if it's anything else than a list of AND, this is an upstream issue, filed https://gitlab.gnome.org/GNOME/gnome-software/issues/421
[13:42] <gitlab-bot> GNOME issue 421 in gnome-software "Custom SPDX expression represented as a flattened list of licenses" (comments: 0) [Opened]
[13:43] <oSoMoN>   ∘ conversations with Robin (web team) and mpt to identify a reliable way for snapcraft.io to determine whether the user's machine can handle the snap:// protocol
[13:43] <oSoMoN>   ∘ tested stable update (67.0.3396.99) and handed over to Chris for publication to {bionic,artful,xenial}-security
[13:43] <oSoMoN>   ∘ updated beta to 68.0.3440.59
[13:43] <oSoMoN>   ∘ updated dev to 69.0.3486.0
[13:43] <oSoMoN>   ∘ OSK: looked into a couple of issues on the gnome-shell side: https://gitlab.gnome.org/GNOME/gnome-shell/issues/135 and https://gitlab.gnome.org/GNOME/gnome-shell/issues/409
[13:43] <gitlab-bot> GNOME issue 135 in gnome-shell "OSK: [Xorg] Unable to type capital letters" (comments: 9) [Opened]
[13:43] <gitlab-bot> GNOME issue 409 in gnome-shell "OSK lacks a Tab key" (comments: 3) [2. Needs Design, Opened]
[13:43] <oSoMoN> • libreoffice
[13:43] <oSoMoN>   ∘ experimented with an updated patch for bug #1766192, and requested comments on libreoffice mailing list, got good feedback and a better approach, so I removed the patch from the snap for now
[13:43] <oSoMoN>   ∘ filed and fixed bug #1781995
[13:43] <oSoMoN>   ∘ looked into https://github.com/ubuntu/gtk-communitheme/issues/350 and pushed a tentative fix
[13:43] <gitlab-bot> ubuntu issue 350 in gtk-communitheme "libreoffice not opening properly on communitheme.snap" (comments: 12) [Snap, Open]
[13:43] <oSoMoN> • snaps
[13:43] <oSoMoN>   ∘ updated play0ad snap to run only a zenity dialog suggesting to uninstall and install 0ad instead, and documented the process at https://forum.snapcraft.io/t/zenity-dialogs-in-a-snap/6359
[13:43] <oSoMoN> 🍉
[13:44] <seb128> thanks oSoMoN
[13:44] <seb128> #topic seb128
[13:44] <seb128> • one swap day after GUADEC
[13:44] <seb128> • some HR related work following the reviews cycle
[13:44] <seb128> • updated the apport translation template in bionic in preparation for new strings to be added in a SRU
[13:44] <seb128> • helped unblocking the pulseaudio/cosmic migration
[13:44] <seb128> • verified the french langpacks SRU candidate for xenial
[13:44] <seb128> • backported/SRUed an udisks fix for iso mounting - https://launchpad.net/bugs/1779238
[13:44] <seb128> • sponsored a SRU fix from andyroc_k https://code.launchpad.net/~azzar1/software-properties/fix-1768797/+merge/348460?
[13:44] <seb128> • uploaded first login wizard enabling for Unity
[13:44] <seb128> • some bionic SRUs verifications
[13:44] <seb128> #topic tkamppeter
[13:44] <seb128> tkamppeter, hey
[13:46] <tkamppeter> hi
[13:46] <tkamppeter> - cups-filters: Released version 1.20.4.Got packaged for Debian, so it should have synced into Cosmic.
[13:46] <tkamppeter> - cups-filters: Tests for investigating printing behavior on auto-discovered driverless printers, especially what happens with a remote CUPS queue, when pdftopdf is running both on the client and on the server and options could get executed twice. Posted on CUPS developer mailing list about this.
[13:46] <tkamppeter> - Google Summer of Code 2018: Mentoring of the students on Common Print Dialog Backends and printer auto-selection by job.
[13:46] <tkamppeter> - Bugs.
[13:47] <seb128> thanks tkamppeter
[13:47] <seb128> #topic trevinho
[13:47] <seb128> 👯 GUADEC: continued discussions, BoFs:
[13:47] <seb128>   🏹 Started hacking on supporting multi-screen (for multi-DPI on X11)
[13:47] <seb128> on mutter
[13:47] <seb128>   🏹 Proposed various suggestions for multi-monitor and multi-workspace
[13:47] <seb128> in g-s
[13:47] <seb128>   🏹 Discussed on tech bits for X11 fractional scaling
[13:48] <seb128>   🏹 Discussed with gnome-shell designers for various shell things including
[13:48] <seb128>     windows filtering and better keyboard usage, started the
[13:48] <seb128> implementation for
[13:48] <seb128>     blurring the desktop (will be used by both activities and lockscreen)
[13:48] <seb128>     🔗 https://gitlab.gnome.org/GNOME/gnome-shell/issues/288
[13:48] <seb128>     🔗 https://gitlab.gnome.org/GNOME/gnome-shell/issues/408
[13:48] <seb128> 📂 Nautilus:
[13:48] <gitlab-bot> GNOME issue 288 in gnome-shell "Readability of the search results depends on the wallpaper" (comments: 9) [1. Bug, 2. Needs Design, 8. Accessibility, To Do, Closed]
[13:48] <seb128>   🏹 Debugging for https://gitlab.gnome.org/GNOME/nautilus/issues/522
[13:48] <seb128>   🏹 Rebased, and added other shell-search fixes to recursive-query-flags PR
[13:48] <seb128>     🔗 https://gitlab.gnome.org/GNOME/nautilus/merge_requests/249
[13:48] <seb128>   🏹 Prepared ubuntu branch with updated patches, crash fix and
[13:48] <gitlab-bot> GNOME issue 408 in gnome-shell "Address legibility issues with Top Bar transparency" (comments: 3) [Opened]
[13:48] <seb128> backports of the
[13:48] <seb128>     patches upstreamed.
[13:48] <seb128>     🔗
[13:48] <seb128> https://code.launchpad.net/~3v1n0/ubuntu/+source/nautilus/+git/nautilus/+merge/349670
[13:48] <seb128> 🐚 Shell world
[13:48] <seb128>   🏹 Updated JS warning fix MP, as per Florian reviews (had some IRL too)
[13:48] <gitlab-bot> GNOME issue 522 in nautilus "Filesystem info is earlier than we get actually know the information" (comments: 0) [Opened]
[13:48] <seb128>   🏹 Updated workspace fixes MPR
[13:48] <gitlab-bot> GNOME issue (Merge request) 249 in nautilus "Recursive query flags" (comments: 26) [3. Review Ready, Opened]
[13:49] <seb128> #topic rlsbugs
[13:49] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-incoming-bug-tasks.html has no desktop entry
[13:49] <seb128> neither has http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-cc-incoming-bug-tasks.html
[13:50] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-tracking-bug-tasks.html the unassigned ones seem to be handler/just need launchpad triaging, I'm going to do that
[13:50] <seb128> and http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-cc-tracking-bug-tasks.html is on shape
[13:50] <seb128> good work team :)
[13:50] <seb128> #topic aob
[13:50] <seb128> any other topic?
[13:51] <didrocks> nothing from me
[13:52] <seb128> k, seems not, let's wrap then
[13:52] <seb128> #endmeeting
[13:52] <meetingology> Meeting ended Tue Jul 17 13:52:21 2018 UTC.
[13:52] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-desktop/2018/ubuntu-desktop.2018-07-17-13.30.moin.txt
[13:52] <seb128> thanks everyone
[13:53] <didrocks> thx!
[13:53] <oSoMoN> thanks!
[14:15] <Wimpress> oSoMoN: Have you started working on making the chromium-ffmpeg-codoces snap?
[14:27] <willcooke> Trevinho, can you point me at the source for your ircbot?
[14:32] <Trevinho> willcooke: https://code.launchpad.net/~3v1n0/ubuntu-bots/gitlab-support
[14:33] <Trevinho> should be updated to be fair..as other changes are only local and I didn't push them
[14:33] <Trevinho> and for github https://code.launchpad.net/~3v1n0/ubuntu-bots/github-support
[14:46] <willcooke> thanks Trevinho
[14:48] <oSoMoN> Wimpress, not yet, on my to-do list
[15:35] <Laney> didrocks: this followTags thing means all the upstream tags end up getting pushed since they're reachable, is that OK to you?
[15:37] <didrocks> Laney: I think it is, I've done it on purpose so that we can still grab the upstream tags from the upstream/latest branch for instance
[15:37] <didrocks> (which could be an interesting info IMHO, wdyt?)
[15:38] <Laney> it's a lot of stuff
[15:38] <Laney> not sure if it matters, maybe not
[15:40] <Trevinho> Laney: my magic command does what we need otherwise
[15:40] <Laney> no it ends up pushing all the tags if you have followtags on
[15:40] <Laney> even if not the next person would do them all anyway
[15:41] <Trevinho>  `git tag | grep -E '^ubuntu/|^debian/|^upstream/' | xargs --no-run-if-empty  git push origin`
[15:41] <Laney> yes
[15:41] <Trevinho> Ah that yes... On push though
[15:41] <Trevinho> not on push tags
[15:42] <Laney> ah well
[15:42] <Laney> tags away
[16:01] <tsimonq2> oSoMoN: Heya! Did you get a chance to look at LibreOffice yet? :)
[16:01] <oSoMoN> tsimonq2, nope, not yet
[16:02] <tsimonq2> oSoMoN: OK, no problem :)
[16:03] <tsimonq2> Thanks.