Troubleshooting¶
Common issues and their solutions when using depkeeper.
Installation Issues¶
pip install fails¶
Error: Could not find a version that satisfies the requirement
Solution:
Command not found¶
Error: depkeeper: command not found
Solution:
# Ensure pip scripts are in PATH
# For Unix/macOS:
export PATH="$HOME/.local/bin:$PATH"
# For Windows (PowerShell):
$env:PATH += ";$env:APPDATA\Python\Scripts"
# Or run as a module:
python -m depkeeper --help
Parsing Errors¶
Invalid requirements file¶
Error: ParseError: Invalid requirement at line X
Common causes:
- Missing version specifier
- Invalid characters in package name
- Malformed URL
Solution:
# Validate your requirements file
pip install -r requirements.txt --dry-run
# Fix the problematic line and try again
Encoding issues¶
Error: UnicodeDecodeError: 'utf-8' codec can't decode
Solution:
# Convert file to UTF-8
# On Unix/macOS:
iconv -f ISO-8859-1 -t UTF-8 requirements.txt > requirements_utf8.txt
# On Windows (PowerShell):
Get-Content requirements.txt | Set-Content -Encoding UTF8 requirements_utf8.txt
Network Issues¶
Connection timeout¶
Error: NetworkError: Connection to pypi.org timed out
Solutions:
# Check network connectivity
ping pypi.org
# If behind a firewall, ensure pypi.org is accessible
curl -I https://pypi.org
SSL certificate errors¶
Error: SSLError: certificate verify failed
Solutions:
# Update certificates
pip install --upgrade certifi
# For corporate proxies, configure CA bundle
export REQUESTS_CA_BUNDLE=/path/to/ca-bundle.crt
Behind a proxy¶
Solution:
# Set proxy environment variables
export HTTP_PROXY=http://proxy.example.com:8080
export HTTPS_PROXY=http://proxy.example.com:8080
# Or configure in pip
pip config set global.proxy http://proxy.example.com:8080
Dependency Resolution¶
Conflict detected¶
Warning: Dependency conflicts shown in check output
Example: package-a requires package-b<2.0, but package-c requires package-b>=2.0
Solutions:
-
Check current state:
-
Find the conflict source:
-
Try updating related packages:
-
Use constraints:
-
As last resort, pin the conflicting package:
Circular dependencies¶
Warning: Circular dependency detected: A -> B -> A
Solution: This is usually not an issue, but if causing problems:
Update Issues¶
Update fails with error¶
Error: FileOperationError: Cannot write to requirements.txt
Common causes:
- Write permission denied
- File locked by another process
- Disk full
Solutions:
# Check file permissions
ls -la requirements.txt
# Close editors that might lock the file
# Try with elevated permissions if needed (Unix/macOS)
sudo depkeeper update
Pre-release versions appearing¶
Issue: Unwanted alpha/beta versions suggested
depkeeper automatically excludes pre-release versions (alpha, beta, rc, dev) by default. If you're seeing pre-releases, this may indicate:
- The package only has pre-release versions available
- The package's versioning scheme doesn't follow PEP 440
Output Issues¶
Garbled output / No colors¶
Issue: Terminal output appears broken
Solutions:
# Force no colors
depkeeper --no-color check
# Or set environment variable
export DEPKEEPER_COLOR=false
JSON output invalid¶
Issue: JSON output mixed with status messages
Solution:
Getting Help¶
If you're still having issues:
-
Check the version:
-
Run with verbose output:
-
Search existing issues: GitHub Issues
-
Report a bug -- include:
- depkeeper version
- Python version (
python --version) - Operating system
- Full error message with verbose output
- Minimal requirements.txt to reproduce
# Gather system info
depkeeper --version
python --version
pip --version
uname -a # or systeminfo on Windows
See Also¶
- Installation -- Installation troubleshooting
- Configuration -- Configure depkeeper behavior
- CLI Reference -- Complete command documentation