[sf-lug] Debian 10 out on ...

[Ken Shaffer]

I used the --allow-releaseinfo-change on the apt-get update command,
and got switched from testing to stable.  Subsequent updates/install
did ask for confirmation of the new repos.
Ken

On 7/7/19, Akkana Peck <akkana at shallowsky.com> wrote:
> aaronco36 writes:
>> FYI, for the very few who may not realize this, one can update one's
>> 10.0.0
>> Buster stable machine following the original installation by performing
>> the
>> /etc/apt/sources.list archive edits as more fully described in [12]
>
> I upgraded my "testing" system today, and hit a couple of snags
> that people might need to know about.
>
> First, I had some references to testing/updates in my
> /etc/apt/sources.list; this apparently is now called
> testing/security, and apparently it no longer has contrib or
> non-free, so I had to change
> deb http://security.debian.org/ testing/updates main contrib non-free
> to
> deb http://security.debian.org/ testing-security main
>
> Second, Debian now requires a confirmation that you understand
> that the codename has changed (not a bad idea in itself):
>
>     E: Repository 'http://deb.debian.org/debian testing InRelease' changed
> its 'Codename' value from 'buster' to 'bullseye'
>     N: This must be accepted explicitly before updates for this repository
> can be applied. See apt-secure(8) manpage for details.
>     E: The repository 'http://security.debian.org/debian-security
> testing/updates Release' no longer has a Release file.
>     N: Updating from such a repository can't be done securely, and is
> therefore disabled by default.
>     N: See apt-secure(8) manpage for repository creation and user
> configuration details.
>     Aborting on non zero error code: 100!
>
> Turns out if you use "apt update", apt will prompt you and you can
> type y. If you're a dinosaur like me and typed "apt-get update", it
> simply prints an error message and exits. And although a web search
> finds a zillion people who have already hit this, very few of them
> actually have the answer, that there's a difference between apt-get
> and apt and you have to use the latter.
>
> (Of course I tried the apt-secure(8) manpage first thing; it does
> mention that a change in codename now requires confirmation, but
> it doesn't say how to do that, or at least I couldn't find it.)
>
>         ...Akkana
>
> _______________________________________________
> sf-lug mailing list
> sf-lug at linuxmafia.com
> http://linuxmafia.com/mailman/listinfo/sf-lug
> SF-LUG is at http://www.sf-lug.org/
>