Your message dated Thu, 04 Feb 2021 11:34:55 -0800
with message-id <87mtwj7hk0.fsf@yucca>
and subject line Re: Bug#981393: ltsp: Unable to generate image
has caused the Debian Bug report #981393,
regarding ltsp: Unable to generate image
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.)
--
981393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981393
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ltsp
Version: 21.01-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
I have a problem with LTSP 21 that renders it unusable with Bullseye. I have
been successfully using old LTSP5 with Buster before.
* What led up to the situation?
Installing packages according to LTSP Documentation and running ltsp image
command as recommended here: https://ltsp.org/docs/installation/
* What exactly did you do (or not do) that was effective (or
ineffective)?
# ltsp image /
* What was the outcome of this action?
ltsp image /
Using x86_64 as the base name of image /
Running: mount -t tmpfs -o mode=0755 tmpfs /tmp/tmp.xFuUMTjWhL/tmpfs
Running: mount -t overlay -o
upperdir=/tmp/tmp.xFuUMTjWhL/tmpfs/0/up,lowerdir=/,workdir=/tmp/tmp.xFuUMTjWhL/tmpfs/0/work
/tmp/tmp.xFuUMTjWhL/tmpfs /tmp/tmp.xFuUMTjWhL/root/
Trying to acquire package management lock: /var/lib/dpkg/lock
Cleaning up x86_64 before mksquashfs...
Traceback (most recent call last):
File "/usr/share/ltsp/client/login/pwmerge", line 440, in <module>
main(sys.argv)
File "/usr/share/ltsp/client/login/pwmerge", line 434, in main
pwm = PwMerge(args[0], args[1], args[2], **dopts)
File "/usr/share/ltsp/client/login/pwmerge", line 117, in __init__
self.dpasswd, self.dgroup = self.read_dir(ddir, dur or dgr)
File "/usr/share/ltsp/client/login/pwmerge", line 188, in read_dir
grn = g2n[pwe[PW_GID]]
KeyError: 1007
LTSP command failed: /usr/share/ltsp/client/login/pwmerge --ltsp --quiet
/tmp/tmp.xFuUMTjWhL/root/tmp/pwempty /tmp/tmp.xFuUMTjWhL/root/etc
/tmp/tmp.xFuUMTjWhL/root/tmp/pwmerged
Aborting ltsp
* What outcome did you expect instead?
Generating the image.
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-2-amd64 (SMP w/4 CPU threads)
Locale: LANG=sk_SK.UTF-8, LC_CTYPE=sk_SK.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 depends on:
ii busybox 1:1.30.1-6+b1
ii openssh-client [ssh-client] 1:8.4p1-3
ii procps 2:3.3.16-5
ii python3 3.9.1-1
ii systemd 247.2-5
Versions of packages ltsp recommends:
ii man-db 2.9.3-2
ii sshfs 3.7.1+repack-1
Versions of packages ltsp suggests:
pn dnsmasq <none>
ii epoptes 21.01-1
ii ethtool 1:5.9-1
ii ltsp-binaries 21.01-1~ubuntu20.04.1
ii net-tools 1.60+git20181103.0eebece-1
ii nfs-kernel-server 1:1.3.4-4
ii openssh-server 1:8.4p1-3
ii squashfs-tools 1:4.4-2
-- no debconf information
--- End Message ---
--- Begin Message ---
On 2021-02-04, Alkis Georgopoulos wrote:
> So IMHO the best approach is to use python exceptions like this one,
> and I've also set up a similar thing in shell, where the "re() - Run or
> die and show the Error" function tells which shell command fails.
>
> E.g. LTSP will tell you "LTSP command failed: cp blah blah",
> but it won't bother to check and tell you that cp failed because your
> SSD is dying; that's a task for a different package, not LTSP.
Yeah, improving the errors would be nicer. :)
> Now if someone could properly close this bug report as I'm a bit time
> pressed currently to search how to do it... :D
Email [email protected] to close bugs, where NNN is the
bugnumber. :)
This message does so.
live well,
vagrant
--- End Message ---
