[ Holger Levsen, 2021-04-21 ]
> we should add autopkgtests to debian-edu-doc to ensure each document
> has been built for the three formats pdf, epub and html.
>
> another condition is that every debian-edu-doc-* package should
> contain at least one document, unless the package has
package: src:debian-edu-doc
severity: wishlist
x-debbugs-cc: Petter Reinholdtsen , Paul Gevers
, 986...@bugs.debian.org, debian-edu@lists.debian.org
Hi,
we should add autopkgtests to debian-edu-doc to ensure each document has been
built for the three formats pdf, epub and html.
another
[Holger Levsen]
> I'll guess I'll invent something myself then...
What about looking for selected keywords like 'Debian Edu', 'Skolelinux,
"$(lsb_release -c -s)" or similar by grepping the documentation files,
to ensure the content is somewhat relevant? And perhaps linting the
HTML
Hi Paul,
On Mon, Apr 19, 2021 at 09:56:01PM +0200, Paul Gevers wrote:
> I guess that's about the best we can do for such -doc packages. I
> realize it's slightly "unfair" because of the different treatment we
> have in the current freeze, but I wonder if adding autopkgtest (to test
> as-installed
[ roman.me...@gismap.ch, 2021-04-21 ]
> I have added the suggested line to LDAP. It looks like this now:
>
> 121 cn=ltspConfigDefault,ou=ltsp,dc=skole,dc=skolelinux,dc=no
> objectClass: ltspClientConfig
> cn: ltspConfigDefault
> ltspConfig: KEEP_SYSTEM_SERVICES=lightdm
> ltspConfig:
Hi Wolfgang,
Sorry, still no good news.
I have added the suggested line to LDAP. It looks like this now:
121 cn=ltspConfigDefault,ou=ltsp,dc=skole,dc=skolelinux,dc=no
objectClass: ltspClientConfig
cn: ltspConfigDefault
ltspConfig: KEEP_SYSTEM_SERVICES=lightdm
ltspConfig: LTSP_FATCLIENT="False"
Hi Roman,
[ roman.me...@gismap.ch, 2021-04-21 ]
> I also played around with LDAP unsuccessfully trying to increasing the
> threshold for my clients to boot as thin client.
Maybe it doesn't take effect anymore for some reason…
But you should be able to do this by setting the client type in LDAP
Hi Wolfgang,
Well, I had to create the i386 image myself because it is not created by
default any longer.
I also played around with LDAP unsuccessfully trying to increasing the
threshold for my clients to boot as thin client.
That's all I can remember. Is the log file I sent not helpful?
Hi Roman,
[ roman.me...@gismap.ch, 2021-04-21 ]
> I just checked the content of /etc/ntp.conf of my "diskless
> workstation" client. No line "server ntp" has been appended.
>
> Guess that explains the problem I'm having, right?
Yes; any LDAP or LTSP chroot changes on your side?
Wolfgang
Hi Wolfgang,
Let me also add the syslog. It may probably help:
Apr 21 08:51:18 tjener dhcpd[1627]: reuse_lease: lease age 93385 (secs) under
25% threshold, reply with unaltered, existing lease for 192.168.0.20
Apr 21 08:51:18 tjener dhcpd[1627]: DHCPDISCOVER from 00:d0:59:22:05:43 via eth1
Apr
Hi folks,
I'm still stuck here not being able to boot my clients as "thin client".
Any ideas what is causing this?
Kind regards,
Roman
> -- Original Message --
> From: roman.me...@gismap.ch
> To: "debian-edu@lists.debian.org"
> Date: 04/20/2021 9:24 AM
> Subject: i386 clients
Hi Wolfgang,
I just checked the content of /etc/ntp.conf of my "diskless workstation"
client. No line "server ntp" has been appended.
Guess that explains the problem I'm having, right?
Kind regards,
Roman
> On 04/20/2021 5:28 PM Wolfgang Schweer wrote:
>
>
> Hi Roman,
>
> [
12 matches
Mail list logo
