Your message dated Wed, 29 May 2024 20:19:30 -0700
with message-id <87le3snfzx.fsf@wireframe>
and subject line Re: Bug#1072172: ltsp-server: ltsp-build-client fails
has caused the Debian Bug report #1072172,
regarding ltsp-server: ltsp-build-client fails
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1072172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072172
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ltsp-server
Version: 5.18.12-3
Severity: normal
After installing the ltsp-server (and -standalone) packages I ran:
ltsp-build-client.
First time it failed with:
> E: The repository 'http://security.debian.org bookworm/updates Release' does
> not have a Release file.
> N: Updating from such a repository can't be done securely, and is therefore
> disabled by default.
> N: See apt-secure(8) manpage for repository creation and user configuration
> details.
> error: LTSP client installation ended abnormally
I reran with: ltsp-build-client --copy-sourceslist
this went further but failed with:
> ...
> I: Configuring locales...
> I: Base system installed successfully.
> Generating locales (this might take a while)...
> en_US.UTF-8... done
> Generation complete.
> Adding 'diversion of /sbin/start-stop-daemon to /sbin/start-stop-daemon.real
> by ltsp-client'
> dpkg-divert: warning: diverting file '/sbin/start-stop-daemon' from an
> Essential package with rename is dangerous, use --no-rename
> update-alternatives: using /usr/sbin/policy-rc.d.ltsp to provide
> /usr/sbin/policy-rc.d (policy-rc.d) in auto mode
> Adding 'diversion of /etc/mtab to /etc/mtab.real by ltsp-client'
> renamed '/opt/ltsp/amd64/etc/apt/sources.list' ->
> '/opt/ltsp/amd64/etc/apt/sources.list.old'
> Hit:1 http://deb.debian.org/debian bookworm InRelease
> Get:2 http://deb.debian.org/debian bookworm-updates InRelease [55.4 kB]
> Get:3 http://deb.debian.org/debian bookworm/main Translation-en [6109 kB]
> Ign:4 http://security.debian.org bookworm/updates InRelease
> Get:5 http://deb.debian.org/debian bookworm-updates/main amd64 Packages [13.8
> kB]
> Get:6 http://deb.debian.org/debian bookworm-updates/main Translation-en [16.0
> kB]
> Err:7 http://security.debian.org bookworm/updates Release
>
> 404 Not Found [IP: 151.101.194.132 80]
> Reading package lists... Done
> E: The repository 'http://security.debian.org bookworm/updates Release' does
> not have a Release file.
> N: Updating from such a repository can't be done securely, and is therefore
> disabled by default.
> N: See apt-secure(8) manpage for repository creation and user configuration
> details.
> error: LTSP client installation ended abnormally
There is no ltsp-client package in debian. When I changed:
/usr/share/ltsp/plugins/ltsp-build-client/Debian/000-basic-configuration
and removed the line:
EARLY_PACKAGES=${EARLY_PACKAGES:-"ltsp-client"}
then it ran to completion.
-- Package-specific info:
packages in chroot: /opt/ltsp/amd64
found: /opt/ltsp/amd64/etc/lts.conf
# This is the default lts.conf file for ltsp 5. For more information about
# valid options please see lts.conf(5) man page, available in the ltsp-docs
# package.
#
# Note that things like sound and local device support are auto-enabled if the
# corresponding packages are installed, there is no need to manually set these
# options anymore.
[default]
LTSP_CONFIG=True
#SOUND=False
#LOCALDEV=False
#CONFIGURE_X=False
found image: /opt/ltsp/images/amd64.img
/opt/ltsp/images/amd64.img: Squashfs filesystem, little endian, version 4.0,
zlib compressed, 206811945 bytes, 13124 inodes, blocksize: 131072 bytes,
created: Wed May 29 05:32:47 2024
-- System Information:
Debian Release: 12.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-18-amd64 (SMP w/56 CPU threads; PREEMPT)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages ltsp-server depends on:
ii debconf [debconf-2.0] 1.5.82
ii debconf-utils 1.5.82
ii debootstrap 1.0.128+nmu2+deb12u1
ii gettext-base 0.21-12
ii iproute2 6.1.0-3
ii lsb-release 12.0-1
ii openssh-client 1:9.2p1-2+deb12u2
ii tcpd 7.6.q-32
Versions of packages ltsp-server recommends:
ii dnsmasq 2.89-1
ii gnupg 2.2.40-1.1
ii nbd-server 1:3.24-1.1
ii openbsd-inetd [inet-superserver] 0.20221205-2~deb12u1
ii openssh-server 1:9.2p1-2+deb12u2
ii squashfs-tools 1:4.5.1-1
Versions of packages ltsp-server suggests:
pn audiooss <none>
ii dnsmasq 2.89-1
ii ldm-server 2:2.18.06-1+deb10u1
ii libasound2-plugins 1.2.7.1-1
ii ltspfs 1.5-2
ii marco [x-window-manager] 1.26.1-3+deb12u2
ii mate-desktop-environment 1.26.0+1
ii mate-session-manager [x-session-manager] 1.26.0-1+deb12u1
ii pulseaudio 16.1+dfsg1-2+b1
pn qemu-user-static <none>
pn sdm <none>
ii x11-utils 7.7+5
ii xauth 1:1.1.2-1
-- debconf information:
ltsp-server/build_client: false
--- End Message ---
--- Begin Message ---
Version: 19.08-1
On 2024-05-29, Jim Mintha wrote:
> My apologies, I guess I still had it in my sources or something. I will use
> the new package and follow the ltsp.org docs.
No worries, sorry the transition wasn't more seamless ... it was a
pretty major redesign, so there was no straightforward way to "upgrade"
so to speak. Hope you will like the "new" LTSP!
> You can close the bug.
Marking as done in the version that switched to the new-style LTSP.
live well,
vagrant
> ----- On May 29, 2024, at 11:50 AM, Vagrant Cascadian [email protected]
> wrote:
>
>> On 2024-05-29, Jim Mintha wrote:
>>> Package: ltsp-server
>>> Version: 5.18.12-3
>>> Severity: normal
>>>
>>> After installing the ltsp-server (and -standalone) packages I ran:
>>> ltsp-build-client.
>>> First time it failed with:
>>
>> ltsp-server, ltsp-build-client, and all ltsp 5.x components were last
>> present two stable releases ago and are no longer part of Debian. While
>> you *might* be able to get it to work by adding buster
>> (a.k.a. oldoldstable) sources and various manual tweaks, I would not
>> recommend it at this point... it receives no real attention or
>> maintenance upstream or in any distro.
>>
>> The current LTSP support is available in Debian as the "ltsp" package,
>> see:
>>
>> https://ltsp.org/docs/
>>
>> live well,
>> vagrant
signature.asc
Description: PGP signature
--- End Message ---
