Jean-Fran�ois Mertens <[EMAIL PROTECTED]> said: >Benjamin Reed wrote: >> disco-volante:/sw/fink/dists/local/rangerrick/common/main/finkinfo/devel >> ranger$ fink remove fink-buildlock-distcc-2.18.3-1 >> Information about 4465 packages read in 7 seconds. >> Failed: no package specified for command 'remove'!
akh had a case where the lock got stuck in the "unpacked" state. That would mean it would appear in 'fink list' but not with status "i", so 'fink remove' might be "too smart" to try to remove it. I (think I) cured the situation that caused this to occur. But regardless, 'dpkg -s' can tell you more details about the package status, and 'dpkg -i' can remove "unpacked" and "half-installed" pkgs that fink would just ignore. > /sw/lib/perl5/Fink# fink remove ztrack-1.0-1 > Information about 5062 packages read in 4 seconds. > Failed: no package specified for command 'remove'! > > Apparently whenever a version seems specified to fink.. Part of the situation may confusion about what a "package name" is. The name of a buildlock pkg (%n) is composed of the name (%n') and version (%v'-%r') of the pkg for which it is a lock: %n = buildlock-%n'-%v'-%r' The lockpkg then has its own version string (which looks like a datestamp (because it is)). So even though "buildlock-distcc-2.18.3-1" looks like a full pkg (%f) identifier, it's really just the name (%n). dan -- Daniel Macks [EMAIL PROTECTED] http://www.netspace.org/~dmacks ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Fink-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-devel
