Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #211277
| From | Tixy <tixy@yxit.co.uk> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: Where'd lsb-compat go? |
| Date | 2019-07-12 10:10 +0200 |
| Message-ID | <yiYMV-MB-3@gated-at.bofh.it> (permalink) |
| References | <yiMiJ-16D-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Thu, 2019-07-11 at 13:48 -0500, Kent West wrote: [..] > Today, > when I go to install "lsb-compat" on the other's, I find it's no longer > available in Buster. Has it been deprecated? Seems so, Googling for "debian lsb-compat buster" shows... https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873090 [...] > For completeness: > > root@lib-pac-04:~# cat /etc/apt/sources.list > # > > > deb http://ftp.us.debian.org/debian/ stable main contrib non-free > deb-src http://ftp.us.debian.org/debian/ stable main contrib non-free [...] Well, the 'stable' release changed from 'stretch' to 'buster' a few days ago, so your systems are possibly now going to be a mix of those two releases, probably not what you wanted. Really, you want the codenames of the release you want to run in sources.list, not 'stable'. Then you can explicitely upgrade to a new release at a time of your choosing, taking into consideration what the release notes say and leasons leaned from upgrading one of your systems first. -- Tixy
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Where'd lsb-compat go? Kent West <westk@acu.edu> - 2019-07-11 20:50 +0200
Re: Where'd lsb-compat go? Dominic Knight <dominicknight@gmx.com> - 2019-07-12 05:10 +0200
Re: Where'd lsb-compat go? Kent West <westk@acu.edu> - 2019-07-12 16:50 +0200
Re: Where'd lsb-compat go? Tixy <tixy@yxit.co.uk> - 2019-07-12 10:10 +0200
Re: Where'd lsb-compat go? Kent West <westk@acu.edu> - 2019-07-15 16:20 +0200
Re: Where'd lsb-compat go? Michael Stone <mstone@debian.org> - 2019-07-15 16:30 +0200
Re: Where'd lsb-compat go? Kent West <westk@acu.edu> - 2019-07-15 21:40 +0200
Re: Where'd lsb-compat go? Greg Wooledge <wooledg@eeg.ccf.org> - 2019-07-15 21:40 +0200
Re: Where'd lsb-compat go? Stefan Monnier <monnier@iro.umontreal.ca> - 2019-07-15 21:50 +0200
Re: Where'd lsb-compat go? Kent West <westk@acu.edu> - 2019-07-15 22:10 +0200
Re: Where'd lsb-compat go? Greg Wooledge <wooledg@eeg.ccf.org> - 2019-07-15 22:20 +0200
Re: Where'd lsb-compat go? Nicolas George <george@nsup.org> - 2019-07-15 23:00 +0200
Re: Where'd lsb-compat go? Kent West <westk@acu.edu> - 2019-07-15 23:20 +0200
Re: Where'd lsb-compat go? Kent West <westk@acu.edu> - 2019-07-15 23:00 +0200
Re: Where'd lsb-compat go? Gene Heskett <gheskett@shentel.net> - 2019-07-15 23:20 +0200
Re: Where'd lsb-compat go? Gene Heskett <gheskett@shentel.net> - 2019-07-15 23:00 +0200
Re: Where'd lsb-compat go? Andy Smith <andy@strugglers.net> - 2019-07-16 14:30 +0200
Re: Where'd lsb-compat go? Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-16 08:50 +0200
Re: Where'd lsb-compat go? Greg Wooledge <wooledg@eeg.ccf.org> - 2019-07-16 14:50 +0200
csiph-web