TBH I just wrote the summary as I felt it comfortable in the terminal, the 80-cols rule came out unintentionally :P
Remove the C/C++ flags patch
Remove dep on leveldb.
Update test plan
This issue has been deemed by the developers to be an issue related to Budgie, our primary desktop environment. As Budgie is a distro-agnostic project, developed by Solus but leveraged by other operating systems and projects, we maintain a dedicated issue tracker for it. This issue tracker can be found at https://github.com/solus-project/budgie-desktop
removed GitHub issue references and git commit links.
Will need @DataDrake's input on this as he's Technical Lead.
This looks good to me.
Please remove the GitHub issue references and git commit links. Thanks.
Your changelog is incorrect, you're using incorrect indentation and indentation formatting. Really your changelog should be:
@livingsilver94 and you need to figure out which one of these patches should be abandoned since you both have mongodb update patches.
Additional revdeps need testing. At the very least, libtorch and pytorch should be rebuilt, minetest should be rebuilt and validated.
Go for it, one less thing for me to maintain.
@JoshStrobl Are you ok if I stepup as Maintainer for this package?
None of the above contradicts what I said about why I opened the request-for-package when the request-for-maintainer was closed. Will keep all further discussion unrelated to patches themselves to IRC. Thanks
This is not how things played out and again, I don't appreciate the way you're framing my actions. I opened the request-for-package because you closed the request-for-maintainer for a package I still needed, regardless of that one use case. But this is dragging on and dumb and there are much more important things to worry about in the world so this is the last I'll say on the matter.
Will get this landed before sync.
The other changelogs, that you personally approved, were copy pastes; just saying. So, again, I'm so very sorry for following the same pattern that was accepted in the seven previous releases. I will summarize the changes.
Further summarize change log
- Changelogs should always be summarized, not verbatim copy / pasta. You read the changelog and use your best judgement to determine what is actually important / noteworthy.
- Regarding GitHub issue stripping, it's because they aren't relevant to us, aren't going to get autolinked, etc. Also...you know...because kyrios is a Global Maintainer and he told you to.
Remove changelog lines related to Windows
Forgot to bump release.
@ermo I also cooked up a .xprofile and tested it on all four DEs. My question is, how should I proceed to create a patch for that? Should I create a patch for baselayout? My concern is that I have no way to test whether the new baselayout package works as intended.
@DataDrake can't really figure out where the building problem is. It may be related to the number of threads the build server CPU can handle, but I can't figure out how to limit the job count if that's the cause.
Update to 6.5.0, fix issue with building with recognized terminals
Remove code which sources key maps and xsessions. Only source .profile, .xprofile and .Xresources.
ikea build them static but couldn't find a reason why