[05:04] <jibel> Good morning
[05:18] <duflu> Morning jibel 
[05:18] <jibel> Hi duflu 
[05:45] <oSoMoN> good morning desktoppers
[05:47] <seb128> goood morning desktopers
[05:47] <seb128> lut oSoMoN, comment ça va aujourd'hui ?
[05:48] <seb128> hey ricotz , how are you?
[05:49] <ricotz> seb128, hey, a bit sleepy ;P, how are you
[05:53] <oSoMoN> salut seb128, ça va bien, et toi?
[05:53] <oSoMoN> hey ricotz 
[05:54] <ricotz> oSoMoN, hey
[06:01] <seb128> the night has been a bit rough, let's see how the day goes, starting with coffee! 
[06:19] <ricotz> seb128, maybe you have a moment after getting coffee for https://bugs.launchpad.net/ubuntu/+source/vala/+bug/1897901 :)
[06:28] <duflu> Morning oSoMoN and seb128 
[07:18] <marcustomlinson> morning jibel duflu oSoMoN seb128 ricotz
[07:25] <jibel> Hi marcustomlinson
[07:26] <GunnarHj> Good morning seb128! Thoughts about bug #1897858?
[07:35] <duflu> Morning marcustomlinson 
[07:52] <didrocks> good morning
[07:58] <duflu> Hi didrocks 
[07:59] <didrocks> hey duflu 
[08:03] <seb128> hey marcustomlinson, didrocks, duflu, how are you?
[08:03] <marcustomlinson> good thanks you?
[08:03] <seb128> GunnarHj, hey, no opinion about this one, I read over it yesterday but I don't know ibus details much, seems fine to me
[08:03] <duflu> seb128, kind of average. See Mattermost :)
[08:03] <seb128> marcustomlinson, the night was a bit cahotic but alright otherwise
[08:04] <marcustomlinson> seb128: hope the day goes better
[08:04] <seb128> let's see how far coffee carries me
[08:05] <seb128> ricotz, you don't need a ffe for a bugfix update, it's only for feature updates. I will sync but the archive is frozen atm for beta so it's probably not going to be accepted today
[08:06] <didrocks> hey seb128, fine, and you?
[08:06] <didrocks> hey marcustomlinson 
[08:06] <seb128> didrocks, tired but rather ok otherwise :)
[08:06] <ricotz> hey marcustomlinson didrocks duflu 
[08:06] <GunnarHj> seb128: Ok, good. Then I'll probably ask you to sponsor if the release team (Laney?) approves.
[08:06] <didrocks> hey ricotz 
[08:07] <ricotz> seb128, ah, I see, the kept me thinking https://bugs.launchpad.net/ubuntu/+source/vala/+bug/1891318/comments/4 :(
[08:07] <seb128> GunnarHj, try rather chasing they on their channel, L_aney is off until monday
[08:08] <GunnarHj> seb128: Ok, will do.
[08:08] <seb128> ricotz, right, SRU team got a bit more picky, they also don't want to give an exception to the shell because it can breaks extensions :-/
[08:10] <ricotz> seb128, I am still hoping to while keeping 0.48.x in groovy it receives enough testing to be ack'd as focal SRU
[08:11] <GunnarHj> seb128: You can blame me about the SRU team's new approach to gnome-shell if you like. :-/ (The bug which started it was filed and fixed by a first time contributor, and I mentored him.)
[08:12] <seb128> ricotz, right, well you don't need the standing exception, as the comment points out you could document is a standard SRU and have a ppa showing the result of rdepends rebuilds
[08:12] <seb128> GunnarHj, not your fault if gnome-shell upstream includes changes in point updates than can break extensions though...
[08:13] <ricotz> seb128, yeah
[08:15] <GunnarHj> seb128: No, of course not. But if that bug reporter hadn't got help, the bug might still have been open and the SRU team unaware of that regression.
[08:15] <seb128> right
[08:15] <seb128> oh well, it's done now!
[08:16] <GunnarHj> yep
[08:17] <cpaelzer> seb128: hiho, I have a question I'd need your team-subscribing powers for
[08:17] <cpaelzer> https://bugs.launchpad.net/ubuntu/+source/pnm2ppa is part of the overall cups stack it seems
[08:17] <cpaelzer> but it was promoted to main in the dark ages (before team splits)
[08:18] <cpaelzer> therefore so far still the only subscriber is ubuntu-server and we have no experience how to deal with it
[08:18] <cpaelzer> most other "print'y" packages are subscribed by the Desktop team (and in addtion by ubuntu-printing)
[08:18] <cpaelzer> seb128: I wanted to ask if we should transition this one as well (you subscribe yours, I unsubscribe my team)
[08:19] <seb128> cpaelzer, hey, that sounds reasonable, I subscribed desktop-packages, feel free to unsubscribe server
[08:19] <cpaelzer> done and thank you
[10:29] <didrocks> mvo: hey! We have a small PR for you on your very active smb project: https://github.com/mvo5/libsmbclient-go/pull/4 :)
[10:29] <didrocks> it’s small, but dense, we first thought the issue was on smbclient side before noticing the swapping of values :p
[10:31] <mvo> didrocks: woah, happy to review. out of curisoity, what do you use it for? it's a bit of a toy from my early go days
[10:32] <mvo> didrocks: I feel the lack of multithreading in libsmbclient make it not super useful except for special usecases I guess
[10:33] <didrocks> mvo: we are exploring GPO support on ubuntu
[10:33] <didrocks> some part is AD connection
[10:33] <didrocks> the rest is about downloading the GPOs, through samba…
[10:33] <didrocks> we’ll probably add krb5 ticket support
[10:33] <didrocks> (to your project)
[10:34] <mvo> didrocks: woah, cool. I *never* thought this would be used outside of me playing around with cgo :)
[10:35] <didrocks> mvo: heh, there is always a use, and TBH, you rank #2 when googling for smb + golang bindings :p
[10:36] <mvo> didrocks: if you really do this I will go over the code again just to make sure that I apply the knowledge I aquired since  I originally wrote it
[10:36] <didrocks> mvo: sounds excellent!
[11:26] <didrocks> mvo: ofc, smbclient is returning an empty SMBFILE and the dreaded 'file exists' errno on existing file or directory, so we can’t really do anything with it right now (as reported on https://github.com/mvo5/libsmbclient-go/issues/1)
[11:27] <didrocks> this is puzzling why smbclient is reporting this
[11:45] <didrocks> (same issue with a local desktop smb share, so not AD related)
[12:45] <mvo> didrocks: hm, hm, I see new PRs, looking
[13:00] <mvo> didrocks: also will try to play with this, just out of curisity, what are you testing against?
[13:01] <mvo> didrocks: samba? a real windows?
[13:08] <didrocks> mvo: we tried both: samba (local desktop share integration) and AD
[13:09] <mvo> didrocks: thanks, I see what I can do, defintiely strange
[13:09] <didrocks> yeah, indeed
[13:20]  * ricotz cries about https://github.com/ubuntu/libreoffice-style-yaru-fullcolor/issues/115
[13:20] <ricotz> hellsworth, hey, I was about to mention the running builds for libreofice 7.0.2~rc2, but ^ :(
[13:33] <didrocks> mvo: so, in pure C, it returns also EEXISTS as errno
[13:33] <didrocks> but it does return a fp
[13:33] <didrocks> my theory is that cgo return "" for first object if errno isn’t null
[13:33] <didrocks> (well, return nil)
[13:34] <mvo> didrocks: that sounds plausible
[13:34] <mvo> didrocks: I'm doing a quick check with older go versions now to see when this broke
[13:36] <didrocks> mvo: ok, if I replace d, err := C.my_smbc_opendir(c.ctx, C.CString(durl)) by d := C.my_smbc_opendir(c.ctx, C.CString(durl)), d now isn’t nil
[13:36] <didrocks> so trying to get the errno will nilify the returned object (as Go standard practice)
[13:36] <didrocks> annoying Cgo does that for you
[13:37] <didrocks> the issue is that smb never returns a non 0 errno
[13:38] <mvo> didrocks: woah, super interessting find
[13:38] <didrocks> I never noticed it, maybe that changed over Go version
[13:38] <didrocks> because I trust that you code used to work :)
[13:39] <didrocks> but annoying in that case, the only way to know something went wrong is to check the returned value
[13:39] <didrocks> but you don’t know which kind of error you got
[13:39] <jibel> it's schrondingo, if you cannot watch both the object and its error ;)
[13:42] <didrocks> confirmed on https://utcc.utoronto.ca/~cks/space/blog/programming/GoCgoErrorReturns
[13:43] <mvo> didrocks: cool
[13:43] <didrocks> well, unsure how cool this is :p but it seems we have to change to not check error and check the returned object, opacifying any error
[13:43] <didrocks> we can propose a PR with this
[13:44] <mvo> didrocks: sounds good to me, I will see if I can enable GH actions to run the tests by default
[13:45] <didrocks> mvo: great! zsys has some example of GH actions with go if you need them
[14:06] <didrocks> ok. let’s close mvo's bug #1 :p
[14:07] <didrocks> (your tests are failing btw, segfault, we don’t touch that, or the Go style for now (underscore in variable names!!! no comment on public method!!!) :))
[14:15] <mvo> didrocks: just pushed https://github.com/mvo5/libsmbclient-go/pull/6 that should fix this
[14:15] <mvo> didrocks: give it time, this was dormant for 7y ;)
[14:15] <didrocks> ahah :)
[14:15] <jibel> mvo, https://github.com/mvo5/libsmbclient-go/pull/7 
[14:15] <didrocks> it never had that much PR in one day :p
[14:15]  * mvo hugs jibel and didrocks 
[14:15] <didrocks> happy that we got it working
[14:16]  * didrocks hugs mvo back
[14:16] <mvo> didrocks: it never had any PR!
[14:16] <didrocks> heh
[14:16] <didrocks> thanks for bootstrapping that work, it saves us time
[14:16] <jibel> Yay we're top contributors :)
[14:16] <didrocks> haha
[14:17] <mvo> didrocks, jibel no more eexists error in the testsuite after your PR! 
[14:21] <jibel> heh, glad to resurrect a project and fix the testsuite after 7y
[14:36] <oSoMoN> seb128, you've probably seen it in #debian-gnome/trello, but just in case: the tepl, gedit and gedit-plugins updates are ready in salsa
[14:37] <seb128> oSoMoN, thanks!
[14:47] <hellsworth> good morning desktopers
[14:47] <oSoMoN> hey hellsworth 
[14:48] <hellsworth> hi there oSoMoN 
[14:50] <hellsworth> ricotz: oh dear. thanks for the heads up
[15:34] <oSoMoN> seb128, the trello card for tracker-miners says 2.3.5, but there's a 3.0 release for both tracker and tracker-miners, is there a reason not to go to 3.0 ?
[15:58] <oSoMoN> seb128, pango 1.46.2 is already in Debian unstable, so we can sync after the beta freeze is over
[15:58] <oSoMoN> there's a 1.47.0 upstream release, do we want that?
[15:59] <oSoMoN> it appears to mostly add new APIs (https://download.gnome.org/sources/pango/1.47/pango-1.47.0.news)
[16:15] <seb128> oSoMoN, not a new serie this cycle no? unless they changed versionning
[16:15] <seb128> tracker we said we would avoid the new 3 serie this cycle
[16:15] <seb128> unsure if miner needs to match the service
[16:41] <oSoMoN> yeah, nevermind that stupid question about tracker 3, I remember we agreed not to go for that new series