[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
 @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
 @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
 pull request for multimonitor wallpaper support. https://github.com/lxqt/pcmanfm-qt/pull/1043
 OOOOOOOO
 phoda!!!
 Thanks! @HMollerCl for your work.
[19:24] <wxl> wow Hans, wow
 Also, @tsimonq2 you grammar nazi
[19:25] <wxl> spelling, to be fair
[19:25] <wxl> semantics and syntax are not the same
 grammar also. from my experience.
 But I apreciate it tho. afterall you are trying to help.
 Just messing here now.
 I'm abstaining from a proper review but I'll happily grammar nazi comments :)
 So grammar nazi is now a verb? Who knew?
 if @tsimonq2 is using it then it must be.
 Must be nice to be a developer….
 "release manager"
 where are your manners? :P
 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
 @HMollerCl [pull request for multimonitor wallpaper support. https://github.com/lxqt/pcmanfm …], This is great Hans!
 *correct
 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
 @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
 @Dreamingwolf [Though, to be fair, as a wordsmith I have 'altered' language on many occasions t …], *mighty
 @Dreamingwolf [Though, to be fair, as a wordsmith I have 'altered' language on many occasions t …], 😆
 XD
 @tsimonq2 [Correct it by pushing a commit to the branch that is the origin for the PR], done
 looking at https://ci.lubuntu.me/ all stable_libfm-qt are building ok but al unstable_libfm-qt are not. Is hat a trend?
 *that
 @kc2bez ^
[19:40] <kc2bez> Somewhat, yes. Stable stays the same and is based on the last merge, unstable is the tip of the git master.
[19:40] <kc2bez> It really depends on how much upstream changes.
 but what is the difference between bionic_Stable and bionic_unstable?
 shouldn't bionic be since months stable?
 It's the same code but built with a bionic base
 All of the code for unstable is the same regardless of the release
 It just depends on the toolchain etc.
 Does that make sense?
 mmm, giving that, it doesn't make sense to me to have bionic_unstable...
 now.
 good point I don't even see bionic branch in phab
 I'm more than willing to remove that :)
 I doubt anyone is using it
 I do that by SSHing into the box, su jenkins, cd ~/jobs/ (or similar), and rm -rf *bionic*
 Remove the release from our config in Git, regen jobs from disk in the Jenkins UI, and remove the Bionic packages from the PPAs
 I don't know that this is documented anywhere but it should be
 I'd be willing to walk someone through for bus factor purposes :)
 We should definitely go through it and I am willing to help. (maybe not right this moment but yeah)
 Sounds good
 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 :)
 @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.
 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...
 it may very well be. I don't know for sure but it probably needs an updated symbols file because upstream has changed.
 (hint: it does for sure)
 it is absolutely why the build failed according to the log.
 I know nothing about symbol files but in my focal libfm-qt builds w/o problem.
 https://qt-kde-team.pages.debian.net/symbolfiles.html "Handling missing symbols"
 If you have questions after reading that, please ask :)
 Bumping SONAME only needs to be done once every archive upload
 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
 (e.g. 1.1}
 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)
 It doesn't make any sense to me at this moment. I need to read more to understand it.
 thanks!
 Thanks, let me know :)
 @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
 @tsimonq2 [I'd also like to walk someone through the release process around release day. Wh …], wxl: go apply. :P
[20:34] <wxl> been there, done that
 Nothing against wxl because he's my backup right now and I took over this position from him, but we need fresh blood :)
 I know wxl is more than capable