On Wed, Jul 17, 2019 at 04:47:53PM +0300, Anton Zhavoronkov wrote: > Problem: > Option --allow-releaseinfo-change-version or > --allow-releaseinfo-change-suite is understood correctly by apt-get, but > has no any effect. > > $ sudo apt-get update --allow-releaseinfo-change-version […] > N: Repository 'http://ftp.debian.org/debian buster InRelease' changed > its 'Version' value from '' to '10.0' > E: Repository 'http://ftp.debian.org/debian buster InRelease' changed > its 'Suite' value from 'testing' to 'stable' > N: This must be accepted explicitly before updates for this repository > can be applied. See apt-secure(8) manpage for details.
--allow-…-version has indeed no effect as the default for version is allowed – so you would need to change your local default via config or use the --no-… version to disallow it. Note that allowed/disallowed just means that the message will the prefixed with an "N:" (for Notice) or "E:" (for Error), so you will always see the messages – if you don't want that you have some options with "quiet" as notices aren't displayed by default with -q>=1. Of course, the "apt-get" call will fail only if one of these messages is an error, if they are all notices apt will exit normally (and it will not show the third line in your example for obvious reasons). In your example you showed --allow-…-version two times, so I am kinda happy that the same thing happened for repeated calls… ☺ (you must accept all changes at the same time, they can't be accepted piecemeal). So, are you sure your second call was really about suite as your example wasn't? I had a quick look at the code and can't spot an obvious error here which would rule out the specialist options to not work (and our testcase checks them – although only with codename, but the implementation is pretty loopy so that should work™). Best regards David Kalnischkies
signature.asc
Description: PGP signature
