[07:27] <didrocks> good morning
[07:28] <duflu> Hi didrocks
[07:28] <duflu> First as always
[07:28] <duflu> usual
[07:28] <didrocks> yes :)
[07:36] <didrocks> duflu: answered on https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1789356/comments/14. I still need to focus on the installer work, so I gave you details of where to tweak the values
[07:36] <didrocks> duflu: can be that the setGradient with GDesktopEnums.BackgroundShading.VERTICAL isn't the same as background-gradient-direction: vertical;?
[07:37] <didrocks> as you didn't mention the gradient to be inverted (which could have happened between top/bottom) and start in the middle of the screen, have different distribution, could be internal to GNOME Shell and thus more worry
[07:37] <duflu> didrocks, thanks. If I can get the yaru patch(es) working in git then I can definitely test and fix things quickly
[07:37] <didrocks> but as the screen only appear for a split second here, it looked similar enough to me
[07:37] <didrocks> duflu: it's not a yaru patch, it's just a patch in GNOME Shell (look at the commit)
[07:37] <jibel> Good morning
[07:37] <didrocks> salut jibel
[07:37] <duflu> didrocks, yes (un)fortunately gnome-shell often skips so many frames that users don't see the faulty ones there :)
[07:38] <didrocks> yeah ;)
[07:38] <duflu> For me it's 50% of login attempts
[07:38] <duflu> Hi jibel
[07:38] <didrocks> duflu: the Shell doesn't pick anything from the theme itself for that background, hence the patch itself… I added the yaru css part which it should match for reference
[07:38] <didrocks> hope that's enough info :)
[08:23] <clobrano> good morning all 0/
[08:24] <didrocks> hey clobrano! Trying some golang from what I saw? :)
[08:24] <clobrano> hey didrocks, yes, tried and the dropped :D
[08:24] <didrocks> oh?
[08:25] <clobrano> didrocks: at the end, convert was all I needed
[08:25] <didrocks> yeah, no need to reimplement what already exists :)
[08:25]  * clobrano can't find a way to use golang :(
[08:25] <clobrano> didrocks: but, yeah, I'm quite happy with the results so far
[08:28] <didrocks> clobrano: yeah, it looks quite good :)
[08:37] <seb128> back, good morning desktopers
[08:37] <didrocks> salut seb128
[08:38] <seb128> duflu, technically I joined first earlier :p I just tend to not talk but do my email backlog before my morning erands :)
[08:39] <duflu> Morning seb128. You win
[08:39] <seb128> :p
[08:39] <seb128> morning!
[08:57] <oSoMoN> good morning deskoppers
[08:57] <oSoMoN> *desktoppers
[08:58] <seb128> lut oSoMoN, en forme ?
[08:58] <didrocks> salut oSoMoN
[08:59] <oSoMoN> salut seb128, didrocks
[08:59] <oSoMoN> la forme, et vous?
[09:01] <seb128> en forme !
[09:02] <Laney> yo
[09:08] <didrocks> la forme aussi :) hey Laney
[09:10] <duflu> lo Laney
[09:12] <Laney> hey d*
[09:12] <seb128> hey Laney, how are you?
[09:17] <Laney> hey seb128
[09:17] <Laney> doing good :.
[09:17] <Laney> :>!
[09:18] <Laney> made a whole load of green tomatoes into salsa last night
[09:18] <seb128> nice
[09:18] <Laney> could have made it a bit spicier
[09:18] <Laney> you?
[09:20] <seb128> I'm good! It' sunny today :) I didn't do much from evening though, gf had sport and baby didn't want to sleep so I had to keep him busy and then clean around :/
[09:22] <Laney> /o\
[09:22] <andyrock> morning all!
[09:23] <Laney> is he quite active?
[09:23] <seb128> hey andyrock, how are you
[09:23] <Laney> hey andyrock
[09:23]  * seb128 ponders upstreaming bug #1794292
[09:23] <Laney> how's london?
[09:23] <seb128> we are getting little downstream traction despite having a reporter who seems to understand a bit what's going on
[09:23] <Laney> I saw in the foundations meeting that c_yphermox was working on that
[09:23] <andyrock> seb128: good drinking some tea
[09:23] <Laney> not much activity on the bug though
[09:24] <andyrock> you?
[09:24] <Laney> :| |: :| |:
[09:24] <seb128> Laney, do you have an opinion on that? e.u.c started receiving report with 0.9.3-1ubuntu10 which was an upload from you (with some upstream backported patches from Hans)
[09:24] <andyrock> Laney: not sure, I still have to open the windows to check 😂
[09:24] <seb128> andyrock, I'm good, done drinking my coffee, I might do another one in a bit
[09:24] <Laney> seb128: what part of it?
[09:25] <Laney> it's known to not be fixed but he was supposed to be working it
[09:25] <seb128> you mean?
[09:25] <seb128> I'm just saying that https://errors.ubuntu.com/problem/d811a3a23b60315368e94d8d6ee10fb908e90d92 shows the first report from -1ubuntu10 so I wonder if that's a problem in one of the patches included in that upload
[09:26] <seb128> or the signature changed and it was there before
[09:26]  * seb128 checks errors
[09:26] <seb128> also good to know that Mathieu is looking at it, would be good if he updated the bug as well
[09:27] <Laney> the bug you linked was pre-existing
[09:28] <seb128> ah, right, https://errors.ubuntu.com/problem/6aa06f1bc51946c787a01d38e58bc76114555334
[09:29] <seb128> it's not the same error though
[09:29] <seb128> sigsegv vs assert
[09:33] <Laney> there's a 0.9.5 now, would be good to get that instead of these millions of patches
[09:33] <Laney> 4*
[09:34] <seb128> right
[09:45] <seb128> ok, well I did upstream it now, so let's see
[09:48] <seb128> jamesh, hey, weekly summary? ;)
[10:15] <didrocks> seb128: duflu: so, I'm not that crazy, my patch is good, unsure if the backport to cosmic matches though? https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1789356/comments/16
[10:16] <seb128> heh
[10:17] <duflu> didrocks, seb128, no I just found the problem. The texture coordinates are off by 0.5, which for a texture that's only 1x2 pixels is a big deal. This doesn't seem to be a bug in mutter though. It's a bug in the Ubuntu patch. I'm not yet sure how to fix it since mutter is rendering the 1x2 texture correctly, just different to how it is rendered on the login screen
[10:19] <duflu> I mean the top of the gradient is 25% down the screen and the bottom is 75% down the screen. Because if it was a proper wallpaper that's the correct calculation
[10:19] <duflu> The login screen uses 0% and 100%
[10:21] <duflu> didrocks, seb128, in summary, I got it and will need more time to find a fix
[10:21] <duflu> Another day because it's already dinner time
[10:22] <seb128> k, doesn't sound like a regression though, unsure what we should do about the SRU but we shouldn't block it long
[10:22] <seb128> so either declare it's fine as it is and we can fix that issue later, or re-upload without the change for now
[10:22] <duflu> seb128, it's a regression in that the original bug is not fixed, and the new behaviour is worse. Not sure what to call that but regression wouldn't be inaccurate
[10:23] <seb128> k, well as I said we need to not sit on tha SRU
[10:23] <duflu> seb128, you can keep the bug open, release the SRU and I can generalise the bug description to cover the new behaviour :)
[10:23] <seb128> so let's see tomorrow
[10:23] <seb128> well, if the SRU introduces a worth user experience we shouldn't release it
[10:24] <duflu> I would agree. And I know enough to be able to fix it fully... this week
[10:24] <seb128> but let's see if we maange to fix or if we should revert the change
[10:24] <seb128> k
[10:24] <seb128> more news tomorrow then
[10:24] <seb128> duflu, enjoy dinner!
[10:24] <seb128> early lunch here!
[12:29] <seb128> jamesh_,  hey, weekly summary? ;)
[13:29] <andyrock> seb128: ptomato released gjs 1.53.3 \o/
[13:29] <seb128> andyrock, nice :)
[13:29] <andyrock> so we don't need to upload our version with 10 cherry-picks :D
[13:30] <andyrock> I'll prepare the upload (so I can distract a little bit from the lock issue)
[13:33] <seb128> k, good
[14:30] <seb128> k, it's meeting time!
[14:31] <seb128> Roll call: andyrock, dgadomski, didrocks, duflu (out), jbicha, jamesh (out), jibel, kenvandine, laney, oSoMoN, seb128, tkamppeter, trevinho, robert_ancell (out), tjaalton, tseliot
[14:31] <didrocks> hey
[14:31] <kenvandine> o/
[14:31] <jibel> hi
[14:31] <andyrock> o/
[14:31] <tseliot> o/
[14:31] <oSoMoN> o/
[14:31] <Laney> nod
[14:31] <seb128> thx for those who included their rls bugs status in their summary
[14:32] <seb128> kenvandine, do you know if jamesh is around this week? He didn't submit his summary and I pinged him here today without result
[14:32] <kenvandine> he should be around
[14:32] <seb128> k, oh well
[14:32] <seb128> let's get started witht he bugs review
[14:33] <tjaalton> yo
[14:34] <seb128> #topic rls-bugs-review
[14:34] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-incoming-bug-tasks.html
[14:34] <seb128> one item https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1758459
[14:34] <seb128> jbicha, why did you nominate that one?
[14:35] <seb128> I guess he's not around
[14:35] <jbicha> .
[14:35] <seb128> I've been keeping an eye on that one for a while but there is no duplicate nor example that can be used as a testcase
[14:35] <jbicha> uh, it says that bionic's transmission can't be used for some torrent trackers/servers/things
[14:36] <jbicha> yeah, no test case :(
[14:36] <seb128> based on the fact that there has been almost no user reporting and that we can't do a SRU without a way to test the issue/fix I vote -1 for the nomination
[14:36] <seb128> it doesn't seem an important issue for our users
[14:36] <seb128> opinions?
[14:37] <Laney> yep
[14:37] <Laney> jbicha or someone could still upload it if they wanted to though
[14:37] <Laney> maybe falls under the gnome ffe
[14:37] <Laney> srue
[14:37] <seb128> right, I would do the update if I had a testcase :)
[14:37] <Laney> whatever you call it
[14:37] <Laney> so you don't need one for that
[14:37] <seb128> I don't think it is, it's not even hosted on the GNOME infra
[14:37]  * Laney shrugs
[14:37] <Laney> you could argue
[14:37] <Laney> or don't do it, that is up to you
[14:38] <seb128> I think the spirit of the GNOME ffe is that they have freezes aligned, etc
[14:38] <seb128> but yeah, let's not discuss that here/now
[14:38] <seb128> rls-not-fixing it
[14:38]  * Laney shrugs again
[14:38] <seb128> sorry :p
[14:38] <seb128> shouldn't have started argumenting
[14:38]  * seb128 shuts up and moves to cc bugs :)
[14:39] <jbicha> I've got to do some other stuff so let me add that I dropped the #1775329 task for bionic. I still want to do an Epiphany upload but not this week
[14:39] <jbicha> bug 1775329
[14:40] <seb128> jbicha, k, thx
[14:40] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-cc-incoming-bug-tasks.html
[14:40] <seb128> that has no desktop item
[14:40] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-dd-incoming-bug-tasks.html
[14:40] <seb128> https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1769383
[14:40] <seb128> I vote +1, that seems like an important issue
[14:40] <andyrock> +1
[14:41] <andyrock> I'm already working on it (without major progress)
[14:41] <seb128> thx
[14:41] <seb128> targetted
[14:41] <Laney> cc too no?
[14:42] <seb128> I guess yes
[14:42] <andyrock> it got the that but was not in the list
[14:42] <seb128> done
[14:42] <Laney> lame, that page didn't update since 0831
[14:42] <seb128> it was not tagged rls-cc-incoming
[14:42] <seb128> oh it was
[14:42] <seb128> anyway, targetted for cosmic
[14:42] <seb128> thx for raising that
[14:43] <Laney> thx
[14:43] <kenvandine> i've seen bug 1769383 on CC
[14:43] <seb128> next https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725384
[14:43] <seb128> that seems an important issue for touch usage which oems care about
[14:43] <seb128> so I +1 to nominate for D
[14:44] <seb128> (we might also want to backport the fix to C or B then)
[14:44] <kenvandine> +1
[14:45] <seb128> k, nominated
[14:45] <seb128> next, https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1730765
[14:45] <seb128> seems like a feature wishlist
[14:45] <didrocks> whishlist?
[14:45] <didrocks> yeah, doesn't really go under "nominate"
[14:45] <seb128> you disagree?
[14:46] <seb128> or was that cross posting of "loos like wishlist"?
[14:46] <didrocks> cross posting
[14:46] <seb128> :)
[14:46] <seb128> anyway, it's non trivial work, we didn't get official/oem requests about it and we are already booked on features
[14:46] <seb128> so -1 from me
[14:46] <didrocks> -1 as well
[14:47] <seb128> thx; rls-not-fixing it, willcooke can raise it by other ways if he cares :)
[14:48] <seb128> I'm still unsure how to handle the -tracking lists best, but if those are listed in the weekly summaries I think we can skip talking about them, unless specific questions are raised
[14:49] <seb128> which can be done by the meeting lead or in ABO
[14:49] <seb128> AOB
[14:49] <seb128> wdyt?
[14:49] <Laney> should look for unassigned ones there
[14:49] <seb128> good point
[14:49] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-cc-tracking-bug-tasks.html is in good shame
[14:49] <seb128> all fix commited but 3 which are assigned
[14:50] <seb128> hum
[14:50] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-dd-tracking-bug-tasks.html
[14:50] <seb128> https://bugs.launchpad.net/ubuntu/+source/ibus-m17n/+bug/1674089 bypassed the process
[14:51] <Laney> O_O
[14:51] <seb128> does anyone want to own it?
[14:52] <seb128> I guess not, I'm going to Cc Gunnar to get his input and add it my list meanwhile
[14:53] <seb128> the other one is
[14:53] <seb128> https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1796622
[14:53] <seb128> which also bypassed the proces
[14:53] <seb128> does anyone want to look at that?
[14:54] <andyrock> happy to help with this
[14:54] <seb128> thx, assigning to you
[14:55] <seb128> I'm happy to help landing a fix, we should also perhaps talk to security if they consider it as a security fix
[14:55] <andyrock> kk
[14:56] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-tracking-bug-tasks.html
[14:57] <seb128> k, basically I need to tide up the unassigned items with the feedback I got from the email discussion we had one that list
[14:57] <seb128> I think we are good for rls?
[14:57] <seb128> #topic AOB
[14:57] <seb128> any other topic?
[14:57] <seb128> shrug, I forgot to #startmeeting :/
[14:57] <Laney> probably put to update on rls status in the first post of the threads from now on
[14:58] <kenvandine> lol
[14:58] <kenvandine> whoops
[14:58] <seb128> #startmeeting Desktop Team Weekly Meeting - 2018-11-13
[14:58] <meetingology> Meeting started Tue Nov 13 14:58:50 2018 UTC.  The chair is seb128. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[14:58] <meetingology> Available commands: action commands idea info link nick
[14:58] <seb128> still doing that
[14:59] <Laney> #topic rls-bb-incoming
[14:59] <Laney> ;-)
[14:59] <seb128> sorry, forgot the bot start the meeting, read the log on https://irclogs.ubuntu.com/2018/11/13/%23ubuntu-desktop.html if interested
[14:59] <seb128> #topic AOB
[14:59] <oSoMoN> this is gonna be the shortest meeting ever :)
[14:59] <seb128> lol
[14:59] <seb128> Laney, what did you mean by rls-status for the first post?
[14:59] <seb128> the urls from the different reports?
[15:00] <oSoMoN> a reminder for everyone to update on their rls bugs assigned I guess
[15:00] <Laney> or in the weekly reminder
[15:00] <Laney> experience is that people "forget"
[15:01] <seb128> right, good point
[15:01] <oSoMoN> I now have it in my weekly update template, to avoid forgetting
[15:01] <seb128> will do for the next one
[15:01] <seb128> ok, on other topics, just few/trivial notes
[15:01] <seb128> - for those who didn't pay attention, the new ubuntu serie is called "disco"
[15:02] <seb128> - it's open of uploads now (good time to do your debian merges if you have some to do, see https://merges.ubuntu.com/main.html)
[15:02] <seb128> - I made version track GNOME 3.30 still for now, I think we should wait a bit before looking at 3.31
[15:02] <seb128> especially that nautilus and some others are having talks about gtk4
[15:03] <seb128> which we probably are not going to want by default this cycle, or not before having more confidence it's going to turn ok by the end of the cycle

[15:03] <seb128> any other comments/topic?
[15:04] <seb128> seems not, it's a wrap then!
[15:04] <seb128> thx desktopers
[15:04] <seb128> #endmeeting
[15:04] <meetingology> Meeting ended Tue Nov 13 15:04:38 2018 UTC.
[15:04] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-desktop/2018/ubuntu-desktop.2018-11-13-14.58.moin.txt
[15:04] <andyrock> thx
[15:04] <oSoMoN> thanks
[15:04] <didrocks> thx
[15:04] <didrocks> seb128: do you mind having a look at the ubuntu-meta NEW binary packages? We are blocked with j_ibel until ubuntu-desktop-minimal is published in the RELEASE pocket and it's in the new fresh disco!
[15:05] <Laney> what's all those removals in ubuntu-meta?
[15:05] <didrocks> because they are all added in the new ubuntu-desktop-minimal
[15:06] <didrocks> and the script doesn't mention it, so I mentionned it manually in d/changelog :)
[15:06] <Laney> how come it doesn't say added for those though, that's weird
[15:06] <seb128> didrocks, k, I can try having a look though I might want to try to get some input from foundations just to check they are fine with the name/change
[15:07] <Laney> there's some script inside Launchpad that needs to be editied btw if you want the Task field to be generated for the new task
[15:07] <seb128> do you know who can do that?
[15:07] <didrocks> Laney: didn't write the d/changelog generator, so I guess they didn't take into account creating new name
[15:08] <Laney> anyone
[15:08] <seb128> do you know where it is in launchpad?
[15:08] <Laney> nope
[15:08] <Laney> I forgot, sorry
[15:08] <seb128> no worry
[15:08] <didrocks> would be great if all that was documented…
[15:09] <seb128> didrocks, you want to investigate/ask on #ubuntu-release about that?
[15:09] <Laney> suggest #launchpad or #launchpad-dev
[15:09] <seb128> or that
[15:10] <didrocks> done, we'll see
[15:11] <didrocks> really annoying you can't try everything locally and have to hack on the production directly to advance (with all the blockers)
[15:12] <didrocks> jibel has the task published in the archive though
[15:14] <Laney> are you together or something?
[15:14] <didrocks> ok, it's only for taskel to know how the task
[15:14] <didrocks> yep
[15:14] <Laney> maybe it was for something else
[15:14] <didrocks> HO, like if we were at an office, for days :p
[15:14] <Laney> just weird to see him talking through you
[15:15] <Laney> I see
[15:15] <jibel> Laney, you want to jkoin the HO?
[15:15] <jibel> -k
[15:15] <didrocks> we need help on the installer :p
[15:15] <Laney> no thanks, I'm naked
[15:17] <andyrock> 😂
[15:19] <Laney> 🧖
[15:29] <Trevinho> Morning... Ouch alarm didn't work well for the meeting :'(
[15:30] <seb128> good morning Trevinho, got hit by DST? ;)
[15:30] <Trevinho> seb128: nope just the phone vibrated only instead of actually ringing
[15:31] <seb128> I can't believe android phones manage to sell, those are so crap. Alarm was not reliable in ringing in my previous s3 mini, but it was getting old and I though that it sucked by ok
[15:31] <seb128> same issue on my new phone :/
[15:37] <seb128> shrug, pep8 is annoying
[15:38] <seb128> "W504 line break after binary operator"
[15:39] <seb128> it's not ok to wrap a line after a "or" now
[15:39] <seb128> but neither it's ok to have it too long :/
[15:40]  * seb128 wonders how to fix/change
[15:40] <seb128> "            if not (depcache.marked_install(pkg) or
[15:40] <seb128>                     depcache.marked_upgrade(pkg)):"
[15:41] <seb128> ah, put the or on the new line?
[15:41]  * seb128 tries
[15:41] <seb128> "W503 line break before binary operator"
[15:41] <seb128> you are kiding me right?
[15:43] <andyrock> seb128: is this for update-notifier?
[15:43] <seb128> yes
[15:43] <seb128> it's blocked in disco-proposed due to that
[15:43] <andyrock> why did it start failing now?
[15:44] <seb128> because pep8 got updated
[15:44] <seb128> and that warning is new in disco
[15:44] <andyrock> ah right
[15:44] <seb128> I'm just going to add W504 to the ignore I think
[15:45] <seb128> that's just stupid
[15:45] <andyrock> seb128: I guess you need to wrap the only thing inside parenthesis
[15:45] <seb128> you mean?
[15:45] <seb128> if not (depcache.marked_install(
[15:45] <seb128>           pkg) or depcache.marked_upgrade(pkg)):"
[15:46] <seb128> like that?
[15:46] <seb128> that's not nice
[15:47] <andyrock> seb128: https://www.python.org/dev/peps/pep-0008/#multiline-if-statements
[15:47] <seb128> well that's how the current code is no?
[15:47] <seb128>  "            if not (depcache.marked_install(pkg) or
[15:47] <seb128>                      depcache.marked_upgrade(pkg)):"
[15:48] <andyrock> you need a ( before no
[15:49] <andyrock> to satisfy the 4 space rule
[15:49] <seb128> andyrock, want to mp the fix so I can approve/upload? ;)
[15:49] <andyrock> seb128: sure
[15:50] <seb128> andyrock, https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/amd64/u/update-notifier/20181112_105721_60823@/log.gz has the 4 errors, in case you work on cosmic
[15:50] <seb128> look for W504
[15:50] <andyrock> seb128: I'll use sbuild with disco
[15:50] <andyrock> should be enough right?
[15:50] <seb128> yes
[15:50] <seb128> but in case you don't want to bother
[15:51] <seb128> you can probably just fix them without testing
[15:51] <seb128> I can test before uploading
[15:51] <seb128> if you know what needs to be done, I mean it's not tricky to test
[15:53] <andyrock> kk should not take long
[16:01] <andyrock> https://www.irccloud.com/pastebin/f1fJVHBU/
[16:01] <andyrock> seb128: ^^^
[16:01] <andyrock> a little bit ugly because continue is aligned with the conditions
[16:02] <andyrock> we can make it more readable doing this:
[16:03] <andyrock> https://www.irccloud.com/pastebin/YQNc6ULn/
[16:03] <andyrock> moving the comment
[16:03] <andyrock> I would suggest the 2nd option
[16:05] <seb128> andyrock, wfm
[16:24] <andyrock> mmm it's also complying here: package_data_downloader.py:163
[16:24] <andyrock> and this looks fine
[16:38] <seb128> andyrock, well, it's the same issue no?
[16:38] <seb128>         if (os.path.splitext(relfile)[1] and
[16:38] <seb128>                 os.path.splitext(relfile)[1].startswith(".dpkg")):
[16:40] <Laney> ignore W503
[16:40] <Laney> that's what we did in update-manager
[16:45] <andyrock> seb128: ^^^
[16:45] <andyrock> Laney: 504 maybe?
[16:45] <Laney> we did 503 in update-manager
[16:46] <andyrock> seb128: but that line already has two parenthesis
[16:46] <seb128> andyrock, that's what I was suggesting, just ignore 504
[16:46] <Laney> would suggest being consistent with that one, it's a related project
[16:46] <Laney> but up to you in the end
[16:47] <andyrock> seb128: I wanted to fix it properly but sbuild fails here and I don't want to dig that much into the problem now
[16:48] <seb128> andyrock, you can probably dpkg -i the disco pep8 on your cosmic and test there
[16:48] <seb128> Laney, well, I mean we don't have 503 errors atm so no point ignore that ... or you mean you would put the "and" at the start of the second line and ignore 503?
[16:49] <Laney> right, those two warnings are the opposite of each other
[16:57] <didrocks> let's see if the package is out of NEW tomorrow
[16:57] <didrocks> time to enjoy the evening
[17:05] <andyrock> https://www.irccloud.com/pastebin/WsNmykoB/
[17:05] <andyrock> seb128: ^^^
[17:05] <andyrock> this should work
[17:06] <andyrock> let me know if you prefer a MR
[17:06] <seb128> Ran 1 test in 0.009s
[17:06] <seb128> OK
[17:06] <seb128> andyrock, yes please, better for the record/tracking
[17:06] <seb128> but confirmed it works, thx!
[17:06] <andyrock> seb128: if you got it already you can take care of it :)
[17:08] <Laney> hahah
[17:09] <andyrock> I'm having fun with clutter
[17:10] <andyrock> and sadly is not a clutter of spiders
[17:24] <seb128> andyrock, k, I can deal with update-notifier landing, thx for fixing it!
[21:07] <kenvandine> robert_ancell: i see your re-upload of gnome-software was rejected
[21:08] <robert_ancell> kenvandine, which one?
[21:08] <kenvandine> https://launchpad.net/ubuntu/bionic/+queue?queue_state=4&queue_text=gnome-software
[21:08] <kenvandine> on friday
[21:08] <robert_ancell> kenvandine, I uploaded a .7 just after that one
[21:08] <kenvandine> i couldn't find it in the queue
[21:08] <robert_ancell> https://launchpad.net/ubuntu/+source/gnome-software/3.28.1-0ubuntu4.18.04.7
[21:11] <kenvandine> oh, it was just accepted :)
[21:11] <robert_ancell> yup
[21:15] <seb128> kenvandine, robert_ancell, it failed to build on ppc64el and s390x it looks like :-/ also when an upload is rejected you can reuse the same number, no need to bump to the revision
[21:15] <robert_ancell> seb128, oh, you can use the same number?
[21:15] <seb128> kenvandine, robert_ancell, also unsure it was a good idea to bundle the autoremove change to that follow up, now instead of fast tracking the old fixes in we need a full/proper round of testing for that new feature and risk having it failing verification and holding the other fixes
[21:16] <seb128> robert_ancell, yes, queue doesn't care, you just can't re-use numbers that have been accepted
[21:18] <robert_ancell> seb128, are we using GNOME 3.32 in disco?
[21:19] <kenvandine> robert_ancell: did you ever get a chance to test the confined simple-scan snap?
[21:20] <robert_ancell> kenvandine, yes, I sent you the results via email
[21:20] <kenvandine> oh... i vaguely recall that :)
[21:20] <seb128> robert_ancell, read the meeting log :) but I recommended staying away from now
[21:21] <seb128> we usually don't start so early, also we want to make sure components don't add a depends on gtk4
[21:21] <seb128> which nautilus is talking about
[21:21] <robert_ancell> seb128, do you know when gtk4 will be packaged in Debian/Ubuntu?
[21:22] <seb128> robert_ancell, it's in Debian https://packages.qa.debian.org/g/gtk+4.0.html
[21:22] <robert_ancell> nice
[21:22] <seb128> we didn't include it in Ubuntu because there is no point having a dev serie so early
[21:22] <seb128> it would be having an outdated snapshot
[21:22] <seb128> it's rather creating problems than solving some
[21:23] <robert_ancell> I want a packaged version to see how hard it is to compile things with it, so when the transition happens we can help push everything over the line at the same time
[21:25] <jbicha> robert_ancell: there's chance we'll rename the source to gtk4 since GNOME is talking about dropping the +
[21:27] <robert_ancell> jbicha, ah, the + so much fun with mistyping things
[21:27] <jbicha> the + is annoying for URLs sometimes
[21:28] <jbicha> packaging is at https://salsa.debian.org/gnome-team/gtk4 but we haven't uploaded it since the switch to meson
[21:28] <kenvandine> robert_ancell: so double clicking the page should open the app registered for the mime type right?
[21:28] <robert_ancell> kenvandine, correct
[21:28] <kenvandine> that's going to be tough in the snap
[21:28] <kenvandine> well, firefox has some magic for that
[21:28] <kenvandine> but it's a pain
[21:29]  * kenvandine didn't even know double clicking the page did anything :)
[21:29] <robert_ancell> kenvandine, right, it's a pretty minor feature. I don't think you should worry about it.
[21:30] <kenvandine> i'd rather it not display an error though
[21:30] <kenvandine> the driver issue is a bigger deal
[21:31] <kenvandine> i'll probably have to build libsane-hpaio from source in the snap
[21:31] <kenvandine> robert_ancell: are there any other cases like that?
[21:32] <robert_ancell> kenvandine, right, so we just need to disable that for snap builds.
[21:32] <robert_ancell> kenvandine, what cases?
[21:32] <kenvandine> other sane drivers that are packaged separately
[21:33] <robert_ancell> kenvandine, the hpaio is the only one I know of as all the others are propietary
[21:34] <seb128> good night desktopers
[21:34] <robert_ancell> kenvandine, do you think it is possible to allow access to system drivers?
[21:34] <kenvandine> ok, so i can't do anything about the proprietary drivers
[21:35] <kenvandine> i don't think we can
[21:35] <kenvandine> willcooke has a scanner that looks on the filesystem for proprietary drivers