[00:35] wxl: https://github.com/lxqt/libfm-qt/pull/439 - SRUable? [00:36] Also, did we ever get that globalkeys fix cherry picked? [00:36] @tsimonq2: glad you saw that. i was getting to it. [00:37] the only thing i can saw is that there *IS* a workaround to the MTP DND [00:37] s/saw/say/ [00:37] otherwise i'd say totally SRU'able [00:39] What's the workaround again? [00:39] I'd totally give an SRU a shot [00:39] copy/paste [00:39] Maybe you can give @kc2bez a runthrough so he knows the process :) [00:39] not to mention `cp` [00:39] Right [00:39] we still have a long list of items to do [00:39] i'd rather not waste efforts on an SRU unless totally necessary [00:40] I've been meaning to ask what's on our plate [00:40] I'd like to start making the 19.10 metatask reflect our current status [00:40] see the 19.10 items [00:40] um [00:40] look on the left hand side of phab XD [00:40] Is that up to date? [00:40] absolutely [00:40] I don't know that we've been doing much with that [00:41] Okay [00:42] it's all automagic as long as we take care of closing the task which we should [00:42] re: globalkeys https://phab.lubuntu.me/D18#454 [00:42] -lugito:#lubuntu-devel- [Needs Revision] Edited shortcuts so that they don't interfere with openbox key bindings.: https://phab.lubuntu.me/D18#454 [00:43] @wxl [ re: globalkeys https://phab.lubuntu.me/D18#454], No, I mean XDG config [00:43] -lugito:#lubuntu-devel- [Needs Revision] Edited shortcuts so that they don't interfere with openbox key bindings.: https://phab.lubuntu.me/D18#454], [00:43] @wxl [ it's all automagic as long as we take care of closing the task which we sh …], Ack [00:43] I want to sit down tonight and figure out some dates to wrap things up [00:44] I also want to start a discussion about next cycle because it's going to be the release that everyone uses. [00:45] I want to write the release notes more than a day before for this cycle XD [00:46] My goal is to take off of school on the final release day (if not the whole week but that's a different discussion) and MAYBE Final Beta [00:47] @tsimonq2 [I want to write the release notes more than a day before for this cycle XD], It'd be cool to get the Lubuntu Globalization Team up and running before these dates occur so we can have a buffer for translations [00:52] @tsimonq2 [It'd be cool to get the Lubuntu Globalization Team up and running before these d …], no problem, we are on fire ;) [00:52] Nice :D [00:55] @tsimonq2: read the comment [00:56] Don't wait for the release, JFDI [00:56] We've had this convo before about globalkeys :) [00:57] the other part is it didn't apply clean [00:57] so that needs some serious investigation [00:58] Want to take a shot at manually patching it in or is this my job now? XD [00:58] https://phab.lubuntu.me/T59#1517 [00:58] -lugito:#lubuntu-devel- [High, Open] fix keyboard shortcuts: https://phab.lubuntu.me/T59#1517 [00:58] take a look there and see if you can figure out some direction and make a comment for raman to run with [01:03] I might JFDI and then leave a verbose comment about why I made the decisions I did [01:03] i think it would be a great one for him to cut his teeth on. i'd give it to him if it all possible [01:04] I'm not at a computer yet, but it depends how complex [01:04] If we're talking backporting 100+ lines of code (been there done that) I'll do it myself [01:04] If it's easy, I'll describe it [01:05] yeah i think that's wise [01:05] One thing we can do though is test with the unstable PPA and see if we can get a testcase down [01:05] If the backport matches the functionality of the tip of master, we're golden [01:06] And, in order to test the backport, the patch can be committed to Git, flow downstream to stable, and we can test the stable package prior to uploading [01:06] Does that plan of attack make sense? [01:06] seems reasonable. hopefully we don't have to even go that route [01:07] I'd like to get Dan to sponsor this one if at all possible [01:07] Just so he gets the practice [01:14] @tsimonq2: word of advice: go test that xdg-settings patch and comment on github that it's good. be extensive as possible. i think that might help with convincing things [01:24] -lugito:#lubuntu-devel- [T59: fix keyboard shortcuts] tsimonq2 (Simon Quigley) commented on the task: https://phab.lubuntu.me/T59#1576 [01:34] remember you complaining about me above? perhaps that was your fault :) [01:35] i'd advise you to make sure you upload what you land or we run the risk of losing sight of it [01:35] Carrying over from the other channel, the one I can think of recently is me landing that lubuntu-default-settings fix but apt-ghetto just needs to fill out the SRU paperwork [01:35] he did [01:39] -lugito:#lubuntu-devel- [T90: Bionic locker should be light-locker] wxl (Walter Lapchynski) commented on the task: https://phab.lubuntu.me/T90#1577 [01:54] -lugito:#lubuntu-devel- [T99: Fix DND with MTP devices] wxl (Walter Lapchynski) just created this task: https://phab.lubuntu.me/T99 [01:54] T99, so cute! [01:54] *looks at T8xxxx on Solus dev tracker* [01:55] Then looks at Ubuntu's and shudders [01:55] makes me think of this https://www.youtube.com/watch?v=jKdPyIvMyEI [01:59] -queuebot:#lubuntu-devel- Unapproved: lubuntu-default-settings (bionic-proposed/universe) [0.54.2 => 0.54.3] (no packageset) [02:00] -lugito:#lubuntu-devel- [T90: Bionic locker should be light-locker] tsimonq2 (Simon Quigley) commented on the task: https://phab.lubuntu.me/T90#1587 [05:52] -lugito:#lubuntu-devel- [rMANUALaa96de39847a: Style distribution updates options] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALaa96de39847a [06:01] @tsimonq2 [Does that plan of attack make sense?], Repeat it in english please. [06:01] @The_LoudSpeaker [Repeat it in english please.], 😆 [06:01] Let me know what you would like me to clarify [06:06] -lugito:#lubuntu-devel- [rMANUALe5f6b326fef5: Add software sources button] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALe5f6b326fef5 [06:07] All of the above messages you wrote, starting from testing using unstable PPA. If you don't mind? … Also, I will be reaching hyd tomorrow and only then will be able to get my hands on the laptop. Then I will try patching the latest upstream release and building it as wxl: commented. … Then I will try to understand and follow [06:07] what you said. [06:07] I did clarify in the task itself, does that make it any clearer? [06:11] Yup! That's clear. But if it was the same thing you wrote here upwards, why did it sound like greek? XD [06:11] In the task I attempted to lay it out clearly [06:11] Some things might not sound correct to non-native speakers [06:11] I'm a native speaker and so is Walter, so I can use specific phrases [06:12] For example "plan of attack" isn't really talking about attacking something, it's referring to the actionable steps to get to a final result. It's used in an informal sense [06:13] "We're golden" doesn't mean it works perfectly (or looks like gold), in this case it means that it works as intended [06:14] You know, a bunch of those phrases I wouldn't normally throw at a non-native speaker unless they sound like they're a native speaker :) [06:15] I guess what I'm looking to describe is connotations associated with phrases [06:16] If you're not talking about the English but rather the process I'm describing, that's also the point of laying it out in the task ;) [06:23] Anyway, please do let me know if you have any questions, either about the English or the technical stuff :) [06:32] Yeah. I wasn't talking about phrases. I was talking about the process. But I read the comment on task. I got it. [06:32] Cool :) [09:12] Anyone online? I want to test something. [09:12] On the irc. [09:13] I'm here. [09:13] Nice. Wait a min please. [09:14] Sure. [11:50] -lugito:#lubuntu-devel- [rLIBFMQTPACKAGING53e5a5569132: Update symbols] apt-ghetto (apt-ghetto) committed: https://phab.lubuntu.me/rLIBFMQTPACKAGING53e5a5569132 [12:37] -lugito:#lubuntu-devel- [rSCREENGRABPACKAGINGa96956cb420c: Fix patches] apt-ghetto (apt-ghetto) committed: https://phab.lubuntu.me/rSCREENGRABPACKAGINGa96956cb420c [15:07] @The_LoudSpeaker you saw i sent you two emails? [15:10] Yup! One had two attachments. I didn't understand why. [15:11] the second one is the one you want [15:11] it's GPG encrypted [15:15] @lugito [ 3[ 13rSCREENGRABPACKAGINGa96956cb420c: Fix patches 3] 15apt-ghetto …], @aptghetto whic is th eproblem with screengrab? [15:16] It did not build from the tip of the master [15:16] The commit is only in ci/unstable [15:24] ok, we need to add screengran in seed, to replace lximage-qt https://github.com/lxqt/screengrab/issues/42 [15:47] @wxl [ it's GPG encrypted], Okay. So it will open from my laptop only. Right? I was trying to log in using phone. … Lite. I will check tomorrow. [15:48] it'll only open from a system where your GPG key is available [15:48] so yes likely only your laptop [15:48] unless you set up a mail app on your phone that has GPG/PGP integration [15:50] e.g. openkeychain [15:50] & since we're using email k9 [15:52] ^ that [15:56] Ack. [16:03] don't mind me [16:03] !hash [16:03] Factoid 'hash' not found [16:04] !md5 [16:04] To verify your Ubuntu ISO image (or other files for which an MD5 checksum is provided), see https://help.ubuntu.com/community/HowToMD5SUM or http://www.linuxquestions.org/linux/answers/LQ_ISO/Checking_the_md5sum_in_Windows [16:04] !gpg [16:04] gpg is the GNU Privacy Guard. See https://help.ubuntu.com/community/GnuPrivacyGuardHowto and class #8 on https://wiki.ubuntu.com/ClassroomTranscripts [20:05] @tsimonq2 I saw the comment on the libfm-qt commit. Should I revert the last (few) commit(s)? [20:06] @apt-ghetto [ @tsimonq2 I saw the comment on the libfm-qt commit. Should I revert …], Go ahead and keep it, just revise them [20:06] And is there any documentation about symbols? I did not found anything useful [20:06] Heh, heh, yeah so about that... [20:06] @RikMills might have some secret links he's been hiding [20:06] *blames @tsimonq2* [20:06] Otherwise it's basically all learned [20:07] I am adding them always manually, which is sometimes a bit hard [20:07] We don't use their tool, but this might help too: https://qt-kde-team.pages.debian.net/symbolfiles.html [20:07] @RikMills might go insane without the tool... [20:09] @tsimonq2 y u no ever clean mailbox [20:09] *points at 32GB of crap in your mailbox* [20:13] Another question: I tried to fix the patches of screengrab on ci/unstable. Is there something like uscan, to download the github master as *orig.tar.xz? [20:16] @apt-ghetto [ Another question: I tried to fix the patches of screengrab on ci/un …], There isn't, but feel free to either grab the orig tarball from the latest build, or look at how the CI does it so you can repro locally: https://phab.lubuntu.me/source/ci-tooling/browse/master/templates/package-unstable.xml$58 [20:16] Remember when I told Hans that copyright is the worst thing about a package? Symbols are definitely a close second [20:18] The goal of symbols is just to make sure that reverse dependencies are updated when a library removes or adds public functionality that it's reverse dependency uses [20:18] *its [20:19] So when you remove a symbol that exposes private functionality, you're fine and you can just go ahead with that [20:19] When you remove a symbol that has public functionality, that's breaking ABI compatibility, and you need to make it clear in the packaging that the new state of the package breaks the old package [20:20] In Kubuntu, we would do this by adding an "abiX" suffix to the library name, where X >=1 and is incremented each time ABI is broken [20:21] Then, you Breaks/Replaces the old library name, and adjust reverse dependencies to depend on the new package name [20:21] It makes sense if you see an example and can internalize why things are done the way they are [20:23] One thing that I had a question about was this: if e.g. Eoan has a package with abi1, and the CI breaks ABI compatibility multiple times, do you just keep bumping X? The answer is no [20:23] You only need to bump the package name to indicate ABI breakage between versions actually uploaded to the archive [20:24] In reality, since the CI rebuilds itself once every day at minimum, and libfm-qt is only used by LXQt packages (I think), you can assume that after at most a day or two that the reverse dependencies are rebuilt against the newly-versioned ABI [20:25] One more thing about this specific instance: libfm-qt builds started breaking on July 10th. I can tell this because it's the most recent build that migrated to the "release pocket" of the CI [20:26] And because it's only for one release, the release in between, I'm with @RikMills in betting it's a compiler issue [20:27] What I would personally do at this point is check the disco-changes mailing list for July 7-9th (phasing, see the SRU page for more details) and see if anything was released to updates that is related to the compiler [20:28] If we're talking about a compiler update breaking existing symbols in a package, while in the package itself you can mark it as optional (see the Debian Qt/KDE page for more), that to me is worth chasing as a compiler regression [20:28] -lugito:#lubuntu-devel- [rMANUALa5d06bc88024: Add listing installed files] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALa5d06bc88024 [20:29] One other thing to note is that if we have proposed enabled for the CI builds (I forget if we do or not, but just in case) you're looking for updates that went into disco-proposed as well [20:29] Does all of this make sense to people who are following? Specifically @aptghetto [20:30] Well, it does not sound wrong [20:31] Heh :) [20:31] @RikMills has had a lot more recent experience with symbols, so, not to put him on the spot (and I'm not saying it's his favorite thing in the world), he can help as well [20:31] I need some time to understand and a lot of practice [20:31] Very much understandable [20:31] And I am working only on ci/unstable [20:32] Sounds good, feel free to experiment there and with local builds :) [20:32] You have an idea about trojita? [20:33] -lugito:#lubuntu-devel- [rMANUALcda5d25cc05b: Add lisitng upgradeable packages] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALcda5d25cc05b [20:33] If you're looking for rapid iteration on your builds, try getting a Disco schroot and setting the CI Unstable PPA as a dependency; details are in https://wiki.ubuntu.com/SimpleSbuild [20:33] @apt-ghetto [ You have an idea about trojita?], I haven't quite looked at that [20:34] Ohh, right, I remember this [20:34] One of the weird architectures has a failing build [20:34] s390x? *shot* [20:34] @teward001 [s390x? *shot*], The other weird one ;) [20:35] ppc64el? arm64? armel? armhf? i386? amd64? :P [20:35] ppc64el [20:35] good so I just had to dump all arches and you figured out which one :stuck: [20:35] armel? 2013 is calling, they want their arch back [20:35] *shot* [20:35] my helpful task today is done :) [20:35] -lugito:#lubuntu-devel- [rMANUAL927ddc3d074a: Add not installed sorting filter] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL927ddc3d074a [20:36] at least it ain't `hurd`. [20:36] apt-ghetto: think of it on simpler terms. libXYZ-1 has the public symbol "int my_func_name(void)" ... later, the signature is changed to "int my_func_name(char *)" - that breaks the application's binary interface since anything that links to libXYZ-1 expects the former. So, you 'bump' the ABI to libXYZ-2 to indicate the public signature of my_func_name changed. [20:36] wxl: how I revert the nm-connection-editor.patch? [20:37] Anyway apt-ghetto, you have a few options here... First off, I would file a bug upstream and try your best to work with them to get a solution. If you can't do that and you're feeling up for it, I can help you get access to a ppc64el porterbox in Debian to debug. Otherwise, if all else fails, just disable building for ppc64el [20:37] @HMollerCl: just make a new commit that reverts the change [20:37] @TJ- [ apt-ghetto: think of it on simpler terms. libXYZ-1 has the public symbol " …], This [20:37] ok, I thought there was an "undo" option [20:37] I think wxl should write some documentation about the symbols talk we just had XD [20:38] not it [20:38] @HMollerCl [ok, I thought there was an "undo" option], There's a short answer and a thorough one [20:38] The short answer is just to comment it out in the series file, and that's what some packagers do *cough* agaida *cough* *cough* [20:38] I would absolutely consider that half-...baked [20:39] Otherwise, you remove the line from series and also remove the patch file completely [20:39] don't even suggest that jeeez [20:39] That being said, although it is GTK, I do think that any GUI is better than no GUI [20:40] @wxl [ don't even suggest that jeeez], It's good to note just in case anyone ever has to do merges from Debian XD [20:40] but for instance, the changelog would have the 2 entries? the change and the revert? [20:41] @HMollerCl [but for instance, the changelog would have the 2 entries? the change and the rev …], If the change has never been in the archive, you can remove that entry [20:41] For all useful purposes you should consider changelog entries that have already been in the archive to be immutable [20:41] I fix whitespace though :) [20:42] @tsimonq2 [I fix whitespace though :)], and should get chastised for it. [20:42] -lugito:#lubuntu-devel- [rMANUALbf10bf632487: Add broken filtering to show broken packages] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALbf10bf632487 [20:42] :P [20:42] ok, thanks! [20:42] Do you know how many whitespace fixes I had to do to the pastebinit package?!? [20:43] Oh and btw wxl, I now maintain pastebinit in Debian [20:44] -lugito:#lubuntu-devel- [T21: Our xscreensaver theme is too old] wxl (Walter Lapchynski) commented on the task: https://phab.lubuntu.me/T21#1589 [20:44] oh yeah? ^^ check that out [20:45] I'm going to continue poking stgraber about working on the upstream as well [20:45] If I continue to get radio silence from him, I'll just fork it myself [20:45] @wxl [ oh yeah? ^^ check that out], Nice! [20:46] -lugito:#lubuntu-devel- [T21: Our xscreensaver theme is too old] wxl (Walter Lapchynski) edited a message on the task: https://phab.lubuntu.me/T21#1589 [20:47] wxl: those colur could match our openbox theme? [20:47] they can be any hex colors afaik [20:47] feel free to have at it! [20:48] i did the hard part, it hink, which is figuring out the fonts [20:48] the x11 fonts are grossssssssss [20:48] those are better fibts [20:48] fonts [20:48] Hey wxl, wanna maintain pastebinit in Phab? XD [20:48] no [20:48] Aww why not? [20:49] It'll be fun! [20:49] arc paste works fine :) [20:50] No, I mean, literally pastebinit upstream [20:50] i don't know maybe [20:50] Perhaps we'd add that functionality to pastebinit as well ;) [20:50] i don't want to give ourselves more projects [20:50] Bah [20:50] we've got enough [20:50] unlike how some people think, we can't do everything [20:50] and even if we could, we couldn't do anything *well* [20:51] I'm not saying we take pastebinit over and completely overhaul the codebase [20:51] But perhaps work on it as a more passive project [20:51] i'm skeptical [20:52] Understandably [20:52] hey wxl, @tsimonq2 lubuntu-update-notifier has the option to do cache-update + upgrade [20:52] We coudl have a .desktop for "search for upgrade" [20:52] should I create it? [20:52] yes! [20:53] ok [20:54] @HMollerCl: I was looking into your code and found a lot of commented out code, in my opinion, you should either remove it, or write a comment, why this is commented out [20:54] How many projects *do* we have right now? I know we have a lot of open tasks, but still [20:54] @apt-ghetto [ @HMollerCl: I was looking into your code and found a lot of comment …], yes, I'm cleaning it out, Thanks! [20:55] Nice work @HMollerCl :) [20:55] @HMollerCl: And in the shell script you write the variable with all caps. A common convention is, that all caps is used for environment and shell variables (IFS is the only i saw). The rest should be lower or camel case [20:56] "camel case" ? [20:56] snake_case > CamelCase [20:56] Er, camelCase [20:56] Camel case is "lowerAndUpperCase" [20:56] ok. [20:56] @tsimonq2 [snake_case > CamelCase], My personal opinion :P [20:57] But camel case is more prone to typos, so maybe only lower case [20:57] Tsimonq2_Case [20:57] XD [20:57] sss_im_a_snake [20:57] -lugito:#lubuntu-devel- [rMANUALb61ef8cbaa0b: Add Residual configuration to muon] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALb61ef8cbaa0b [20:58]