gospt crashing easily #2
Labels
No Label
bug
duplicate
enhancement
help wanted
question
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: abs3nt/gospt#2
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hi,
Continuing the reddit discussion here instead.
I've asked a couple of fellow devs to test the package, which I've imported to our WIP-repository, http://mail-index.netbsd.org/pkgsrc-wip-changes/2023/01/16/msg026094.html
Quoting the response,
and some other times,
Do you believe these are only related to a missing background client running?
Thanks!
the second one looks like its happening when opening the tui if you have no artists saved in your account which i can add checks for to make it not do that. as for the first one when is that happening? it might be related but i am not sure what events led to the crash
i just pushed a fix for the second issue
ea69ad6310
it may also fix the first issue but i am not sureI couldn't tell but, I can ask if you want.
Would you agree with the comment I've added to the package?
Or, would you prefer to express it in another way?
Cheers! I'll keep updating the package.
this is accurate
didnt mean 2 close this
You may close it now if you would like.
Things are working fine. Will test for a few hours and merge it if I don't hit any issues.
@abs3nt Package merged into the main branch now. See commit, http://mail-index.netbsd.org/pkgsrc-changes/2023/01/18/msg267288.html
To install it on NetBSD you will simply need to run:
Or, if you prefer to build it from source:
Regards,
pin
FYI, up-to-date http://mail-index.netbsd.org/pkgsrc-changes/2023/01/21/msg267547.html
Have you thought about a ChangeLog?
nice thank you. does netbsd pull from something like CHANGELOG.md or is it a manual entry. I might add one in the next release im not sure yet.
it's a manual entry. usually, I just copy the ChangeLog or, release notes and paste this into the commit message.
got it. I can just make release notes for more important changes / updates in the future.