So, I deleted the ~/.deken directory, and then also ran 'sudo apt-get
remove deken' (because I think I had also done 'sudo apt-get install
deken'). Then, there was still a deken executable in my system, so I ran
it and it installed deken! It seems that now deken works fine, in the
latest version, 0.9.3.
Thanks for the help!
On 30/6/22 10:08, IOhannes m zmoelnig wrote:
On 6/30/22 08:38, Alexandros wrote:
first thing to try is simply to self-update deken:
```
deken update --self
```
This goes though some process but ends up with the following:
Traceback (most recent call last):
File "/home/alexandros/.deken/virtualenv/bin/pip", line 5, in <module>
from pip._internal.cli.main import main
ModuleNotFoundError: No module named 'pip'
Installation of requirements failed.
You probably should install the following packages first:
- 'python3-dev'
- 'libffi-dev'
- 'libssl-dev'
I did install the recommended packages, but keep on getting this error.
it seems that the final error hint ("you should install...") is simply
wrong.
the important error message is "No module named 'pip'".
the "you should install..." is simply the printout for *anything* that
goes wrong, as it assumes that the most that could go wrong is some
problem with building some modules; but your problem is much deeper.
in fact, it seems that you somehow managed to "uninstall" various
python modules, but keep their cmdline wrappers available (even though
both the modules and the wrappers are installed by the very same
packages).
```
deken uninstall --self
This can't run, I get the same error concerning hy
very unlikely.
it's not that i don't believe you (or your observations), but running
"deken uninstall --self" *should* bypass all things hy... (and i just
checked the code of upstream/0.6.0, upstream/main and Debian/0.6.0-1
to confirm that it really should do this)
...unless you somehow pass additional arguments (e.g. via aliases),
which you shouldn't; or unless you have completely bonkered your
python installation, in which case i would like to stop this thread
and ask you to repair the system first).
Can't I uninstall it with apt-get? Or delete some files manually? If
so, which files are these?
ah well:
(in theory) you can install deken in two ways:
- via apt-get
- via the manual bootstrap
the two ways are fundamentally different (as in: they install files to
very different locations) and you cannot really *mix* the two.
in practice it is possible install deken both manually and via apt on
your system, but it is not recommended. actually: i would discourage
this.¹
so:
0. decide which route you want to take (apt, or manual bootstrap).
1. get your system clean.
esp. make sure to uninstall the "other" deken (the one you decided
to not use)
it's probably simplest to just make sure that deken is neither
installed via apt nor via the manual bootstrap process.
3. ensure that `which deken` is what you expect (if you decided to go
the manual route, the system should NOT find the binary in /usr/; vice
versa, it shouldn't find the binary in your home if you go the apt
route; if you decided to start from scratch, it shouldn't find a
binary at all!)
4. only once you have completely purged the "other" deken, start
installing deken.
gmdars
IOhannes
PS: oh, and "deken uninstall --self" simply removes the deken script
itself and everything in ~/.deken~/; so if you somehow cannot manage
to run "deken uninstall --self", you could also do this manually.
PPS: do *not* run the manualy bootstrap process as root/superuser.
¹ this is actually true for all software.
_______________________________________________
Pd-dev mailing list
[email protected]
https://lists.puredata.info/listinfo/pd-dev
_______________________________________________
Pd-dev mailing list
[email protected]
https://lists.puredata.info/listinfo/pd-dev
