[00:57] <marathon> @ItzSwirlz, I didn't mean anything negative by that comment, was just noticing what the banner said about being read-only. ;-)
[01:06] <ItzSwirlz> I know you didn't mean anything mean :) but I guess the trello is readonly. But I don't have to be apart of it since that's not my area of work
[01:10] <marathon> Cool :)
[02:11] <jamesh> marathon: the note is indeed about the Trello board: it's used for coordination by the Ubuntu Desktop developer team. We've got other non-read only avenues for community feedback though (IRC, Discourse forum, bug reports, etc)
[02:33] <callmepk> good morning
[03:08] <duflu> Morning callmepk 
[03:09] <callmepk> morning duflu 
[05:32] <jibel> Good morning all
[05:36] <duflu> Morning jibel 
[05:51] <oSoMoN> good morning desktoppers
[05:58] <duflu> Hi oSoMoN 
[05:59] <oSoMoN> hey duflu 
[06:07] <jamesh> oSoMoN: fwiw, it looks like they've changed how the $PIPEWIRE_CONFIG_DIR environment variable is used (making it take precedence over built in options): https://gitlab.freedesktop.org/pipewire/pipewire/-/merge_requests/699
[06:07] <gitlab-bot> PipeWire issue (Merge request) 699 in pipewire "conf: PIPEWIRE_CONFIG_DIR should take precedence if set" [Merged]
[06:07] <ubot3> Merge 699 in pipewire/pipewire "conf: PIPEWIRE_CONFIG_DIR should take precedence if set" [Merged]
[06:07] <jamesh> I also submitted a PR for that object path issue in the portal module: https://gitlab.freedesktop.org/pipewire/pipewire/-/merge_requests/702
[06:07] <gitlab-bot> PipeWire issue (Merge request) 702 in pipewire "module-portal: direct GetConnectionUnixProcessID call to /org/freedesktop/DBus" [Opened]
[06:07] <ubot3> Merge 702 in pipewire/pipewire "module-portal: direct GetConnectionUnixProcessID call to /org/freedesktop/DBus" [Opened]
[06:08] <jamesh> still not sure why that code would have been running within chromium though
[06:23] <oSoMoN> jamesh, thanks!
[07:05] <callmepk> hi jibel oSoMoN
[07:08] <jibel> Hey callmepk, how are you?
[07:08] <didrocks> good morning
[07:08] <didrocks> hey callmepk, salut jibel 
[07:08] <callmepk> hi didrocks 
[07:09] <jibel> salut didrocks 
[07:12] <callmepk> jibel not good... Today's Windows Insider update brick my Windows 10 partition and have to backup my Windows 10 parition while I work
[07:15] <callmepk> good thing is ubuntu-wsl-integration is now in the upload queue
[07:20] <jibel> callmepk, man, that's bad. Does this kind of breakage happens frequently with Insider?
[07:23] <callmepk> jibel it is actually pretty rare... Also Nvidia Driver is the blame for my case, from information of my GSOD the nVidia Driver corupt the Windows Kernel
[07:24] <jamesh> so I guess Nvidia doesn't just cause problems for bleeding-edge Linux kernels
[08:01] <oSoMoN> hey callmepk, salut jibel & didrocks 
[08:03] <jibel> Bonjour oSoMoN 
[08:07] <oSoMoN> callmepk, https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#ubuntu-wsl-integration says "ubuntu-wsl-integration has no binaries on any arch", I'm not sure what that means but I suspect the error message isn't correct, there are binary packages for amd64 and arm64
[08:07] <oSoMoN> didrocks, any clue on what the problem is with this package? ^
[08:18] <jibel> oSoMoN, the binaries had not been accepted. didrocks did it
[08:18] <jibel> oSoMoN, FYI we are fixing the packaging with callmepk and will do another upload
[08:20] <oSoMoN> ack, let me know if you need sponsoring
[08:21] <oSoMoN> so the source package had been accepted, but not the binaries? archive admin is a bit of a black box to me I admit…
[08:31] <marcustomlinson> morning callmepk duflu jibel oSoMoN jamesh didrocks
[08:32] <oSoMoN> good morning marcustomlinson 
[08:32] <jamesh> hi marcustomlinson
[08:33] <jamesh> marcustomlinson: one small step closer to getting the snapd theme API accessible from a snap
[08:34] <duflu> Hi marcustomlinson 
[08:36] <didrocks> oSoMoN: yeah, basically, archive admins review the source package
[08:37] <didrocks> then the package build
[08:37] <didrocks> builds* event
[08:37] <didrocks> even*
[08:37] <didrocks> and only then, once the binaries are published, they are in NEW again (as any new binary package provided by a source)
[08:37] <didrocks> and needs to be rereviewed…
[08:38] <didrocks> and hey oSoMoN, marcustomlinson, jamesh :)
[08:39] <oSoMoN> didrocks, that makes sense, thanks for the explanation
[08:39] <didrocks> yw :)
[08:48] <marcustomlinson> jamesh: 👌
[10:00] <seb128> goood morning desktopers
[10:00] <didrocks> salut seb128, ça va ?
[10:01] <seb128> didrocks, ouais, quelques pbs de connection à IRC mais ça semble réglé ! et toi ?
[10:03] <seb128> seems I should have waited an extra day to review ubuntu-wsl-integration :p
[10:03] <seb128> didrocks, I didn't want to bother you and asked oSoMoN to sponsor so I could NEW review, but seems like that plan didn't work out :p
[10:04] <seb128> oSoMoN, sorry for the distracting you with that one!
[10:05] <oSoMoN> no worries
[10:18] <didrocks> seb128: no worry :) We were doing another check/pre-MIR round anyway :)
[10:19] <seb128> I didn't want to bother callmepk with the trailing ',' but I see you got that changed ;-)
[10:19] <seb128> also nice to see that building with one version of python3 worked, I suggest that but Patrick said it was not working and I wanted to check why today
[10:20]  * seb128 crosses that item for the todolist :-)
[10:20] <didrocks> heh :)
[10:22] <seb128> didrocks, callmepk, dh13 ... we don't plan to try to get that on focal at some point?
[10:22] <seb128> I mean ubuntu-wsl-integration
[10:22] <seb128> (focal only has dh12)
[10:27] <marathon> @jamesh, Thank for the explanation
[10:30] <didrocks> seb128: it’s an easy dh-compat = 12 in that case
[10:31] <didrocks> (we did this for adsys)
[10:31] <seb128> k, I guess it's an easy diff to maintain. I usually go for using 12 since there is no reason we absolutely need to be on the latest for $current
[10:31] <seb128> but yeah, either way works
[10:33] <didrocks> it was at 10 though (not 12)
[10:34] <seb128> yeah, I was just asking if we wanted to stick at 12 to be able to reuse on focal without change
[10:35] <seb128> updating the dh version makes sense, I just didn't want to discourage Patrick by making the reviews comments longer ;-)
[10:38] <didrocks> yeah, we did it via HO and liveshare, it’s more interactive and fun :)
[10:38] <seb128> :-)
[10:43] <didrocks> seb128: ubuntu-wsl-oobe in NEW for you btw!
[10:43] <seb128> didrocks, ah, checking
[11:17] <seb128> didrocks, callmepk, why are bindings for apport or curtin needed to build the package?
[11:21] <seb128> detail but the debian/copyright has 2015 - 2020 where the README has 2021
[11:52] <didrocks> seb128: we are going to do a secondary check once we MIR it, but we need to write a testsuite first which will collect those deps (so this is intended as #2)
[11:53] <didrocks> ack on README, we will update it
[11:56] <seb128> didrocks, thx, I will accept since those are not blocker issues
[11:59] <didrocks> thanks! Interestinly, there is a FTBFS due to subiquitycore not being there
[11:59] <seb128> that dir is empty in the source package but I though that was expected
[12:00] <didrocks> it’s a symlink
[12:00] <didrocks> unsure what happens in debuild -S, should check vendoring
[12:00] <didrocks> worked in a ppa though…
[12:00] <seb128> well external/subiquity/ is empty which is what I meant
[12:00] <seb128> that's the target of the symlink
[12:01] <seb128> if it's meant to include a subiquity checkout and I understand the build-depends on curtin and apport better
[12:02] <didrocks> indeed, it’s supposively pointing to a subdirectory of subiquity (which is in extra/)
[12:02] <didrocks> oh I know
[12:02] <didrocks> my fault, we did run it on jibel’s machine
[12:02] <didrocks> and upload to his ppa
[12:02] <didrocks> but for uploading, I checked it out on my machine
[12:02] <didrocks> and uploading
[12:03] <didrocks> without using git submodules
[12:03] <didrocks> I think debian/rules should fail building the source package without the directory…
[12:03] <seb128> would be nice to avoid such upload errors indeed
[14:43] <hellsworth> good morning desktopers
[14:54] <diddledan> hellsworth: have you seen this news? https://glimpse-editor.org/posts/a-project-on-hiatus/
[14:56] <hellsworth> i sure did, diddledan
[14:57] <hellsworth> too bad really
[14:58] <oSoMoN> good morning hellsworth 
[14:58] <hellsworth> hi there oSoMoN !
[15:01] <jibel> Good morning hellsworth 
[15:01] <hellsworth> good morning jibel :)
[17:13] <bittin_> Hello o/ 
[17:13] <ItzSwirlz> heyo
[17:25] <mitya57> Trevinho: https://launchpad.net/ubuntu/+source/gnome-panel/1:3.41.2-1ubuntu1
[17:25] <mitya57> (dep-waits, as expected)
[17:26] <bittin-> first Ubuntu twitch broadcast in less then an hour http://twitch.tv/ubuntuonair
[17:27] <Trevinho> mitya57: thanks
[18:50] <ItzSwirlz> wa
[18:50] <ItzSwirlz> twitch? awesome
[18:52] <bittin-> ItzSwirlz: yeah they created a twitch account earlier this week and this is the first stream
[20:39] <seb128> GunnarHj, hey, someone on the GNOME IRC pointed you that https://help.ubuntu.com/stable/ubuntu-help/sharing-desktop.html.en needs to be update now that vino is deprecated, is that an ubuntu-docs issue?
[21:05] <GunnarHj> seb128: Didn't see that. No, it's upstream. Just submitted an issue:
[21:05] <GunnarHj> https://gitlab.gnome.org/GNOME/gnome-user-docs/-/issues/124
[21:05] <gitlab-bot> GNOME issue 124 in gnome-user-docs "sharing-desktop.page: Replace vino with gnome-remote-desktop" [Opened]
[21:05] <ubot3> Issue 124 in GNOME/gnome-user-docs "sharing-desktop.page: Replace vino with gnome-remote-desktop" [Opened]
[21:05] <ubot3> Bug 124 in Launchpad itself "dilys needs to know what production and dogfood are" [Medium, Fix Released] https://launchpad.net/bugs/124
[21:28] <seb128> GunnarHj, thanks!