On 13 August 2010 09:07, Stu Hodgson <[email protected]> wrote: > Russell, hey thank you for the message and encouragement. > > After the first pacman-g2 -Sy command, after the package integrity was > completed, it returned to the command prompt but since the next command > failed to lock the file, maybe it was still running in the background? I > didn't delete the lock file but after a minute or two, the command actually > ran and gave the "failed to add target" error as opposed to the "unable to > lock database" error. > > When I run the upgrade command now, it runs and gives the same error ... > > resolving dependencies... done. > error: failed to prepare transaction (could not satisfy dependencies) > :: wget: requires openssl=0.9.8 > :: curl: requires openssl=0.9.8 > > I should probably mention that when I was having problems, I downloaded a > few packages (pacman-g2, openssl and gnome-mount) and tried to install them > from file using the pacman gui rather than the command line - I can't > remember now which ones worked - I think pacman-g2 installed alright. > > Thanks again, Stu > > On Thu, Aug 12, 2010 at 6:51 PM, Russell Dickenson > <[email protected]> wrote: >> >> On 13 August 2010 07:22, Stu <[email protected]> wrote: >> >> [snip] >> >> > Nope, just tried it ... >> > >> > pacman-g2 -Sy pacman-g2 curl wget proftpd bash-completion >> > :: Synchronizing package databases... >> > frugalware-current is up to date >> > :: bash-completion-20060301-8: local version is newer. >> > Upgrade anyway? [Y/n] y >> > >> > resolving dependencies... done. >> > looking for inter-conflicts (9/9) >> > [#######################] 100% >> > >> > Targets: xz-4.999.9beta-1 openssl-1.0.0-3 libarchive-2.8.4-2 >> > pacman-g2-3.7.8-1 >> > libssh2-1.2.5-1 curl-7.20.0-2 wget-1.12-3 >> > proftpd-1.3.3-2 >> > bash-completion-1.1-6 >> > >> > Total Package Size: 6.2 MB >> > >> > Total Uncompressed Package Size: 21.8 MB >> > >> > Proceed with upgrade? [Y/n] y >> > >> > checking package integrity... done. >> >> >> > >> > That was where that stopped, then >> >> Just checking - pacman simply stopped doing anything after it had >> checked the packages' integrity? >> >> >> > pacman-g2 -Rd pident ctorrent farsight gst-plugins-farsight >> > libjingle-tapioca libchipcard2 libchipcard3 bitswash >> > error: failed to init transaction (unable to lock database) >> > if you're sure a package manager is not already >> > running, >> > you can remove //tmp/pacman-g2.lck >> >> When pacman runs, it creates a "lock" file named /tmp/pacman-g2.lck - >> to prevent pacman running more than once at a time - e.g. a separate >> virtual terminal, for example. If you are confident that pacman is not >> running anywhere else, you can (and should) delete this file. >> >> > Got that for a while, then when it could lock the database I >> > got ... >> > >> > error: failed to add target 'pident' (could not find or read >> > package) >> > >> > for each package listed (tried them one at a time). >> > >> > Then got the same error message as before when trying to >> > upgrade??? >> >> # pacman-g2 -Sy pacman-g2 curl wget proftpd bash-completion >> >> So when you ran this command again, pacman simply stops? >> >> > Any offers? Seems like I've messed it up pretty good. >> >> Don't worry too much. You haven't messed up anything. The messages you >> are getting are "normal" to some degree and a result of complex >> dependencies between packages. Let's keep working on this together and >> I'm sure it will be fixed soon. >> >> >> May you always be Frugal, >> >> Russell Dickenson (AKA phayz)
Stu, I understand the error messages you're getting from pacman but I'm not sure how to fix it. I have used unofficial, risky methods to work around these sort of problems but I wouldn't recommend that approach to anyone else. May you always be Frugal, Russell Dickenson (AKA phayz) _______________________________________________ Frugalware-devel mailing list [email protected] http://frugalware.org/mailman/listinfo/frugalware-devel
