Thanks for pointing that out, that would have saved some time If I'd seen that the description section wasn't a simple description of what the utility does.
I usually skip directly past the man page description section as in almost every case I've come across it is a simple description of what the utility is or does. I still believe this is a valid bug insofar as the apt-get --allow-unauthenticated does not function as described. Additionally, the manpage for apt-secure and apt-get are at odds (inconsistent). The apt-secure page indicates the default behaviour of not downloading packages that are unsigned may be overridden explicitly for apt-get (--allow-unauthenticated is the only switch on the apt-get manpage which addresses this, and it doesn't work). The apt-secure does provide for ways to allow insecure archives first and foremost (not optimal) and briefly mentions a Trusted option which did refer to sources as a way of removing warnings. Maybe I'm missing something, its my understanding that warnings are an outputted warning and action continues, and errors actually stop a process. The allow-unauthenticated did not downgrade all errors relating to signing to warnings. If it had, the apt-get update would have included the new packages and it would find the packages during an install command, but may not allow installation without explicit confirmation. The error resulting from the apt-get install command with the appropriate confirmation switch is a package not found error. Thus the --allow-unauthenticated is not downgrading signing related errors to warnings (which may along the line of though expressed in the description of apt-secure, or not, the documentation is unclear). As a result of the above inconsistencies, standard troubleshooting practices would place a technically savvy user down a path that takes a significant amount of time, unnecessarily. In addition to that, the inconsistencies also move the performance of a simple task of installing packages from a local resource into the realm of tacit knowledge as one must make the determination what's failing to work around the problem and anyone relying on the documentation will have to resolve several conflicts within the documentation before a solution can be found. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680261 Title: apt-secure ignoring allow-unauthenticated during apt-update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1680261/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
