Closed mtalexan closed 1 year ago
EDIT: So apparently I was looking at the index in nix profile list
with my initial report, not the home-manager generation, so I've updated the description with the more specific usage problem I'm encountering: nothing actually got installed.
Maybe fleek is only adding the home-manager config for these packages and isn't installing the actual nix packages? If so, that would probably be at least part of the bug, but doesn't explain the aliases not working.
I can run nix profile install nixpkgs#neovim
and it installs it successfully.
Confirmed. fleek add
adds to the packages
list and not the programs
list. Also, having the same package in both the packages
and programs
list causes a conflict. If it's added to the programs
list and removed from the packages
list, the fleek apply
correctly installs it and it shows up in the nix profile list
.
I'm updating the title accordingly.
At this point there's no documentation on what was intended from these, so I'm just guessing.
In the current state it appears fleek
can be used to (mutually exclusively) define the nix packages you want installed (programs
section), or define the home-manager config of a package you installed manually (packages
section). Fleek produces an error if the same package is listed in both places, even though that seems to be the exact use case for the tool. Or maybe I'm misunderstanding what the packages
list does, but either way fleek add
then fleek apply
does not work like the fleek.gif in the README.md shows, that will fail 100% of the time on the final which dnf
command.
I just cleared out the old fleek config and re-installed:
fleek eject
rm ~/.fleek.yaml
rm -rf ~/.local/share/fleek
And re-installed it from scratch with git already setup:
curl -fsSL https://getfleek.dev/installer | bash
git config --global user.email
GitHub
SSH keyThen edit the .fleek.yaml
to set bling: none
. Then I ran the all-in-one command fleek add --apply neovim
and got a warning message about my .bash_profile
and .bashrc
being in the way and getting backed up (for the first time ever).
The nix profile list
still only lists the home-manager-path
, but which nvim
is successfully finding the package now.
So it seems there's a bug somewhere in the fleek
installation and fleek init
process. Likely an interrupted fleek init
(which is guaranteed to happen since the GitHub email and SSH key requirements are undocumented) can cause a screwed up init state that in my case manifested as home-manager not actually managing the environment.
I'm closing the issue since I seem to have gotten past the problem and can't figure out what caused it in the first place.
Describe the bug
fleek apply
doesn't install any of thefleek add
ed packages or make any of the custom aliases available.To Reproduce
fleek init
fleek add neovim
fleek apply -v
fleeks
alias
which nvim
nix profile list
cat ~/.fleek.yaml
Actual behavior
fleeks
reports the command is unknown.alias
reports thefleeks
alias doesn't exist.which nvim
reports no such command is found.nix profile list
reports that onlyhome-manager-path
is installed and notneovim
.Expected behavior
The default
fleeks
alias should exist and work.The
nvim
command, which is installed as part ofneovim
should be installed in the nix profile.Environment
Additional context
The
~/.fleek.yaml
listsneovim
in thepackages
section after thefleek add neovim
, and thealiases
section does include the defaultfleeks
alias.EDIT: It turns out the issue is
fleek add
adding to the wrong list in the.fleek.yaml
so the package isn't usable (not sure what thepackage
list can even be used for, it seems to be completely non-functional).