usage: dbpInstaller.sh [-h] [-i pck [pck ...]] [-d dest] [-u] [-U] [-l] [-I]
install DBP packages.
optional arguments:
-h, --help show this help message and exit
-i pck [pck ...], --install pck [pck ...]
Install the packages from a list of package id
-d dest, --dest dest SD-Card to use
-u, --update Update the cache
-U, --upgrade Upgrade installed packages
-l, --list List known packages
-I, --installed List installed packages
What is ketm?
I dont get your question.there are some DPB out there that ditnt work because they were made for a early prototypes Debian, will they also get showed?
Yes, there's a disconnect what you think constitutes the word 'available' and what sebt thinks it means. For him it's about whether a dbp it well formed such that it can be investigated and installed. For you it also includes whether it works or not after you install it as well. I'm not sure there's one better than the other or not there. I don't know why they wouldn't get updated if the member is stiill active about these parts and is notified that their dbp isn't working.My question was also not that good, if there are non working dbp , the dbp installer can’t know that it’s not working, so it’s more the task of the dbp maker to update them , but if these are still on the Repo i doubt the will get updated.. You can say everything after Wally’s drastic Port should work
Traceback (most recent call last):
File "/mnt/dbp/union/dbpInstaller_sebt3/dbpinstaller/ui/installerui.py", line
207, in on_update
self.installer.get_packages_list(),
AttributeError: 'DbpInstaller' object has no attribute 'get_packages_list'
It's indeed a typo introduced during code refactoring (my fault, btw. Sorry.).Looks like an untested typo in the python code to me.
my bad : I should have tested more in deep. Like I did for this batch of changes you sent(my fault, btw. Sorry.).