Re: netcfg: proposal for template change
Ben Hutchings wrote: > On Fri, 2020-01-10 at 22:01 +0100, Holger Wansing wrote: >> I would like to propose a change on a template in netcfg: > [...] >> _Description: Malformed IP address >> The IP address you provided is malformed. It should be in the form >> - x.x.x.x where each 'x' is no larger than 255 (an IPv4 address), or a >> - sequence of blocks of hexadecimal digits separated by colons (an IPv6 >> + x.x.x.x where each 'x' is an integer not larger than 255 (for an IPv4 >> address), or >> + ::::::: each '' being a block of >> hexadecimal digits (for an IPv6 >> address). Please try again. > [...] > > But IPv6 addresses do not have to look like that: leading zeroes in > each group can be omitted and a run of all-zero groups in the middle > can be omitted. > > And really I think the tiny proportion of users who need to enter > static network configuration will already know what an IP address looks > like. In fact it might be more likely to be helpful if it said: The value you provided is not a usable IPv4 or IPv6 address. Please try again; for instance when setting up an IPv4 local area network you might use an address such as "192.168.0.1". On the other hand if they specifically want to configure an IPv6 address, they've probably just typed it in wrong (again). -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package
Re: netcfg: proposal for template change
On Fri, 2020-01-10 at 22:01 +0100, Holger Wansing wrote: > Hi, > > I would like to propose a change on a template in netcfg: [...] > _Description: Malformed IP address > The IP address you provided is malformed. It should be in the form > - x.x.x.x where each 'x' is no larger than 255 (an IPv4 address), or a > - sequence of blocks of hexadecimal digits separated by colons (an IPv6 > + x.x.x.x where each 'x' is an integer not larger than 255 (for an IPv4 > address), or > + ::::::: each '' being a block of > hexadecimal digits (for an IPv6 > address). Please try again. [...] But IPv6 addresses do not have to look like that: leading zeroes in each group can be omitted and a run of all-zero groups in the middle can be omitted. And really I think the tiny proportion of users who need to enter static network configuration will already know what an IP address looks like. Ben. -- Ben Hutchings Anthony's Law of Force: Don't force it, get a larger hammer. signature.asc Description: This is a digitally signed message part
installation-guide: build version
Hi, I have just added a build version (the latest version number parsed from the debian/changelog file at build time) to the installation-guide. Makes it easier to spot build failures or other problems at the website or the like. FYI Holger -- Holger Wansing PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Re: netcfg: proposal for template change
Holger Wansing wrote: > I would like to propose a change on a template in netcfg: [...] > _Description: Malformed IP address > The IP address you provided is malformed. It should be in the form > - x.x.x.x where each 'x' is no larger than 255 (an IPv4 address), or a > - sequence of blocks of hexadecimal digits separated by colons (an IPv6 > + x.x.x.x where each 'x' is an integer not larger than 255 (for an IPv4 > address), or > + ::::::: each '' being a block of > hexadecimal digits (for an IPv6 > address). Please try again. Pedantically I think there ought to be commas around , each '' being a block of hexadecimal digits, - or you could repeat the phrasing as "where each '' is a block of hexadecimal digits". > I would like to make the description of the format more clearer, especially > the IPv6 variant does not give much detailed information. > If you typed a malformed IPv6 address, that message does not give you much > help, how it should look like ... > > Any comments/objections? > > debian-l10n-english in CC for review, too. I can see why you might want to make the descriptions of dotted quads and colonic octopoids more closely parallel, but is it really useful to give this much advice and no more? Users have already been warned "if you don't know what to use here, consult your network administrator"; if they're seeing this error because they tried typing in "0.0.0.0", the rules given won't help them find an address they can use. It might be better to simplify in the general direction of The value you provided is not a usable IPv4 or IPv6 address. Please consult your network administrator and try again. -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package
netcfg: proposal for template change
Hi, I would like to propose a change on a template in netcfg: #. Type: error #. Description #. IPv6 #. :sl2: #: ../netcfg-static.templates:2001 msgid "" "The IP address you provided is malformed. It should be in the form x.x.x.x " "where each 'x' is no larger than 255 (an IPv4 address), or a sequence of " "blocks of hexadecimal digits separated by colons (an IPv6 address). Please " "try again." msgstr "" _Description: Malformed IP address The IP address you provided is malformed. It should be in the form - x.x.x.x where each 'x' is no larger than 255 (an IPv4 address), or a - sequence of blocks of hexadecimal digits separated by colons (an IPv6 + x.x.x.x where each 'x' is an integer not larger than 255 (for an IPv4 address), or + ::::::: each '' being a block of hexadecimal digits (for an IPv6 address). Please try again. I would like to make the description of the format more clearer, especially the IPv6 variant does not give much detailed information. If you typed a malformed IPv6 address, that message does not give you much help, how it should look like ... Any comments/objections? debian-l10n-english in CC for review, too. Holger -- Holger Wansing PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Re: New development of how to build the installation-guide for the website [ Re: Bug#930846: partman-auto-lvm: debconf show guided_size during auto install ]
Hi Laura, Laura Arjona Reina wrote: > Hi > > El 9/1/20 a las 20:49, Holger Wansing escribió: > > > > To make a new build happen, manual intervention is > > needed now ( because there is no new source package > > version available for installation-guide since the last build, no new build > > is trigered). > > One need to go to > > /srv/www.debian.org/cron/log/ig-stable-built.txt > > and change that file (for example just change into an > > empty file). > > This is documented in the 1installation-guide script in > > lessoften (cron git-repo). > > That will trigger a new build at the next day. > > I've just done this (copied /srv/www.debian.org/cron/log/ig-stable-built.txt > to > /srv/www.debian.org/cron/log/ig-stable-built.txt.old and then changed > ig-stable-built.txt to be an empty file). Hrr, this did not work. Sorry The variant with the empty file was my first idea, but that did not work. So I changed that, now the file has to be removed. May I bother you again, to remove the file instead? (Also, there is no need to keep the old file. You can remove it too.) I have just updated the documentation in the 1installation-guide lessoften script accordingly. Many thanks + Sorry again Holger -- Holger Wansing PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Re: New development of how to build the installation-guide for the website [ Re: Bug#930846: partman-auto-lvm: debconf show guided_size during auto install ]
Hi El 9/1/20 a las 20:49, Holger Wansing escribió: > > To make a new build happen, manual intervention is > needed now ( because there is no new source package > version available for installation-guide since the last build, no new build > is trigered). > One need to go to > /srv/www.debian.org/cron/log/ig-stable-built.txt > and change that file (for example just change into an > empty file). > This is documented in the 1installation-guide script in > lessoften (cron git-repo). > That will trigger a new build at the next day. I've just done this (copied /srv/www.debian.org/cron/log/ig-stable-built.txt to /srv/www.debian.org/cron/log/ig-stable-built.txt.old and then changed ig-stable-built.txt to be an empty file). Kind regards, -- Laura Arjona Reina https://wiki.debian.org/LauraArjona
Re: Planning 10.3 and 9.12
On Mon, Jan 06, 2020 at 09:42:29PM +, Adam D. Barratt wrote: > Hi, > > It's (really past) time to consider a date for the next point releases > for buster and stretch. > > I've listed some suggested dates below; please indicate which you would > be available for. > > - January 25th > - February 1st > - February 8th > - February 15th > The first 3 should work for me. Feb 15 I'm not sure yet. Cheers, Julien
