-
Notifications
You must be signed in to change notification settings - Fork 62
kiss aborts during checksum verification when it shouldn't #248
Comments
I can reproduce. On it. |
Fixed. Thanks for your continued reports. Let me know if the issue still occurs, I can no longer reproduce. (Issue was |
Is indeed resolved now, thank you sir! |
Will push a release shortly. While I have you, what do you think of this (related to #224)?
|
(This is not really a proposal as the mere change to execute hooks in non-Git repositories makes this possible.) Just letting you know this is now a "feature" I guess? 😆 |
I love the idea of this -- part of my interest in this (kiss-community@e04b26d) change was so that
Very important. It also means that users aren't forced to stay inline with the repository maintainer just to do updates (though you did allow this in dfd000e which I love). I think this change is a Good Idea(tm); it's not really burdensome on users - there's... a single extra step for repository maintainers (which they have to do probably just once, if at all), and the requirement for a user is basically equivalent to them checking out the repository in the first place. There's a small amount of friction there, though; perhaps the hook should be enabled by default, or a prompt for users to inspect the hook (print it to |
This is what it looks like: #251
The idea behind utilizing The package manager doesn't store any kind of persistent state (only downloaded package sources and built binaries) so there's Anyway... will tinker with this and come up with some kind of one-step process (though I quite like the two-step process regardless). |
So I made a pull request for my repos repo to use the new hook system, and had a few questions:
As far as 'one step process' I think this should work, though I need to test it this week. |
Please correct me if I am misunderstanding, but I don't think the package manager needs to do anything special regarding tracking state for hooks compared to any other package. If we package hooks, then we can use all the facilities we have for managing system state for free. |
Description
Packages which have git+* sources don't have checksums, but
kiss
will abort during the checksum check. However, this ONLY seems to happen in cases where that package 1) has a dependency that isn't already built or installed, and 2) has a source which requires no checksum.All of this is done in a fresh chroot, where
kiss
is latest master.Error message
Verbose log
If I do
kiss b ncurses
and installncurses
first, the build forvim
proceeds as normal.The text was updated successfully, but these errors were encountered: