[09:18] <TJ-> Seeing big problems with unconfied snaps causing this and other related issues: "ssh: symbol lookup error: /snap/core18/current/lib/x86_64-linux-gnu/libpthread.so.0: undefined symbol: __libc_vfork, version GLIBC_PRIVATE']"
[09:18] <TJ-> see it wwas hit in microstack and addressed partially with bug #1860660
[10:45] <lotuspsychje> bug #1868359 duped to the main bug
[13:24] <lotuspsychje> sveinse: https://ubuntu.com/blog/canonical-technical-support-during-the-covid-19-pandemic
[17:59] <nael_n> A few weeks ago, following the decision to ship gnome-software as a snap package (called snap-store) rather than an APT package, and the decision to ship gnome-{calculator,logs,characters} as APT packages rather than snap packages, I mentioned here that regularly updating my 20.04 setup left me with two versions of the aforementioned applications,
[17:59] <nael_n> e.g. two Calculators, the snap version and the deb version. This is still the case, and we are past UserInterfaceFreeze. I'm not sure if it's normal? I also still don't have the snap-store, only the APT gnome-software.
[18:00] <nael_n> lotuspsychje, can you please confirm if it's also still the case on your computer? Maybe it's just me
[18:01] <lotuspsychje> nael_n: after the libc6 crash bug, i had to reinstall fresh, and that wiped away the old calculator
[18:01] <lotuspsychje> nael_n: i now only have the grey/organge one
[18:01] <lotuspsychje> well yellow
[18:03] <nael_n> The yellow one is the APT one. OK, thanks for confirming. I've seen a few videos on youtube of guys with Ubuntu 20.04 desktop that only had the APT Calculator, and a snap-store. I assume you've got the snap-store too, instead of the APT gnome-software?
[18:04] <lotuspsychje> nael_n: the snap store joined, but gnome software is still there
[18:05] <nael_n> The plot thickens. I think I'm gonna ask #ubuntu-desktop if it's normal
[18:06] <lotuspsychje> nael_n: i think ive readed both apt & snap will be on the snap store at final
[18:07] <nael_n> What do you mean? I've read that the snap store will be able to install and update both snap applications and APT packages
[18:08] <lotuspsychje> yeah
[18:08] <lotuspsychje> but sure, ask away, we read so much...
[23:38] <nael_n> lotuspsychje: got no reply from #ubuntu-desktop so I've filled bug 1868409 against the source package for the ubuntu-desktop binary package (which installs the gnome-{calculator,logs,characters} packages as recommended dependencies)


[00:50] <johnsonshi> What is the upstream team's planned cutoff date for the 20.3 release of cloud-init? I looked at the bi-weekly meetings, the cloud-init docs, and ubuntu wiki, but I couldn't find a projected release timeline.
[00:50] <johnsonshi> I'm assuming the following historical precedent, the cutoff date for 20.3 will be sometime soon (next 2-3 weeks)?
[12:11] <meena> "when it's ready" ?
[15:49] <paride> smoser, hey, I'm reviewing https://github.com/canonical/uss-tableflip/pull/57 and wonder where get-orig-tarball comes from
[15:52] <smoser> https://gist.github.com/smoser/fa77f61a2b650d115b5fc2a8ab028ede
[15:52] <smoser> i'm fine if you want to pull that in somewhere else.
[15:58] <smoser> paride: and if you know of an easier way to do that, i'm all for it.
[15:58] <smoser> its suprisingly difficult in my experience to find an orig tarball.
[16:06] <smoser> paride: do you know what the correct behavior is if upstream has a debian/ in the tarball ?
[16:07] <smoser> does build-package extract the debian.tar.gz over the top? or remove the existing and then extract
[16:10] <smoser> as we should make build-package do the right thing.
[17:08] <chillysurfer> hello, all! could i get a review for merge on this pr? thanks in advance! smoser reviewed some time ago but not sure if another maintainer needs to check it out as well
[17:08] <chillysurfer> https://github.com/canonical/cloud-init/pull/509 forgot the pr link
[18:00] <johnsonshi> Ooops I got logged off so I would not have been able to see whether there was a response regarding the SRU cutoff date. :)
[18:01] <johnsonshi> When is the projected SRU/release cut off date for cloud-init by the way?
[18:14] <johnsonshi> (for 20.3).
[18:33] <rick_h> johnsonshi:  soon, we're going to write up the announcement to prepare it tomorrow I think
[18:33] <rick_h> johnsonshi:  so we're looking this week at WIP that needs to land and try to get a sha that's ready before EOW
[18:34] <johnsonshi> rick_h: Thanks! So the likely timeline for the cutoff date is very soon?
[18:34] <rick_h> johnsonshi:  this week for sure
[18:34] <rick_h> johnsonshi:  what are you wanting to get in?
[18:35] <johnsonshi> rick_h: Thanks! Just asking because I've got a couple of internal teammates asking about the cutoff date to align priorities.
[18:35] <rick_h> johnsonshi:  ah ok. Let me know if there's anything we want to make sure and we'll try to help review/etc to get it in.
[18:40] <AnhVoMSFT> rick_h: when will the next SRU be after this one?
[18:43] <rick_h> AnhVoMSFT:  so after that we've got a project to dev the hotplug support through and the SRU will be after that. Maybe by end of cycle Oct?
[18:44] <AnhVoMSFT> thanks rick_h
[18:45] <AnhVoMSFT> If it's at all feasible it would be nice to land this one for this SRU https://github.com/canonical/cloud-init/pull/529
[18:48] <rick_h> AnhVoMSFT:  ty, will do. Dan was trying to get to it before his holiday but we spoke today about getting it picked up by others. We'll get eyes on it.
[20:08] <johnsonshi> Would the upstream team be open to allowing the Azure apply_network_config option to be set through Azure instance metadata? Referring to https://bugs.launchpad.net/cloud-init/+bug/1889112
[20:28] <johnsonshi> The Azure datasource's apply_network_config flag determines whether cloud-init is supposed to set up the instance's networking stack by querying IMDS.
[20:28] <johnsonshi> As of now, this flag is only read by cloud-init from the disk configs at /etc/cloud/cloud.cfg.d/*.cfg.
[20:29] <johnsonshi> By default, Azure apply_network_config flag is set to true for the Ubuntu 18.04 LTS images published on Azure.
[20:43] <johnsonshi> A customer that wants to "opt out" of this flag cannot do it during deployment time, as this config cannot be set using the Azure datasource.


[15:00] <rbalint> o/
[15:00] <slyon> o/
[15:00] <mclemenceau> o/
[15:00] <sil2100> o/
[15:00] <juliank> o//
[15:01] <waveform> o/
[15:03] <juliank> o-=
[15:03] <rbalint> o<-<
[15:03] <sil2100> #startmeeting Weekly Ubuntu Foundations team
[15:03] <meetingology> Meeting started Thu Oct 15 15:03:55 2020 UTC.  The chair is sil2100. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[15:03] <meetingology> Available commands: action commands idea info link nick
[15:04] <sil2100> #topic Lightning rounds
[15:04] <sil2100> echo $(shuf -e vorlon bdmurray xnox tdaitx doko sil2100 rbalint infinity mwhudson juliank waveform slyon)
[15:04] <sil2100> doko infinity bdmurray rbalint mwhudson xnox juliank tdaitx slyon vorlon waveform sil2100
[15:05] <sil2100> doko: o/
[15:05] <sil2100> Ok, let's skip doko for now
[15:05] <sil2100> rbalint: ^
[15:05] <rbalint> (short week due to holidays)
[15:05] <rbalint> * verification of many glibc bugs for the Bionic SRU
[15:06] <rbalint> * partner work
[15:06] <rbalint> * MIRs of new lintian dependencies
[15:06] <rbalint> (done)
[15:06] <xnox> uploaded LP: #1899621
[15:06] <xnox> uploaded (LP: #1665384)
[15:06] <xnox> uploaded (LP: #1872186)
[15:06] <xnox> worked on https://bugs.launchpad.net/ubuntu-cdimage/+bug/1899632
[15:06] <xnox> providing efi/grub support for UC20
[15:06] <xnox> done
[15:07] <juliank> oh my turn already?
[15:07] <xnox> yeap
[15:07] <juliank> * more shim review triaging and upstream discussions
[15:07] <juliank> * security work
[15:07] <juliank> * learning vim as I go along
[15:07] <juliank> * 360
[15:07] <juliank> * python-apt 2.1.4 release
[15:07] <juliank> (done)
[15:07] <tdaitx> * synced openjdk-8 and openjdk-11 repositories
[15:07] <tdaitx>   - add missing uploads and new releases
[15:07] <tdaitx>   - created gbp repo for openjdk-lts
[15:07] <tdaitx> * got openjdk-11 and -8 migrated into groovy; had to retry some failing tests
[15:07] <tdaitx> * investigated popularity-contest, removed all use of ubuntu addresses and left empty fields so debian does not get spammed by our users
[15:07] <tdaitx>   - now testing upgrade paths
[15:07] <tdaitx> Other:
[15:07] <tdaitx> - got a usb-c to hdmi dongle that does 4k 60hz
[15:07] <tdaitx> - being punished by pulseaudio and echo-cancel module
[15:07] <tdaitx> (done)
[15:07] <slyon> - 360s
[15:07] <slyon> - Fixed klibc FTBFS, needs review/sponsor
[15:07] <slyon> - Some s390-tools SRU handholding
[15:07] <slyon> - Prepared cloud-init MAAS/OVS fix, PR#608
[15:07] <slyon> - Learning about s390x architecture/vocabulary
[15:07] <slyon> [15:07] <slyon> - 0.100 Focal SRU verification, LP: #1894197
[15:07] <slyon> - Found solution for MAAS/OVS/PXE bug #1898997
[15:07] <slyon>   * landed fix in Groovy via 0.100-0ubuntu5
[15:07] <slyon>   * prepared new SRU with fix for Focal, needs sponsor
[15:07] <slyon>     https://code.launchpad.net/~slyon/netplan/+git/ubuntu/+merge/392290
[15:07] <slyon> (done)
[15:07] <vorlon>  * short week, US holiday on Monday and was out on Tuesday
[15:07] <vorlon>  * fixing up various corner case boot issues with groovy images (LP: #1886148, LP: #1899308)
[15:07] <vorlon>  * reviews for release
[15:08] <vorlon> (done)
[15:08] <sil2100> waveform: ^
[15:08] <waveform> * Dog-fooding the pi desktop image; have only resorted to laptop for three video calls this week; everything else done on a variety of pi4's running the desktop
[15:08] <waveform> * Working on FTBFS for numpy (final issue)
[15:08] <waveform> * Tweaks for pi-bluetooth MIR (LP: #1897920)
[15:08] <waveform> * Reported LP: #1899953 for groovy release notes
[15:08] <waveform> * Reported LP: #1899962 for groovy release notes
[15:08] <waveform> * Tested "more new stuff", including fixes in flash-kernel and linux-firmware-raspi2
[15:08] <waveform> * Still working on one remaining bluetooth failure
[15:08] <xnox> vorlon:  btw so far my extra attempts were unfruitful
[15:08] <waveform> (done)
[15:08] <sil2100> - SRU reviews and releases
[15:08] <sil2100> - Queue reviews for groovy
[15:08] <sil2100> - Looking into the fix for the keyboard layout selection issues
[15:08] <sil2100> - 360
[15:08] <sil2100> - Fixed FTBFS of libpsl
[15:08] <sil2100> - Pi Desktop:
[15:08] <sil2100>   * Additional fixes for pi desktop - adding the 1GB swapfile
[15:08] <vorlon> xnox: ok; but you didn't say in the bug what those attempts were?
[15:08] <sil2100>   * Sponsoring some uploads for Dave
[15:08] <sil2100> - 20.10 preparation
[15:09] <sil2100>   * Preparing to start final base langpack export
[15:09] <sil2100>   * Release meeting, touch base on status before final freeze
[15:09] <sil2100>   * Sending out reminder for release notes update
[15:09] <sil2100>   * Working though the checklist, getting in touch with the webteam etc.
[15:09] <xnox> vorlon:  vmware easy-not-actually-easy-install
[15:09] <sil2100> - Further work on the snap promoter scripting, trying to handle per-arch cases better
[15:09] <sil2100> (done)
[15:10] <sil2100> Ok, any more questions about status?
[15:10] <doko>  - started with python3.9, test ppa builds, filing bugs, fixing bugs
[15:10] <doko>  - preparing Python2 and Python3 SRUs for bionic
[15:10] <doko>  - preparing separate python3.9 SRU for focal
[15:10] <doko>  - some ftbfs fixes
[15:10] <doko> (done)
[15:11] <sil2100> #topic Release Incoming Bugs
[15:11] <sil2100> #link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-gg-incoming-bug-tasks.html#foundations-bugs
[15:11] <sil2100> http://launchpad.net/bugs/1890435
[15:12] <doko> blocked
[15:13] <sil2100> Ok, should we leave it there then?
[15:16] <sil2100> This needs more investigation and doko is on it, so yeah
[15:16] <sil2100> Moving on
[15:17] <sil2100> https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538 - I guess this one is still not reproducible by anyone of us?
[15:17] <slyon> unfortunately, no
[15:19] <sil2100> Ok, continuing
[15:19] <sil2100> https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1899462 <- this looks new!
[15:20] <vorlon> it looks already targeted
[15:21] <xnox> juliank:  should take it =)
[15:21] <sil2100> Is it carded?
[15:21] <xnox> and he did =)
[15:21] <vorlon> and I'm not sure about the bug title accuracy
[15:21] <mclemenceau> not yet
[15:21] <sil2100> mclemenceau: can you card it? ;)
[15:21] <vorlon> "mount: /var/lib/grub/esp: special device /dev/disk/by-id/ata-KINGSTON_SA400S37480G_50026B73804E7AF8-part1 does not exist."
[15:22] <juliank> vorlon: irrelevant-ish
[15:22] <vorlon> juliank: which part? :)
[15:22] <juliank> vorlon: the entire line
[15:22] <juliank> vorlon: about the nonexisting device
[15:23] <juliank> vorlon: What happens is that this partition goes away, and no partitions are recognized as ESPs and hence you don't get choices
[15:23] <vorlon> ... goes away
[15:23] <juliank> we did debug all this in #ubuntu-devel :)
[15:23] <vorlon> well, that would've been a better thing to put in the bug description than the debug output ;)
[15:23] <vorlon> anyway
[15:23] <vorlon> I guess you agree this needs fixing?
[15:24] <sil2100> Let's make the bug description better and pull it in then o/
[15:24] <juliank> yes
[15:24] <sil2100> Moving on
[15:24] <sil2100> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1897991
[15:24] <sil2100> Whoop
[15:24] <sil2100> Wrong one
[15:24] <sil2100> https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1898342
[15:24] <sil2100> This one
[15:25] <juliank> how is this a bug?
[15:25] <juliank> person gets offered to install to 3 locations, says cancel, and it's cancelled?
[15:25] <sil2100> I think the bug is that he got the prompt
[15:26] <sil2100> But this bug isn't very informative
[15:26] <vorlon> I don't see enough information there to proceed, yeah
[15:27] <sil2100> Should we ask for more info and leave it?
[15:27] <vorlon> and do we think this is related to LP: #1885414?
[15:27] <xnox> i asked for more info
[15:28] <vorlon> (or duplicate of)
[15:28] <xnox> hmmmmmmm
[15:29] <sil2100> Weirdness!
[15:29] <sil2100> Anyway, moving on for now: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1899026
[15:31] <sil2100> Let's card it then
[15:32] <sil2100> https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1899507
[15:32] <mclemenceau> ok
[15:35] <sil2100> mclemenceau: can you run your magic script on this one too?
[15:35] <mclemenceau> sure
[15:35] <mclemenceau> done
[15:35] <sil2100> Should we also look at ff or skip because of release week?
[15:36] <vorlon> if we have time, we might as well look at them; processing the queue doesn't mean we're committed to working on them during release week
[15:37] <sil2100> #link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ff-incoming-bug-tasks.html#foundations-bugs
[15:37] <sil2100> True!
[15:37] <sil2100> So skipping those that are already targeted it seems
[15:37] <sil2100> https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1898729
[15:37] <vorlon> if they're already targeted the tag should be removed
[15:37] <mclemenceau> this one is already carded
[15:38] <sil2100> This one seems to have a card too!
[15:38] <sil2100> Removing the tags for those
[15:38] <vorlon> ok, targeting the bug then
[15:38] <sil2100> https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1898614 <- ok, this one seems Incomplete still
[15:39] <sil2100> I guess it requires mwhudson to take a look at the logs now
[15:40] <sil2100> Switched it to 'New'
[15:41] <sil2100> I don't know what our process here is - if we're waiting for Michael to check the logs, should we target it for focal already?
[15:41] <sil2100> Or leave as is before we know more?
[15:41] <vorlon> if we think the bug as described is serious enough to commit to, then we should target it now
[15:42] <vorlon> if the resolution is he looks at the logs and determines there's no action to take, that's fine
[15:42] <sil2100> Targeting then, but mclemenceau will have to card it! :)
[15:42] <mclemenceau> ok then
[15:43] <sil2100> The last one was carded already, just needed targeting
[15:43] <slyon> I removed the tags
[15:43] <sil2100> And Brian was looking at it
[15:43] <sil2100> Ok, I think we're done o/
[15:43] <sil2100> #topic Team proposed-migration report
[15:43] <sil2100> It's almost Final Freeze, but I guess it makes sense to take a look anyway
[15:44] <sil2100> vorlon: o/
[15:44] <vorlon> [LINK] https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses_by_team.html#foundations-bugs
[15:44]  * juliank hides
[15:44] <vorlon> only MIRs to look at
[15:44] <vorlon> rbalint: any updates from your side on these? I see the MIRs are all filed at leat
[15:44] <vorlon> least
[15:45] <vorlon> the gce one is assigned to the security team
[15:45] <rbalint> lintian mirs are assigned to doko, guest-agent to the security team
[15:45] <vorlon> doko: will you have time to review the lintian MIRs, so we can possibly resolve this before release?
[15:45] <vorlon> (otherwise, I have to hack my script for removal of unwanted i386 binaries)
[15:46] <vorlon> (or maybe I don't, removing the binaries from groovy and letting them respawn in hh is fine if it's not going to migrate...)
[15:47] <xnox> and zlib is mine
[15:47] <xnox> juliank:  you don't want to take aptdaemon?
[15:47] <doko> vorlon: yes, doing the pi one today, the others tomorrow
[15:47] <vorlon> doko: thanks
[15:47] <juliank> xnox: I did retry aptdaemon just now
[15:47] <vorlon> xnox, juliank: I already retried the aptdaemon failure
[15:47] <vorlon> heh
[15:48] <juliank> or we badtest armhf as it's like 50% flaky
[15:49] <juliank> i think i just retried a second time by clicking wrong link in history
[15:50] <vorlon> anyway, that's all for proposed-migration
[15:50] <vorlon> sil2100:
[15:52] <sil2100> o/
[15:52] <sil2100> So the assigned FTBFS issues seem to have been resolved
[15:52] <sil2100> #topic AOB
[15:53] <sil2100> I'm half-off tomorrow, and starting Monday we're on the usual virtual release sprint thingy
[15:53] <vorlon> "resolved" - https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20200925-groovy-groovy.html#foundations-bugs still shows 5 failures?
[15:53] <rbalint> i'll be out on Monday, and next Friday
[15:53] <vorlon> is the report just not updated?
[15:54] <doko> vorlon: the creation date is on the top
[15:54] <sil2100> Oh, I only checked the jira card
[15:54] <sil2100> And all the ones that were there were fixed, hm, but maybe not all got carded?
[15:54] <vorlon> so the report is reasonably current and the "done" status is a lie :)
[15:54] <sil2100> Ah!
[15:54] <slyon> klibc is fixed, but needs sponsoring (probably in hh): https://paste.ubuntu.com/p/TCS9csM656/
[15:55] <sil2100> Sorry
[15:55] <sil2100> I mis-read jira!
[15:55] <sil2100> Since the tasks are 'striked through' so I thought they're done
[15:55] <sil2100> So yeah, numpy in progress - waveform I guess that was yours?
[15:55] <vorlon> slyon: we wouldn't want to fix this is groovy via an upstream merge; any chance of a cherry-pick fix?  Because we do want packages buildable in release
[15:55] <waveform> yup, nearly there with the numpy one - final fix looks like it's worked - I'm just confirming the output
[15:56] <sil2100> waveform: give us a poke if you need sponsoring o/
[15:56] <waveform> will do
[15:56] <xnox> slyon: yeah, i'm not confident to merge new klibc
[15:57] <slyon> vorlon: yeah. I can look into finding a smaller fix
[15:57] <vorlon> slyon: thanks
[15:59] <sil2100> What about python-apt? I see waveform mentioned you to review something?
[15:59] <sil2100> By 'you' I meant juliank
[16:00] <juliank> I just released python-apt 2.1.4 with waveform's changes
[16:00] <rbalint> fixing strace would have been too intrusive, so i'm uploading 5.9 for a 0-day sru (like for focal :-\ but now we'd be running ahead of Debian)
[16:00] <juliank> they've been in groovy for a while already
[16:01] <sil2100> rbalint: no minimal change to get it fixed I guess?
[16:01] <sil2100> Ok, so I guess it's all under control at least
[16:01] <sil2100> Now we should be 'done' with the FTBFS
[16:01] <sil2100> ;)
[16:01] <sil2100> Anything else?
[16:02] <sil2100> Going once!
[16:02] <sil2100> Going twice!
[16:02] <sil2100> ...
[16:02] <rbalint> sil2100, no small fix for strace that would make sense
[16:02] <sil2100> #endmeeting
[16:02] <meetingology> Meeting ended Thu Oct 15 16:02:54 2020 UTC.
[16:02] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2020/ubuntu-meeting.2020-10-15-15.03.moin.txt
[16:03] <sil2100> Thanks guys o/
[16:03] <rbalint> o/


[00:44] <KGB-0> libsoup signed tags 8296eed Jeremy Bicha upstream/2.74.1 * Upstream version 2.74.1 * https://deb.li/3YNH1
[00:45] <KGB-0> libsoup upstream/latest 3ed0d71 Jeremy Bicha * pushed 10 commits (first 5 follow) * https://deb.li/DLs4
[00:45] <KGB-0> libsoup upstream/latest 36f23cc Patrick Griffis libsoup/soup-session.c * docs: Refer to 2.74.0 for ssl changes * https://deb.li/iW4bV
[00:45] <KGB-0> libsoup upstream/latest e190e70 Christoph Reiter meson.build * meson: skip the fallback for sysprof on Windows * https://deb.li/iNvg
[00:45] <KGB-0> libsoup upstream/latest 80a7e4f Rico Tzschichholz libsoup/ Soup-2.4-custom.vala Soup-2.4.metadata * vala: Better fix for #234 supporting older vala * https://deb.li/3QK7l
[00:45] <KGB-0> libsoup upstream/latest 47106e6 Alan Mortensen po/da.po * Updated Danish translation * https://deb.li/14nx
[00:46] <KGB-0> libsoup upstream/latest c1f6422 Patrick Griffis docs/reference/meson.build * build: Fix generating docs * https://deb.li/3VLdE
[00:46] <KGB-0> libsoup pristine-tar ea5ce51 Jeremy Bicha libsoup2.4_2.74.1.orig.tar.xz.delta libsoup2.4_2.74.1.orig.tar.xz.id * pristine-tar data for libsoup2.4_2.74.1.orig.tar.xz * https://deb.li/3RNFD
[02:00] <callmepk> good morning
[02:09] <duflu> Morning callmepk
[02:09] <callmepk> hi duflu
[06:35] <oSoMoN> good morning desktoppers
[06:35] <duflu> Hi oSoMoN
[06:35] <oSoMoN> hey duflu
[06:37] <callmepk> hi oSoMoN
[06:37] <oSoMoN> hey callmepk
[06:58] <didrocks> good morning
[07:01] <jpnurmi> good morning
[07:02] <jpnurmi> hey didrocks oSoMoN callmepk duflu
[07:05] <didrocks> hey jpnurmi
[07:05] <duflu> Hi didrocks and jpnurmi
[07:08] <oSoMoN> salut didrocks, good morning jpnurmi
[07:14] <callmepk> hi diddledani jpnurmi
[07:14] <callmepk> oops
[07:14] <callmepk> hi didrocks
[07:16] <didrocks> hey callmepk
[07:16] <didrocks> salut oSoMoN, hey duflu
[07:24] <jibel> Good morning flaks
[07:25] <jibel> folks*
[07:25] <jibel> fingers are still cold :)
[07:26] <didrocks> salut jibel
[07:27] <duflu> Hi jibel
[07:28] <callmepk> hi jibel
[07:28] <seb128> goood morning desktopers
[07:33] <duflu> Hi seb128
[07:34] <didrocks> salut seb128
[07:35] <callmepk> hi seb128
[07:39] <ricotz> hello desktopers :)
[07:40] <didrocks> hey ricotz
[07:42] <seb128> hey duflu callmepk ricotz
[07:42] <seb128> lut didrocks
[07:42] <seb128> how are you? had a nice weekend?
[07:44] <duflu> seb128, not great.  That's one part of a house you don't expect to fail
[07:44] <duflu> How about you, seb128 ?
[07:44] <seb128> duflu, :-(
[07:45] <didrocks> had a good week-end, full of house work, as usual, but good, and you?
[07:45] <seb128> duflu, tired, we had nice time in France during school holidays, but driving back yesterday and I was woken up at 1am and 6am so starting the week a bit short on sleep
[07:45] <duflu> seb128, I'm also in that boat with you
[07:48] <duflu> On the upside, we have got so much rain this year that it causes sinkholes
[11:24] <seb128> for those who wonder why their GNOME / meson snaps started failing to build
[11:24] <seb128> https://github.com/mesonbuild/meson/issues/9441
[11:25] <seb128> basically the way i18n.merge_file is used in GNOME components is incorrect but meson ignored it before and is erroring out now
[11:25] <seb128> kenvandine, ^
[11:28] <seb128> sergiusens, ^ it's somewhat a snapcraft problem since you are pulling in the latest meson automatically. Is there a way from the snapcraft.yaml to specify a meson version to use for the build?
[12:30] <kenvandine> seb128: there is, I think meson-version
[12:31] <seb128> kenvandine, hey, thanks, Sergio replied on the chat, it's just the internet documentation being outdated and not mentioning it
[12:32] <seb128> kenvandine, I will use it to workaround that meson issue unless they revert for 0.60.1
[13:08] <seb128> jibel, could you check if you see anything wrong on the utah network config? the jobs are red on old and new serie with connectivity issue it seems
[13:21] <jibel> seb128, I'll have a look
[13:21] <seb128> jibel, thanks!
[14:36] <jibel> seb128, not sure what's going on, I did some cleanup and restarted libvirtd and dnsmasq
[14:36] <jibel> it looks like VMs are failing to start
[15:00] <KGB-2> evolution-data-server Sebastien Bacher 279959 * commented merge request !5 * https://deb.li/3Vp0s
[15:14] <seb128> jibel, thanks
[16:22] <KGB-1> evolution-data-server Philip Withnall 279965 * commented merge request !5 * https://deb.li/Pbt2
[16:23] <KGB-1> evolution Philip Withnall 279966 * commented merge request !3 * https://deb.li/3JXBC