-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: Kali kali-rolling is unsupported. You can specify Ubuntu or Debian manually. #19
Comments
Kali is based on Debian correct? If it's rolling I would assume it's based on sid? If this is the case you can use I would need the output of sources.list (just to see which repos they use) |
I can help with the Kali system info. Here is the following sources for PRETTY_NAME="Kali GNU/Linux Rolling"
NAME="Kali GNU/Linux"
VERSION_ID="2023.4"
VERSION="2023.4"
VERSION_CODENAME=kali-rolling
ID=kali
ID_LIKE=debian
HOME_URL="https://www.kali.org/"
SUPPORT_URL="https://forums.kali.org/"
BUG_REPORT_URL="https://bugs.kali.org/"
ANSI_COLOR="1;31"
# See https://www.kali.org/docs/general-use/kali-linux-sources-list-repositories/
deb http://http.kali.org/kali kali-rolling main contrib non-free
# Additional line for source packages
deb-src http://http.kali.org/kali kali-rolling main contrib non-free |
I have added a list of different repos in the sources.list.d folder but cant see a way to use this within fetch. Is this possible? |
Sorry I'm so late on this. But not really, the distros have to be supported in the code base, because there is parsing required depending on source. Like Debian uses their Deb format which is easy and used everywhere in Debian, Ubuntu I have to parse RSS. This is kind of a weird thing I need to rethink on how we can make it better, and probably a way you can pass through a mirror list manually that it can use to test. For Kali specifically though I am having trouble finding if they even have a definitive list of mirrors like some of the other distros. http://kali.download/kali/README?mirrorlist, I have found this which isn't very helpful, seems to imply I will get to a mirror list some where but I never do. https://mirror-traces.kali.org/ This appears to be the best choice, but parsing HTML is not the best idea for stability, as if they change their website a little bit it will break. Additionally they are not sorted by country code, some of them have country code as the TLD, but that's not guaranteed. If there is a source of mirrors in the deb format like https://mirror-master.debian.org/status/Mirrors.masterlist, it would be pretty trivial to add it. Something like json, xml, rss wouldn't be too difficult either. |
What can I do in this case?
It doesn't seem to support Kali Linux
Is it possible for you to explain to me what to do about this? Would love to hear all possible tips and explanations.
By the way, great software in my opinion!
sudo nala fetch
Error: Kali kali-rolling is unsupported.
You can specify Ubuntu or Debian manually.
Usage: nala fetch [OPTIONS]
Nala will fetch mirrors with the lowest latency.
For Debian https://mirror-master.debian.org/status/Mirrors.masterlist
For Ubuntu https://launchpad.net/ubuntu/+archivemirrors-rss
╭─ Options ──────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ --debian sid Choose the Debian release. │
│ --ubuntu jammy Choose the Ubuntu release. │
│ --devuan stable Choose the Devuan release. │
│ --fetches INTEGER Number of mirrors to fetch. [defaults: 16, --auto(3)] │
│ --https-only Only get https mirrors. │
│ --sources Add the source repos for the mirrors if it exists. │
│ --non-free Add contrib and non-free repos. │
│ --auto Run fetch uninteractively. Will still prompt for overwrite. │
│ --debug Logs extra information for debugging. │
│ --assume-yes -y --assume-no -n Assume 'yes' or 'no' to all prompts. [default: n] │
│ --country -c US Choose only mirrors of a specific ISO country code. │
│ [default: None] │
│ --verbose -v Disable scrolling text and print extra information. │
│ --help -h Show this message and exit. │
╰────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
The text was updated successfully, but these errors were encountered: