Have you tried blacklisting the nouveau driver?

I made an effort to implement the script in bash, but it's buggy as hell. Definitely not going to be a viable option.

Is this still an issue? If so, please provide an lspci and let us know which kernel you are currently using.

Started trying to port the mksh scripts to bash. This will take a while if I'm doing it alone, as I've never scripted mksh/ksh93 before. Lots of differences, some bigger then others.

Figured it out, currently have a pr on Github. Unless you want to have a separate boot partition when using xfs on bios only system, we may need to not enable xfs for root as grub panics when trying to boot from it.

The gpg agent still uses the ssh keys when adding ssh agent functionality. It needs ksshaskpass for ssh keys (in a Gui), and the pinentry program is used for gpg keys.

As for not using mksh, I never tried without it. Can give it a try in a vm in a bit.

In T6236#112879, @sunnyflunk wrote:

Okay, lets have a look at what the issues are that this solves (and it will have to solve it out of the box to be worthwhile). Perhaps they can be solved without the package at all. My issues are (that seem relevant to this package):

• Need to enter password every single time ssh is used (I definitely think it can be fixed without kwalletcli, but needs configuration)
• Signing git commit without password cause it should be saved in kwallet

Both hurt Solus development productivity. Are there any others that this package solves?

Issues with kwalletcli:

• Really shouldn't require mksh to function (i.e. test patching out defining mksh as the bash interpreter in the scripts)

What is the client side configuration you are using with kwalletcli?

Also, fixes T3625

This package is required for D2754.

Added 2 new packages, D2754 and D2755 which add kwalletcli and mksh packages.

Anybody getting the tests to run properly in mksh using solbuild? Tests run perfect when building on my system, but as soon as I use solbuild, it complains about a missing tty (fd I think) and fails the check stage.

@JoshStrobl and @ikey how can I generate a test install image? I'm currently upgrading a bunch of packages in the livedvd environment in VirtualBox to get my git fork of the installer to test. There must be a better way.

Mainly because I have to learn python to do this. I'm not sure what will be easier to do, but I'm going to study the source and see about integrating it for /home as a start.

Sorry, this was an accident.

Need this included soon, so I don't have to go through the hassle of configuring a docker xdebug session. Downloaded and tested that the package builds, and can be used for debug sessions when done.

@JoshStrobl maybe in your spam box? Either way, I can host a Canadian mirror, just need to know how to set it up, and how to help ease the process.

I sent a couple emails to @JoshStrobl about hosing a Canadian package mirror. Is this the hold up? If so, what can I do to help out?

Thanks for walking me through this @JoshStrobl. I want to be a frequent contributor however I can, but learning a new flow can be daunting.

Added test plan

Updated pspec.xml as per JoshStrobl

Forgot to update the release number.