[00:55] -lugito:#lubuntu-devel- [rMANUAL5501ba98a6eb: reload button] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL5501ba98a6eb [00:55] -lugito:#lubuntu-devel- [rMANUALeca27a2de5c1: Add description of save as button] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALeca27a2de5c1 [00:57] @HMollerCl [Do we have something about high dpi in the manual? @lynorian maybe this could co …], Hans we had something but I have not looked at high dpi for like this release [00:59] -lugito:#lubuntu-devel- [rMANUAL28beebf215ff: Remove uneeded double space] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL28beebf215ff [01:03] -lugito:#lubuntu-devel- [rMANUAL39098dfb5a80: Add left and right arrow buttons to lximage] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL39098dfb5a80 [01:18] -lugito:#lubuntu-devel- [rMANUAL8ace3c55a784: Add other ways to fullscreen pictures] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL8ace3c55a784 [01:19] @HMollerCl There is something else in that I had not considered was scaling thing like parition manager [13:55] -lugito:#lubuntu-devel- [T134: Calamares: Slideshow doesn’t show] ItzSwirlz (Joshua Peisach) commented on the task: https://phab.lubuntu.me/T134#2773 [19:18] pull request for multimonitor wallpaper support. https://github.com/lxqt/pcmanfm-qt/pull/1043 [19:19] OOOOOOOO [19:22] phoda!!! [19:23] Thanks! @HMollerCl for your work. [19:24] wow Hans, wow [19:25] Also, @tsimonq2 you grammar nazi [19:25] spelling, to be fair [19:25] semantics and syntax are not the same [19:26] grammar also. from my experience. [19:26] But I apreciate it tho. afterall you are trying to help. [19:27] Just messing here now. [19:27] I'm abstaining from a proper review but I'll happily grammar nazi comments :) [19:28] So grammar nazi is now a verb? Who knew? [19:28] if @tsimonq2 is using it then it must be. [19:28] Must be nice to be a developer…. [19:29] "release manager" [19:29] where are your manners? :P [19:30] If correcto those typos in the branch with a new commit, the new commit will be in the pr? Or I have to do something else [19:30] @HMollerCl [pull request for multimonitor wallpaper support. https://github.com/lxqt/pcmanfm …], This is great Hans! [19:30] *correct [19:30] Though, to be fair, as a wordsmith I have 'altered' language on many occasions to suit my needs… … And I heartily apologize for misrepresenting the might Oz…. I mean @tsimonq2 [19:31] @HMollerCl [If correcto those typos in the branch with a new commit, the new commit will be …], Correct it by pushing a commit to the branch that is the origin for the PR [19:31] @Dreamingwolf [Though, to be fair, as a wordsmith I have 'altered' language on many occasions t …], *mighty [19:31] @Dreamingwolf [Though, to be fair, as a wordsmith I have 'altered' language on many occasions t …], 😆 [19:32] XD [19:35] @tsimonq2 [Correct it by pushing a commit to the branch that is the origin for the PR], done [19:38] looking at https://ci.lubuntu.me/ all stable_libfm-qt are building ok but al unstable_libfm-qt are not. Is hat a trend? [19:38] *that [19:39] @kc2bez ^ [19:40] Somewhat, yes. Stable stays the same and is based on the last merge, unstable is the tip of the git master. [19:40] It really depends on how much upstream changes. [19:42] but what is the difference between bionic_Stable and bionic_unstable? [19:43] shouldn't bionic be since months stable? [19:43] It's the same code but built with a bionic base [19:43] All of the code for unstable is the same regardless of the release [19:44] It just depends on the toolchain etc. [19:44] Does that make sense? [19:45] mmm, giving that, it doesn't make sense to me to have bionic_unstable... [19:45] now. [19:46] good point I don't even see bionic branch in phab [19:46] I'm more than willing to remove that :) [19:46] I doubt anyone is using it [19:47] I do that by SSHing into the box, su jenkins, cd ~/jobs/ (or similar), and rm -rf *bionic* [19:48] Remove the release from our config in Git, regen jobs from disk in the Jenkins UI, and remove the Bionic packages from the PPAs [19:48] I don't know that this is documented anywhere but it should be [19:49] I'd be willing to walk someone through for bus factor purposes :) [19:51] We should definitely go through it and I am willing to help. (maybe not right this moment but yeah) [19:53] Sounds good [19:54] I'd also like to walk someone through the release process around release day. Whether that person becomes assistant release manager is up to them :) [19:54] @HMollerCl back to the differences between unstable and stable, I don't know offhand but you would have to do a diff on the branches to see. [19:55] thanks @kc2bez I was trying to se why libfm-qt failed in unstable, and since it failed i all, I thought it could something more systemic... [19:57] it may very well be. I don't know for sure but it probably needs an updated symbols file because upstream has changed. [19:57] (hint: it does for sure) [19:57] it is absolutely why the build failed according to the log. [19:59] I know nothing about symbol files but in my focal libfm-qt builds w/o problem. [19:59] https://qt-kde-team.pages.debian.net/symbolfiles.html "Handling missing symbols" [19:59] If you have questions after reading that, please ask :) [20:00] Bumping SONAME only needs to be done once every archive upload [20:00] So e.g. if 1.0 bumps SONAME and in CI you have multiple reasons to bump it, only bump it once before your next archive upload [20:01] (e.g. 1.1} [20:02] If any part of that doesn't make sense, let me know (it can help me explain it more effectively for the next person that needs to know) [20:02] It doesn't make any sense to me at this moment. I need to read more to understand it. [20:03] thanks! [20:03] Thanks, let me know :) [20:09] @HMollerCl [It doesn't make any sense to me at this moment. I need to read more to understan …], Feel free to experiment in the unstable branch [20:34] @tsimonq2 [I'd also like to walk someone through the release process around release day. Wh …], wxl: go apply. :P [20:34] been there, done that [20:54] Nothing against wxl because he's my backup right now and I took over this position from him, but we need fresh blood :) [20:54] I know wxl is more than capable