Re: debian-edu-doc: reworking content of binary packages

2020-09-02 Thread Holger Levsen
Hi,

Wolfgang and Frans, thanks for your analysis here!

On Tue, Sep 01, 2020 at 01:19:55PM +0200, Wolfgang Schweer wrote:
[audacity manual]
> My opinion: maybe useful in parts, but not what you would qualify as a 
> manual for users. Keep it on wiki.debian.org with a remark like 
> 'Outdated, but still useful in parts'. Drop it from weblate. Ship 
> already existing translations in legacy packages.

(based on the non quoted stuff) sounds good to me.
 
> Rosegarden:
> Hence the same suggestion as for the Audacity manual.

also.
 
> ITIL:
> -
> 
> The extremely outdated part about Coyote firewall has been excluded from 
> the AllInOne page recently, see:
> https://wiki.debian.org/DebianEdu/Documentation/ITIL/AllInOne?action=info

good

> More content could be excluded, e.g. these sections:
> <>
> <>
> <>
> 
> But I'm undecided if this is a good idea, maybe better keep it like it 
> is now and treat it like the Audacity and Rosegarden manuals.

it be curious what the ITIL documentation authors think, Petter?


-- 
cheers,
Holger

---
   holger@(debian|reproducible-builds|layer-acht).org
   PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C

There are no jobs on a dead planet.


signature.asc
Description: PGP signature


Re: Problem: Debian-Edu i386 ThinClients

2020-09-02 Thread Roland F.Teichert
Thanks Wolfgang,

I think, I did so. But I will do it again.
You say, there is no trick :-)

I'll be in touch.
Roland

On 01.09.20 14:19, Wolfgang Schweer wrote:
> Hi Roland,
> 
> [ Roland F.Teichert, 2020-09-01 ]
>> following problem:
>> Debian-Edu Buster net works fine. Also ThinClients with default amd64
>> Image. But I need i386.
>> I did everything, described in the documentation. No error messages,
>> but the ThinClients doesn't work.
>> Messages on the Clients like kernel panic, cannot find /dev/ndb0
>>
>> Different thinclients give different error messages. They worked fine
>> with Jessie.
>>
>> What did I do wrong? Where can I look for problems?
> 
> Did you follow the instructions in the manual? See:
> https://wiki.debian.org/DebianEdu/Documentation/Buster/HowTo/NetworkClients#Add_LTSP_chroot_to_support_32-bit-PC_clients
> 
> If you've got a single LTSP network all clients (i.e. both 64 and 32 bit 
> machines) would then use the 32 bit image like it has been before Buster.
> 
>> I need them. :-)
> 
> Hope it helps...
> 
> Wolfgang
> 



signature.asc
Description: OpenPGP digital signature


Re: Problem: Debian-Edu i386 ThinClients

2020-09-02 Thread Wolfgang Schweer
Hi Roland,

[ Roland F.Teichert, 2020-09-02 ]
> I think, I did so. But I will do it again.

I guess you only have to check a few things:

NBD image:
--
root@tjener:~# ls -lh /opt/ltsp/images/
total 3.4G
-rw-r--r-- 1 root root 3.4G Aug  1 20:39 i386.img
root@tjener:~#

Relevant part in LDAP (default LTSP network):
-
83 
cn=subnet00.intern,cn=dhcp,cn=tjener,ou=servers,ou=systems,dc=skole,dc=skolelinux,dc=no
dhcpOption: routers ltspserver00.subnet00
dhcpOption: domain-name "intern"
dhcpOption: subnet-mask 255.255.255.0
dhcpOption: broadcast-address 192.168.0.255
dhcpOption: root-path "/opt/ltsp/i386"
dhcpOption: ntp-servers ntp
dhcpOption: wpad-url "http://wpad/wpad.dat";
dhcpOption: smtp-server postoffice
dhcpOption: domain-name-servers 10.0.2.2
dhcpStatements: default-lease-time 432000
dhcpStatements: max-lease-time 432000
dhcpStatements: filename "/var/lib/tftpboot/ltsp/i386/pxelinux.0"
dhcpStatements: next-server ltspserver00.subnet00
dhcpStatements: authoritative
dhcpStatements: allow unknown-clients
dhcpStatements: allow bootp
dhcpStatements: allow booting
cn: subnet00.intern
objectClass: top
objectClass: dhcpSharedNetwork
 
TFTP directory:
-
Run 'ltsp-update-image' to be sure things are up-to-date.

Good luck,

Wolfgang


signature.asc
Description: PGP signature


Re: debian-edu-doc: reworking content of binary packages

2020-09-02 Thread Frans Spiesschaert
Hi Wolfgang,

Wolfgang Schweer schreef op di 01-09-2020 om 13:19 [+0200]:
> Hi Frans,
> 
> To come to a conclusion for myself, I've taken a look at the Audacity 
> and Rosegarden programs (and at all three manuals).

I am impressed with your thorough analysis below. Moreover, I feel in
favour of the solutions you propose, and I understood also Holger does.

Nevertheless, I just have no idea whether, by acting like this, we will not
make too sudden a break with the past for the target audience of the
manuals and for those educational institutions that may rely on it. Let me
try to explain my concerns in this regard.
If I'm not mistaken the Audacity and Rosegarden manuals are primarily
targeted at classroom teachers, while the ITIL manual is primarily meant
for the school management, and the buster/bullseye manual being helpful in
the first place for the school IT responsible. I don't know if e.g. even
the very concise and outdated Audacity manual might be helpful for teachers
to get started with that program. I honestly have no idea. While the
program itself is indeed translated into the languages of the Debian Edu
founding father's countries, Norway and France, and many other languages,
there are on the contrary no translations at all of the very comprehensive
manual. The same applies to the Rosegarden manual, while this program even
lacks a Norwegian Bokmål translation, e.g. Won't people on the ground feel
themselves deprived of an, admittedly very imperfect, resource?
Given these doubts in me, let me just say that I stay behind your proposals
and that I hope that we will receive signals if it turns out that people on
the ground consider this a too drastic change.
I feel less insecure about treating the ITIL manual the same as you propose
to treat the Audacity and Rosegarden manuals, because for a long time the
ITIL manual has only been possibly meaningful to Norwegian schools in the
absence of an English version.

> 
> Audacity:
> -
> 
> The GUI has changed over the years and is nowadays translated into a lot 
> of languages (menu items, mouse over information), see: 
> https://manual.audacityteam.org/man/languages.html#lang
> 
> The Audacity manual screenshots contain a lot of information, but don't 
> match the GUI anymore. It also doesn't make much sense if a translation 
> shows the screenshots in English. This is the case for all translations 
> with (fr) as the only exception.
> 
> A lot of up-to-date information is available, e.g. see:
> https://manual.audacityteam.org
> 
> My opinion: maybe useful in parts, but not what you would qualify as a 
> manual for users. Keep it on wiki.debian.org with a remark like 
> 'Outdated, but still useful in parts'. Drop it from weblate.

So, If I understand this correctly, this means no longer seeking new
translations and translation updates.

>  Ship 
> already existing translations in legacy packages.
> 
> Rosegarden:
> ---
> 
> Different GUI compared to the one from years ago, translated into 21 
> languages (12 fully translated), see:
> https://salsa.debian.org/multimedia-team/rosegarden/-/tree/master/data/locale
> 
> While the Rosegarden manual screenshots are available in {en,fr,nb}, 
> they are outdated as well. Further, installation instructions (QjackCtl, 
> Qsynth, soundfont) are from ancient times.
> 
> A lot of up-to-date information is available, e.g. see:
> https://www.rosegardenmusic.com/tour/
> 
> Hence the same suggestion as for the Audacity manual.

Agreed, against the background of the feelings of doubt I expressed above.

> 
> ITIL:
> -
> 
> The extremely outdated part about Coyote firewall has been excluded from 
> the AllInOne page recently, see:
> https://wiki.debian.org/DebianEdu/Documentation/ITIL/AllInOne?action=info
> 
> More content could be excluded, e.g. these sections:
> <>
> <>
> <>
> 
> But I'm undecided if this is a good idea, maybe better keep it like it 
> is now and treat it like the Audacity and Rosegarden manuals.

Here, I would opt for the latter option.

> 
> Wolfgang

-- 
Kind regards,
Frans Spiesschaert