Re: `boot-floppies' documentation naming conventions?
On Sat, Mar 25, 2000 at 05:39:13PM -0500, Adam Di Carlo wrote: Adam Di Carlo [EMAIL PROTECTED] writes: The current state is that translations are relying on the existance of www.es.debian.org and www.br.debian.org, both of which are not very reliable. In fact, neither is currently accessable. This isn't very robust. Well, lets just have it all point, for web pages, to www.debian.org. Go ahead and change that in slink, I'll hack it for potato. For downloads, should we point to http.us.debian.org or is there something better? James, if you don't have time to fix the broken links, could you at least send the list of broken links to the debian-boot mail list? I'll try pointing the urlchecker at http://www.debian.org/releases/potato and see what happens. -- James (Jay) Treacy [EMAIL PROTECTED]
Re: `boot-floppies' documentation naming conventions?
James A. Treacy [EMAIL PROTECTED] writes: I'll try pointing the urlchecker at http://www.debian.org/releases/potato and see what happens. Oh, I don't have the documentation up there yet. I was asking more about the slink stuff. You were saying you'd go thru that ... It would help me not to have to go back and fix that stuff up but I can if I need to. -- .Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/
Re: `boot-floppies' documentation naming conventions?
On Sat, Mar 25, 2000 at 11:34:06PM -0500, Adam Di Carlo wrote:
James A. Treacy [EMAIL PROTECTED] writes:
I'll try pointing the urlchecker at http://www.debian.org/releases/potato
and see what happens.
Oh, I don't have the documentation up there yet.
It's probably a good idea for us to check the pages before they become
public. Once you update them, I can force a mirror to va and can run
the url checker from there.
I was asking more about the slink stuff. You were saying you'd go
thru that ... It would help me not to have to go back and fix that
stuff up but I can if I need to.
Here's the most recent results. I've gone through and grouped most of
the ones due to related problems. Some also have suggested fixes attached.
Looking into http://localhost/releases/slink/i386/reports
http://insite.verisim.com/search/debian/simple : error 500 Can't connect to
insite.verisim.com:80 (Bad hostname 'insite.verisim.com')
Should be changed to look in http://www.debian.org/search (using a relative URL
if possible).
Looking into http://localhost/releases/slink/index.hr.html
http://netgod.net/x/apt_0.3.7slink0_i386.deb : error 500 Can't connect to
netgod.net:80 (Connection timed out)
The next big bunch of problems are all in
http://localhost/releases/slink/{alpha,i386,m68k,sparc}/install.{es,pt}.html
All references to www.es.debian.org and www.br.debian.org should be changed
to relative links
Looking into http://localhost/releases/slink/sparc/install.pt.html
http://www.br.debian.org/releases/2.1/sparc/release-notes/ : error 500 Can't
connect to www.br.debian.org:80 (Connection timed out)
Looking into http://localhost/releases/slink/sparc/install.es.html
http://www.es.debian.org/releases/2.1/sparc/release-notes/ : error 500 Can't
connect to www.es.debian.org:80 (Connection timed out)
Looking into http://localhost/releases/slink/i386/install.pt.html
http://www.br.debian.org/releases/2.1/i386/release-notes/ : error 500 Can't
connect to www.br.debian.org:80 (Connection timed out)
Looking into http://localhost/releases/slink/i386/install.es.html
http://www.es.debian.org/releases/2.1/i386/release-notes/ : error 500 Can't
connect to www.es.debian.org:80 (Connection timed out)
Looking into http://localhost/releases/slink/alpha/install.pt.html
http://www.br.debian.org/releases/2.1/alpha/release-notes/ : error 500 Can't
connect to www.br.debian.org:80 (Connection timed out)
Looking into http://localhost/releases/slink/alpha/install.es.html
http://www.es.debian.org/releases/2.1/alpha/release-notes/ : error 500 Can't
connect to www.es.debian.org:80 (Connection timed out)
Looking into http://localhost/releases/slink/m68k/install.pt.html
http://www.br.debian.org/releases/2.1/m68k/release-notes/ : error 500 Can't
connect to www.br.debian.org:80 (Connection timed out)
Looking into http://localhost/releases/slink/m68k/install.es.html
http://www.es.debian.org/releases/2.1/m68k/release-notes/ : error 500 Can't
connect to www.es.debian.org:80 (Connection timed out)
Looking into
http://localhost/releases/slink/sparc/release-notes/ch-whats-new.pt.html
http://www.br.debian.org/Bugs/ : error 500 Can't connect to
www.br.debian.org:80 (Connection timed out)
Looking into
http://localhost/releases/slink/sparc/release-notes/ch-upgrading.pt.html
http://www.br.debian.org/releases/2.1/sparc/dselect-beginner : error 500
Can't connect to www.br.debian.org:80 (Connection timed out)
Looking into
http://localhost/releases/slink/i386/release-notes/ch-upgrading.pt.html
http://www.br.debian.org/releases/2.1/i386/dselect-beginner : error 500 Can't
connect to www.br.debian.org:80 (Connection timed out)
Looking into
http://localhost/releases/slink/alpha/release-notes/ch-upgrading.pt.html
http://www.br.debian.org/releases/2.1/alpha/dselect-beginner : error 500
Can't connect to www.br.debian.org:80 (Connection timed out)
Looking into
http://localhost/releases/slink/m68k/release-notes/ch-upgrading.pt.html
http://www.br.debian.org/releases/2.1/m68k/dselect-beginner : error 500 Can't
connect to www.br.debian.org:80 (Connection timed out)
Looking into http://localhost/releases/slink/sparc/ch-welcome.pt.html
http://www.br.debian.org/social_contract : error 500 Can't connect to
www.br.debian.org:80 (Connection timed out)
http://www.br.debian.org/doc/debian-policy/ : error 500 Can't connect to
www.br.debian.org:80 (Connection timed out)
http://www.br.debian.org/doc/FAQ/ : error 500 Can't connect to
www.br.debian.org:80 (Connection timed out)
http://www.br.debian.org/releases/2.1/ : error 500 Can't connect to
www.br.debian.org:80 (Connection timed out)
http://www.br.debian.org/releases/2.1/sparc/install : error 500 Can't connect
to www.br.debian.org:80 (Connection timed out)
Looking into http://localhost/releases/slink/sparc/ch-hardware-req.pt.html
http://www.br.debian.org/MailingLists/subscribe : error 500 Can't connect to
www.br.debian.org:80 (Connection timed
Re: `boot-floppies' documentation naming conventions?
Adam Di Carlo [EMAIL PROTECTED] writes: The current state is that translations are relying on the existance of www.es.debian.org and www.br.debian.org, both of which are not very reliable. In fact, neither is currently accessable. This isn't very robust. Well, lets just have it all point, for web pages, to www.debian.org. Go ahead and change that in slink, I'll hack it for potato. For downloads, should we point to http.us.debian.org or is there something better? James, if you don't have time to fix the broken links, could you at least send the list of broken links to the debian-boot mail list? -- .Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/
Re: `boot-floppies' documentation naming conventions?
Where is the install doc source for slink? I'd like to get rid of as many of the broken links in it as possible. If the install docs aren't going to be updated ever again, I could simply make the changes in the current .html. In looking through the doc source for potato, I notice that www-debian-org can be replaced in each language by their choice of site. This is not a good idea since it assumes that people speaking that language have good connectivity to that site. For example, I know a lot of people in Quebec that would not like being pushed over to www.fr.debian.org simply because they chose French as the default language for their browser. If it is necessary to use an absolute URL for the Debian site, either point to www.debian.org or list all the official mirrors. All links to documents that can be found locally should be relative. Once a user chooses a site, they should be able to stay on that site. -- James (Jay) Treacy [EMAIL PROTECTED]
Re: `boot-floppies' documentation naming conventions?
Where is the install doc source for slink? I'd like to get rid of as many of the broken links in it as possible. If the install docs aren't going to be updated ever again, I could simply make the changes in the current .html. Don't do that. Oh, Ick. Use the included CVS instructions. Use the slink branch of CVS. In looking through the doc source for potato, I notice that www-debian-org can be replaced in each language by their choice of site. This is not a good idea since it assumes that people speaking that language have good connectivity to that site. For example, I know a lot of people in Quebec that would not like being pushed over to www.fr.debian.org simply because they chose French as the default language for their browser. Seems like a decent heuristic to me. Of course, nothing is certain. If it is necessary to use an absolute URL for the Debian site, It is... Users may have the documentation on a CD or from the web. Links off the document onto the www.debian.org site must be absolute. For potato, it's pretty easy to set some vars different for the version which is destined for www.debian.org. either point to www.debian.org or list all the official mirrors. All links to documents that can be found locally should be relative. Once a user chooses a site, they should be able to stay on that site. Uh... As for listing the official mirrors, I'd rather not. It would be nice if there was a CGI where I could point to a special URL and it would list all possible mirrors and give the user a cookie or something so they use that in the future. Like TUG or perl.org does. But I can't count on such counter-factual scenarios. I have to deal with reality as it is. I wouldn't put too much structural effort like this into slink but rather focus on potato. .Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/
Re: `boot-floppies' documentation naming conventions?
On Fri, Mar 24, 2000 at 02:53:05PM -0500, Adam Di Carlo wrote: Uh... As for listing the official mirrors, I'd rather not. It would be nice if there was a CGI where I could point to a special URL and it would list all possible mirrors and give the user a cookie or something so they use that in the future. Like TUG or perl.org does. I'll consider this. But I can't count on such counter-factual scenarios. I have to deal with reality as it is. The current state is that translations are relying on the existance of www.es.debian.org and www.br.debian.org, both of which are not very reliable. In fact, neither is currently accessable. This isn't very robust. -- James (Jay) Treacy [EMAIL PROTECTED]
Re: `boot-floppies' documentation naming conventions?
The current state is that translations are relying on the existance of www.es.debian.org and www.br.debian.org, both of which are not very reliable. In fact, neither is currently accessable. This isn't very robust. Well, lets just have it all point, for web pages, to www.debian.org. Go ahead and change that in slink, I'll hack it for potato. For downloads, should we point to http.us.debian.org or is there something better? .Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/
Re: Please rebuild *.ja.txt under releases/slink on web (Re: `boot-floppies' documentation naming conventions? )
Hi, thank you for your reply ! In [EMAIL PROTECTED], at Wed, 22 Mar 2000 11:00:31 -0500, with Re: Please rebuild *.ja.txt under releases/slink on web (Re: `boot-floppies' documentation naming conventions? ) , Adam Di Carlo [EMAIL PROTECTED] writes: adam Adam, can you rebuild *.ja.txt under releases/slink on www.debian.org adam with the recent potato version of debiandoc-sgml ? adam adam # if I can do, I will happily do it. adam adam If you have an account on master, you can just replace the file, I adam think. I'm not sure. Why don't you try and let me know. If you adam can't, I'll replace it. OK, I'll try, and report the result to you. Thanks ! -- Taketoshi Sano: [EMAIL PROTECTED],[EMAIL PROTECTED],[EMAIL PROTECTED]
Please rebuild *.ja.txt under releases/slink on web (Re: `boot-floppies' documentation naming conventions? )
Adam, can you rebuild *.ja.txt under releases/slink on www.debian.org with the recent potato version of debiandoc-sgml ? # if I can do, I will happily do it. From Debian Bug report logs - #60354 (http://www.debian.org/Bugs/db/60/60354.html) | Subject: Re: Bug#60354: www.debian.org: http://www.debian.org/releases/slink/ | i386/dselect-beginner.ja.txt is broken | Message-ID: [EMAIL PROTECTED] | References: [EMAIL PROTECTED] 23161806.DA | [EMAIL PROTECTED] | Mime-Version: 1.0 | Content-Type: text/plain; charset=us-ascii | User-Agent: Mutt/1.0pre2i | In-Reply-To: [EMAIL PROTECTED] | | On Fri, Mar 17, 2000 at 03:06:24AM +0900, Yoshizumi Endo wrote: | /releases/slink/i386/dselect-beginner.ja.txt is broken because | debiandoc2text is (was?) not support folding for Japanese language | correctly. I heard that potato version debiandoc-sgml is work fine. | | All *.ja.txt files under the directory /releases/slink/ have same | problem. Please regenerate these *.ja.txt files with potato version | debiandoc-sgml. | | It seems that debiandoc-sgml (version 1.1.40) works fine on my | machine. | | BTW, I got that latest version of debiandoc-sgml installed on va.d.o the | other day (thanks, James :), so a simple rebuild should do. | | -- | enJoy -*/\*- don't even try to pronounce my first name The documentation for potato will be good, but some users may use slink after potato released for some months until they can get their CDs, so I think the problem with the documentation for slink should be fixed. Thanks. -- Taketoshi Sano: [EMAIL PROTECTED],[EMAIL PROTECTED],[EMAIL PROTECTED]
Re: `boot-floppies' documentation naming conventions?
James A. Treacy [EMAIL PROTECTED] writes:
On a related note, is boot-floppies responsible for the files in
releases/{slink,potato}/? There are a number of problems with links there
and I need to know who to forward problems/bugs to (and there are currently
a LOT of broken links). If I had access to the source, I'd even be willing
to fix problems with the links.
Yes, I did 'make all-lang-arch-docs' to populate the slink
documentation. The rest is in WML.
I haven't had a chance to populate the potato data yet. So any broken
links there are purely WML problems.
Oh, and for slink, I copies the boot-floppies materials into the
webroot for mirroring, which was a quick-hack decision but nasty
nasty. For potato, at least theoretically, we just set the
boot-floppies archive URL, say, to
http.us.debian.org/dists/potato/main/ or something, and then we don't
have to have all those megs and megs of data in place for downloading
off the web to work.
Are you volunteering to help with the getting the potato documentation
fully web ready? That would be great. I can give you CVs
instructions.
--
.Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/
Re: `boot-floppies' documentation naming conventions?
On Mon, Mar 20, 2000 at 10:48:15PM -0500, Adam Di Carlo wrote: I haven't had a chance to populate the potato data yet. So any broken links there are purely WML problems. I'm going to generate a new broken url list as soon as todays mirror update is done. Oh, and for slink, I copies the boot-floppies materials into the webroot for mirroring, which was a quick-hack decision but nasty nasty. For potato, at least theoretically, we just set the boot-floppies archive URL, say, to http.us.debian.org/dists/potato/main/ or something, and then we don't have to have all those megs and megs of data in place for downloading off the web to work. We got a lot of complaints from people who had trouble accessing the archive because too many people were using it and/or they didn't have good access to the site listed. That was why we included the files on the web site - automatic mirroring and guarantee that the URLs would work. I have no problem with pointing into an ftp archive (or archives if a DNS round-robin is used). as long as the machine(s) listed can handle the load (without hitting max users) and a reasonable portion of the world is represented. Are you volunteering to help with the getting the potato documentation fully web ready? That would be great. I can give you CVs instructions. I am willing to fix some broken links. Wish I had time to do more. -- James (Jay) Treacy [EMAIL PROTECTED]
Re: `boot-floppies' documentation naming conventions?
On Mon, Mar 20, 2000 at 10:48:15PM -0500, Adam Di Carlo wrote:
On a related note, is boot-floppies responsible for the files in
releases/{slink,potato}/? There are a number of problems with links there
and I need to know who to forward problems/bugs to (and there are currently
a LOT of broken links). If I had access to the source, I'd even be willing
to fix problems with the links.
Yes, I did 'make all-lang-arch-docs' to populate the slink
documentation. The rest is in WML.
Ah. Finnally someone said something concrete about this. :) So all the
boot-floppies does to the web pages is generate the installation manual,
dselect tutorial, and the release notes, and put it in the right place.
Right?
The rest should be in:
cvs -d :ext:username@cvs.debian.org:/cvs/webwml co webwml/english/releases/
--
enJoy -*/\*- don't even try to pronounce my first name
Re: `boot-floppies' documentation naming conventions?
Ah. Finnally someone said something concrete about this. :) So all the boot-floppies does to the web pages is generate the installation manual, dselect tutorial, and the release notes, and put it in the right place. Right? Right. .Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/
Re: `boot-floppies' documentation naming conventions?
On Sun, Mar 19, 2000 at 03:29:05AM -0800, Karl M. Hegbloom wrote:
Debian == Debian Bug Tracking System [EMAIL PROTECTED] writes:
Debian Processing commands for [EMAIL PROTECTED]:
reassign 58638 boot-floppies
Debian Bug#58638: The documentation in disks-i386 is not available in
other languages
Debian Bug reassigned from package `ftp.debian.org' to `boot-floppies'.
This reminds me... Not only do we need to ensure that the
non-english documentation gets installed by our `make release'
target, we need to make sure that the file names are of the correct
form so that content negotiation will function correctly.
Yesterday was the first time I read anything about that... What I
learned is that with Apache Options Multiviews, a file named like
name.html.en will be found when name.html is requested, but a
name like name.en.html will not, unless `mod_rewrite' is used...(?)
Can you clue me in? What should we be naming the documentation files
like so that things will function correctly on
URL:http://http.us.debian.org/debian and others?
Please name file using the convention foo.lang.html . We decided on that
format instead of foo.html.lang because apache can get confused on the
mime type. Local links should be relative and only name the file base,
e.g. foo.
On a related note, is boot-floppies responsible for the files in
releases/{slink,potato}/? There are a number of problems with links there
and I need to know who to forward problems/bugs to (and there are currently
a LOT of broken links). If I had access to the source, I'd even be willing
to fix problems with the links.
In the future, could you send mail directly to debian-www? We'd combine
webmaster and debian-www, but webmaster occasionally gets mail not meant
for public consumption.
--
James (Jay) Treacy
[EMAIL PROTECTED]
Re: `boot-floppies' documentation naming conventions?
On Sun, Mar 19, 2000 at 03:48:31PM -0800, Karl M. Hegbloom wrote: Adam == Adam Di Carlo [EMAIL PROTECTED] writes: Yesterday was the first time I read anything about that... What I learned is that with Apache Options Multiviews, a file named like name.html.en will be found when name.html is requested, but a name like name.en.html will not, unless `mod_rewrite' is used...(?) Can you clue me in? What should we be naming the documentation files like so that things will function correctly on URL:http://http.us.debian.org/debian and others? Adam The file naming we currently use is *guaranteed* to work on Adam www.debian.org and debian mirrors. I don't know about the foo.en.html Adam vs foo.html.en -- I just did things (for slink, even!) the way that Adam they actually do other such pages on the debian web site. Adam Its already there for the slink area and it works. Webmaster? Can you please show me how you configure Apache for that, just so I know how it's done? It's as simple as: Directory /home/treacy/public_html Options +Multiviews /Directory in your /etc/apache/access.conf. You also need to make sure that every language you wish to serve has an AddLanguage line in srm.conf and is listed in LanguagePriority. -- James (Jay) Treacy [EMAIL PROTECTED]
