Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #211247
| From | Kent West <westk@acu.edu> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Where'd lsb-compat go? |
| Date | 2019-07-11 20:50 +0200 |
| Message-ID | <yiMiJ-16D-1@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
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" do, that maybe I can duplicate manually, etc?)? I thought maybe "lsb-release" might do the same thing, as the basic problem is that the SMA's client piece on the Debian boxes had stopped finding the version of Debian installed on the box, which broke the reporting process. When I installed "lsb-compat", the SMA client piece could once again detect the Debian version. 2) When I compare two of my Debian boxes (set up at different times and probably in slightly different ways), I find that the /etc/apt/sources.list files are functionally identical (with no extras in the sources.list.d directory), but when I do an "aptitude search lsb" on each, they give different results. Huh? That doesn't make sense to me. 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 deb http://security.debian.org/debian-security stable/updates main contrib non-free deb-src http://security.debian.org/debian-security stable/updates main contrib non-free # stable-updates, previously known as 'volatile' deb http://ftp.us.debian.org/debian/ stable-updates main contrib non-free deb-src http://ftp.us.debian.org/debian/ stable-updates main contrib non-free ---- root@lib-pac-04:~# aptitude search lsb p liblist-utilsby-perl - higher-order list utility functions p liblist-utilsby-xs-perl - XS implementation of List::UtilsBy i lsb-base - Linux Standard Base init script functionality i lsb-release - Linux Standard Base version reporting utility r ==== root@mcg-pac-03:~# 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 deb http://security.debian.org/ stable/updates main contrib non-free deb-src http://security.debian.org/ stable/updates main contrib non-free #deb http://security.debian.org/debian-security stable/updates main contrib non-free #deb-src http://security.debian.org/debian-security stable/updates main contrib non-free # stretch-updates, previously known as 'volatile' deb http://ftp.us.debian.org/debian/ stable-updates main contrib non-free deb-src http://ftp.us.debian.org/debian/ stable-updates main contrib non-free ---- root@mcg-pac-03:~# aptitude search lsb p liblist-utilsby-perl - higher-order list utility functions p liblist-utilsby-xs-perl - XS implementation of List::UtilsBy v lsb - i lsb-base - Linux Standard Base init script functionality i lsb-compat - Linux Standard Base Compatibility v lsb-core - i A lsb-release - Linux Standard Base version reporting utility Thanks! -- Kent
Back to linux.debian.user | Previous | Next — 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