Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #224436
| From | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: sources.list for security |
| Date | 2020-07-06 14:20 +0200 |
| Message-ID | <Apygh-48i-7@gated-at.bofh.it> (permalink) |
| References | (2 earlier) <Ap7J7-4gv-1@gated-at.bofh.it> <Ap8vv-4Lh-3@gated-at.bofh.it> <Apdvc-7Xk-1@gated-at.bofh.it> <Apf3X-lQ-5@gated-at.bofh.it> <Apl9n-4gq-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
> >> >> https://bugs.debian.org/931785 Which says "security suite renamed to bullseye-security (from buster/updates)". On Sun, Jul 05, 2020 at 05:44:44PM -0400, songbird wrote: > >> wishlist for an alias to testing so nobody who=20 > >> follows testing will need to keep changing their > >> sources.list every time there is a release. > > > > What more than the 'testing' alias are you looking for? > > the one i should use... If you are running "eternal testing" (you never convert it to a stable release), then you HAVE NO security support. None. There is no line you should use for security, because there isn't any security. (Many years ago, someone created a "security for testing" repository, and for a little while, it was used, but now it just sits there idle and devoid of packages. So, while *technically* there is a testing security repository, it's not really *useful* and it would be a waste of time and bandwidth to add it to your sources.) The announcement in question (#931785) is for what the security repository will be called when bullseye is *stable* and receives security support. People who track bullseye at this time in its lifespan (while it is in testing) may add the security line in anticipation of it becoming useful once bullseye becomes stable. Eternal-testing users should only use the one line that points to the testing repository (two lines if you want deb-src as well).
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
sources.list for security Pierre Frenkiel <p.frenkiel@laposte.net> - 2020-07-05 08:40 +0200
Re: sources.list for security "der.hans" <deb-user@LuftHans.com> - 2020-07-05 09:00 +0200
Re: sources.list for security john doe <johndoe65534@mail.com> - 2020-07-05 09:00 +0200
Re: sources.list for security Andrei POPESCU <andreimpopescu@gmail.com> - 2020-07-05 09:40 +0200
Re: sources.list for security Salvatore Bonaccorso <carnil@debian.org> - 2020-07-05 10:00 +0200
Re: sources.list for security Andrei POPESCU <andreimpopescu@gmail.com> - 2020-07-05 10:50 +0200
Re: sources.list for security songbird <songbird@anthive.com> - 2020-07-05 16:10 +0200
Re: sources.list for security Andrei POPESCU <andreimpopescu@gmail.com> - 2020-07-05 17:50 +0200
Re: sources.list for security songbird <songbird@anthive.com> - 2020-07-06 00:20 +0200
Re: sources.list for security Dan Ritter <dsr@randomstring.org> - 2020-07-06 01:20 +0200
Re: sources.list for security songbird <songbird@anthive.com> - 2020-07-06 01:40 +0200
Re: sources.list for security Keith bainbridge <keithrbau@gmail.com> - 2020-07-06 04:20 +0200
Re: sources.list for security Andrei POPESCU <andreimpopescu@gmail.com> - 2020-07-06 08:00 +0200
Re: sources.list for security songbird <songbird@anthive.com> - 2020-07-06 19:10 +0200
Re: sources.list for security Greg Wooledge <wooledg@eeg.ccf.org> - 2020-07-06 14:20 +0200
Re: sources.list for security songbird <songbird@anthive.com> - 2020-07-06 19:20 +0200
csiph-web