[05:10] Merry Christmas to those who celebrate [05:11] @kc2bez wxl When do we want to do Raman's grilling? [05:11] I'm abstaining from voting until that's done :) [05:28] Uh doodle poll [05:29] https://lists.ubuntu.com/archives/lubuntu-devel/2019-December/001714.html [05:30] What's Doodle? XD [05:31] Now we just need Dan [05:36] I should also bookmark mailing list archives. I think. :) [10:29] @tsimonq2 [Now we just need Dan], I've checked some boxes. [11:10] So tonight for me. [11:14] * The_LoudSpeaker fastens the armour [11:18] * RikMills looks for a big mace with armour piercing spikes... [13:13] @The_LoudSpeaker now I have some time, do you have the logs of the conversation in #lxqt? [13:13] Yup! [13:13] One sec. [13:18] [10:09 pm] <+afb3agaidaand the problem is real but not that easy to fix - to be honest, it works most of the time fine but will need some structural changes in some data models [13:18] [10:10 pm] <+afb3agaidaso the priority isn't that high - there are a lot of other things to be cleaned up first [13:18] [10:11 pm] <76b3The_LoudSpeakernoted. I will try to document and file a bug soon. [13:18] [10:14 pm] <+afb3agaidait boils down to - the shortcuts should not be written to panel and runner configurations, only to shortcut handling - and only get from there [13:18] [10:16 pm] <+afb3agaidasetting these things from within an application is totally fine - will never work 100% safe without locking mechanisms, but fine until someone is willing to break this willingly [13:18] There you go @hmollercl [13:19] thanks [13:21] honestly I don't remember which is the current problem, I mean right now on clean installation it works. So the problem only is when new panels are created? [14:14] yup! [14:15] and if user wants to change config from lxqt-globalkeys [14:15] for runner and for panel [14:15] there was a detailed discussion. agaida tested things himself and confirmed. I will pm you the detailed log. [14:17] also, @teward001 the script to replace our packaging requirements is ready? I can test it. I just nuked the container which I used to use. [14:17] creating one with a gui profile. [14:20] Ugghhh! I kept my phone away and no arcanist asks me to provide api token which needs the 2FA authentication from my phone. [14:20] *now [14:26] @The_LoudSpeaker [there was a detailed discussion. agaida tested things himself and confirmed. I w …], mmm, that doesn't seems to be an easy fix to do it ourselves. I would document it clear in the manual. to avoid mistakes and leave it as known bugs. [14:31] @HMollerCl [mmm, that doesn't seems to be an easy fix to do it ourselves. I would document i …], yup! we should do that for eoan. For focal, I think we can push upstream for a fix maybe? wxl ? we can anyway always put it in focal's manual i needed. :P [14:34] @The_LoudSpeaker [creating one with a gui profile.], Now I can use sublime from container. yay! [14:43] How did I author this? I don't see a diff linked.https://phab.lubuntu.me/rLXQTGLOBALKEYSPACKAGING8d14dd93bcc80f95cf12cd04ad932091de9c5194 [14:44] I forgot actually. 😁 Can someone remind me how we pick latest git from upstream? [14:56] sorry, haven't done that, only patches. [14:58] I need to find exact commit which was done before we (I) picked from upstream that day. Then create a patch from that to commit defining latest release. [15:03] afaik there are no changes. [15:03] But how do we confirm? [15:06] oh wait. [15:06] there are many changes. [15:06] prior to picking the git, we were using 0.14.1 [15:06] with our own versions appended [15:07] the pick was just before upstream's 0.14.2 [15:07] But final version released is 0.14.3 [15:08] so i need to make a patch from 0.14.2 to 0.14.3 [15:36] @kc2bez [I've checked some boxes.], So @kc2bez wxl that's 11:30 AM Central today? [15:36] yes, 12:30 Eastern [15:37] Sounds good. Technically there's two of us needed for quorum but all three is great too :) [15:38] The more the merrier :D [15:39] @RikMills @teward001 @HMollerCl etc. while y'all don't have final voting rights, you're welcome to attend and participate in the grilling :) [15:40] I will have guests about that time, so looks like I can't 😢 [15:40] @RikMills [I will have guests about that time, so looks like I can't 😢], You're welcome to leave questions here too... ;) [16:14] The source which I had fixed got lost when I deleted the container. :( [16:24] while applying `git diff COMMIT COMMIT^ > patchname.patch` which commit is written first? the start one or the end one? [16:26] @The_LoudSpeaker [while applying git diff COMMIT COMMIT^ > patchname.patch which commit is written …], Doing this gets a patch which undoes COMMIT [16:26] If you want a patch that applies COMMIT, reverse the two [16:26] okay. [16:28] Because it's saying "given this base COMMIT, produce a diff that gets me to ANOTHER COMMIT" [16:28] yeah so it should take 2 different commits as input na? [16:29] Your original command says "given the base of COMMIT, give me the diff to get back to COMMIT^" [16:29] @The_LoudSpeaker [yeah so it should take 2 different commits as input na?], Correct [16:29] the one without "^" is the destination commit right? [16:29] No! it is the start one [16:30] It goes git diff ORIGINAL DESTINATION [16:30] @The_LoudSpeaker [No! it is the start one], Yeah :) [16:30] *facepalms* [16:30] Thanks! [16:30] No worries [16:30] also what about this: … `ubuntu@focal-dev:~/lxqt-globalkeys$ git apply --check ~/release.patch --3way … error: config/translations/lxqt-config-globalkeyshortcuts_gl.ts: does not exist in index` [16:31] I just got that when I tried a correct patch. [16:31] That's not something I'd be able to tell you off the top of my head, hm [16:31] Have you tried cherry picking patches instead of manually creating a patch and re-applying it? [16:32] Earlier I had created a patch using gitk and that did not apply but the one created when using correct git diff command as you specified, gives me this^ [16:33] @tsimonq2 [Have you tried cherry picking patches instead of manually creating a patch and r …], Nope. Not cherry picking. But let me try something. one sec [16:34] idk why but this doesn't apply: … `git diff 76eace1f491b14ab3f1b0c688493ca3a11d22ebd 9ae09e4684e8daae19eceef8548c3cd31abd1bef` [16:35] This should work na? 🤔 [16:35] OH WAIT. [16:35] I know why it isn't [16:35] probably [16:38] no. [16:38] :( [16:39] I will just clone from MoM, fix it, commit locally. then create a patch and apply it to clone from phab. [16:39] https://phab.lubuntu.me/w/packaging/packaging_for_new_upstream_releases/ [16:41] wow! How did I miss this doc when I searched on phab earlier? [16:42] that's for releases, not git verson [16:42] tho I did have the idea of modifying the version in changelog and then running uscan [16:43] Yeah true @hmollercl [16:46] but it can be applied here i think [16:55] How do I do the copyright update? [16:56] scan for changes in the diff created between versions? in this case the patch that I created from out pick to the latest release? [17:35] Let's get this rolling here [17:35] wxl @kc2bez roll call? [17:35] o/ [17:35] o/ [17:35] Walter might be late [17:36] So basically, our goal is to ask you questions to ensure that you're qualified to be a Lubuntu Developer [17:36] ready. [17:36] This could last up to an hour and ends when there are no more questions for you [17:36] Answer each question to the best of your ability [17:36] understood. [17:36] Dan, want to go first or should I? [17:36] I can go. [17:37] First question. [17:37] Which pocket does an upload go to for the development series? [17:38] proposed [17:38] I am not sure [17:38] proposed is the answer. [17:38] ufff. [17:39] Simon do you want to go? [17:39] At what point in the cycle should you be careful not to introduce any new features, and what day is that for the 20.04 cycle? [17:40] The point is Feature freeze [17:40] and for the date, give me a sec. [17:40] feb 27 [17:41] Correct. [17:41] Dan? [17:42] What is the rationale for a SRU? [17:44] The update should be very very stable and shoudn't cause regressions in any way. users expect a high degree of stability [17:44] That is true. [17:45] I have a follow-up to that. [17:45] Any update shouldn't cause any problems in their day to day activities. instead it should improve their experience. Fot that, the SRU should be extremly stable [17:46] Also true. [17:46] Here is my follow-up: [17:46] Does a SRU make sense even if a bug is not high impact? [17:48] If the bug is a low impact one, it doesn't make sense to push the fix. there are costs of network and time for downloading updates. it should be worth it. [17:49] Possible regressions should play a factor too. [17:49] It is a judgement call though. [17:49] Simon? [17:49] examples of such bugs are those which do not affect users at run time. they should be instead staged and released along with other high impact fixes. [17:50] What is the name of the tool which does Proposed Migration in Debian and Ubuntu, what is the criteria for a package to migrate to the release pocket in Ubuntu, and for bonus points, what pop culture reference does it come from? (If you can't answer the last one, that's okay.) [17:52] The proposed-migration scripts do the migration in Debian an Ubuntu. [17:52] The criteria is as follows: [17:52] 1. must be built and published on all supported architectures. [17:53] 2. all the dependencies must be already satisfied or should be installed along with the package. [17:54] 3. there should be no bugs with the tag "block-proposed" against the package [17:55] 4. the package or its binaries should pass the reverse-dependencies test in autopkgtests [17:55] 5. finally, the introduction of the package shouldn't break any packages already in release package [17:56] don't know the pop culture reference. [17:57] The answer I was looking for is https://youtu.be/elueA2rofoo - the rest is acceptable, thanks. XD [17:57] Dan? [17:58] britney spears. ggwp! [17:58] XD [17:58] Which of those 5 do you need for the package to be considered a valid candidate? [17:59] 1, 2 and 4 [17:59] correct. [17:59] Did Walter make it here yet? [17:59] nope I think. [17:59] I don't think so [17:59] ok [17:59] I just pinged him. [18:00] Simon? [18:00] This is more of a nuanced question but one worth exploring nonetheless: what's the difference between the Archive Admins and the Release Team, and where do you find who is in each? [18:04] I am not completely sure about the roles of archive admins. Release team moderates the SRUs , mointor new relases of (l/x/k)ubuntu and they are the ones you can go to if you want to get your packages into proposed without satisfying "valid candidate" and to get features in after freezes. [18:04] you can find who is which team by looking at their launchapad pages. [18:05] Archive Admins accept packages from the NEW queues, Release Team can let packages in. SRU Team, while it has some overlap in members from other teams, is its own team [18:05] And, into the release pocket, not proposed :) [18:05] Dan? [18:06] yup. released. my bad. [18:06] What is the general process for a feature freeze exception? [18:09] the request should be filed as bug against the package in launchpad with status of "NEW" The request shoul contain the following information: [18:09] 1. enough description of changes to gauge the impacts [18:10] 2. a section explaining benefits from the changes [18:10] 3. additional information that could be useful to take the decision. [18:11] sounds good. Simon? [18:11] Why is it important to always do high quality work and ask if you're unsure before uploading? Who does it reflect on, who does it impact, and what levers would you be able to pull? [18:15] It is important because changes one makes affect a large variety of users who expect a stable and high definition experience from the ubuntu and its flavours. As a developer making those changes, one should make sure they meet the expectations. It reflects the quality of the work done by the developer himself. [18:15] I am not sure I understand the last part of the question. [18:16] As in, how are you able to influence Lubuntu and Ubuntu as a whole with developer powers? [18:19] With developer powers, I have the ability to change the user experience drastically, even with small changes. Thus, it is a huge responsiblity. As user experience ultimately leads to the image of Lubuntu and Ubuntu as a whole in the minds of the users. [18:19] Nice answer. I'm ready to vote [18:19] Dan? [18:19] wait a minute [18:19] it's time for my traditional trick question [18:19] Look who decided to show up XD [18:19] Okay [18:19] go wxl [18:19] yay! sensei is here finally! [18:20] well first thing's first. how do you upload a change to the archive? [18:23] as a lubuntu-dev I can only make changes to packages that are in lubuntu packageset. to make changes, I should find the source of the package in ubuntu. can be phab or launchpad in case of lubuntu packages. I should make changes locally. push them through arcanist or bzr. [18:24] * The_LoudSpeaker fingers crossed. [18:25] ok so let's say you're going to play sponsor for someone [18:25] how do you upload their changes? [18:26] wait. I can also use dput. But I don't currently have much idea about how to do that. [18:26] yep, that's the right answer [18:26] to upload changes for someone I am sponsoring, I should check and accept their diffs on phab. [18:27] dput is also used to upload where? [18:27] arc land [18:27] one sec. I will say the whole process [18:27] naw that's good [18:28] but outside of the archive, what can you use dput for? uploading where? [18:28] uploading to ppas [18:29] nice [18:29] I did that with lubuntu-grub-theme [18:29] if you do not specify a location in dput, what happens? where does it upload to? [18:30] goes to ubuntu archives by default. [18:31] so how are you going to keep yourself from mistakenly uploading to the archive when you mean to go to a ppa? :) [18:31] put a local dput file for ppa. or edit the /etc/dput.cf [18:31] (I've done that btw, it's embarrassing) [18:32] Me too [18:32] oh you're prepared. nice. [18:32] ok, i'm ready. [18:32] Me too. Dan? [18:32] I have nothing further, I am ready. [18:32] Voting in [18:32] 5 [18:32] 4 [18:32] 3 [18:32] 2 [18:32] 1 [18:32] +1 [18:33] * The_LoudSpeaker armour waiting for rikmills [18:33] +1 [18:33] +1 [18:33] Congratulations @The_LoudSpeaker on becoming the fourth Lubuntu Developer! [18:33] \o/ [18:33] I'll add him on LP real quick [18:33] Thanks! [18:34] good job :) [18:35] Thanks! [18:35] congrats @The_LoudSpeaker [18:36] also, I just remembered https://phab.lubuntu.me/P53 being open in one of the 30 tabs I had. wxl: you think It can be applied directly ? This was created from MoM [18:36] Thanks! @hmollercl [18:37] @HMollerCl [congrats @The_LoudSpeaker], Now where's your application? XD [18:37] @tsimonq2 [Now where's your application? XD], https://phab.lubuntu.me/w/lubuntu-dev/applications/theloudspeaker/ [18:38] No, Hans' [18:38] XD [18:38] XD [18:38] @The_LoudSpeaker [https://phab.lubuntu.me/w/lubuntu-dev/applications/theloudspeaker/], it's in the future.. [18:39] @The_LoudSpeaker [ Thanks!], Congrats [18:39] Congratulations @The_LoudSpeaker [18:39] Thanks! @kc2bez @RikMills [18:39] Now go upload your own stuff XD [18:39] @RikMills where is your mace? [18:40] @tsimonq2 [Now go upload your own stuff XD], XD tomorrow morning. gotta sleep now. :) [18:40] I think the better question is where @RikMills' core dev app is 😆 [18:40] @The_LoudSpeaker [XD tomorrow morning. gotta sleep now. :)], Have fun! [18:43] wait. while we were talking, I think the build I put succeded. And i managed to bump the version of lxqt-globalkeys I think. [18:44] one query: we don't have .mailman folder right? [18:44] @The_LoudSpeaker [one query: we don't have .mailman folder right?], * . mailmap [18:47] @The_LoudSpeaker [also, @teward001 the script to replace our packaging requirements is ready? I ca …], No, having some issues getting the arc scripts installed, because git clone is inefficient [18:47] and can't get it into a PPA in a way that works [18:47] @teward001 [No, having some issues getting the arc scripts installed, because git clone is i …], No you [18:47] @tsimonq2 [@RikMills @teward001 @HMollerCl etc. while y'all don't have final voting rights, …], E:CONTEXT [18:47] oh dev membership [18:48] *is still waking up today* [18:49] @The_LoudSpeaker [wait. while we were talking, I think the build I put succeded. And i managed to …], nvm this. [19:44] @tsimonq2 wxl, I changed the sleep time in lubuntu-update-notifer, changelog should be updated to 0.2 or 0.1ubuntu1 ? [19:45] 0.2 since it's a native package [19:45] Only quilt packages or Ubuntu revisions of native packages in Debian use ubuntu [19:45] oh hey while you're at it trim down the short name [19:45] !info lubuntu-update-notifier [19:45] lubuntu-update-notifier (0.1, focal): Package includes a bash daemon (lubuntu-upg-notifier.sh) which. In component universe, is optional. Built by lubuntu-update-notifier. Size 9 kB / 61 kB [19:45] er short desc [19:45] you can see it cuts off there [19:46] ok [19:47] I already pushed a commit changing the time (forgot the changelog), can/should I use the same commit or should I use a new on? [19:47] *one [19:47] packaging guide says "certainly under 80" but clearly you're limited to 62 [19:48]