Welcome to CRUX bug tracking.

FS#434 - prt-get listlocked behaviour and error codes

Attached to Project: CRUX
Opened by Jose V Beneyto (sepen) - Monday, 06 April 2009, 13:27 GMT
Last edited by Tim Biermann (tb) - Saturday, 07 May 2022, 12:17 GMT
Task Type Feature Request
Category tools → prt-get
Status Closed
Assigned To Johannes Winkelmann (jw)
Operating System CRUX
Severity Low
Priority Normal
Reported Version Development
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


after a fresh install you don't have /var/lib/pkg/, so prt-get returns an error code and that isn't good for other tools which are dependent of prt-get:

# prt-get listlocked
Failed to open lock data file
# echo $?
# prt-get lock gcc && prt-get unlock gcc
# prt-get listlocked
# echo $?

IMHO, prt-get should provide the lock data file via .footprint or post-install script:

# touch /var/lib/pkg/
# prt-get listlocked
# echo $?
This task depends upon

Closed by  Tim Biermann (tb)
Saturday, 07 May 2022, 12:17 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed by 7bb2365d5e0247eca46b92dd4df160f7b6e46081
Comment by Johannes Winkelmann (jw) - Sunday, 16 September 2012, 19:16 GMT
I agree, but wonder whether it would be best to do so in Pkgfile for now; I guess one could argue that make install should install a working version... not sure for now. Care to fix it in Pkgfile for now?