Jörg Sommer wrote: > Package: apt > Version: 0.7.20 > Severity: normal > > Hi, Hello Jörg, > apt-get behaves differently on reinstalling. > > % LCC apt-get -o Dir::State::status=/tmp/status -o Dir::Cache=/tmp --reinstall --quiet=2 --print-uris --ignore-missing install java-common pkg1 > 'ftp://ftp.de.debian.org/debian/pool/main/j/java-common/java-common_0.30_all.deb' java-common_0.30_all.deb 77022 SHA256:600554190a9c05d2f2b93b803eb146627208edb6acf8030f0cde3cb10a9e2bc0 > % LCC apt-get -o Dir::State::status=/tmp/status -o Dir::Cache=/tmp --reinstall --quiet=2 --print-uris --ignore-missing install java-common pkg2 > E: Package pkg2 has no installation candidate > % echo $? > 100 > > In the first case it ignores the package it hasn't an installation > candidate for, No, first package has the installation candidate itself - it's installed version. Yes, there is other question why it hasn't failed to reinstall it, it would be good to see 'apt-cache policy pkg1' to make sure there was no other installation candidates. > but in the second it fails. I've expected it would ignore > in the second case, too. Package pkg2 has really no installation candidates, so package pkg2 really can't be reinstalled. I believe this behavior is right. > The option --ignore-missing doesn't change > anything. '--ignore-missing' has other meaning: it ignores the (versions of) packages that cannot be retrieved due to some reason, but available in Packages. > How is it possible to make apt-get ignores non‐available not fully > installed packages? At least now - probably, no way. You may want to try aptitude here, it has less strict rules in some places. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com Ukrainian C++ Developer, Debian Maintainer, APT contributor
Attachment:
signature.asc
Description: OpenPGP digital signature