Accepted dict-wn 2.0-2 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 11 Jan 2004 16:33:06 -0500 Source: dict-wn Binary: dict-wn Architecture: source all Version: 2.0-2 Distribution: unstable Urgency: low Maintainer: Bob Hilliard [EMAIL PROTECTED] Changed-By: Bob Hilliard [EMAIL PROTECTED] Description: dict-wn- WordNet v2.0 Closes: 221188 222794 Changes: dict-wn (2.0-2) unstable; urgency=low . * Fixed formatting of header to make dict -i and dict 00-databse-info work properly. I fixed this in debian/patch-wn, instead of the sed command included in Bug Report #221188 submitted by Grant Hollingworth [EMAIL PROTECTED]. Thanks, Grant. Closes: #221188. . * Corrected typo under espouse s/Catholocism/Catholicism/. Closes: #222794. Files: 69cd38f1405561f027d5683a0b387170 561 text optional dict-wn_2.0-2.dsc 99ae76fe1898b8051263023f880179d0 8006 text optional dict-wn_2.0-2.diff.gz 1cca9e8a029187e1d1b44a98c728e142 10403636 text optional dict-wn_2.0-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFAAdbdn+Nh6TkNZVkRAtj/AKDFNFQvlEeQn+5BMC9+sU+s2A7JcgCfd4Ad 8nBJpGzD+v3UGyrMk+Sipzk= =w12v -END PGP SIGNATURE- Accepted: dict-wn_2.0-2.diff.gz to pool/main/d/dict-wn/dict-wn_2.0-2.diff.gz dict-wn_2.0-2.dsc to pool/main/d/dict-wn/dict-wn_2.0-2.dsc dict-wn_2.0-2_all.deb to pool/main/d/dict-wn/dict-wn_2.0-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted dict-devil 1.0-8 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 26 Dec 2003 17:52:12 -0500 Source: dict-devil Binary: dict-devil Architecture: source all Version: 1.0-8 Distribution: unstable Urgency: low Maintainer: Bob Hilliard [EMAIL PROTECTED] Changed-By: Bob Hilliard [EMAIL PROTECTED] Description: dict-devil - The Devil's Dictionary by Ambrose Bierce Closes: 221190 222494 Changes: dict-devil (1.0-8) unstable; urgency=low . * Edited devils.txt: . under LAUREL s/_vide supra_/LAUREATE/ (vide supra is not appropraite when only one entry is displayed by dict). . The following correct typos in the original: under FRYING-PAN s/broiling in/broiling is/ under I s/clearer the/clearer to the/ under K s/pums/puns/ under PRE-ADAMITE s/race of antedated/race that antedated/ under RICE-WATER s/fat which/fat witch/ . * Used modified devil2dict from Matej Vela [EMAIL PROTECTED] instead of my sedscript for pre-processing devils.txt. This indexes multi-word, hyphenated, and apostrophized headwords. Closes: #222494. This includes the fix provided by Grant Hollingworth [EMAIL PROTECTED] in Bug #221190. Closes: #221190. Thanks, Grant and Matej, Files: 99bb8f9c73c5f82a3a7ab5cfb29bc89a 590 text optional dict-devil_1.0-8.dsc 4171eda36973af080c1ee8e6124cc54c 7996 text optional dict-devil_1.0-8.diff.gz 30b00f56907f652e73bf497dcbe77ce2 179444 text optional dict-devil_1.0-8_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE//eqbn+Nh6TkNZVkRAuYmAKC6wc4yKNPSJEGhe5nC1ursxwXRnACggFjt LDO/uJsB7IwfgLqTTYZegvI= =eI5W -END PGP SIGNATURE- Accepted: dict-devil_1.0-8.diff.gz to pool/main/d/dict-devil/dict-devil_1.0-8.diff.gz dict-devil_1.0-8.dsc to pool/main/d/dict-devil/dict-devil_1.0-8.dsc dict-devil_1.0-8_all.deb to pool/main/d/dict-devil/dict-devil_1.0-8_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted dict-devil 1.0-7 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 02 Nov 2003 12:04:21 -0500 Source: dict-devil Binary: dict-devil Architecture: source all Version: 1.0-7 Distribution: unstable Urgency: low Maintainer: Bob Hilliard [EMAIL PROTECTED] Changed-By: Bob Hilliard [EMAIL PROTECTED] Description: dict-devil - The Devil's Dictionary by Ambrose Bierce Closes: 218707 Changes: dict-devil (1.0-7) unstable; urgency=low . * Corrected format of Build-Depends-Indep: Closes: #218707 Files: 6c0f48ce7c5f8e4c4eb43db38792d25d 590 text optional dict-devil_1.0-7.dsc a325023aea17177bfdb08a353f0fcaa8 4826 text optional dict-devil_1.0-7.diff.gz 29adc0f42c64fdf1a51d8fe246fafe1c 178948 text optional dict-devil_1.0-7_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/pTlKn+Nh6TkNZVkRAhcmAJ0TwSIZGtDKPsdONEsriIhpZk0ZKwCgqV33 LWeDlhafvWKS8ZQNYJT5Zao= =Da5n -END PGP SIGNATURE- Accepted: dict-devil_1.0-7.diff.gz to pool/main/d/dict-devil/dict-devil_1.0-7.diff.gz dict-devil_1.0-7.dsc to pool/main/d/dict-devil/dict-devil_1.0-7.dsc dict-devil_1.0-7_all.deb to pool/main/d/dict-devil/dict-devil_1.0-7_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted dict-gcide 0.48-4 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 02 Nov 2003 11:40:23 -0500 Source: dict-gcide Binary: dict-gcide dict-web1913 Architecture: source all Version: 0.48-4 Distribution: unstable Urgency: low Maintainer: Bob Hilliard [EMAIL PROTECTED] Changed-By: Bob Hilliard [EMAIL PROTECTED] Description: dict-gcide - A Comprehensive English Dictionary dict-web1913 - Empty package to assist the transition to dict-gcide Closes: 218709 Changes: dict-gcide (0.48-4) unstable; urgency=low . * Corrected format of Build-Depends-Indep: Closes: #218709 Files: deef6e4908a410aaca1ed3dbff379d48 614 text optional dict-gcide_0.48-4.dsc ea677b071564643bca79941f6fe9c03d 52392 text optional dict-gcide_0.48-4.diff.gz 3f21cc6cffa361b2ced3ab0f38a04ac4 15124092 text optional dict-gcide_0.48-4_all.deb 2592d3222a35b037ff27086297a350b7 1386 text optional dict-web1913_1.4-0.47pd-9_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/pYgtn+Nh6TkNZVkRAuMkAJ9uL8gD6Do7CyARV5JHemJwrTT0rACfVu2r Dz/BVpeAQEmnVTq3o/+PYWg= =i/Jp -END PGP SIGNATURE- Accepted: dict-gcide_0.48-4.diff.gz to pool/main/d/dict-gcide/dict-gcide_0.48-4.diff.gz dict-gcide_0.48-4.dsc to pool/main/d/dict-gcide/dict-gcide_0.48-4.dsc dict-gcide_0.48-4_all.deb to pool/main/d/dict-gcide/dict-gcide_0.48-4_all.deb dict-web1913_1.4-0.47pd-9_all.deb to pool/main/d/dict-gcide/dict-web1913_1.4-0.47pd-9_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted dict-devil 1.0-6 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 21 Sep 2003 15:48:30 -0400 Source: dict-devil Binary: dict-devil Architecture: source all Version: 1.0-6 Distribution: unstable Urgency: low Maintainer: Bob Hilliard [EMAIL PROTECTED] Changed-By: Bob Hilliard [EMAIL PROTECTED] Description: dict-devil - The Devil's Dictionary by Ambrose Bierce Closes: 204618 Changes: dict-devil (1.0-6) unstable; urgency=low . * Fixed typo in entry for woman - s/Greeland/Greenland/ - Closes: #204618 (At first I thought this might be deliberate - Bierce was fond of invented proper names and fanciful expressions, and this line contains three apparent typos. I obtained a hard-copy of the Devil's Dictionary, and verified that this was a typo in the e-text.) (All copies of the Devil's Dictionary that I could find on line are based n the same e-test as this package.) Files: 190e95dbda773d43b255302e88af011d 587 text optional dict-devil_1.0-6.dsc 4b61c39856ea2d9ebddf1fe7df6f858e 4800 text optional dict-devil_1.0-6.diff.gz ad3608dc2184724f7b0f5b6c2b9b3f7d 17 text optional dict-devil_1.0-6_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/bgJ/n+Nh6TkNZVkRAosoAJwKCtNpEOmLM3O+5x5moMav+f9OAACgmE+4 EtCgHfWXNQ/reH13hZecVUI= =SVLN -END PGP SIGNATURE- Accepted: dict-devil_1.0-6.diff.gz to pool/main/d/dict-devil/dict-devil_1.0-6.diff.gz dict-devil_1.0-6.dsc to pool/main/d/dict-devil/dict-devil_1.0-6.dsc dict-devil_1.0-6_all.deb to pool/main/d/dict-devil/dict-devil_1.0-6_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted dict-wn 2.0-1 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 31 Aug 2003 18:26:19 -0400 Source: dict-wn Binary: dict-wn Architecture: source all Version: 2.0-1 Distribution: unstable Urgency: low Maintainer: Bob Hilliard [EMAIL PROTECTED] Changed-By: Bob Hilliard [EMAIL PROTECTED] Description: dict-wn- WordNet v2.0 Closes: 137882 160852 175916 177314 Changes: dict-wn (2.0-1) unstable; urgency=low . * New upstram release . * Copied ../dict-wn-2.0 to dict-wn-2.0 and replaced contents of ../data subdirectory with files from WordNet 2.0 Created dict-wn_2.0.orig.tar.gz. . * Increased buffer size in wnfilter to prevent segfault when formatting dict-wn-2.0. . * This version corrects typographical errors previously reported: in advantage entry - closes: #137882 in lederhosen entry - closes: #160852 and modifies definition of quid pro quo, which eliminates a typo - closes: #177314 . * The following changes have been made for this Debian version: added a pasture grass prefixing the black grama and blue grama entries added entry for ROI and return on investment- closes: #175916 corrected typo s/an/and/ in baroque entry. removed redundant ands in informatics entry Files: e4db5005aaf049dcc9810cf6afdac337 561 text optional dict-wn_2.0-1.dsc 0863abe7ca0ff6e1526e875f34119710 8136043 text optional dict-wn_2.0.orig.tar.gz e4eebd22270adeac43fdd1ccc8016bb6 7352 text optional dict-wn_2.0-1.diff.gz ada38fb74186f22581185ae6801b0e3d 10413050 text optional dict-wn_2.0-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/Unv1n+Nh6TkNZVkRAl9dAKDCMCuRjpsO3MqbytQI9ulr1vdetACg03q2 bXCX8NIZLZlzBsvhLHPlb4Q= =Ob0d -END PGP SIGNATURE- Accepted: dict-wn_2.0-1.diff.gz to pool/main/d/dict-wn/dict-wn_2.0-1.diff.gz dict-wn_2.0-1.dsc to pool/main/d/dict-wn/dict-wn_2.0-1.dsc dict-wn_2.0-1_all.deb to pool/main/d/dict-wn/dict-wn_2.0-1_all.deb dict-wn_2.0.orig.tar.gz to pool/main/d/dict-wn/dict-wn_2.0.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ITA freedict
Steve Langasek [EMAIL PROTECTED] writes: . . . LOCPATH=/tmp/usr/lib/locale dictfmt --locale ($LOCALE_NAME).$(LOCALE_CHAR= SET) ought to have the desired effect. All locale-related glibc functions should respect the value of LOCPATH Thanks, Steve. It works as advertised now. I had set the value of LOCPATH earlier in the rules file, but I didn't export it. PEBCAK! Regards, Bob -- _ |_) _ |_Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) 1294 S.W. Seagull Way [EMAIL PROTECTED] Palm City, FL 34990 USA GPG Key ID: 390D6559
Re: ITA freedict
Petter Reinholdtsen [EMAIL PROTECTED] writes: If you set LOCPATH to the equivalent of /usr/lib/locale, and LC_ALL to the name of the locale you generate, you should get what you want without being root. Something like this (mostly cut-n-paste from d-i build system): # The variables LOCALE_PATH=/tmp/usr/lib/locale LOCALE_NAME=en_IN LOCALE_CHARSET=UTF-8 # Generating the locale mkdir -p $LOCALE_PATH localedef -i $LOCALE_NAME.$LOCALE_CHARSET -f $LOCALE_CHARSET \ $LOCALE_PATH/$LOCALE_NAME.$LOCALE_CHARSET # Using the locale LOCPATH=$LOCALE_PATH LC_ALL=$LOCALE_NAME.$LOCALE_CHARSET date Steve Langasek [EMAIL PROTECTED] added: Looks like this needs to be localedef -i $LOCALE_NAME -f $LOCALE_CHARSET instead, but otherwise, I've confirmed that this works. I need to use this locale as a command line argument to dictfmt --locale. dictfmt calls this locale with setlocale(3). I have tried --locale $(LOCALE_NAME).$(LOCALE_CHARSET) and --locale $(LOCPATH)/$(LOCALE_NAME).$(LOCALE_CHARSET). Both return invalid locale, which is the error message dictfmt emits when it cannot open the specified locale file. The locale _is_ generated in $LOCALE_PATH. Is the environment variable LOCPATH used by setlocale(3)? Can anyone suggest what I need to try to make this work? Regards, Bob -- _ |_) _ |_Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) 1294 S.W. Seagull Way [EMAIL PROTECTED] Palm City, FL 34990 USA GPG Key ID: 390D6559
ITA freedict
I sent the following message with the X-Debbugs-CC: debian-devel@lists.debian.org header, but apparently [EMAIL PROTECTED] doesn't recognize that header, so I am resending it. -- tags 206113 +ITA thanks I intend to adopt freedict, which was recently orphaned. dict-freedict consists of 42 utf-8 encoded bi-lingual dictionaries. In the past dict-freedict has included pre-formatted dictionaries downloaded from www.freedict.de. However, these pre-formatted dictionaries do not work with modern versions of dictd. In the dict-* packages that I maintain, I have always formatted the dictionary as part of the build process. This presents a problem for the dict-freedict package, in that a xx_YY.utf-8 locale must be available on the build machine. AFAIK there is no way to guarantee that a specific locale is available on the buildds. It would be possible for debian/rules to generate a xx_YY.utf-8 locale, but this would require rules to run as root, which is not permissible by policy. The simplest approach would be to format the dictionaries on my machine, and include them in the source package. This would be similar to the previous dict-freedict packages. Would this be acceptable? Regards, Bob -- _ |_) _ |_Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) 1294 S.W. Seagull Way [EMAIL PROTECTED] Palm City, FL 34990 USA GPG Key ID: 390D6559
/usr/bin/pager
Is /usr/bin/pager a Debianism, or is it common to other distributions and/or unices? Regards, Bob -- _ |_) _ |_Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) 1294 S.W. Seagull Way [EMAIL PROTECTED] Palm City, FL 34990 USA GPG Key ID: 390D6559
Re: Future releases of Debian
John Hasler [EMAIL PROTECTED] writes: Bob Hilliard wrote: A true newbie would be one who has never used a computer before. To such a person, a CLI is much more intuitive than any GUI. Colin Walters writes: And your research supporting this is...? No research, but I've had a couple of experiences that tend to confirm it. It's irrelevant, though, because people who have never used Windows or Mac are getting scarce. John answered before I got to it, but he said essentially what I would have. 1 Regards, Bob -- _ |_) _ |_Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) 1294 S.W. Seagull Way [EMAIL PROTECTED] Palm City, FL 34990 USA GPG Key ID: 390D6559
Re: Future releases of Debian
Bernhard R. Link [EMAIL PROTECTED] writes: Taken this statement directly it's user-unfriendly in both the sense of newbie-unfriendly and experienced-unfriendly. (A newbie might like it, but he will still suffer from it). There is a widespread tendency to consider newbie to mean a refugee from MS or some other eye-candy system. A true newbie would be one who has never used a computer before. To such a person, a CLI is much more intuitive than any GUI. Regards, Bob -- _ |_) _ |_Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) 1294 S.W. Seagull Way [EMAIL PROTECTED] Palm City, FL 34990 USA GPG Key ID: 390D6559
Re: May packages rm -rf subdirectories of /etc/ ?
Manoj Srivastava [EMAIL PROTECTED] writes: Umm. apt allows you to determine reverse depends. From there there is an easy hop to sending email to ask the develoeprsa in question; or to exaimine a package to look at its conffiles. Slightly off-topic, is there any tool to easily determine reverse build-depends? Regards, Bob -- _ |_) _ |_Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) 1294 S.W. Seagull Way [EMAIL PROTECTED] Palm City, FL 34990 USA GPG Key ID: 390D6559
Re: Excessive wait for DAM - something needs to be done
In my experience, James has been very responsive, albeit not verbose, to reasonable questions/requests that don't start out saying James is a bum - throw him out. Regards, Bob -- _ |_) _ |_Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) 1294 S.W. Seagull Way [EMAIL PROTECTED] Palm City, FL 34990 USA GPG Key ID: 390D6559
Accepted dict-gcide 0.48-3 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 03 Jun 2003 17:46:12 -0400 Source: dict-gcide Binary: dict-web1913 dict-gcide Architecture: source all Version: 0.48-3 Distribution: unstable Urgency: low Maintainer: Bob Hilliard [EMAIL PROTECTED] Changed-By: Bob Hilliard [EMAIL PROTECTED] Description: dict-gcide - A Comprehensive English Dictionary dict-web1913 - Empty package to assist the transition to dict-gcide Closes: 181564 195074 Changes: dict-gcide (0.48-3) unstable; urgency=low . * Modified postinst.web and config to eliminate bashisms. Closes: 195074 . * Corrected typos in: cide.s under Shark: s/baskin/basking/ cide.a under Antiperistasis: s/asquires/acquires/ Closes: #181564 Files: 33847eb916a4187bbcde2eb6863cc932 609 text optional dict-gcide_0.48-3.dsc c904905624de59afaad1d712be31af02 52109 text optional dict-gcide_0.48-3.diff.gz 08ba9c4a151c5207b311844c684bf105 15124026 text optional dict-gcide_0.48-3_all.deb 4a04b6645cc5d115efafa2765c2e2675 1386 text optional dict-web1913_1.4-0.47pd-8_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+3SDbn+Nh6TkNZVkRAsFLAJ9ixBs7v9U2VPKofSm6cfvU8MY5vACgj5Jb CzQm2Fr/q4gxVKQHrwPEs4Y= =afn3 -END PGP SIGNATURE- Accepted: dict-gcide_0.48-3.diff.gz to pool/main/d/dict-gcide/dict-gcide_0.48-3.diff.gz dict-gcide_0.48-3.dsc to pool/main/d/dict-gcide/dict-gcide_0.48-3.dsc dict-gcide_0.48-3_all.deb to pool/main/d/dict-gcide/dict-gcide_0.48-3_all.deb dict-web1913_1.4-0.47pd-8_all.deb to pool/main/d/dict-gcide/dict-web1913_1.4-0.47pd-8_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian conference in the US?
Please take all of these political screeds off -devel!! Regards. Bob -- _ |_) _ |_Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) 1294 S.W. Seagull Way [EMAIL PROTECTED] Palm City, FL 34990 USA GPG Key ID: 390D6559
Re: Questions regarding utf-8
Andreas Metzler [EMAIL PROTECTED] writes: *prompt* echo ö§ | recode latin1..ascii oSS *prompt* echo ö§ | iconv -f latin1 -t ascii//TRANSLIT ; echo $? oe? -- »oe« is much better than »o« and »SS« is no usable replacement for »§« (I do not think there is one), it would be nice if iconv's exit-status reflected whether questionmarks were used, but changing this would probably break existing software. I agree oe is much better than o, but I can't get that: bob:vc-p2:bobecho ö§ | iconv -f latin1 -t ascii//TRANSLIT ?? I have iconv 2.3.1. Is it possible that my locale affects the glyphs iconv returns? My locale is C. What locale are you using? Following are the values recode gives for the most common non-ASCII characters: ä à ç ñ ê ô ö ß £ a `a c ~n ^e ^o o ss lb For all of these, iconv returns '?' on my system. I have not been able to find recode's transliteration of é. In all cases I have tried, recode truncates the balance of the word containing é, and the beginning of the next word, as in the following examples: Pierre Bézier Pierre B Conseil Européen pour la Normalisation. Conseil Europour la Normalisation. Comité Européen de Normalisation Comitrope Normalisation André Fischer Andrcher Réseaux Associés pour la Recherche Européenne Rx Associur la Recherche Europ Répondez s'il vous plait Rez s'il vous plait I am not happy with the values recode gives, but, in most cases, they are better than the ?. I would like to learn how to make iconv give results similar to those you get. Regards, Bob -- _ |_) _ |_Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) 1294 S.W. Seagull Way [EMAIL PROTECTED] Palm City, FL 34990 USA GPG Key ID: 390D6559
Re: Questions regarding utf-8
Thanks to all who replied to my recent question on this subject. Andreas Metzler [EMAIL PROTECTED] wrote: With glibc I'd use iconv --from=SRC-ENCODING --to=DST-ENCODING//TRANSLIT if it is acceptable to change the length of strings. This will replace e.g. the Euro-Symbol with EUR. Without //TRANSLIT, iconv fails if DST-ENCODING is US or ASCII, but with //TRANSLIT, all characters that aren't included in ASCII are rendered as `?'. This useful, but not as useful as the conversions performed by recode. Where is `//TRANSLIT' documented? Regards, Bob -- _ |_) _ |_Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) 1294 S.W. Seagull Way [EMAIL PROTECTED] Palm City, FL 34990 USA GPG Key ID: 390D6559
Re: The Debian Mentors Project
Christoph Haas [EMAIL PROTECTED] writes: However the service was created especially for people who e.g. have written an application themselves and do not care about becoming a DD. I object to the conept of people who do not care about becoming a DD becoming maintainers of packages. Permitting prospective developers to get sponsored packages in Debian is generally accepted (but not by me), but allowing any random hacker to get a package in without even starting the new-maintainer process is totally unacceptable. Regards, Bob -- _ |_) _ |_Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) 1294 S.W. Seagull Way [EMAIL PROTECTED] Palm City, FL 34990 USA GPG Key ID: 390D6559
Problems with XFS patch and SMP
I wrote: Bug#171943 reports that dictd 1.8.0 fails to start with the following error message: [EMAIL PROTECTED]:~$ /usr/sbin/dictd -d nofork :I: 2535 starting dictd 1.8.0/rf on Linux 2.4.19-xfs Tue Dec 3 23:43:09 2002 dictd (dict_index_open): Cannot mmap index file /dev/null(dict_index_open) Cannot mmap index file /dev/nulldict_index_open: No such device (dict_index_open) dict_index_open: No such device I have not experienced any problems with this version in woody, sarge or sid, using a 2.4.18 kernel, and I have not received any other similar bug reports. The reporter is running a 2.4.19 kernel with the XFS patch and SMP support. Are there any known issues with the XFS patch and SMP support that could contribute to this problem? Is anyone running dictd with a 2.4.19 kernel with the XFS patch and SMP support? Thanks to Craig Saunders, Russell Coker, and Bernd Eckenfels for helpful comments. The problem turns out not to be related to XFS or SMP. It was a configuration error caused by the dictdconfig script. All dictionaries had been removed from the submitter's system, without his being aware of it. If dictdconfig doesn't find any installed dictionaries, it creates a configuration item for a dummy dictionary in /dev/null. This was a misguided attempt to prevent dictd from failing to start if no dictionaries are installed. This will be fixed. Especial thanks to Craig for installing dictd on a machine with a 2.4.19 kernel with XFS and SMP for testing. This can be removed whenever you like. Regards, Bob -- _ |_) _ |_Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) 1294 S.W. Seagull Way [EMAIL PROTECTED] Palm City, FL 34990 USA GPG Key ID: 390D6559
Problems with XFS patch and SMP
Bug#171943 reports that dictd 1.8.0 fails to start with the following error message: [EMAIL PROTECTED]:~$ /usr/sbin/dictd -d nofork :I: 2535 starting dictd 1.8.0/rf on Linux 2.4.19-xfs Tue Dec 3 23:43:09 2002 dictd (dict_index_open): Cannot mmap index file /dev/null(dict_index_open) Cannot mmap index file /dev/nulldict_index_open: No such device (dict_index_open) dict_index_open: No such device I have not experienced any problems with this version in woody, sarge or sid, using a 2.4.18 kernel, and I have not received any other similar bug reports. The reporter is running a 2.4.19 kernel with the XFS patch and SMP support. Are there any known issues with the XFS patch and SMP support that could contribute to this problem? Is anyone running dictd with a 2.4.19 kernel with the XFS patch and SMP support? Regards, Bob -- _ |_) _ |_Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) 1294 S.W. Seagull Way [EMAIL PROTECTED] Palm City, FL 34990 USA GPG Key ID: 390D6559
Re: Packages still in Potato
Otto Wyss [EMAIL PROTECTED] writes: Packages: dict-easton, dict-gazetteer, dict-hitchcock The listed packages are still located in the Potato directory, possibly because there wasn't any update necessary during the full Woody development phase, but maybe also because there is no interest in these packages. So please check your packages and do an upload, so they get into the pool, or orphan them so others can take over or they get removed. Please inform me what you are doing or not doing. This way I may ask others to do NMU's just in case. These packages have not needed any updates. The last update was solely to add the /usr/share/doc directory. I had not contemplated another upload until post-woody, when the /usr/doc symlink could be removed. In previous releases (before the pool concept was adopted), the unstable directory contained symlinks to the unstable directory, and the last step before release was converting any remaining symlinks to hard links. Is it really necessary to make a new upload, rather than copying or linking these packages to the pool? I will make a new upload before the woody release if it is necessary to do so. Please let me know it this is required. Bob -- _ |_) _ |_ Robert D. Hilliard [EMAIL PROTECTED] |_) (_) |_) 1294 S.W. Seagull Way [EMAIL PROTECTED] Palm City, FL USA GPG Key ID: 390D6559 PGP Key ID: A8E40EB9 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BSP?
Alan James [EMAIL PROTECTED] writes: Is there a dict dictionary with all these debian TLAs in it ? I've dont think I've heard BSP before. dict-vera contains most Debian TLAs. I will add BSP to the next release. dict-foldoc includes many Debian TLAs, and defines many Debian-specific terms. Bob -- _ |_) _ |_ Robert D. Hilliard [EMAIL PROTECTED] |_) (_) |_) 1294 S.W. Seagull Way [EMAIL PROTECTED] Palm City, FL USA GPG Key ID: 390D6559 PGP Key ID: A8E40EB9 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BSP?
Alan James [EMAIL PROTECTED] writes: Maybe I'll have a look at creating a dict-debian, there seem to be quite a few potential entries :-) Joey Hess started one several years ago, but abandoned it when I offered to incorporate his work into dict-foldoc. We discussed (I think on -devel) whether or not it should be a stand alone package or be incorporated in an existing dictionary. Most, but not all, of the Debian-specific terms that I have submitted have been incorporated upstream. Ones that have not yet been incorporated upstream are inserted by me in the Debian package. If you submit proposed new definitions to me, I will add them to the Debian package. Acronyms without a separate definition would go into vera, while terms with definitions, and acronyms for these terms, go into foldoc. Bob -- _ |_) _ |_ Robert D. Hilliard [EMAIL PROTECTED] |_) (_) |_) 1294 S.W. Seagull Way [EMAIL PROTECTED] Palm City, FL USA GPG Key ID: 390D6559 PGP Key ID: A8E40EB9 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: rdate can't connect socket
Samuel Tardieu [EMAIL PROTECTED] writes: On 16/09, Bob Hilliard wrote: | This has worked consistently for a long time, but for the past | week or two it returns: | rdate: Could not connect socket: Connection refused | | This message returns almost instantly - too quickly, I believe, | to be a connection refused at the remote server. | | Can this be a socket on my machine that refuses a connection? Did you by chance update your firewall? Could it be rejecting this outgoing connection? I don't have a firewall as such. I deny ALL in /etc/host.deny, and have most services commented out in /etc/inetd.conf, but nothing has changed in these areas since long before rdate started failing. However, see below. Michael B. Taylor [EMAIL PROTECTED] writes: I cant say whether your theory is correct or not. It sounds plausible. However, I did have the same problem a while back. I am pretty sure it the remote server refusing. I resolved the problem by installing the nptdate package, and using my name server as a time host also. You seem to be right. I have successfully tried rdate nameserver. As a matter of interest, I have a rather clueless isp (local cable company) using M$ software. The time returned from its nameserver is three to four minutes slow. My domain is hosted by Greenbush Technologies, which uses Debian, and is run by a clueful administrator. That nameserver gives the correct time. Thanks to both of you for your responses. Bob -- _ |_) _ |_ Robert D. Hilliard [EMAIL PROTECTED] |_) (_) |_) 1294 S.W. Seagull Way [EMAIL PROTECTED] Palm City, FL USA GPG Key ID: 390D6559 PGP Key ID: A8E40EB9
rdate can't connect socket
I posted the following to -user three days ago with no response. Can someone here help? I have the following command in a cron.daily script: rdate time.mist.god This has worked consistently for a long time, but for the past week or two it returns: rdate: Could not connect socket: Connection refused This message returns almost instantly - too quickly, I believe, to be a connection refused at the remote server. Can this be a socket on my machine that refuses a connection? I have rdate 1.3-3. Bob -- _ |_) _ |_ Robert D. Hilliard [EMAIL PROTECTED] |_) (_) |_) 1294 S.W. Seagull Way [EMAIL PROTECTED] Palm City, FL USA GPG Key ID: 390D6559 PGP Key ID: A8E40EB9
Bug reports - copies to submitter
This is probably in the documentation somewhere, but I haven't been able to find it. Which messages to the bug reporting system are automatically forwarded to the submitter, and which must be explicitly copied to [EMAIL PROTECTED] Bob -- _ |_) _ |_ Robert D. Hilliard [EMAIL PROTECTED] |_) (_) |_) 1294 S.W. Seagull Way [EMAIL PROTECTED] Palm City, FL USA GPG Key ID: 390D6559 PGP Key ID: A8E40EB9
GRUB Questions
Is there a GRUB mailing list, or is this the proper forum for GRUB questions? Bob -- _ |_) _ |_ Robert D. Hilliard [EMAIL PROTECTED] |_) (_) |_) 1294 S.W. Seagull Way [EMAIL PROTECTED] Palm City, FL USA GPG Key ID: 390D6559 PGP Key ID: A8E40EB9
Re: wnpp bug reports
Josip Rodin [EMAIL PROTECTED] writes: On Fri, Dec 22, 2000 at 12:58:54PM -0500, Bob Hilliard wrote: Is there any way to submit an ITP bug on WNPP, so that the bug number appears in the copy to -devel? Yes, put -devel in Cc: or (X-Debbugs-Cc:) fields. When I have done this, the report shows up on -devel the same as I submitted it - the Bug Number doesn't appear. -- _ |_) _ |_ Robert D. Hilliard [EMAIL PROTECTED] |_) (_) |_) 1294 S.W. Seagull Way [EMAIL PROTECTED] Palm City, FL USA GPG Key ID: 390D6559 PGP Key ID: A8E40EB9
Re: Single architecture on -announce lists
Ben Collins [EMAIL PROTECTED] writes: On Fri, Mar 17, 2000 at 04:49:54PM -0500, Bob Hilliard wrote: During the slink freeze there was some discussion of the wasted bandwidth due to -devel-announce and -announce listing all packages installed/uploaded to all architectures. As I recall, the consensus was that, after slink was released, these lists would be split by architecture, and anyone interested in more than one architecture could subscribe to as many lists as required. I am sure that the overwhelming majority would subscribe to only one list. [EMAIL PROTECTED](11:01am)-/var/list]%ls -d debian-*-changes debian-all-changes/ debian-devel-changes/ debian-hurd-i386-changes/ debian-alpha-changes/debian-devel-hurd-i386-changes/ debian-i386-changes/ debian-arm-changes/ debian-devel-i386-changes/ debian-m68k-changes/ debian-devel-all-changes/debian-devel-m68k-changes/ debian-powerpc-changes/ debian-devel-alpha-changes/ debian-devel-powerpc-changes/ debian-sparc-changes/ debian-devel-arm-changes/debian-devel-sparc-changes/ The lists already exist, they are just not used at all. Maybe it would be easier to keep just the one debian-devel-changes list to send to and write some extra procmail stuff into sending it to the write outlist. That was what I understood was the intention last year. Apparently the listmasters created the lists, but no one set up the scripts or procmail stuff to implement it. Is it the listmasters responsibility to set this up, or does it belong to admin? I would certainly like to see it happen. Bob -- _ |_) _ |_ Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9
Single architecture on -announce lists
During the slink freeze there was some discussion of the wasted bandwidth due to -devel-announce and -announce listing all packages installed/uploaded to all architectures. As I recall, the consensus was that, after slink was released, these lists would be split by architecture, and anyone interested in more than one architecture could subscribe to as many lists as required. I am sure that the overwhelming majority would subscribe to only one list. What happened to this idea? Bob -- _ |_) _ |_ Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9
Re: Single architecture on -announce lists
Branden Robinson [EMAIL PROTECTED] writes: --n8g4imXOkfNTN/H1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Mar 17, 2000 at 04:49:54PM -0500, Bob Hilliard wrote: During the slink freeze there was some discussion of the wasted bandwidth due to -devel-announce and -announce listing all packages installed/uploaded to all architectures. =20 Funny, I don't notice any such messages going to -devel-announce or -announce. --=20 G. Branden Robinson|Murphy's Guide to Science: Dh!! s/announce/changes/ Soory about that. Bob -- _ |_) _ |_ Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9
Volunteer(s) needed
I will be unable to prepare/maintain the Release-Notes for potato. At least one volunteer to take over this this important but unexciting job is urgently needed. The slink Release-Notes attempted to cover the important new and changed features in slink, and to give instructions for upgrading from previous versions. I now believe it would be preferable to split this into two documents: Release-Notes and Upgrade-Notes. This would make it very easy to split the work between two maintainers. Anyone who is interested should contact Adam DiCarlo [EMAIL PROTECTED] or me [EMAIL PROTECTED] by private mail. Bob -- _ |_) _ |_ Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9
Re: pending normal debian bugs for debian-devel@lists.debian.org
[EMAIL PROTECTED] (Marco d'Itri) writes: On May 18, Nag [EMAIL PROTECTED] wrote: #20734 general autoup.sh http://www.debian.org/Bugs/db/20/20734.html #20743 general autoup.sh: wtmp, utmp and btmp http://www.debian.org/Bugs/db/20/20743.html Isn't autoup.sh obsolete? No, it isn't, unless we want to abandon our promise of upgradeability, rather than installing new, for any Debian system. AFAIK, we have lost the capability of upgrading from a.out to elf. Hopefully we won't lose the capability of upgrading from pre-hamm systems. There are still a lot of bo and rex production systems out there. Bob -- _ |_) _ |_ Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9
Compiling wordinspect for potato
I have recently adopted wordinspect and am trying to compile it for potato. The slink version lists the following dependencies: Depends: dict, libc6 (= 2.0.7u), libglib1.1 (= 1.1.3-2), libgtk1.1 (= 1:1.1.\2-2), xlib6g (= 3.3-5) libglib1.1 and libgtk1.1 are not in potato under those names. libglib1.2 seems to be a logical replacement for libglib1.1, but there are many libgtk* libraries. I installed libglib1.2_1.2.3-1.deb, libglib1.2-dev_1.2.3-1.deb, libgtk1.2_1.2.3-1.deb, and libgtk1.2-dev_1.2.3-1.deb, and built the package. It compiled cleanly, and runs as it did in slink, except that every time it pops up a window it displays the following message: Gtk-WARNING **: gtk_scrolled_window_add(): cannot add non scrollable widget use gtk_scrolled_window_add_with_viewport() instead Would another libgtk be a better choice to replace libgtk1.1, and possibly get away from this warning message, or will the source have to tweaked to avoid this? Bob -- _ |_) _ |_ Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9
dupload problem
When I upload a package I first issue the command ssh-agent
bash, then dupload -t master package-name.changes. This does the
job, but asks for my pass-phrase twice for each file being uploaded.
I think it used to require entering the pass-phrase only once for
each package, but I don't remember making any changes to
/etc/dupload.conf recently. The section of /etc/dupload.conf
pertaining to master is:
$cfg{master} = {
fqdn = master.debian.org,
login = hilliard,
method = scp,
incoming = /home/Debian/ftp/private/project/Incoming/,
mailto = [EMAIL PROTECTED], # stable, contrib, non-free
mailtx = [EMAIL PROTECTED], # unstable, exper.
visibleuser = hilliard,
visiblename = debian.org,
fullname = Bob Hilliard,
};
How can I eliminate the excessive number of pass-phrase entries?
Bob
--
_
|_) _ |_ Robert D. Hilliard[EMAIL PROTECTED]
|_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9
Corporate Visibility for Linux
The following is quoted from the column Business Bulletin on the front page of today's Wall Street journal, which is probably the most widely read newspaper by corporate America: 'FREEWARE' STIRS debate while entrepreneurs find a nice niche. Advocates prefer to call the free software from developers open source software, stressing the fact that the source code used for programming is open and constantly improved. Skeptics fear hackers and the lack of support offered by commercial firms. Enter value added outfits like Caldera Systems, Inc. and Red Hat Software. They package and offer support services for Linux, a popular open-source software version of the Unix operating system created in1991 by Finnish graduate student Linus Torvalds. O'Reilly Associates, a publisher in Sebastopol, Calif., expects about half of is $40 million in revenue this year to come from the sale of open source books. Even the big firms are involved: IBM, for instance, licensed Apache, an open-source product for Web sites. Potential corporate users have a mixed view. Many firms, such as Virginia Power, Wells Fargo Co., Ipalco Enterprises, Inc. and Boeing Co. discourage use of freeware, although some allow special use. Some fear viruses. The City of Garden Grove, Calif. has used a Linux-based network since 1995. Bob -- _ |_) _ |_ Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9
Re: apt and hamm
[EMAIL PROTECTED] (Adam P. Harris) writes: Bob Hilliard [EMAIL PROTECTED] writes: I will be out of town after tomorrow for about a week, so I won't be able to do anything on the README before then, but I don't think 2.0 will be released before then. Perhaps not. Anyhow we should take the autoup README and also add alternative instructions for using apt, I think. If anyone's interested (especially Bob!) I have a collection of notes on how to go about upgrading with apt. Do you contemplate making one upgrade document that includes both autoup and apt? If so, please mail me your notes (directly please, I will probably unsubscribe from the lists for a week), and I will prepare a draft of such a document as soon as I get back early next week. If this needs to be an sgml document, please give me detailed instructions, as I have never used sgml (I normally use emacs for everything; I know emacs has an sgml mode, but I don't know how to use it. Does a document have to be started under sgml, or can I write in emacs and then call the sgml mode to convert it?) On a related note, autoup.sh can upgrade a buzz (1.1.x) system, but it must have dpkg version 1.4 or higher available. So a .deb from bo is required on the CD - probably in the same directory where autoup.sh resides. It certainly shouldn't be in the regular archive! Bob -- _ |_) _ |_ Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: apt and hamm
[EMAIL PROTECTED] (Adam P. Harris) writes:
Bob Hilliard [EMAIL PROTECTED] writes:
There is a README for autoup.sh on
{ftp|http}://debian.vicnet.net.au/autoup/.
Both the README and autoup.sh should have a separate (simplified)
version for use on the CD. (For instance, the script doesn't have to
be interactive on the CD.) The CD versions will be quick and easy to
write, but can't be written until we know exactly where on the disk
autoup.sh is located, and path to the hamm files.
If Igor wanted to incorporate the autoup.sh README in
install.txt, that would eliminate the need to include it as a separate
file on the CD
Interesting. Apparently, there's going to be coverage of these topics
in the release notes, not the install.sgml document.
Volunteers? I'm a bit overcommitted ;)
I wrote the autoup.sh README, and have always expected to update it
for the CD and for the ftp archives and web page when hamm is stable.
Either Craig or I could update autoup.sh pretty quickly, once the
structure of the CD is established. I would prefer to have Craig do
the autoup.sh update, since he doesn't always agree with my
modifications.
I will be out of town after tomorrow for about a week, so I won't
be able to do anything on the README before then, but I don't think
2.0 will be released before then.
Bob
--
_
|_) _ |_ Robert D. Hilliard[EMAIL PROTECTED]
|_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: apt and hamm
[EMAIL PROTECTED] (Adam P. Harris) writes:
(a) we need specific installation instructions for upgrading. Igor,
is this supposed to be part of the install.sgml document, or is it
separate?
(b) recommend for upgrades that users use *either* autoup.sh or, if
they are daring, 'apt-get dist-upgrade' followed by making it
dselect's acquisition method. It would be excellent to support
both of these methods via CDROM is possible, but I would hate to
see that slow down the hamm release cycle.
There is a README for autoup.sh on
{ftp|http}://debian.vicnet.net.au/autoup/.
Both the README and autoup.sh should have a separate (simplified)
version for use on the CD. (For instance, the script doesn't have to
be interactive on the CD.) The CD versions will be quick and easy to
write, but can't be written until we know exactly where on the disk
autoup.sh is located, and path to the hamm files.
If Igor wanted to incorporate the autoup.sh README in
install.txt, that would eliminate the need to include it as a separate
file on the CD
Bob
--
_
|_) _ |_ Robert D. Hilliard[EMAIL PROTECTED]
|_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
dict-foldoc-19980612 removed from Incoming
Yesterday, 12 Jun 1998, I uploaded dict-foldoc-19980612, which included a new upstream version. After uploading it, I realized that dpkg-buildpackage had treated it as a Debian specific package, so no .orig.tar.gz or .diff was included in the upload. I have removed this package from Incoming, and will upload it again after I figure out and fix whatever errors I made in preparing the package. Bob -- _ |_) _ |_ Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Volunteer(s) wanted to help with owner@bugs.debian.org
I will volunteer to work on: 1. Reading and responding to [EMAIL PROTECTED] mail, and 2. Actual administration and maintenance of the bug system (to the extent of my capabilities - I will yell quickly if I get stuck). I would prefer to share these functions with someone else, since I will be unavailable for several weeks during the summer. Bob -- _ |_) _ |_ Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mirror-2.9 released, and hopefully DFSG compliant
Hi, What new and improved features would we forego if you released a mirror28 package? I guess I will have to install 2.9 to see if I'm happy with it. Perhaps you could persuade the author to add support for restarts on partially downloaded files, and any other desirable patches that are not included in 2.9. Dirk Eddelbuettel [EMAIL PROTECTED] writes: Bob I would like to see this feature continued if it isn't in 2.9-1 Bob by default. Note that the license currently states that distributing modified versions of mirror is not koscher. There were way more patches, big and small. Maybe I should release a mirror28 package which preserves these ? Bob -- _ |_) _ |_ Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mirror-2.9 released, and hopefully DFSG compliant
Hi, This new release is fresh code, and I won't pull out all the patches we applied against mirror_2.8. Let me know if there is a feature in 2.8 that you really miss. I could make a 'retro' package mirror28 of the old release. The changelog for mirror 2.8-15 included: * Applied patch by Adam Heath [EMAIL PROTECTED] to allow restarts on partially downloaded files (fixes #19239) I would like to see this feature continued if it isn't in 2.9-1 by default. Bob -- _ |_) _ |_ Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: hamm
[EMAIL PROTECTED] writes: Trying to upgrade via FTP to hamm would be too painfull at 28.8KB! Hi, It depends on your pain threshold, I guess. I thought that too, until I started the bo testihng program a little over a year ago. Since then I have updated from rex to bo, then bo to hamm, and am maintaining a hamm and slink mirror (i386 binary only), all over a 28.8 link. Bob -- _ |_) _ |_ Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ppp: how to tell the connection speed?
Marcelo E. Magallon [EMAIL PROTECTED] writes: On Sat, May 02, 1998 at 08:12:35AM -0500, [EMAIL PROTECTED] wrote: Marcelo E. Magallon writes: As you can see chat breaks the CONNECT line. Is there a way to tell the connection speed? 'ATW2' will make the modem (or at least, my modem) emit something like 'CONNECT 26400'. mine is ATX4 With my ZOOM modem, ATX4 reports all responses, but the manual isn't clear if it means DCE (modem-modem) speed or DTE (computer-modem) speed. I blieve DTE is the most commonly reported value. ATW0 reports DTE speed only; ATW1 reports DCE speed, error correction protocol and DTE speed; ATW2 reports DCE speed only. If the -v option is set in the chat command line, this response appears in the ppp.log file. An excerpt from my ppp.log follows: May 2 14:37:51 bobspc chat[199]: ATDT3350566^M^M May 2 14:37:51 bobspc chat[199]: CARRIER 26400^M May 2 14:37:51 bobspc chat[199]: ^M May 2 14:37:51 bobspc chat[199]: PROTOCOL: LAP-M^M May 2 14:37:51 bobspc chat[199]: ^M May 2 14:37:51 bobspc chat[199]: CONNECT May 2 14:37:51 bobspc chat[199]: -- got it May 2 14:37:54 bobspc pppd[192]: Serial connection established. I use ATW1, but this report doesn't seem to include the DTE speed (which is 115600). BTW has anyone else run across a modem that reports 'CARRIER' instead of 'CONNECT'? Note the above log fragment. My ZOOM modem reports Carrier speed before it reports the CONNECT. Bob -- _ |_) _ |_ Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Boot Disks
Lindsay Allen [EMAIL PROTECTED] writes: May I suggest that you forward your message upstream to either the kernel people or those who do the drivers. It is downright embarrasing to have our favourite OS not be able to read a floppy reliably. Actually, my points were that almost all of the failures I have observed were in reading the rescue disk (which AFIK is read by the BIOS drivers), and that the failures were truly random, and that new disks performed no better than used ones. The previous message, from Jason Gunthorpe [EMAIL PROTECTED], I believe, made the suggestion that the Linux drivers were the source of the problem. Bob -- _ |_) _ |_ Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Proposed Constitution
Mark Baker [EMAIL PROTECTED] wrote: They is not only a singular, it is also widely accepted as a singular pronoun, and has been used as such by not only ordinary people but also great writers for hundreds of years. All of my dictionaries give nominative plural of he, she, or it as the primary definition of they. My unabridged dictionary adds (used with an indefinite singular antecedent in place of the definite masculine he or definite feminine she). The examples cited are for indefinite antecedents such as anyone or whoever. I do not think Project Leader is an indefinite antecedent. Bob -- _ |_) _ |_ Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Conflicts between developers and policy
Raul Miller [EMAIL PROTECTED] writes: Why do you think that these are the reasons? You might be right, but I'd like to know your reasons before agreeing that these are the primary reasons for bugs not being fixed. There are a nuamber of sub-threads in this thread using the same header. My posting was written before I saw the one that discussed open bugs. The problem that I was referring to was the disagreement between those who felt policy should be a binding document, and those who think policy may be ignored when it is inconvenient. I have no opinion regarding the reason or reasons for the large number of open bugs, and think that they are irrelevant to the subject that was being discussed. Bob -- _ |_) _ |_ Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) Palm City, FL USAPGP Key ID: A8E40LB9 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Boot Disks
Jason Gunthorpe [EMAIL PROTECTED] writes: On Tue, 28 Apr 1998, Hamish Moffatt wrote: The sensitivity to good disks is, as I understand it, caused by poor BIOS floppy drivers and is independent of the Linux kernel, let alone which distribution you are running. Actually, as I understood it, the problem was poor linux floppy drivers. You'll note that when most errors occure is when reading the base image or rescue disks, I have very rarely had the boot disk fail. Between my initial rex installation, and bo and hamm testing, I have installed (or attempted to install) debian from floppies close to 100 times. I have rarely seen a base image disk fail, but have seen quite a few boot disks fail, and many rescue disks fail. I am convinced that the failures are truly random, and are not, in most cases, caused by the disks themselves. In one experiment, during the bo testing, I made one set of disks using brand new 3M disks, and another set from recycled AOL disks. I attempted the installation at least 20 times with each set, and recorded the results, including the number of dots displayed when it failed. I consider the number of dots to be a reasonable measure of the point within the image where failure occurred. Unfortunately, I lost my record of these tests when I trashed a partition last year, and Dale's recent hardware catastrophe undoubtedly destroyed his copy of my test report giving the figures. There were slightly more failures with the virgin disks than with the recycled ones, and the number of dots at failure was completely random. In one instance, I observed half a dozen consecutive failures, followed half a dozen successful installations with the same floppies. My experience leads me to believe that the failures are random, and primarily occur when disks are being read by the bios. I have long maintained that we place too much emphasis on making new disks with new floppies, re-downloading the files, etc., and not enough emphasis on simply repeating the installation many times. I have no cure to offer for the problem, just what may be a better insight into where to look for a cure. Bob -- _ |_) _ |_ Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Directory for dictionary databases
Andreas Tille [EMAIL PROTECTED] writes: But in my opinion it is a bad solution if every translation related data should be stored in different directories. I think a directory structure should be as logical as possible. Im not familiar with FHS and havn't enough time to learn about it. But in my opinion it is necessary to store data together if they have the same purpose. I would suppose to store translation related data in /usr/share/lang or /usr/share/trans [-lation] or /usr/share/lingua or may be /usr/share/lingua-mono AND /usr/share/lingua-bi (lingua-multi) The latter case means to store monolingual databases like wordnet and dict in lingua-mono and bilingual databases (I plan to maintain a English-German dictionary) in lingua-bi. (We should think about the Euro-wordnet project which is multilingual.) Supporting this hierarchie wie can store in this directory single file dictionaries and in a subdirectory if there are more files like in the case of wordnet. I don't think a mono-lingual dictionary is translation related data. I agree that bi-lingual files deserve a separate location, but a structure such as you suggest would only be useful if accepted as a standard. So far, at least, the FHS committee has avoided specifying in much detail the subdirectory structure (/usr/share/man and usr/share/dict are exceptions). They do recommend : | Any program or package which contains or requires data that doesn't need | to be modified should store that data in /usr/share (or | /usr/local/share, if installed locally). It is recommended that a | subdirectory be used in /usr/share for this purpose. We should keep in mind that databases for programs like dictd (I don't know if this is true of WordNet) are formatted so that it is difficult, at best, to access them with other programs, so there is less need to keep them together. I think if we don't do that we will end up in so many directories in /usr/share after some years that it would be horror. Think of NLS and such stuff. There will be more and more needs for dictionaries and we should do it right from the beginning. I don't see this as too much of a problem. Look at /usr/doc, with a subdirectory for every executable. Please foreward this to the FHS team because I'm not able to involve in this theme. I have no contact with the FHS committee, and I don't have time to get involved in it either. There is an FHS mailing list, but I don't know its address. The current draft of the FHS is available at tsx-11.mit.edu:/pub/linux/docs/linux-standards/fsstnd. Bob -- _ |_) _ |_ Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Conflicts between developers and policy
Cc: Debian Developers list debian-devel@lists.debian.org, Debian policy list debian-policy@lists.debian.org From: Manoj Srivastava [EMAIL PROTECTED] Date: 27 Apr 1998 14:47:23 -0500 Lines: 44 Hi, Manoj Srivastava [EMAIL PROTECTED] wrote: Hmm. I think I like the idea of the policy documents being the law, and the technical committee like the justices, who lay down interpretations (which are referred to latter as and adjunct to prior law). Exactly. I think the problem has arisen because 1) the policy documents have not sufficiently delineated the difference between prescriptive (shall, must) provisions and (strong) recommendations (should, must), and 2) because some (many?) developers disagree with some policy provisions and feel that they have had insufficient input in the process of formulating policy. Christian has started the process of rectifying the first item. I believe the remedy for the second point is _not_ to make policy some vague advisory document. I believe the remedy is to establish a more formal policy making process. It would probably be necessary to provide for some type of super-majority to establish prescriptive policy provisions, with, perhaps less support required for suggestive provisions. In some cases it seems that some developers have failed to read the lists for some lengthy period of time, then found that policy provisions had been adopted that they find objectionable. A formal policy making process should provide for a process to change it when the developer community agrees it is desirable. Bob -- _ |_) _ |_ Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Proposed Constitution
I suggest that Section B. Use of language and typography be amended to include a statement similar to Where the context permits, the masculine shall include the feminine, and the singular shall include the plural. Then all of the clumsy constructions using plural pronouns (they, their) to refer to singular entities (Leader, Secretary, etc.) should be changed to use singular masculine pronouns (him, his). Bob -- _ |_) _ |_ Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Directory for dictionary databases
In earlier discussions, it was agreed that the proper location
for dictionary databases under the FHS would be
/usr/share/dict/pkgname.
Subsequently, I have obtained a copy of the FHS, and have
discussed this subject with the upstream author of the dictd package.
An abbreviated extract from the FHS follows is appended to this
message.
It appears that the FHS considers the /usr/share/dict directory
to be for word lists, such as those used for spell checkers, not for
dictionaries in the wider sense.
Rik Faith [EMAIL PROTECTED], the author of dictd, says:
I argue that dictd is an application which stores read only information in
a proprietary[1] format which is not easily used by other applications, and,
as such, the data should be stored in the top level directory:
/usr/share/dictd
After reviewing the FHS, I agree with Rik, and will build the
dictionary packages that I expect to upload tomorrow to install in
/usr/share/dictd.
I suggest that you consider /usr/share/wordnet for your packages.
Bob
[1] This does not mean proprietary in the non-free sense. Rik means
unique to the dictd package.
--
_
|_) _ |_ Robert D. Hilliard[EMAIL PROTECTED]
|_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9
Abbreviated extract from the
Filesystem Hierarchy Standard -- Version 2.0
4.8 /usr/share : Architecture-independent data
/usr/share -- Architecture-independent data
|
+-dict Word lists
. . . . .
Any program or package which contains or requires data that doesn't need
to be modified should store that data in /usr/share (or
/usr/local/share, if installed locally). It is recommended that a
subdirectory be used in /usr/share for this purpose.
. . . . .
4.8.1 /usr/share/dict : Word lists
Recommended files for /usr/share/dict:
{ words }
Traditionally this directory contains only the English words file, which
is used by look(1) and various spelling programs.
. . . . .
Word lists for other languages may be added using the English name for
that language, e.g., /usr/share/dict/french
. . . . .
Other word lists, such as the web2 dictionary should be included here,
if present.
BEGIN RATIONALE
The reason that only word lists are located here is that they are the
only files common to all spell checkers.
END RATIONALE
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: wu-ftpd important bug(s)
More formal definitions:
From Jargon File (4.0.0/24 July 1996) [jargon]:
deprecated /adj./ Said of a program or feature that is
considered obsolescent and in the process of being phased out,
usually in favor of a specified replacement. Deprecated features
can, unfortunately, linger on for many years. This term appears
with distressing frequency in standards documents when the
committees writing the documents realize that large amounts of
extant (and presumably happily working) code depend on the
feature(s) that have passed out of favor. See also {dusty
deck}.
From WordNet (r) 1.6 [wn]:
depreciate
v 1: belittle; The teacher should not deprecate his student's
efforts [syn: {deprecate}]
2: lower the value of something; The Fed depreciated the
dollar once again [ant: {appreciate}]
3: lose in value; The dollar depreciated again [syn:
{undervalue},
{devaluate}, {devalue}] [ant: {appreciate}]
Bob
--
_
|_) _ |_ Robert D. Hilliard[EMAIL PROTECTED]
|_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: gpm and time after hamm upgrade
Corey Miller [EMAIL PROTECTED] wrote: After upgrading to hamm, I have experienced the two following problems. First, gpm no longer seems to work with my mouse. I have a PS/2 M$ Intellimouse, which used to work fine as type ps2. I tried that setup, under which it only moves the cursor erratically and seems to randomly select text. I tried setting the mouse to type ms3, but that produced nothing at all. I have tried setting the mouse as /dev/psaux and /dev/mouse, and have tried closing x windows completely before starting gpm, but nothing seems to help. I am using gpm 1.13-4. The other problem is that, whenever I reboot the machine, it sets the clock back about four hours, but it keeps the timezone as EDT. My timezone is set as America/Detroit.I am using timezones 2.0.7pre3-1. I can't offer any help on the mouse problem. It sounds like your system thinks the hardware clock is set to GMT, but it is really set to local zone time. Check /etc/default/rcS for the correct setting of the GMT variable: | # Set GMT=-u if your system clock is set to GMT, and GMT= if not. | GMT= Bob -- _ |_) _ |_ Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Upgrading Debian 1.3.1r6 to frozen
Hi, Did you really mean 18 or is that a typo for 19? Is it going to hamm or slink? It seems to me that emacs19 should be in 2.0, but the release policy would seem to require it to go in slink. Bob Manoj Srivastava [EMAIL PROTECTED] wrote: emacs18 is also present in Incoming now, and has the same problem with elib (I locally hacked the Makefile to make it work). -- _ |_) _ |_ Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Dictionary directory
When we discussed directory locations several weeks ago, I said I would wait for some policy statements about the FHS. After looking at how much is already in /usr/share, I have changed my mind and now agree with you. I am almost finished with my dictionary packages, and have built them to go into /usr/share/dict. Bob -- _ |_) _ |_ Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Wordnet Package: (Was Re: Dictionary directory)
Hi, DISCLAIMER: I am a new developer also, and my advice may not be very good. Also I am building my packages by hand, and have never looked at any of the helper scripts, so I can't address how to make debstd put the files where you want them. If I understand you correctly, you want to keep the original source as one .orig.tar.gz, but make three binary packages, separated as the earlier wordnet packages did. The obvious solution would be to make one package, but you may have good reasons for wanting to make them separate. When you say Wordnet comes in different directories: dict/ man/ paper/ src/ do you mean that the source unpacks into those three directories? Does the upstream Makefile have separate targets to make in all four directories, and does it have separate install targets for each directory? To make multiple binary packages, you have to branch the debian tree into debian/tmp, debian/tmp-2, debian/tmp-3, etc. (You could make them debian/tmp, debian/tmp-base and debian/tmp-doc if you like mnemonic names). I am aware of two techniques for getting the build files into the proper debian/tmp* tree. One is to let the Makefile build and install into debian/tmp, them move each file from the debian/tmp tree to the appropriate debian/tmp-? tree. This is most useful when only a few files need be moved. The other is to manipulate variables in a $(MAKE) install statement in the rules file. This can be done by hacking the variable assignments in the Makefile, or by defining variables in the rules file, then $(MAKE) install varname=$(VARNAME) where varname is the variable used in the Makefile install target and VARNAME is the variable defined in the rules file. In this case, depending on how the Makefile is set up, you may have to hack the Makefile to use var1, var2, etc., and define VAR1, VAR2, etc. in the rules file. Depending on how the upstream package is set up, you may have to do this in the Makefiles in each of the subdirectories, with different variables defined. Any modifications you make should be in Makefile.in, not the Makefile itself, so they will be preserved when the configure target is run. Any such Makefile hacks should be documented in your changelog file. I have one package that produces two .debs from one source, and I am now working on one that will produce four .debs. Later this evening I will send you copies of the rules file and Makefile for these to illustrate what I am talking about. I hope this helps. Bob -- _ |_) _ |_ Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: build: no utmp entry available
Hi, You wrote: PS: Should I post such kind of questions to debian-mentors? I'm afraid an overflow of my mailbox if I subscribe more and more mailing lists. debian-mentors is relatively low volume, and will likely produce better responses to new maintainer type questions than debian-devel. Bob -- _ |_) _ |_ Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Upgrading Debian 1.3.1r6 to frozen
Hi, Thanks and bravo! I'm getting tired of fighting with dselect, which insists on replacing my emacs 19.34-13 with emacs20. Bob Hi, I meant emacs19, and I think it is felt to be a bug fix release, (not working with the other debian emacsen setup is a pretty major bug) so it shall be in hamm (I think the release manager has already blessed this). -- _ |_) _ |_ Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
New install.txt
Sorry I'm late in getting back to you with comments on your new version of install.txt. I think this is a big improvement over previous versions. A few minor points to consider: Under Information You'll Need, you should tell the reader that he doesn't need the network information for a dialup ppp connection, so he doesn't start looking for it before he comes to Configure the Network. (I don't mean that you should take it out of the latter section.) This is important information, and I have always been troubled that it hasn't been available in the past. Under Boot Device Selection should you mention the possibility of booting from a CD. (This is covered later under specific installation directions.) Under Installing from floppies, in the Base Disks section HREF=base12-1.bin looks like a misplaced HTML tag. The last sentence under Configure the Network says has a spurious B. (On a Debian system, daemons are started by scripts B in /etc/init.d .) ^ Under Setting up PPP you advise reading .gz files with zless. IIRC, less is not on the base disks, but more and zmore are available. Also in this section you advise the user to edit some ppp config files. For the benefit of true newbies, you should mention what editor is available (ae, I think), and how to invoke it. Setting up PPP is a badly needed addition and should help to reduce the traffic on debian-user. (Maybe I'm overly optimistic in assuming enough people will read it.) However, I still wish the pppconfig package were included in the base disks. Under Floppy-disk Reliability you say: If you are having the installation stall at a particular floppy, the first thing you should do is re-download the floppy disk image and write it to a different floppy. I believe the user should be advised to attempt rebooting multiple times before making a new download or using a new floppy. There has always been too much emphasis on bad disks and not enough on the random nature of these errors. During the bo testing period, I made one set of installation disks from brand new virgin disks, and one set from recycled AOL disks (I still get at least one a month in the mail). I made in excess of 20 installations from each set. I recorded the number of dots showing in the installation message to get a rough idea of where in the progress failures occurred. I found that the failures were totally random, and that the recycled disks performed slightly better than the new ones (probably not statistically significant, however). In one test, I had five or six successive failures with one set, followed by six or seven successive successes. Therefore, I am convinced that downloading a new image and making new disks on the first failure is a waste of time and effort. Bob -- _ |_) _ |_ Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
dictd and wordnet
Hi, This is in response to your message of Wed, 8 Apr 1998. I apologize for taking so long to get back to you. As I said before, I am packaging dictd, containing the client server software developed by the DICT Group. There will be a number of separate packages containing the dictionary databases used by the server. One of these is the WordNet 1.6 database. The dictd server is queried with a word, and returns all definitions of that word found in the dictionaries available to it. The most important of these is the 1913 Webster's Unabridged Dictionary, which provides very lengthy definitions, illustrated by quotations from literature. Since the 1913 Webster is out of date (but also out of copyright), it is supplemented by WordNet. This provides some redundancy, but is very comprehensive. The dictd server does not use the special lexical/syntactical organization of WordNet - it simply uses it as an alphabetized list of words and definitions. None of the WordNet software or documentation is included in the dictd package of wordnet. The dict versions of the databases utilize a special .dz file format, which is produced by the dictzip program. This is a compressed format that permits searching by decompressing only relatively small portions of a large file. As far as I can see, the WordNet software would not work with the database as formatted by dictd, and dictd would not work with the WordNet database as distributed. Therefore there would not be any direct benefit to have the two packages maintained by the same person. However, I think that most people who would use one would want to install the other. I currently use dict regularly, and will certainly install the wordnet package on my machine. I had been thinking about taking over the wordnet packages, but you got there first, and I won't argue about it. If you change your mind about them, let me know. We must coordinate the location and name of the WordNet database file(s). The dictd program installs them in /usr/lib/dict/wn.dict.dz and /usr/lib/dict/wn.index. I doubt if that will conflict with the WordNet names and locations. I plan to name the package containing the WordNet database dict-wn, so there shouldn't be any further namespace conflicts. I have completed my packages dictd and dict, but will not release them until I have the database packages ready. The 1913 Webster is held up because of a copyright problem, so I don't think I will be able to release any of these packages before the end of this month. Bob -- _ |_) _ |_ Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dictd and wordnet
Hi, You wrote: I'm in the process of becomming a Debian maintainer. Unfortunately this process isn't finished since two weeks (may be it is delayed because of the efforts in the upcomming hamm release). I would like to maintain wordnet than. But may be I would need your help because it is my first serious package (I don't consider xteddy to be serious but only for the sake of learning maintaining a package). I'm also a new maintainer, and dictd is my first package, so it's doubtful that I could give you much help, but I'll be glad to try if you have problems. You should subscribe to debian-mentors, if you haven't already. A number of very experienced developers read that list and are very quick to respond with helpful answers. Would you think that /usr/lib/dict is an appropriate directory for the Wordnet database (the filenames didn't conflict!). The old WordNet packages used usr/lib/wordnet/dict/. I believe either /usr/lib/dict/ or /usr/lib/dict/wordnet/ (since wordnet installs about 25 files, it could justify its own subdirectory) would be appropriate. As far as I can see, all three of these choices would conform to the FSSTND. When we move to the FHS, I believe they would go into /usr/share. Regards, Bob -- _ |_) _ |_ Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: where can i get debhelper and lintian
Martin Schulze [EMAIL PROTECTED] wrote: They're part of the distribution - hamm. The newest lintian is in the incoming since yesterday - and installed on master+va. IIRC, Christian's message yesterday said the newest lintian was in slink, not hamm. I downloaded it from slink on ftp.debian.org yesterday. Bob -- _ |_) _ |_ Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dictd and wordnet
Jean Pierre LeJacq [EMAIL PROTECTED] wrote: Actually, /usr/share/dict. Shouldn't new package be constructed from the start to use FHS? IIRC, it is intended to implement the FHS with symlinks initially. Until a definite announcement is made regarding the policy for implementing the FHS, I expect to continue following the FSSTND. What format are these files in? Are they ASCII? The reason I ask is that I'm the maintainer of the cracklib package that uses lists of words to prevent the selection of easily guessed passwords. If the wordnet database is in a suitable format, it may make an excellect source or words for cracklib. The wordnet database is ASCII. The wordnet packages have been orphaned, but you can download the wordnetbase_1.5-1 sources from debian/project/orphaned/ on the mirrors. The dictionary databases for the dict program, which I am packaging, are compressed in .dz format. This is close enough to .gz that zless can read it. The sources are ASCII after extracting from the tarball. They may be obtained from ftp.cs.unc.edu/pub/users/faith/dict or ftp.dict.org/pub/dict. Bob -- _ |_) _ |_ Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dictd and wordnet
Hi, The old WordNet packages used usr/lib/wordnet/dict/. I believe This seemed me a bad choice and so I wanted to change it. I agree. It seems undesirable to create a directory with nothing in it but a subdirectory, if there is no expectation of adding more files or directories to it. either /usr/lib/dict/ or /usr/lib/dict/wordnet/ (since wordnet installs The last choice /usr/lib/dict/wordnet is possibly the best one in my opinion. Agreed. Hmm, so we should think about using /usr/share from the beginning because hamm is frozen and will not contain wordnet ( :-( ) and 2.1 will move to FHS. That would mean that the wordnet dictionaries should go into /usr/share/dict/wordnet right? I think so. However I haven't heard any policy statements about how to implement the FHS, so I don't know if its appropriate to start doing this now. Maybe someone more knowledgeable will comment on this. Bob -- _ |_) _ |_ Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Dictionary Packages
David Frey [EMAIL PROTECTED] writes: Personally I'd prefer to have additional packages dictd-web1913, dictd-foldoc, dictd-... (depending on dictd), That's exactly what I had in mind. Sorry if my message left the wrong impression. I envisage four source packages and seven or eight binary packages. Even split up, some of the binary packages are quite large, and the total space in the archive and on the CD is the same. so that I could omit the bible-related stuff on my computer and to have a better granularity. Exactly why the split is necessary. I find the bible-related stuff quite useful, not for religious reasons, but as a literary reference. Bob -- _ |_) _ |_ Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Dictionary Packages
I have just packaged dictd, containing client/server software for accessing dictionaries. To do anything useful, the server must have dictionaries and indices in a suitable format. There are eight dictionaries available from the same site that provides the source for the client/server software. These dictionaries total about 32 mb in compressed form. Two of them, which amount to about 24 mb, are essential for a satisfactory server, but it would be highly desirable to have all installed. Is there any policy regarding large text packages? I can not find anything on this subject in the Policy Manual, but I remember that Ian Jackson has expressed his disapproval of large text packages that are not documentation. One person has suggested to me that introducing such bloat into the distribution would be undesirable. I would like to package these eight dictionaries to accompany dictd, but if there is a policy against such large text packages, I could make installer packages to format and install the tarballs that are available for anonymous ftp from the Dict Group's site. The use of installer packages would reduce the size of the archive by about 60 mb, including source, but it would penalize those users who have slow or no net access, or who exorbitant telephone and Internet access rates. The largest, and most important, of these dictionaries has a copyright that is not DFSG compliant. I have been corresponding with the author, however, and expect to have a version that is DFSG compliant within a few weeks. I would like comments from the developers about the desirability of packaging these dictionaries. Is this a subject that should be raised on policy? Bob -- _ |_) _ |_ Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Questions for maintaining several packages
Andreas Tille [EMAIL PROTECTED] wrote: 3) A free English dictionary (www.dict.org). I found a hint on http://www.debian.org/doc/prospective-packages.html that such a dictionary exists and is desired to be included into Debian. Is there any effort on this? I would think about maintaining this package. I have been working on this, and expect to release this package soon. (Actually, it is two binary packages from one source.) wordnet (which you mentioned in your message) is one of the 7 dictionary databases made available by the DICT group in a format suitable for use by the dictd client/server software. I have downloaded the wordnet source package from project/orphaned, but haven't had a chance to look at it. I don't know if that package includes any more functionality than the dict package. Bob -- _ |_) _ |_ Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9 LocalWords: EB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
