Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #236162
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: upgrade to testing |
| Date | 2021-06-16 13:30 +0200 |
| Message-ID | <CqBU6-28m-3@gated-at.bofh.it> (permalink) |
| References | <CqlcB-nl-3@gated-at.bofh.it> <CqmBI-1kP-19@gated-at.bofh.it> <CquIV-67M-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Wed, Jun 16, 2021 at 11:47:21AM +0800, Robbi Nespu wrote: > On 6/16/21 1:56 AM, Gary Dale wrote: > > sed -i -s 's/buster/bullseye/g' /etc/apt/sources.list > > I like this way, it easier and i don't need to open file and change it > manually. Yeah, it's wonderfully concise. Too bad it's wrong. The format of the security repository lines has changed for bullseye. You can't just replace buster with bullseye this time around. In addition, *every* time you do a release upgrade, you need to decide how to handle third-party repositories. The typical way you do that is to disable them temporarily, perform the upgrade, and then re-enable them -- either exactly as they were before, or with a slightly different URL pointing to a different version, depending on the repository. In some cases, you might even be able to get away with leaving the third-party repository alone and it'll sit there doing nothing during the release upgrade. In other cases, it'll interfere, possibly breaking the upgrade. We have no way to know other than trial and error. Another special case is the set of official backports repositories. You probably don't want to "just replace buster with bullseye" if you were using buster-backports. Most likely you simply want to get rid of that repository entirely. If you need bullseye-backports in the future, after it comes into existence, then you can add it at that time. Please see the release notes, or the DebianBullseye wiki page, or the NewInBullseye wiki page. I've given the URLs already.
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
upgrade to testing Wil <wil@desanti.co.uk> - 2021-06-15 19:40 +0200
Re: upgrade to testing Charles Curley <charlescurley@charlescurley.com> - 2021-06-15 19:50 +0200
Re: upgrade to testing john doe <johndoe65534@mail.com> - 2021-06-15 20:00 +0200
Re: upgrade to testing Henning Follmann <hfollmann@itcfollmann.com> - 2021-06-15 20:20 +0200
Re: upgrade to testing Greg Wooledge <greg@wooledge.org> - 2021-06-15 20:30 +0200
Re: upgrade to testing john doe <johndoe65534@mail.com> - 2021-06-16 08:30 +0200
Re: upgrade to testing "Andrew M.A. Cater" <amacater@einval.com> - 2021-06-15 20:10 +0200
Re: upgrade to testing Francisco M Neto <fmneto@gmail.com> - 2021-06-16 00:10 +0200
Re: upgrade to testing "Paul M. Foster" <paulf@quillandmouse.com> - 2021-06-16 00:30 +0200
Re: upgrade to testing Greg Wooledge <greg@wooledge.org> - 2021-06-16 00:30 +0200
Re: upgrade to testing Wil <wil@desanti.co.uk> - 2021-06-16 06:50 +0200
Re: upgrade to testing dalios <dalios@eumx.net> - 2021-06-16 15:20 +0200
Re: upgrade to testing Gary Dale <gary@extremeground.com> - 2021-06-15 21:10 +0200
Re: upgrade to testing Robbi Nespu <robbinespu@gmail.com> - 2021-06-16 05:50 +0200
Re: upgrade to testing Greg Wooledge <greg@wooledge.org> - 2021-06-16 13:30 +0200
Re: upgrade to testing Brian <ad44@cityscape.co.uk> - 2021-06-15 21:30 +0200
csiph-web