[06:37] <didrocks> good morning
[06:38] <jibel> Salut didrocks
[06:49] <didrocks> salut jibel
[06:56] <duflu> Morning didrocks, jibel
[07:13] <didrocks> hey duflu
[07:40] <oSoMoN> good morning desktoppers
[07:42] <didrocks> salut oSoMoN
[07:43] <duflu> Hi oSoMoN
[07:43] <oSoMoN> salut didrocks
[07:43] <oSoMoN> hey duflu
[07:47] <seb128> good morning desktopers
[07:49] <jamesh> hi seb128
[07:49] <duflu> Hi seb128 and jamesh
[07:50] <seb128> hey jamesh, duflu, how are you? did you have a good w.e? and how is monday going?
[07:50] <duflu> seb128, going well. The weekend was busy. In the middle of 6 birthdays in quick succession plus father's day. Monday is also good. How are you?
[07:50] <oSoMoN> salut seb128
[07:52] <andyrock> good morning!
[07:52] <duflu> Hey andyrock
[07:52] <oSoMoN> morning andyrock
[07:53] <seb128> hey andyrock! wb! had good holidays?
[07:53] <seb128> lut oSoMoN
[07:53] <seb128> duflu, I'm good, spent 3 days in France visiting my gf's familly, her sister just had a baby
[07:54] <andyrock> seb128: yeah doing camping in northern Greece
[07:55] <seb128> nice
[07:55] <jamesh> It's starting to feel like winter has ended, which is nice
[07:56] <duflu> jamesh, I hope you're right because I have some walking and bussing tomorrow. The forecast is not good
[07:56] <duflu> But yeah. Windows all open finally
[07:58] <duflu> And now it starts raining
[08:01] <Laney> YEAHHHHHH
[08:04] <duflu> Laney wins for enthusiasm. Morning Laney
[08:04] <oSoMoN> good morning Laney
[08:04] <duflu> And morning willcooke
[08:05] <didrocks> hey Laney! welcome back
[08:06] <willcooke> hihihi
[08:07] <seb128> hey Laney, wb! how are you? had good holidays?
[08:07] <seb128> hey willcooke
[08:08] <oSoMoN> hey willcooke
[08:11] <Laney> hey duflu oSoMoN didrocks seb128 willcooke!!!!!
[08:11] <Laney> how's it going?
[08:12] <duflu> I would say well, but sounds like not as well as you, Laney
[08:12] <Laney> had a good time yes, surfing (campsite in a cloud at the top of big hill was less fun, rain every evening) was nice & visiting ireland was grrrrrrrrrrrreat
[08:12] <Laney> I had 1 pint of Guinness to confirm that it isn't all that over there either
[08:13] <Laney> duflu: Just seen my emails, excitement abating.
[08:13] <Laney> what did I miss?
[08:16] <seb128> not a lot, business as usual
[08:16] <seb128> GNOME .0 tarballs day today!
[08:17] <seb128> also I think the appstream service went down after a maintainance round on the machine and it looks like nobody out of you has any clue about it so it stayed like that waiting for you :-/
[08:18] <Laney> someone want to learn?
[08:19] <seb128> maybe ask in the meeting tomorrow
[08:19] <seb128> otherwise I wonder if we should get someone from foundations to learn about it
[08:19] <Laney> ok then, for information I asked in the past too
[08:19] <seb128> it's sort of part of the deb/apt stack nowadays
[08:19] <seb128> willcooke, ^
[08:19] <Laney> k, feel free to do that if you want
[08:19] <Laney> what is the problem?
[08:20] <seb128> I don't know, someone on #u-r mentioned a "failed to connect" error
[08:20] <seb128> and jbicha was asking around about it
[08:20] <seb128> so I would guess the service is down
[08:21] <seb128> like it didn't come back up after an outage
[08:21] <Laney> does http://appstream.ubuntu.com/ work for you?
[08:21] <seb128> yes
[08:21] <willcooke> seb128, sounds like a topic for our Foundations meeting for sure, but yeah, makes sense for at least some other people in our team to know more about it
[08:22] <seb128> Laney, is there a timestamp of the last update somewhere?
[08:22] <Laney> in the .yml.gz file
[08:22] <seb128> Laney, https://irclogs.ubuntu.com/2018/08/22/%23ubuntu-release.html#t08:47
[08:22] <seb128> was the "report"
[08:23] <seb128> but maybe they sorted it out anyway
[08:23] <seb128> if you say everything is fine?
[08:23] <seb128> anyway, I wanted to point it out in case
[08:23] <Laney> dunno, let me look
[08:23] <Laney> thx
[08:23] <Laney> an email would have been good probably
[08:23] <Laney> ok, that's the internal rsync
[08:24] <seb128> right, I tried to chase down foundation/Steve, I though someone there would know aobut it
[08:24] <Laney> that is more information
[08:24] <seb128> ah
[08:24] <seb128> good :)
[08:24] <Laney> probably the  archive's copy is out of date then
[08:25] <seb128> andyrock, gnome-online-accounts 3.30 is in Debian if you feel like doing the merge/rebasing ours to the current one? :)
[08:25] <andyrock> seb128: kk
[08:25] <seb128> thx
[08:25] <Laney> laney@nightingale> GET http://archive.ubuntu.com/ubuntu/dists/cosmic/main/dep11/Components-amd64.yml.gz | zcat | sed '6q;d'                                                                                                       ~
[08:25] <Laney> Time: 20180821T043423
[08:26] <seb128> what does that sed bit does?
[08:26] <seb128> but yeah, outdated
[08:26] <seb128> I know where to check next time at least
[08:26] <Laney> print the nth line
[08:27] <Laney> sed -n '/^Time:/p' would hhave been cooler
[08:28] <seb128> :)
[08:28] <Laney> ubuntu@juju-prod-ue-appstream-back-machine-5:~$ uptime
[08:28] <Laney>  08:28:41 up 13 days,  1:11,  1 user,  load average: 1.09, 1.09, 1.07
[08:28] <Laney> bet that's when it broke
[08:31] <Laney> better now, had to restart the rsync daemon
[08:35] <seb128> jbicha, ^
[08:35] <seb128> Laney, thx
[08:35] <seb128> Laney, do we have any documentation at all about the service? could be useful to at least have a wiki page describing where the service is, how to connect to the machine and how to start/restart it in such situation
[08:36] <Laney> ok
[08:36] <seb128> thx
[08:37] <Laney> I still would like a co maintainer
[08:37] <seb128> Yes, agreed
[08:38] <Laney> good
[08:41] <willcooke> https://twitter.com/barton808/status/1035617038478336000 <-- moar Dell laptops with Ubuntu on
[08:50] <juliank> willcooke: It seems that some users are confused by the applications showing in the initial setup screen. I think the intention there was showing apps the user might not know already, but I'm not sure.
[08:50]  * juliank reads to much reddit
[08:51] <juliank> I found it interesting to see some apps I've never even heard of
[08:52] <juliank> but it might be worthwhile mixing in some popular apps too, for users new to Ubuntu so they see their favorite apps are available too
[08:53] <juliank> reference https://www.reddit.com/r/Ubuntu/comments/9c4m9w/is_there_a_reasoning_behind_the_welcome_apps/
[08:54] <willcooke> juliank, that list is dynamically updated from the promoted snaps at that time (do a "$ snap find")
[08:55] <juliank> I see
[08:55] <willcooke> so the advocacy team tend to promote things around release time like Spotify
[08:56] <willcooke> and then they cycle through the many other snaps as and when.  They might have a push on developer tools one week and games the next
[08:56] <willcooke> so it should be a continually revolving list
[08:56] <darkxst> hey desktopers, any plans to get spidermonkey 60 in for cosmic?
[08:56] <willcooke> juliank, reading the reddit thread now
[08:57] <juliank> It might make sense to have two lists "popular" and "promoted" and show both
[08:57] <willcooke> juliank, yeah, could be.  FWIW - it also hides snaps you already have installed
[09:39] <oSoMoN> popey, Wimpress: do we have a Travis CI account associated to https://github.com/ubuntu ?
[09:40] <popey> Not that I'm aware of
[09:40] <popey> Not sure I would know though.
[09:43] <oSoMoN> popey, do you know who might know if we do?
[09:43] <darkxst> also is there a freeze exception for 3.30 bits? or need to file FFe's for anything I want to upload? (mainly tracker right atm)
[09:43] <oSoMoN> didrocks, maybe you do ? ^
[09:44] <seb128> darkxst, there is no ffe, you need to ask for one
[09:45] <duflu> gdm3 will get updated, right?.... https://bugs.launchpad.net/ubuntu/+source/gdm3/+bugs?field.tag=fixed-in-gdm-3.29.92
[09:46] <darkxst> seb128, ok, that is fine, was only asking because sometimes in the past there was
[09:47] <oSoMoN> Laney, would you mind merging https://code.launchpad.net/~osomon/britney/hints-ubuntu-libreoffice/+merge/354161 ? I am currently re-assessing the situation with that java crash on i386, but don't want to block the LO migration in the meantime
[09:48] <seb128> darkxst, there is a standing ffe for GNOME minor updates, not for bumping through series
[09:49] <seb128> duflu, yes, anything that is on 3.29 is going to be updated to the stable version
[09:49] <seb128> probably even to .1 before 1801
[09:49] <seb128> 01->10
[10:05] <darkxst> seb128, and spidermonkey 60?
[10:05] <seb128> darkxst, no idea about that, no plan that I read of
[10:06] <popey> oSoMoN: ask kenvandine[m]  according to https://github.com/orgs/ubuntu/people
[10:06] <darkxst> so gjs will stay on a dev release?
[10:08] <darkxst> there are currently issues with i386 tests failing but otherwise it seems ok
[10:09] <seb128> I've no idea about that stack, they bumped the depends between 1.53.3 and stable?
[10:10] <RAOF> Hey desktop frens! In putting the finishing touches to the new colord I see Lintian suggesting the girs should go in the multiarch paths but meson doesn't put them there by default.
[10:10] <RAOF> How are people (or are people) getting their girs in the right place?
[10:11] <darkxst> seb128, yep, mozjs60 port came in around 1.53.90
[10:11] <darkxst> currently hanging in debian new queue
[10:11] <darkxst> mozjs60 that is
[10:13]  * duflu suggests a plymouth update for bug 1767918 and simultaneously runs away to make dinner
[10:22] <seb128> darkxst, well, I've no idea, best asking chrisccoulson maybe or jbicha
[10:22] <seb128> hey RAOF
[10:30] <seb128> RAOF, I don't know about the gir question, looks to gnome-bluetooth as an example it doesn't seem to do anything special  and it ends up in the multiarch dir
[10:30] <darkxst> seb128, chrisccoulson has nothing to do with spidermonkey
[10:31] <seb128> darkxst, good, you seem to know who does and who to ask then :)
[10:37] <darkxst> seb128, what is with the animosity? Yes I know someone that can help, but sometimes wonder why I should
[10:37] <seb128> ?
[10:38] <seb128> I'm unsure what's the problem, I tried to help, you didn't like my answer, no big deal
[10:39] <seb128> Chris had been doing recent mozjs update for security and knows about that stack, I though he could have an opinion
[10:39] <seb128> https://launchpad.net/ubuntu/+source/mozjs52/52.9.1-0ubuntu0.18.04.1 is no "nothing" btw
[10:40] <Laney> I'd have thought whoever was doing the gjs update would sync / upload that
[10:43] <RAOF> <freenode_seb "RAOF, I don't know about the gir"> Hm. Ok, I'm check out gnome-bluetooth tomorrow...
[10:44] <darkxst> Laney, its still in Debian NEW and then still has issues, but yes
[10:46] <Laney> hopefully no big deal
[10:47] <darkxst> but it is a question of pre-release mozjs
[10:47] <Laney> pre release?
[10:47] <darkxst> yes
[10:48] <Laney> k, I miss that information, where's that?
[10:48] <darkxst> while gjs switched over, there is no official real yet of the standalone spidermonekry stuff
[10:49] <darkxst> http://ftp.mozilla.org/pub/spidermonkey/prereleases/60/
[10:51] <seb128> RAOF, totem-pl-parser and nautilus also don't do anything special and have their file in the multiarch dir ...  maybe your libdir is not correctly set?
[10:51] <RAOF> The shared libraries end up in the right libdir...
[10:52] <seb128> weird
[10:52] <seb128> I don't know then, sorry
[10:55] <seb128> RAOF, https://github.com/mesonbuild/meson/blob/master/mesonbuild/modules/gnome.py#L643
[10:55] <seb128> RAOF, that suggests the default in meson is to use libdir
[10:55] <RAOF> Hrm. It does, doesn't it. Thanks, I'll poke around a bit more tomorrow.
[10:58] <Laney> darkxst: right, that's mozjs releases for you, it comes from http://ftp.gnome.org/pub/gnome/teams/releng/tarballs-needing-help/mozjs/
[10:59] <Laney> similar happened for 52
[11:08] <darkxst> laney, without questioning their release process with is close to useless, the question was more will we be able to land it in cosmic
[11:09] <oSoMoN> thanks Laney for the hints update!
[11:44] <Laney> oSoMoN: np, forgot to reply on IRC, sorry!
[11:44] <didrocks> oSoMoN: no, it's just my personal account
[11:45] <Laney> darkxst: don't see why not, I think we basically just take whatever they throw out
[11:45] <Laney> probably will even update bionic with 60 at some point
[11:46] <Laney> but that means fixing javascript to not break
[11:46] <Laney> there's a tool to check for that in gjs tho, which is cool
[12:31] <didrocks> Trevinho: thanks for reducing the diff on Yaru!
[12:56] <didrocks999> dac, je viens de voir l'invitation :)
[12:56] <didrocks999> jibel: ^
[12:57]  * didrocks had a kernel freeze, looking for logs…
[13:12] <Trevinho> didrocks: yw, and eventually that line was the only wrong I think
[13:12] <didrocks> great!
[13:12] <didrocks> Trevinho: I'll be back on your MPs soon, have you updated the bileto ticket, do you think you need testing or can I just trust you? ;)
[13:13] <Trevinho> didrocks: I double-checked again, probably it was more manual mistake when adding that line than other
[13:13] <Trevinho> didrocks: well, bileto is updated
[13:13] <Trevinho> so testing can always be appreciated :)
[13:13] <didrocks> Trevinho: oki :)
[13:13] <didrocks> speaking of issues, the last one who merge the icon theme in Yaru did a cp instead of git merge…
[13:13] <didrocks> so now, conflicts everywhere
[13:13] <Trevinho> didrocks:  prior of syncing the VCS's I've to push the taged and changelog finalisation commits
[13:14] <Trevinho> didrocks: yay :-D
[13:14] <didrocks> Trevinho: ok! Let me deal with the merge, then back to your reviews, if all good testing and pinging you :)
[13:14] <Trevinho> Laney: ah.... you're back, welcome back then! :)
[13:15] <Trevinho> didrocks: and with L_aney we were saying about using telling them to use gbp dch for generating the changes, so we did last time... It works fine, but it tends not to group items per user properly...
[13:15] <Trevinho> so implies some manual fixes -_-
[13:15] <Trevinho> unless there's a dch flag for fixing it
[13:15] <didrocks> Trevinho: is there any documentation in our wiki page for this?
[13:15] <Trevinho> as otherwise changelog entries won't say much and since it's a native package is nice to have debian/changelog to match
[13:15] <didrocks> I don't know about gbp dch either
[13:16] <Trevinho> didrocks: nope, we just said we could use that... and we did :-D
[13:16] <Laney> moin Trevinho
[13:16] <Trevinho> you know, we're less prone to legislation than you
[13:16] <Trevinho> 😂
[13:16] <didrocks> better to document if we want everyone to use it though :p
[13:16] <didrocks> so, I'll let you Laney and Trevinho doing this ;)
[13:16] <Trevinho> anyway, yes... I can add it somewhere, desktop/git or somewhere else?
[13:17] <didrocks> a note on desktop/git sounds good!
[13:17] <Laney> depends if it's recommended for all packages or just yaru
[13:17] <Trevinho> it's just ` gbp dch --debian-branch=$(git current-branch)`
[13:17] <Trevinho> well without the 2nd part whichj works only ehre
[13:17] <Trevinho> `gbp dch` works
[13:17] <didrocks> recommended for all native package I would say?
[13:17] <Trevinho> I'd say for native packages always
[13:17] <Trevinho> yep
[13:18] <didrocks> the lack of "moving directories" is a little bit annoying…
[13:18] <didrocks> like, as when merging Suru icon (even if the last merger did it right), the new icons are in Suru/ instead of icons/
[13:21] <Trevinho> Ouch.... those moments when you get to your bt keyboatd and the trackpoint gum is missing :-(
[13:32] <jbicha> seb128: you may want to cherry-pick https://gitlab.gnome.org/GNOME/gnome-disk-utility/commit/e13e73797f
[13:45] <didrocks> excellent, didn't know about git merge -s recursive -Xsubtree=…
[13:47] <seb128> jbicha, thx
[13:49] <jbicha> Trevinho: there is a multimaint-merge option for gbp-dch, we could probably add that to debian/gbp.conf
[13:49] <Trevinho> didrocks: how could you miss that... 😅
[13:49] <seb128> is there a gbp special worklow to cherry pick an upstream commit as patch?
[13:50] <Trevinho> (joking)
[13:50] <seb128> or do I just git show > patch and add to the serie as usual?
[13:50] <Trevinho> I mean, how with git can change the world by different arguments
[13:50] <Trevinho> noooo
[13:50] <Trevinho> seb128:
[13:50] <Trevinho> gbp pq import
[13:50] <Trevinho> git cherry-pick sha
[13:50] <jbicha> Trevinho: https://salsa.debian.org/systemd-team/systemd/blob/master/debian/gbp.conf
[13:50] <Trevinho> gbp pq export --no-patch-numbers
[13:50] <Trevinho> done
[13:51] <seb128> Trevinho, thx
[13:52] <Trevinho> seb128: it's basically this https://wiki.ubuntu.com/DesktopTeam/git#Working_on_patches
[13:52] <Trevinho> i'd add the --no-patch-numbers as default to gbp.conf though
[13:52] <didrocks> Trevinho: sure! That was sooooooooooooo obivous ;)
[13:53] <seb128> Trevinho, number or not I don't care, it's just cosmetic of filenames
[13:53] <seb128> it's somewhat easier to reference/read in order with numbers imhop
[13:53] <seb128> but that's personnal taste
[13:54] <didrocks> seb128: feel free to rephrase if you didn't find it as https://wiki.ubuntu.com/DesktopTeam/git#Pick_some_upstream_commits
[13:55] <seb128> didrocks, ah thanks, I read the page but I forgot about that section
[13:56] <didrocks> well, with the amount of info, not surprised :)
[13:56] <seb128> especially that I'm still not comfortable with git
[13:56] <Trevinho> seb128: well, if they all were with numnbers... but well, changing numbering is bad
[13:57] <seb128> I did nuke a checkout again earlier today because it's just easier than trying to figure out how to "undo" changes to several branches
[13:57] <seb128> (I did a gbp import-orig on debian/experimental instead of debian/unstable)
[13:57] <Trevinho> seb128: in case of troubles, improvise :-D
[13:58] <Trevinho> seb128: do you have a ~/.bashrc with a PS1 so that you show the current branch on the cmd prompt?
[13:58] <seb128> now I'm trying to understand the difference between pq import and rebase and which one makes more sense to create a patch :p
[13:58] <seb128> Trevinho, no, but I knew in what branch I was
[13:58] <Trevinho> seb128: well, gbp pq import or git rebase or gbp pq rebase?
[13:58] <seb128> I just forgot that 3.30 uploads were going to unstable now
[13:58] <seb128> unless 3.29 which which we were uploading to experimental
[13:59] <seb128> Trevinho, sorry, gbp pq import vc gbp pq rebase
[13:59] <Trevinho> as gbp pq import only transforms patches into commits, gbp pq rebase refreshes the patches allowing you to fix conflicts on the way
[13:59] <Trevinho> so rebase is needed only when you've imported something old and need then to rebase on the latest one
[14:00] <seb128> well I don't want to "edit" other patches
[14:00] <Trevinho> like you import new upstream, patch doesn't apply, you force the import to an old version then it will rebase and stop for fixing
[14:00] <seb128> I think I'm just going to git show patch and add that to srie :p
[14:00] <Trevinho> nooooo
[14:00] <seb128> oh yes
[14:00] <seb128> simple & efficient :)
[14:00] <Trevinho> if gbp pq import doesn't work, then neither the build will
[14:00] <seb128> well I don't know
[14:00] <Trevinho> i tell you...
[14:00] <seb128> you guys gave me different workflows/commands
[14:00] <Trevinho> it's three commands for easy picking,
[14:01] <seb128> and I'm lost in deciding now
[14:01] <Trevinho> import -> cherry-pick -> export. Done
[14:01] <seb128> k, let me try that
[14:01] <Trevinho> and then you'll understand my love for this :D. or maybe not
[14:02] <seb128> let's see ;)
[14:02] <seb128> oh, lol
[14:02] <seb128> ok, not for this cycle, I forgot that gnome-disk-utility doesn't have a vcs on launchpad
[14:02] <seb128> WIN, I get the easy way out, dch & cp & debuild -S  & dput
[14:02] <seb128> \o/
[14:04] <Trevinho> oh... This old guy! :-D
[14:05] <Trevinho> hours of development in tools, when cp was the only method for making him happy!
[14:05] <seb128> :)
[14:05] <seb128> well, I did my share of updates using the new workflow now
[14:06] <seb128> so I'm fine with it
[14:06] <didrocks> and snapcraft starts to fail on CI…
[14:06]  * didrocks goes to #snappy once again
[14:06] <seb128> I keep forgetting to push tags and it's quite some commands/work but it's ok
[14:07] <seb128> I mean it probably take twice the time to do trivial updates compared to a more minimalistic workflow, but I accept that it pays back for those who do complex work then
[14:07] <seb128> still I'm happy when I can have an "easy" update ;)
[14:08] <didrocks> seb128: hum, if you initialize the repo with the command I gave, at least, tags shouldn't be an issue
[14:08] <didrocks> there can be others, I agree, but not that one :)
[14:09] <seb128> didrocks, I stopped doing that in Debian after spamming the #debian-gnome for 1 hour by pushing 70 upstream tags that were not in their vcs :/
[14:09] <seb128> each push trigerring some pipeline job in salsa
[14:09] <seb128> or something
[14:10] <didrocks> argh
[14:10] <didrocks> sorry for this :)
[14:10] <jbicha> seb128: blame mbiebl for that one, he didn't want upstream tags pushed there at first
[14:10] <seb128> he changed his mind?
[14:10] <jbicha> um
[14:10] <Trevinho> seb128: make your own script for using dch with cp.... so you'll get all done with a command again :)
[14:11] <jbicha> I don't know
[14:11] <seb128> k, anyway I stopped setting the followTag now because of that
[14:11] <didrocks> I imagine a lot of "oh, forgot to the tags" then :/
[14:11] <didrocks> (happens already in a lot of upstream projects…)
[14:19] <didrocks> Trevinho: ahah, you have been tricked by copy/paste and vcscode reformatting the C for you ;)
[14:19] <didrocks> Trevinho: keep happening when dealing with C code, paste, then Ctrl+Z to remove the autoformatting :p
[14:22] <didrocks> Trevinho: https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-calculator/+git/gnome-calculator/+merge/353828/comments/921762 as well
[14:23] <didrocks> Trevinho: have you just repushed another commit with the initial date staying the same? (hard to know with launchpad MP UI)
[14:24] <didrocks> which sounds like from the diff
[14:24] <didrocks> ah interesting, you can switch the diff and you see the the new diff was generated on the 30 while the commit is still on the 28… (but no evidence that you pushed a new commit)
[14:25] <didrocks> quite confusing, used to gitlab/github when you see something else was pushed and overrides
[14:28] <Trevinho> didrocks: yeah, on vscode I've to use that ctrl+z, dont' know how to disable without getting the best part of it
[14:29] <didrocks> Trevinho: same, it's rather keep it or disable it completely, which is a shame as it's good otherwise :)
[14:29] <didrocks> Trevinho: trying your ppa, do you have special instructions to test long queries which should be cancelled?
[14:29] <Trevinho> didrocks: as for MP's I've subseeded them since I used different branches...
[14:29] <didrocks> Trevinho: not the one I pointed
[14:30] <Trevinho> didrocks: well, on gnome-calculator is easy
[14:30] <didrocks> but it's ok, it's just launchpad UI ;)
[14:30] <Trevinho> type 10!!! in the shell. and see cpu spinning
[14:30] <Trevinho> close the overlay and it should stop
[14:30] <Trevinho> check on top ofc
[14:30] <didrocks> good use case :)
[14:30] <Trevinho> for nautilus is the same, though it's not spining hard as htat
[14:31] <didrocks> Trevinho: mutter has no MP because we are in sync with debian I guess
[14:31] <Trevinho> if you try that on bionic (cosmic pre ppa) you keep that running forever.
[14:31] <didrocks> ok, it's from experimental
[14:31] <Trevinho> didrocks: yep
[14:31] <Trevinho> copied from there
[14:31] <didrocks> Trevinho: yeah, only testing cosmic though
[14:31] <didrocks> good!
[14:31] <didrocks> so, if my weechat crashes and didrocks is disappearing, blame Trevinho
[14:32] <Trevinho> good test case :D
[14:32] <didrocks> :p
[14:33] <Trevinho> didrocks: I'm pushing the finalize changelog commits and tags too then
[14:33] <didrocks> Trevinho: do I need to restart nautilus (nautilus-desktop) or this is an independant component?
[14:33] <Trevinho> it's independent, it's nautilus itself
[14:33] <Trevinho> didrocks: you can check by just using nautilus as `nautilus --gapplication-daemon` or whatever is
[14:33] <didrocks> k
[14:34] <Trevinho> `--gapplication-service`
[14:34] <Trevinho> if you want to check that process too
[14:34] <Trevinho> for calculator is under /lib/x.../gnome-calculator/...
[14:34] <didrocks> hum, it's helding back the Shell on upgrade
[14:34] <Trevinho> well libexec default
[14:34] <didrocks> let me check, can be due to some local modifications…
[14:35] <didrocks> The following packages have been kept back:
[14:35] <didrocks>   gnome-shell-common
[14:35] <didrocks> apt policy shows that I'm in sync with cosmic…
[14:35] <didrocks> and if I want to install -common, it wants to remove   chrome-gnome-shell gdm3 gnome-shell ubuntu-desktop ubuntu-session
[14:36] <didrocks> The following packages have unmet dependencies:
[14:36] <didrocks>  gnome-shell : Depends: libc6 (>= 2.28) but 2.27-3ubuntu1 is to be installed
[14:36] <didrocks>  libc6 | 2.28-0ubuntu1     | cosmic-proposed  | amd64, arm64, armhf, i386, ppc64el, s390x
[14:36] <didrocks> lalalala
[14:36] <Trevinho> a part from ordering... https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/354045
[14:37] <Trevinho> ah, ok.
[14:37] <didrocks> yeah, basically libc6 has some transitions or something forcing the new version
[14:37] <didrocks> do I really want to install it from -proposed? :p
[14:37] <Trevinho> well keep it temporary :)
[14:37] <Trevinho> that's why I use plenty of VMs and/or schroot more than actual metal
[14:38] <didrocks> yeah, let me dl a cosmic image and spawn a vm
[14:38] <didrocks> sounds safer
[14:48] <didrocks> installing "locale" on the live image and so recompiling/regenerating all of them, always a pleasure ;)
[14:48] <didrocks> ok, alt-f2 -> r, didn't crash :p
[14:50] <didrocks> ok, sounds to work
[14:51] <didrocks> Trevinho: +1 for me "works in my vm" is the new trend :)
[14:51] <Trevinho> :)
[14:51] <Trevinho> didrocks: I noticed I had to push this https://git.launchpad.net/~3v1n0/ubuntu/+source/gnome-calculator/commit/?id=1c45339f350ca659afe1ecb0c6827a3eac9777aa
[14:51] <Trevinho> can we leave it as unreleased for now and then we add on next round?
[14:51] <Trevinho> otherwise need to redo the package build and you can do that, but doing through bileto for me is annoying like hell
[14:51] <didrocks> good for me, so just merging all?
[14:52] <Trevinho> (as deleting the package takes forever)
[14:52] <Trevinho> yeah, let me push other branches finalizations
[14:52] <didrocks> did you see my space comment btw?
[14:53] <Trevinho> mh, ok... I'll do that at next iteration
[14:54] <Trevinho> as at that time I'll cherry-pick upstream finally approved commit again
[14:55] <didrocks> sounds good :)
[14:55] <Trevinho> ok, shell is updated too
[14:55] <Trevinho> missing nautilus
[14:56] <jbicha> one of these days I think I'm just going to upload that gnome-calculator epoch to Debian 😈
[14:59] <didrocks> lalalala :)
[15:01] <Trevinho> jbicha: ahaha, yeah, let's change epoch, this one is already boring
[15:01] <Trevinho> didrocks: nautilus pushed too
[15:02] <Trevinho> didrocks:  for shell, pull pristine-tar and upstream/latest from salsa, not sure I pushed to mine
[15:02] <Trevinho> but since we're 1:1 salsa, just use them
[15:04] <didrocks> Trevinho: sounds good! so, all everything is in sync?
[15:04] <Trevinho> didrocks: should be yes.
[15:04] <didrocks> s/all//
[15:04] <Trevinho> at least I've pushed :D
[15:04] <didrocks> ok, doing the branch dance :)
[15:05] <Trevinho> another option for such cases could be that we do the release with bileto then the sponsor does the gbp import-dsc from the one pushed...
[15:05] <Trevinho> so we're sure we don't miss anything
[15:06] <didrocks> Trevinho: as you wish, that's another option I'm fine with
[15:06] <Trevinho> like vcs merge of the proposed branch -> land bileto -> get the dsc published and update vcs with that
[15:06] <didrocks> Trevinho: if you prefer that, I can do
[15:06] <Trevinho> didrocks: it's too late now, as iv'e pushed the tags
[15:06] <didrocks> what branch did you use for g-s? as there were 2
[15:07] <Trevinho> but, next times we can go with that, so the sponsor does the import commit
[15:07] <Trevinho> didrocks: last one is based on the 1st
[15:07] <Trevinho> so.. .pulll the last (one with xubuntu-cancel)
[15:08] <Trevinho> didrocks: once bileto figures out the .diff is there, also https://bileto.ubuntu.com/#/ticket/3398 is ready to land if you're fine with that.
[15:09] <didrocks> Trevinho: one sec, doing one thing at a time, but ok ;)
[15:09] <Trevinho> so with this we can experiment the mixed merge way (merge vcs and then use dsc too)
[15:09] <Trevinho> yeah, sure.. I just noticed it was there on bileto, so I did that to you
[15:10] <Laney> why would you import a dsc?
[15:10] <Trevinho> Laney: to get the final changelog with proper timing, without that is me doing it
[15:10] <Trevinho> or well, you can also just do that part you
[15:10] <Laney> can't you push the finalise changelog commit?
[15:10] <Trevinho> but... if the .dsc was generted from bileto, and thus has my "finalse" entry, it needs to be 1:1 with that
[15:11] <Trevinho> I can, but then sponsor needs to remember tagging and such... so this coudl be another way to make sure that the vcs is 1:1 with packaging
[15:11] <didrocks> Trevinho: so, all pristine-tar and upstream/latest for the 3 components from salsa, correct?
[15:11] <Trevinho> as ometimes someone could forget a commit around or a change that didn't or did went though the .deb
[15:12] <Trevinho> didrocks: only for shell should be needed
[15:12] <Trevinho> the others are already in sync iirc
[15:12] <Laney> they need to remember the import-dsc, this is just a different command (gbp buildpackage --git-tag-only)
[15:12] <Laney> that is much more normal as a sponsorship workflow
[15:12] <didrocks> ok
[15:12] <Laney> imho
[15:12] <didrocks>  ! [rejected]            upstream/latest -> upstream/latest (non-fast-forward)
[15:12] <Trevinho> Laney: sure, but if I used bileto, you guys can't sponsor that way...
[15:12] <didrocks> Trevinho: so, merging?
[15:12] <Laney> publishing is sponsoring no?
[15:12] <Trevinho> and I rpefer to use bileto so I have all the components ready for you guys only have to hit a button.
[15:13] <Trevinho> Laney: yeah, but in that case is me doing the "finalise" commit.
[15:13] <Trevinho> while instead could be me the author, while the sponsor the committer.
[15:13] <Laney> you don't have to tag it though, that is the more important one
[15:13] <Trevinho> just formal thing, but..
[15:13] <didrocks> yeah, both pristine-tar and upstream/latest from salsa are conflicting with our branch as it's not a ff
[15:14] <Trevinho> ah ok... so... didrocks feel free to retag instead of me with your signature
[15:14] <didrocks> how do you want to handle those, merging or -f? (-f, we may miss some release)
[15:14] <Trevinho> if you wish
[15:14] <didrocks> Trevinho: the issue is not tagging here…
[15:14] <Trevinho> didrocks: well, if using my tag, just pull --tags from me
[15:14] <Trevinho> fetch --tags whatever
[15:14] <didrocks> Trevinho: you didn't get me, I'm talking about the salsa branches
[15:15] <didrocks> both branches from debian are conflicting with ours
[15:15] <Trevinho> ahhhh... sorry
[15:15] <Trevinho> mh, weird, what happened there... mhmh
[15:15] <Trevinho> I didn't touch ~ubuntu-desktop branches so not sure, but well, merge with salsa if that's the case.
[15:15] <didrocks> yeah
[15:16] <Trevinho> there should not be conflicts though.
[15:16] <Trevinho> if there are we've a problem
[15:17]  * Trevinho hads to put some woods on fire, back soon.
[15:17] <Trevinho> has*
[15:38] <andyrock> seb128: did you see this? https://code.launchpad.net/~azzar1/update-manager/add-livepatch-reminder/+merge/353304
[15:51] <didrocks> Trevinho: both bileto tickets published
[15:51] <didrocks> didn't merge gnome-session if you want to try the new workflow afterwards
[17:59] <willcooke> night all
[18:08] <seb128> andyrock, I did but I was waiting for Brian to review ... I'm going to have a look since he doesn't seem to pick it up again