Add a reference to the upstream issue edit: (to the commit body)

Let's get the description moved to be immediately after summary, otherwise LGTM, thanks!

done

Bump package release, thanks @Jacalz o/

I'm not sure what's going on with the pspec file here... I get this massive diff: https://paste.sr.ht/~robertgzr/a598cf3ca6dc4fb47017f357bedc05f9669015d2

What's the status of this? I hit this myself trying to package imv

rebased

This will be blocked on https://dev.getsol.us/D5611

Very nice!

I have updated wayland-protocols to 1.17 https://dev.getsol.us/D5611

Rebase repo onto https://dev.getsol.us/source/alacritty/

Include 0.2.8

In D5048#84647, @JoshStrobl wrote:

You didn't update this against our alacritty repo

You have to keep in mind that the solus team is not the biggest so it sometimes takes a while... and this is foss after all so they don't really owe you anyting ;)

Include 0.2.6 and 0.2.7

In D5048#81612, @sborer wrote:

In the meantime 0.2.6 and 0.2.7 have been released.

Adding this enables hardware acceleration when screencapturing

Update pspec

forgot to add the updated pspec -.-

Fixes according to review

In T7206#140045, @DataDrake wrote:

Well you never reopened the patch.

I had literally submitted a differential before creating this task - which was pointed out to me to be a mistake :p

Added the terminfo files to the package

What needs to be done to move this forward?

@Girtablulu I was aware of their request not to package it at this point...

Do I also create separate tasks for the new dependencies?

ping

Addressed comments and updated to latest release v0.2.4

Skip 0.3.0 in favour of 0.3.1 (latest)

But I just saw https://github.com/neovim/pynvim/releases/tag/0.3.1

In D4364#70316, @DataDrake wrote:

Not building, did the hash change?

If anybody is familiar with fish, can you check that this is right.
I checked https://fishshell.com/docs/current/index.html under the "Where to put completions" section
and third-party vendor provided seemed to be appropriate.

I mentioned it because it seems an indicator (to me at least) they actually want people to package it

As a heads up, it seems like they're doing proper versioned builds now, including deb packages

Sorry for the noise then :p

Sorry if I'm spamming here... I would love to contribute to solus more now. Do I just go ahead and open a pkg update for review if I already have the patch for it? For new pkgs it seems you need to have at least a request for them before submitting them for inclusion

Do I make a package request myself?

@Jacalz awesome, thanks

👌

I've been using the same keepass database for as long as I've been on the internet. The last at least 2 years of this time with KeeWeb, mostly because MacPass was abandoned and it had tags which I began to use instead of groups.