Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #211263
| From | Dominic Knight <dominicknight@gmx.com> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: Where'd lsb-compat go? |
| Date | 2019-07-12 05:10 +0200 |
| Message-ID | <yiU6B-6eh-1@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: > Two issues: > > > 1) I have several Debian boxes running as kiosks, and reporting to a > centralized Quest-branded "Systems Management Appliance" (SMA). With > a > recent update to the SMA, the Debian boxes stopped reporting in. > After > several weeks, I finally discovered that the installation of > "lsb-compat" on several of them restored their functionality. 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? Why? Any ideas how I'm > going to get my boxes reporting again to the SMA (what does "lsb- > compat" ****** The Linux Standard Base (http://www.linuxbase.org/) was a standard core system that third-party applications written for Linux could depend upon. This package provides the most minimal layer to be able to install and run selected legacy LSB packages on Debian. ****** (untested) Maybe temporarily set your sources to old stable or stretch and pick it up from there (then reset them of course). I could only guess when you installed on the other boxes it was set to stable (stretch) which was then stable but is now buster.
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