Troubleshooting¶
Solutions to common problems with Stout.
Installation Issues¶
"Command not found: stout"¶
Stout isn't in your PATH.
Solution:
# Add to PATH
export PATH="$HOME/.local/bin:$PATH"
# Add to your shell config file
echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.bashrc # or ~/.zshrc
source ~/.bashrc
"Permission denied" during installation¶
The installation directory isn't writable.
Solution:
# Option 1: Fix permissions on Homebrew directory
sudo chown -R $(whoami) /opt/homebrew
# Option 2: Use a local prefix
stout prefix create ~/.stout
stout --prefix=~/.stout install <package>
"Binary not found for your platform"¶
No pre-built binary for your system.
Solution:
Build from source:
Update Issues¶
"Signature verification failed"¶
The index signature is invalid or expired.
Solution:
If problem persists, check your system clock is correct.
"Failed to download index"¶
Network connectivity issue.
Solution:
# Check connectivity
curl -I https://raw.githubusercontent.com/neul-labs/stout-index/main/index.json
# Use a mirror if available
stout --mirror=http://internal-mirror.company.com update
"Index too old"¶
Your local index hasn't been updated recently.
Solution:
Package Installation Issues¶
"Package not found"¶
The package doesn't exist or isn't indexed.
Solution:
# Update index
stout update
# Search for the package
stout search <partial-name>
# Check if it's in a tap
stout tap neul-labs/extra
stout search <package>
"Checksum mismatch"¶
Downloaded file doesn't match expected hash.
Solution:
If problem persists, the package may have been updated. Run stout update.
"Bottle not available"¶
No pre-built binary for your platform/version.
Solution:
"Dependency conflict"¶
Two packages require incompatible dependency versions.
Solution:
# Check dependencies
stout deps --tree <package>
# Try installing without conflicting package
stout uninstall <conflicting-package>
stout install <package>
"Disk space full"¶
Not enough space for installation.
Solution:
# Clean old downloads and versions
stout cleanup
# Check what's using space
stout list --versions
# Remove unused dependencies
stout autoremove
Runtime Issues¶
"Too many open files"¶
Hit system file descriptor limit.
Solution:
# Increase limit for current session
ulimit -n 10240
# Make permanent (add to shell rc file)
echo 'ulimit -n 10240' >> ~/.bashrc
"Library not found"¶
Dynamically linked library is missing.
Solution:
# Reinstall the package
stout reinstall <package>
# Or reinstall dependencies
stout reinstall $(stout deps <package>)
"Command not working after install"¶
Symlinks may not have been created.
Solution:
Cask Issues¶
"Application can't be opened (macOS)"¶
macOS Gatekeeper is blocking the app.
Solution:
- Open System Preferences > Security & Privacy
- Click "Open Anyway" for the blocked app
Or remove quarantine:
"Cask install fails with existing app"¶
Application already installed outside of Stout.
Solution:
# Remove existing app first
rm -rf /Applications/<app>.app
# Or force install
stout cask install --force <cask>
"Zap leaves files behind"¶
Some files weren't identified for removal.
Solution:
Check common locations manually:
# Application Support
ls ~/Library/Application\ Support/<app>
# Preferences
ls ~/Library/Preferences/com.<app>.*
# Caches
ls ~/Library/Caches/<app>
Performance Issues¶
"Stout is slow"¶
First run is slower while building cache.
Solution:
"Downloads are slow"¶
Network or server issues.
Solution:
# Check parallel download setting
stout config
# Increase parallel downloads
cat >> ~/.stout/config.toml << EOF
[install]
parallel_downloads = 8
EOF
Configuration Issues¶
"Config file not loading"¶
Syntax error in TOML file.
Solution:
# Validate TOML syntax
cat ~/.stout/config.toml
# Check for common issues:
# - Missing quotes around strings
# - Wrong indentation
# - Invalid values
# Reset to defaults
rm ~/.stout/config.toml
"Environment variable not working"¶
Variable may not be exported.
Solution:
# Make sure to export
export STOUT_PREFIX=/custom/path
# Not just
STOUT_PREFIX=/custom/path # This doesn't work
Multi-Prefix Issues¶
"Wrong prefix being used"¶
Default prefix may be set incorrectly.
Solution:
# Check current default
stout prefix list
# Set correct default
stout prefix default /path/to/prefix
# Or specify explicitly
stout --prefix=/path/to/prefix install <package>
Diagnostic Commands¶
Use these commands to gather information for troubleshooting:
# System health check
stout doctor
# Show configuration
stout config
# Show version
stout --version
# Verbose output
stout --verbose install <package>
# Check what's installed
stout list --versions
Getting Help¶
If these solutions don't resolve your issue:
-
Search existing issues: github.com/neul-labs/stout/issues
-
Open a new issue with:
- Stout version (
stout --version) - Operating system and version
- Complete error message
- Steps to reproduce
-
Output of
stout doctor -
Community help: Discussions on GitHub