Bug#3323: MakeTeXPK mis-invokes ps2pk
package: mflib
Version: 1.0-5
Maintainer: Nils Rennebarth [EMAIL PROTECTED]
possibly also:
Package: xdvik
Version: 18f-5
The remaining possibly related items are:
ii dvipsk 5.58f-5TeX DVI-driver for Postscript
ii ps2pk 1.4-4 Create pk fonts from type1 fonts
ii psnfss 5.2-1 Support for Postscript fonts with LaTeX
ii texpsfnt1.0-1 Virtual fonts and TFM's to use Postscript fo
ii latex 2e-4 Write structured documents with TeX
ii latex2e-doc 1.6-0 LaTeX2e documentation in info format
ii latex2rtf 1.1-3 LaTeX text to RTF format translator.
ii texbin 3.1415-5 TeX - The typesetting system
ii texlib 1.0-4 Auxiliary Files to run TeX
ii mfbasfnt1.0-3 TeX's default fonts.
ii mfbin 2.71-4 Metafont - TeX's font engine
ii mflib 1.0-5 Auxiliary files to run Metafont
ii mfnfss 2.1g-1 Use additional Metafont fonts with LaTeX
xdvi runs
MakeTeXPK ptmb8r 432 300 'magstep(2.0)' deskjet
which ends up running
ps2pk -X432 -e8r.enc -a ptmb8r.432pk
which gives a usage message and fails, because -a should be followed
by an AFMname. Dropping the -a causes ps2pk to complain that the name
couldn't be found.
The first iteration of errors from xdvi looks like this:
% xdvi autopaper
kpathsea: Running MakeTeXPK ptmb8r 432 300 magstep\(2.0\) deskjet
Running MakeTeXPK ptmb8r 432 300 magstep(2.0) deskjet
mv: ptmb8r.432pk: No such file or directory
/usr/bin/MakeTeXPK: Could not mv ptmb8r.432pk
/var/spool/texmf/fonts/pk/ps2pk/pktmp.6552.
mv: pktmp.6552: No such file or directory
chmod: ptmb8r.432pk: No such file or directory
kpathsea: Appending font creation commands to missfont.log.
xdvi: Can't find font ptmb8r; using cmr10 instead at 432 dpi.
A full run of the document produces:
% cat missfont.log
MakeTeXPK ptmb8r 432 300 magstep\(2.0\) deskjet
MakeTeXPK ptmr8r 360 300 magstep\(1.0\) deskjet
MakeTeXPK ptmri8r 360 300 magstep\(1.0\) deskjet
MakeTeXPK pcrr8r 270 300 0+270/300 deskjet
MakeTeXPK ptmb8r 360 300 magstep\(1.0\) deskjet
MakeTeXPK ptmr8r 300 300 1+0/300 deskjet
MakeTeXPK pcrr8r 300 300 1+0/300 deskjet
The style in question is the usenix-2e style, most of which is:
[EMAIL PROTECTED] twocolumn.sty\fi
\usepackage{times}
plus some hacking for section and paper titles; I'll append that in
case it might help.
_Mark_ [EMAIL PROTECTED]
Cygnus Support, Eastern USA
% usenix-2e.sty - to be used with latex2e (the new one) for USENIX.
% To use this style file, do this:
%
%\documentclass[twocolumn]{article}
%\usepackage{usenix-2e}
% and put {\rm } around the author names.
%
% $Id: usenix-2e.sty,v 1.1 1996/05/29 18:56:03 jtk Exp $
%
% The following definitions are modifications of standard article.sty
% definitions, arranged to do a better job of matching the USENIX
% guidelines.
% It will automatically select two-column mode and the Times-Roman
% font.
%
% USENIX papers are two-column.
% Times-Roman font is nice if you can get it (requires NFSS,
% which is in latex2e.
[EMAIL PROTECTED] twocolumn.sty\fi
\usepackage{times}
%
% USENIX wants margins of: 7/8 side, 1 bottom, and 3/4 top.
% 0.25 gutter between columns.
% Gives active areas of 6.75 x 9.25
%
\setlength{\textheight}{9.25in}
\setlength{\columnsep}{0.25in}
\setlength{\textwidth}{6.75in}
%\setlength{\footheight}{0.0in}
\setlength{\topmargin}{-0.25in}
\setlength{\headheight}{0.0in}
\setlength{\headsep}{0.0in}
\setlength{\evensidemargin}{-0.125in}
\setlength{\oddsidemargin}{-0.125in}
%
% Usenix wants no page numbers for submitted papers, so that they can
% number them themselves.
%
\pagestyle{empty}
%
% Usenix titles are in 14-point bold type, with no date, and with no
% change in the empty page headers. The whol author section is 12 point
% italic--- you must use {\rm } around the actual author names to get
% them in roman.
%
\def\maketitle{\par
\begingroup
\renewcommand\thefootnote{\fnsymbol{footnote}}%
[EMAIL PROTECTED] [EMAIL PROTECTED]@[EMAIL PROTECTED]
[EMAIL PROTECTED] 1em\noindent
\hbox [EMAIL PROTECTED]@thefnmark}$}##1}%
[EMAIL PROTECTED]
[EMAIL PROTECTED]
\else \newpage
[EMAIL PROTECTED]@
[EMAIL PROTECTED] [EMAIL PROTECTED]
\endgroup
\setcounter{footnote}{0}%
\let\maketitle\relax
[EMAIL PROTECTED]
[EMAIL PROTECTED]@[EMAIL PROTECTED]
[EMAIL PROTECTED]
\vbox to 2.5in{
\vspace*{\fill}
\vskip 2em
\begin{center}%
{\Large\bf [EMAIL PROTECTED] \par}%
\vskip 0.375in minus 0.300in
{\large\it
\lineskip .5em
[EMAIL PROTECTED]
\end{tabular}\par}%
\end{center}%
\par
\vspace*{\fill}
% \vskip 1.5em
}
}
%
% The abstract is preceded by a 12-pt bold centered heading
\def\abstract{\begin{center}%
{\large\bf [EMAIL PROTECTED]
\end{center}}
\def\endabstract{}
%
% Main
Re: 1.2 source archive and packaging issues
I also think that's important. The source packages should be very simple, and the source unpacker/packer should be written in a scripting language. tar xzf source-version.tar.gz mv source.version source.version.orig tar xzf source-version.tar.gz cd source.version zcat ../diff-version-revision.diff.gz | patch the above lines aren't very difficult but we need to continue with a few checks IMHO: dpkg --status various packages needed for building this package should be installed ok From what I've gathered, the rpm format for sources is basically lines of text giving control information, followed by a cpio of all the gzipped tars. The control field gives commands to do things like unpack, build, etc. Because we already mandate commands for debian.rules, such complexity is not needed. This program (dsource?) would know that it just needs to run debian.rules build to build, debian.rules dist for a distribution, etc. The only information in the control field is how to unpack. Not only how to unpack, but also a possibility to download the original sources (so an URL to the original sources at the original site should be provided). The copyright field which comes with rpm might be usefull too, in the debian source handling approach. We might construct a automatic /usr/doc/copyright/package file by using this copyright field, the maintainer information, the url to the original sources, the organization where the package comes from, the package name the revision name, the changes made for this revision from debian.Changelog and the contents of debian.README (which would contain other info than it does right now, only the copyright info from the original sources). All this can be translated into some machine created sentences like: ---/usr/doc/copyright/package This is the Debian Linux prepackaged version of the organization package distribution. This package package-version-revision was put together by maintainer, from the organization sources, which were obtained from source-url. The changes for revision revision are listed below: revision changes The debian specific changes are copyrighted by maintainer and put under the gpl (see /usr/doc/copyright/GPL). The original sources from organization/author are put under the copyright license. contents debian.README ---/usr/doc/copyright/package Additionally we need the possibility to use more than one source (tar.gz) file. Example is web2c and kpathsea and those big things. So we need more than one source field and related debian diff field which specify the patches to be applied at the original sources. Unix: 30 definitions of regular expressions living under one roof D.E. Knuth Erick Branderhorst http://www.iaehv.nl/users/branderh/
Re: 1.2 source archive and packaging issues
'J.H.M.Dassen wrote:'
Bruce wrote:
Also, we should think about source packaging again. We are welcome to take
anything we want from RPM source packaging, if that would help.
RPM has the advantage that it include _pristine_ source (identical
(cmp or md5sum-wise) to the upstream sources, which are patched during
the build process. IMO this is what we should work towards to.
These are a venerable goals. But I like that the Debian source packages
can be untarred by anyone without dpkg and/or rpm installed.
Yes, this is very useful (and would even be more so if the source is
pristine).
And if we
were to force use of dpkg for installing the source code, I'd like more
freedom over which directory/partition the source ends up in than rpm
allows.
Of course.
Anyway those are the two advantages of Debian's current source
packaging that I hope we don't abandon.
There has been some discussion earlier on about pristine source, and
how to debianize it;
you may want to check out the following:
- 1.0 issues: Packaging (esp. source) thread in October 1995:
Start: http://www.debian.org/Lists-Archives/debian-devel-9510/msg00460.html
- Debian for Linux/{non-i386} / source packaging thread in September 1995:
Start: http://www.debian.org/Lists-Archives/debian-devel-9509/msg00159.html
Greetings,
Ray
--
POPULATION EXPLOSION Unique in human experience, an event which happened
yesterday but which everyone swears won't happen until tomorrow.
- The Hipcrime Vocab by Chad C. Mulligan
Re: What should I do about getpgrp?
On 19 Jun 1996 [EMAIL PROTECTED] wrote: I'm working on a package that makes extensive use of getpgrp(pid), but the getpgrp() that comes in libc5 doesn't take an argument (which is not fun if you're managing a number of process groups from a number of distinct sessions). The fifth item in /proc/pid/stat is the pgrp. You could easily write a getpgrp() which makes use of that. See fs/proc/array.c getstat() for more details. Guy
Re: the Search system
Hi Susan, you're keeping me quite busy today :-) I just found the Debian search system on http://www.debian.org/ghindex.html. This seems to me like a big step forward, and am sorry I didn't see it before. Just yesterday I remarked to someone (for whom I had answered a user-question by specifying the appropriate HOWTO) that the HOWTO's desperately needed a search interface. Questions and comments: 1. In the line Files in this directory, what does the word 'this' refer to? The root directory of the web pages directory structure. 2. Would it be possible (i.e., would the motivation/pain ratio exceed 1) to add the HOWTO's to the list of indexed files, Hmmm... I'm extracting /usr/info already... I'll put it on the todo list. and then automate the rebuild of the glimpse index as new packages appear for doc-linux? The glimpse index is rebuilt daily. 3. Going further, would it possible (same as above) to simply add all of /usr/doc and all of /usr/info to the list of indexed files? Hmm... doable... Also http://www.debian.org/cgi-bin/info2www will hopefully work again someday soon. If so, the text above the search engine form could be greatly streamlined. 4. Comment: it would be nice to put the selectable directories in a SELECTOPTION /SELECT grouping, where the default was ALL. It's autogenerated; I don't want to mess with it right now. Greetings, Ray -- POPULATION EXPLOSION Unique in human experience, an event which happened yesterday but which everyone swears won't happen until tomorrow. - The Hipcrime Vocab by Chad C. Mulligan
Bug#3321: libgdbm.so version number...
could you give me more information on this? (I'm the current libgdbm maintainer.) Calling it libgdbm.so.2.0 would really seem like a mistake, since after all, libgdbm itself is only at 1.7.3... but I can probably put in a compatibility link if there's enough evidence for it (namely, programs which need it that aren't debian packages - since those can all be fixed ;-)
What should I do about getpgrp?
I'm working on a package that makes extensive use of getpgrp(pid), but the getpgrp() that comes in libc5 doesn't take an argument (which is not fun if you're managing a number of process groups from a number of distinct sessions). Unfortunately, I can't get libc5's source right now because ftp.debian.org is unavailable, and debian.crosslink.net doesn't mirror the source. Harumph... I don't know the right way here, and I'm impatient. I suppose the right thing to do is file a bug report against libc5, but I was hoping to go further than that. [This is a case where there are so many standards I doubt this is really a bug.] Anyone have any ideas? -- Raul
textutils very big m68k
The textutils package in the Incoming dir on master for the m68k architecture is 1.1 meg big, much bigger than the ?? k under i386. Is this normal or did something went wrong during building, I would like to know because I'm maintaining the thing right now. Can't download it myself, because I'm using a paid line of 14k4, so that would take at least 10 minutes to download the thing. Can someone tell me what happened with this (dpkg --contents text*) Unix: 30 definitions of regular expressions living under one roof D.E. Knuth Erick Branderhorst http://www.iaehv.nl/users/branderh/
New shadow package uploaded
-BEGIN PGP SIGNED MESSAGE- Date: 19 Jun 96 12:28 UT Format: 1.6 Distribution: unstable Urgency: Low Maintainer: Michael Meskes [EMAIL PROTECTED] Source: shadow Version: 960530-1 Binary: shadow Architecture: i386 source Description: shadow: Manage shadow password and group files Changes: New upstream version Files: e79ae7b3cf784746de4f52bb4480b33f 320032 experimental - shadow_960530-1.tar.gz 15728562a5b7a45afd1aca5f76b65bc0 8062 experimental - shadow_960530-1.diff.gz 7424ba0389551c0bcfe7cce56c7874d9 265880 experimental extra shadow_960530-1_i386.deb -BEGIN PGP SIGNATURE- Version: 2.6.2i iQCVAwUBMcfyiCpaNcQEtuj1AQEWfgP/cGlaPszRVlu555FnRIuxHEIhWL/1fFJ2 SrBU+2Wor78uaeyFGMZ485HEeDSfw9mbkEazBEz1vXtTw0zCj56NN7DPF4ODUuoY qwKizh09mxHrjRXIlNT6CTdV+HdroIV0Tpli/mcy7EtMX9FFZrNNsGGWwAJCwb/0 mpQwxt44o0g= =+Sy1 -END PGP SIGNATURE- -- Michael Meskes |_ __ [EMAIL PROTECTED] | / ___// / // / / __ \___ __ [EMAIL PROTECTED] | \__ \/ /_ / // /_/ /_/ / _ \/ ___/ ___/ [EMAIL PROTECTED]| ___/ / __/ /__ __/\__, / __/ / (__ ) Use Debian Linux!| //_/ /_/ //\___/_/ //
Re: What should I do about getpgrp?
[EMAIL PROTECTED] writes: I'm working on a package that makes extensive use of getpgrp(pid), but the getpgrp() that comes in libc5 doesn't take an argument (which is not fun if you're managing a number of process groups from a number of distinct sessions). The manpage indicates that getpgid is what you want. Unfortunately, I can't get libc5's source right now because ftp.debian.org is unavailable, and debian.crosslink.net doesn't mirror the source. Not mirroring the source makes it awfully easy for them to violate the GPL. David -- David EngelOptical Data Systems, Inc. [EMAIL PROTECTED] 1101 E. Arapaho Road (214) 234-6400 Richardson, TX 75081
Re: 1.2 modem devices
This is an old issue for which we have not made a decision and written down as policy. I motion that all serial port modem traffic to be used on /dev/ttyS*. We need the consistency in the serial post lock names. Thanks, Costa Subject: Re: 1.2 modem devices To: [EMAIL PROTECTED] (Bill Mitchell) Date: Tue, 18 Jun 1996 20:06:00 +0200 (MET DST) From: Peter Tobias [EMAIL PROTECTED] Cc: debian-devel@lists.debian.org Bill Mitchell wrote: On Sun, 16 Jun 1996, Peter Tobias wrote: IMHO we should change our comm packages for Debian 1.2 to use /dev/ttyS* instead of /dev/cua*: I'm hardly expert in standard practices in this area, but I'm under the impression that the cua* devices are for dial-out. This may not be definitive, but I note the following in /usr/source/linux/Documentation/devices.txt: The reasons why this should be changed were part of the mail from Theodore Ts'o. The cua devices use a kernel based locking mechanism which can't be used in all situations. For example I have to use the ttyS* devices for mgetty/dip/minicom (dip and minicom won't work with the cua* devices). But that is much better explained in the mail from Theodore Ts'o. Thanks, Peter -- Peter TobiasEMail: Fachhochschule Ostfriesland [EMAIL PROTECTED] Fachbereich Elektrotechnik und Informatik [EMAIL PROTECTED] Constantiaplatz 4, 26723 Emden, Germany [EMAIL PROTECTED]
Bug#3325: /usr/include/bsd/signal.h:7: No include path in which to find signal.h
Package: libc5-dev
Version: 5.2.18-6
# cat test.c
#include bsd/signal.h
main() {}
# make test
cc test.c -o test
In file included from test.c:1:
/usr/include/bsd/signal.h:7: No include path in which to find signal.h
make: *** [test] Error 1
--
Raul
Re: 1.2 source archive and packaging issues
On Wed, 19 Jun 1996, Chris Fearnley wrote: But I like that the Debian source packages can be untarred by anyone without dpkg and/or rpm installed. I also think that's important. The source packages should be very simple, and the source unpacker/packer should be written in a scripting language. From what I've gathered, the rpm format for sources is basically lines of text giving control information, followed by a cpio of all the gzipped tars. The control field gives commands to do things like unpack, build, etc. Because we already mandate commands for debian.rules, such complexity is not needed. This program (dsource?) would know that it just needs to run debian.rules build to build, debian.rules dist for a distribution, etc. The only information in the control field is how to unpack. Guy
Re: Need help creating a .deb package
On Wed, 19 Jun 1996 [EMAIL PROTECTED] wrote: Last night I read all the documents in the doc/package-developer directory and when I was finished I realised that I still did not know how to create the .deb package. Get the hello package, and emulate it. Guy
Re: textutils very big m68k
On Wed, 19 Jun 1996 [EMAIL PROTECTED] wrote: Can someone tell me what happened with this (dpkg --contents text*) The binaries are all enormous, about 10x what they are on my i386. Maybe it wasn't stripped? Also, the foreign language support at the end? drwxr-xr-x root/root 0 Jun 16 14:25 1996 ./ drwxr-xr-x root/root 0 Jun 16 14:24 1996 usr/ drwxr-xr-x root/root 0 Jun 16 14:22 1996 usr/doc/ drwxr-xr-x root/root 0 Jun 16 14:22 1996 usr/doc/copyright/ -rw-r--r-- root/root 1699 Jun 16 14:22 1996 usr/doc/copyright/textutils drwxr-xr-x root/root 0 Jun 16 14:25 1996 usr/bin/ -rwxr-xr-x root/root 78188 Jun 16 14:23 1996 usr/bin/cksum -rwxr-xr-x root/root 78232 Jun 16 14:23 1996 usr/bin/comm -rwxr-xr-x root/root121128 Jun 16 14:23 1996 usr/bin/csplit -rwxr-xr-x root/root 81572 Jun 16 14:23 1996 usr/bin/cut -rwxr-xr-x root/root 78820 Jun 16 14:23 1996 usr/bin/expand -rwxr-xr-x root/root 82428 Jun 16 14:23 1996 usr/bin/fmt -rwxr-xr-x root/root 79708 Jun 16 14:23 1996 usr/bin/fold -rwxr-xr-x root/root 79248 Jun 16 14:23 1996 usr/bin/head -rwxr-xr-x root/root 85212 Jun 16 14:23 1996 usr/bin/join -rwxr-xr-x root/root116104 Jun 16 14:23 1996 usr/bin/nl -rwxr-xr-x root/root 93684 Jun 16 14:23 1996 usr/bin/od -rwxr-xr-x root/root 79556 Jun 16 14:23 1996 usr/bin/paste -rwxr-xr-x root/root 93828 Jun 16 14:23 1996 usr/bin/pr -rwxr-xr-x root/root102492 Jun 16 14:23 1996 usr/bin/sort -rwxr-xr-x root/root 81444 Jun 16 14:23 1996 usr/bin/split -rwxr-xr-x root/root 77740 Jun 16 14:23 1996 usr/bin/sum -rwxr-xr-x root/root113480 Jun 16 14:23 1996 usr/bin/tac -rwxr-xr-x root/root 86560 Jun 16 14:23 1996 usr/bin/tail -rwxr-xr-x root/root 88540 Jun 16 14:23 1996 usr/bin/tr -rwxr-xr-x root/root 79032 Jun 16 14:23 1996 usr/bin/unexpand -rwxr-xr-x root/root 81492 Jun 16 14:23 1996 usr/bin/uniq -rwxr-xr-x root/root 77756 Jun 16 14:23 1996 usr/bin/wc drwxr-xr-x root/root 0 Jun 16 14:25 1996 usr/info/ -rw-r--r-- root/root 14165 Jun 16 14:24 1996 usr/info/textutils.info-2.gz -rw-r--r-- root/root 8651 Jun 16 14:24 1996 usr/info/textutils.info-3.gz -rw-r--r-- root/root 1556 Jun 16 14:24 1996 usr/info/textutils.info.gz -rw-r--r-- root/root 12877 Jun 16 14:24 1996 usr/info/textutils.info-1.gz drwxr-xr-x root/root 0 Jun 16 14:24 1996 usr/man/ drwxr-xr-x root/root 0 Jun 16 14:25 1996 usr/man/man1/ -rw-r--r-- root/root 1490 Jun 16 14:24 1996 usr/man/man1/fmt.1.gz -rw-r--r-- root/root 951 Jun 16 14:24 1996 usr/man/man1/uniq.1.gz -rw-r--r-- root/root 894 Jun 16 14:24 1996 usr/man/man1/cut.1.gz -rw-r--r-- root/root 1579 Jun 16 14:24 1996 usr/man/man1/nl.1.gz -rw-r--r-- root/root 2168 Jun 16 14:24 1996 usr/man/man1/od.1.gz -rw-r--r-- root/root 694 Jun 16 14:24 1996 usr/man/man1/sum.1.gz -rw-r--r-- root/root 3379 Jun 16 14:24 1996 usr/man/man1/tr.1.gz -rw-r--r-- root/root 574 Jun 16 14:24 1996 usr/man/man1/tac.1.gz -rw-r--r-- root/root 782 Jun 16 14:24 1996 usr/man/man1/expand.1.gz -rw-r--r-- root/root 744 Jun 16 14:24 1996 usr/man/man1/fold.1.gz -rw-r--r-- root/root 561 Jun 16 14:24 1996 usr/man/man1/paste.1.gz -rw-r--r-- root/root 1426 Jun 16 14:24 1996 usr/man/man1/pr.1.gz -rw-r--r-- root/root 1173 Jun 16 14:24 1996 usr/man/man1/tail.1.gz -rw-r--r-- root/root 836 Jun 16 14:24 1996 usr/man/man1/unexpand.1.gz -rw-r--r-- root/root 680 Jun 16 14:24 1996 usr/man/man1/wc.1.gz -rw-r--r-- root/root 696 Jun 16 14:24 1996 usr/man/man1/cat.1.gz -rw-r--r-- root/root 622 Jun 16 14:24 1996 usr/man/man1/cksum.1.gz -rw-r--r-- root/root 513 Jun 16 14:24 1996 usr/man/man1/comm.1.gz -rw-r--r-- root/root 1975 Jun 16 14:24 1996 usr/man/man1/csplit.1.gz -rw-r--r-- root/root 755 Jun 16 14:24 1996 usr/man/man1/head.1.gz -rw-r--r-- root/root 1139 Jun 16 14:24 1996 usr/man/man1/join.1.gz -rw-r--r-- root/root 2972 Jun 16 14:24 1996 usr/man/man1/sort.1.gz -rw-r--r-- root/root 896 Jun 16 14:24 1996 usr/man/man1/split.1.gz drwxr-xr-x root/root 0 Jun 16 14:25 1996 usr/share/ drwxr-xr-x root/root 0 Jun 16 14:25 1996 usr/share/locale/ drwxr-xr-x root/root 0 Jun 16 14:25 1996 usr/share/locale/de/ drwxr-xr-x root/root 0 Jun 16 14:25 1996 usr/share/locale/de/LC_MESSAGES/ -rw-r--r-- root/root 64682 Jun 16 14:25 1996 usr/share/locale/de/LC_MESSAGES/textutils.mo drwxr-xr-x root/root 0 Jun 16 14:25 1996 usr/share/locale/fr/ drwxr-xr-x root/root 0 Jun 16 14:25 1996 usr/share/locale/fr/LC_MESSAGES/ -rw-r--r-- root/root 67962 Jun 16 14:25 1996 usr/share/locale/fr/LC_MESSAGES/textutils.mo drwxr-xr-x root/root 0 Jun 16 14:25 1996 usr/share/locale/ko/ drwxr-xr-x root/root 0 Jun 16 14:25 1996 usr/share/locale/ko/LC_MESSAGES/ -rw-r--r-- root/root 19892 Jun 16 14:25 1996 usr/share/locale/ko/LC_MESSAGES/textutils.mo
taper still r6.2
Is Joe Kirby still with us? I noticed that taper is r6.2. In the meantime we are at r6.7x ? Joe, do you have the time to debianize r6.7? Or - is anybody else willing to do the job? Michael Gaertner [EMAIL PROTECTED] Tel/Fax +49-761-32684
Re: origin and pronunciation of Debian
On Tue, 18 Jun 1996, Susan G. Kleinmann wrote: I'm working on the FAQ now, and believe it or not, these questions come up (at least in the back of people's minds) fairly often. So, is it Deee'-bian (long e) or Deb'-ian (short e), or something else? rumours say its Deb-Ian, from Ian Murdock and his wife Deb. ;-) jjm -- Juergen Menden | Disclaimer: The opinions expressed by me, tel:+49 (89) 289 - 22387 +---+ are (usually) not the opinions e-mail: [EMAIL PROTECTED] | of anyone else on this planet. Hi! I'm a .signature virus! Add me to your .signature and join in the fun!
Bug#3321: libgdbm.so version number...
Mark Eichin writes: could you give me more information on this? (I'm the current libgdbm maintainer.) Calling it libgdbm.so.2.0 would really seem like a mistake, since after all, libgdbm itself is only at 1.7.3... but I can Well, it appears that the shared lib version number of libgdbm was bumped to 2.0 at some point in the development of libc 5.2 ... see http://imageek.york.cuny.edu/pub/sunsite/HJL/release.libc-5.2.3 and http://sunsite.kth.se/Linux/GCC/ChangeLog I can't pretend to understand the reasoning behind this, but both slackware and redhat appear to have gone along with it. If debian doesn't have it, it's effectively going to lose binary compatibility for programs using gdbm that were compiled on slackware or redhat. I guess the affected binaries fall into two groups: (1) precompiled binary distributions of software. An altavista search suggests that some releases of sendmail, NCSA httpd, and kerberos at least are dynamically linked against a libgdbm.so.2.0 (2) stuff compiled by endusers before they moved to debian. I hit category #2 (quite hard, since in my case it was a kerberized /bin/login that wouldn't work!). The problem is worsened by the fact that most people are not likely to realize that the missing 2.0.0 is in fact the 1.7.3 lib they already have; I certainly didn't. So: I guess I'm suggesting an extra symlink just to maintain compatibility with the other major linux distributions. Perhaps it would be worth contacting H. J. Lu to find out the rationale for the version number change. (He's the author of the info in both of the URLs above.) I guess libgdbm was separated from the libc distribution sometime after this version # change, but it would appear that most people haven't dropped the version # back down after the split. Thanks, -Arup
Bug#3326: zegrep missing
Package: gzip
Version: 1.2.4-10
bash$ type zgrep
zgrep is /usr/bin/zgrep
bash$ type zegrep
type: zegrep: not found
bash$ grep grep= /usr/bin/zgrep
*egrep) grep=${EGREP-egrep} ;;
*fgrep) grep=${FGREP-fgrep} ;;
*) grep=${GREP-grep} ;;
grep=egrep
bash$
I think it's reasonable to provide lines for zegrep and zfgrep. No?
--
Raul
Bug#3321: libgdbm.so version number...
[Dan, this is about the correct .so-name for libgdbm; your list has liggdbm.so.1.7.3, whereas the libc5.2 docs, Slackware, Red Hat have libgdbm.so.2.0] if this is truly a bug, can you explain the two URLs I mentioned in the message below? (Already sent to debian-bugs, hence not CC'ed again here...) I believe that the libgdbm version number got bumped 'cos the libc 5.2 folks bumped it. I'm mostly worried that debian's fixing of this is going to be an annoying source of binary incompatibility for some people OK. It looks like this is a synchronization problem with the shared lib list. If H.J. has bumped the version number, we should definitively go along with it. Greetings, Ray Mark Eichin writes: could you give me more information on this? (I'm the current libgdbm maintainer.) Calling it libgdbm.so.2.0 would really seem like a mistake, since after all, libgdbm itself is only at 1.7.3... but I can Well, it appears that the shared lib version number of libgdbm was bumped to 2.0 at some point in the development of libc 5.2 ... see http://imageek.york.cuny.edu/pub/sunsite/HJL/release.libc-5.2.3 and http://sunsite.kth.se/Linux/GCC/ChangeLog I can't pretend to understand the reasoning behind this, but both slackware and redhat appear to have gone along with it. If debian doesn't have it, it's effectively going to lose binary compatibility for programs using gdbm that were compiled on slackware or redhat. I guess the affected binaries fall into two groups: (1) precompiled binary distributions of software. An altavista search suggests that some releases of sendmail, NCSA httpd, and kerberos at least are dynamically linked against a libgdbm.so.2.0 (2) stuff compiled by endusers before they moved to debian. I hit category #2 (quite hard, since in my case it was a kerberized /bin/login that wouldn't work!). The problem is worsened by the fact that most people are not likely to realize that the missing 2.0.0 is in fact the 1.7.3 lib they already have; I certainly didn't. So: I guess I'm suggesting an extra symlink just to maintain compatibility with the other major linux distributions. Perhaps it would be worth contacting H. J. Lu to find out the rationale for the version number change. (He's the author of the info in both of the URLs above.) I guess libgdbm was separated from the libc distribution sometime after this version # change, but it would appear that most people haven't dropped the version # back down after the split. Thanks, -Arup -- POPULATION EXPLOSION Unique in human experience, an event which happened yesterday but which everyone swears won't happen until tomorrow. - The Hipcrime Vocab by Chad C. Mulligan
Re: 1.2 source archive and packaging issues
'J.H.M.Dassen wrote:' Bruce wrote: Also, we should think about source packaging again. We are welcome to take anything we want from RPM source packaging, if that would help. RPM has the advantage that it include _pristine_ source (identical (cmp or md5sum-wise) to the upstream sources, which are patched during the build process. IMO this is what we should work towards to. These are a venerable goals. But I like that the Debian source packages can be untarred by anyone without dpkg and/or rpm installed. And if we were to force use of dpkg for installing the source code, I'd like more freedom over which directory/partition the source ends up in than rpm allows. Anyway those are the two advantages of Debian's current source packaging that I hope we don't abandon. -- Christopher J. Fearnley|Linux/Internet Consulting [EMAIL PROTECTED] |UNIX SIG Leader at PACS http://www.netaxs.com/~cjf |(Philadelphia Area Computer Society) ftp://ftp.netaxs.com/people/cjf|Design Science Revolutionary Dare to be Naive -- Bucky Fuller |Explorer in Universe
the Search system
I just found the Debian search system on http://www.debian.org/ghindex.html. This seems to me like a big step forward, and am sorry I didn't see it before. Just yesterday I remarked to someone (for whom I had answered a user-question by specifying the appropriate HOWTO) that the HOWTO's desperately needed a search interface. Questions and comments: 1. In the line Files in this directory, what does the word 'this' refer to? 2. Would it be possible (i.e., would the motivation/pain ratio exceed 1) to add the HOWTO's to the list of indexed files, and then automate the rebuild of the glimpse index as new packages appear for doc-linux? 3. Going further, would it possible (same as above) to simply add all of /usr/doc and all of /usr/info to the list of indexed files? If so, the text above the search engine form could be greatly streamlined. 4. Comment: it would be nice to put the selectable directories in a SELECTOPTION /SELECT grouping, where the default was ALL. I would have been happy to send this directly to the author of the ghindex.html, but I don't know who that is. It might be useful to add a mailto: at the bottom of the page. Cheers, Susan Kleinmann [EMAIL PROTECTED]
sudo-1.4.3-2
-BEGIN PGP SIGNED MESSAGE- Date: 19 Jun 96 11:51 UT Format: 1.6 Distribution: unstable Urgency: Low Maintainer: Michael Meskes [EMAIL PROTECTED] Source: sudo Version: 1.4.3-2 Binary: sudo Architecture: i386 source Description: sudo: Provides limited super user privileges to specific users. Changes: Applied upstream patch1 Files: 2ed1070a3826ca07a4434395a71877ef 155723 admin - sudo_1.4.3-2.tar.gz da4b1e74d08e6e22b46a5887ea68fcf7 28369 admin - sudo_1.4.3-2.diff.gz c708408deda73dc6acddf5ec2f3f985c 53656 admin standard sudo_1.4.3-2_i386.deb -BEGIN PGP SIGNATURE- Version: 2.6.2i iQCVAwUBMcfp8ipaNcQEtuj1AQGUlQQAr6K5LXX79B2QkFXPd+0JITdX4HSHj3Mn v6Xld2wPbIj5RTqBRoZLZbEBROEDhRYItE4d68hfogDdZYxnDUifzc97fnk3JuZd WJf7DbhIg06L6tZ7ykDKAs5hMPSUjL3x8xe7Gh+Nipr1BkyMsoPb66J7Lp2y+FVg Fn96gnpQxmg= =UzzE -END PGP SIGNATURE- -- Michael Meskes |_ __ [EMAIL PROTECTED] | / ___// / // / / __ \___ __ [EMAIL PROTECTED] | \__ \/ /_ / // /_/ /_/ / _ \/ ___/ ___/ [EMAIL PROTECTED]| ___/ / __/ /__ __/\__, / __/ / (__ ) Use Debian Linux!| //_/ /_/ //\___/_/ //
More uploads
-BEGIN PGP SIGNED MESSAGE- Date: 19 Jun 96 09:57 UT Format: 1.6 Distribution: unstable Urgency: Low Maintainer: Michael Meskes [EMAIL PROTECTED] Source: lshell Version: 2.01-2 Binary: lshell Architecture: i386 source Description: lshell: Enforce limits to protect system integrity. Changes: Fixed postinst Files: 0f11d4968ef0941f6abaa42b42696b9d 8244 admin - lshell_2.01-2.tar.gz aefb8ab1facfcd11028e71ab9d2172fd 5668 admin - lshell_2.01-2.diff.gz e6c4475f203cbf6befe265513e637926 8754 admin optional lshell_2.01-2_i386.deb -BEGIN PGP SIGNATURE- Version: 2.6.2i iQCVAwUBMcfPOSpaNcQEtuj1AQGyYAQAkuXgkepnCRbJL6aeGNzXdGRcJYLJo2jI ieDr3sIIOUkaboupDodX87s2YAOLN/WVhFpE+LqAJtCT2FB9cBB13Ja1+N7TpdEK yG6/bDnXqYU/kbCQHTOfrBgckxgpzuX93dkLNICehLAQy0KSIafoTMTdea3gkFot q2XXJGEi6aA= =I53A -END PGP SIGNATURE- -BEGIN PGP SIGNED MESSAGE- Date: 19 Jun 96 09:54 UT Format: 1.6 Distribution: unstable Urgency: Low Maintainer: Michael Meskes [EMAIL PROTECTED] Source: quota Version: 1.55-1 Binary: quota Architecture: i386 source Description: quota: An implementation of the diskquota system. Changes: New upstream version Files: d4d5e3423fce6f475fef7d8392888a43 42505 admin - quota_1.55-1.tar.gz 38d200b6979868c0349e526dd549bcef 12748 admin - quota_1.55-1.diff.gz f79a94ab7b04ec4c900421453906822f 40986 admin standard quota_1.55-1_i386.deb -BEGIN PGP SIGNATURE- Version: 2.6.2i iQCVAwUBMcfOZypaNcQEtuj1AQHYLQQAy/to6so+505thi8xut3f03Qkxq66UQlG 1KmEiW8OF0dpXWQyjjV2mLLU+nXVF5R2LGPngbpLExqRbZ+CrDpBjxEL+q1FA8t8 PljBkjEG6sE8xfVFG1ncjIg6jq/kdpp51OjDVdmXVCFM45ibn+A1fOoObPrilfyb E+Zp1Pisf7I= =0KSC -END PGP SIGNATURE- Michael -- Michael Meskes |_ __ [EMAIL PROTECTED] | / ___// / // / / __ \___ __ [EMAIL PROTECTED] | \__ \/ /_ / // /_/ /_/ / _ \/ ___/ ___/ [EMAIL PROTECTED]| ___/ / __/ /__ __/\__, / __/ / (__ ) Use Debian Linux!| //_/ /_/ //\___/_/ //
Bug#3318: traceroute doesn't work with 1.2.13
Michael Shields writes: Package: netstd Version: 2.05-1 Debian 1.1 is supposed to work with kernel 1.2.13. But traceroute is broken. Who said that? We are running 2.0.x as _STABLE_ kernel release ... Bruce Perens said a few days ago that you could probably upgrade to 1.1 without 2.0. It's not so much work -- yesterday I upgraded daedalus.crosslink.net to 1.1 while keeping my 1.2 kernel, and as far as I can tell only traceroute broke. I've already sent in patches for that that preserve the new functionality while remaining backwards-compatible. -- Shields, CrossLink.
Bug#3318: traceroute doesn't work with 1.2.13
Michael Shields writes: Package: netstd Version: 2.05-1 Debian 1.1 is supposed to work with kernel 1.2.13. But traceroute is broken. Who said that? We are running 2.0.x as _STABLE_ kernel release ... Dominik
Re: What should I do about getpgrp?
Unfortunately, I can't get libc5's source right now because ftp.debian.org is unavailable, and debian.crosslink.net doesn't mirror the source. This wasn't intentional -- I was mirroring sun10.sep.bnl.gov, which stopped carrying source due to lack of space. I'm moving over to taking it from master directly, and then will carry the full archive (i.e., everything except WebPages and Incoming). -- Shields, CrossLink.
Bug#3318: traceroute doesn't work with 1.2.13
Wouldn't it be easier to do something like I did with BIND -- detect
the protocol not available (ENOPROTOOPT?) and don't use the feature,
instead of calling it an error...
That was my thought. These patches should do it.
--- traceroute-4.4BSD/traceroute.c Sun Jan 28 22:47:27 1996
+++ traceroute.cWed Jun 19 06:36:15 1996
@@ -310,6 +310,9 @@
struct protoent *pe;
struct sockaddr_in from, *to;
int ch, i, on, probe, seq, tos, ttl;
+#ifdef IP_HDRINCL
+ int hdrincl_works = 1;
+#endif
on = 1;
seq = tos = 0;
@@ -454,8 +457,12 @@
#ifdef IP_HDRINCL
if (setsockopt(sndsock, IPPROTO_IP, IP_HDRINCL, (char *)on,
sizeof(on)) 0) {
- perror(traceroute: IP_HDRINCL);
- exit(6);
+ if (errno == ENOPROTOOPT) {
+ hdrincl_works = 0;
+ } else {
+ perror(traceroute: IP_HDRINCL);
+ exit(6);
+ }
}
#endif IP_HDRINCL
if (options SO_DEBUG)
@@ -475,7 +482,7 @@
}
outpacket-ip.ip_src = from.sin_addr;
#ifndef IP_HDRINCL
- if (bind(sndsock, (struct sockaddr *)from, sizeof(from)) 0) {
+ if (hdrincl_works bind(sndsock, (struct sockaddr *)from,
sizeof(from)) 0) {
perror (traceroute: bind:);
exit (1);
}
--
Shields, CrossLink.
Bug#3327: cern-httpd postinst hangs if daemon configured for inetd
Package: cern-httpd Version: 3.0-6 The cern-httpd postinst tries to start the daemon, like this: start-stop-daemon --start --quiet --oknodo --exec /usr/sbin/cern-httpd If the server is configured to run out of inetd, as I have it, this (probably) runs cern-httpd and hangs. If you type an HTTP request into it it works and marks the package configured, as desired. My lightly edited cern-httpd.conf is below. Ian. # This file was automatically generated by the postinstallation script. # # # Sample configuration file for cern_httpd for running it # as a normal HTTP server. # # See: # http://www.w3.org/hypertext/WWW/Daemon/User/Config/Overview.html # # for more information. # # Written by: # Ari Luotonen April 1994 [EMAIL PROTECTED] # # Minimally Hacked for Debian GNU/Linux by: # Ted HajekAprli 1995[EMAIL PROTECTED] # # Set this to point to the directory where you unpacked this # distribution, or wherever you want httpd to have its home # ServerRoot /usr/lib/cern-httpd # # The default port for HTTP is 80; if you are not root you have # to use a port above 1024; good defaults are 8000, 8001, 8080 # # Port 80 # # General setup; on some systems, like HP, nobody is defined so # that setuid() fails; in those cases use a different user id. # UserId nobody GroupId nogroup # # Logging; if you want logging uncomment these lines and specify # locations for your access and error logs # AccessLog /var/log/httpd/access.log ErrorLog/var/log/httpd/error.log LogFormat Common LogTime LocalTime # # User-supported directories under ~/(UserDir) # UserDir public-html # # Scripts; URLs starting with /cgi-bin/ will be understood as # script calls in the directory /your/script/directory # Exec/cgi-bin/* /usr/lib/cern-httpd/cgi-bin/* # # URL translation rules; default location of documents. # Pass/* /home/www/*
Bug#3321: libgdbm.so version number...
Package: libgdbm1 Version: 1.7.3-11 Hi, I believe that the shared library exported by this package (libgdbm.so.1.7.3) is basically the same thing that other linux distributions (slackware and redhat in particular) choose to ship as libgdm.so.2.0.0 ... Perhaps Debian too should do this? In the current state, dynamically linked programs compiled under other distributions look for a libgdbm.so.2 under debian and fail because they can't find it. That is a bug in their distributions. At http://users.ox.ac.uk/~jo95004/liblist.html Daniel Barlow (maintainer of GCC-HOWTO and such) maintains the List of Libraries, which is intended to get .so names consistent accross distributions. It's entry for gdbm is: gdbm Description: The GNU dbm library Author/Maintainer: Keeper of the soname: Christopher Wiles [EMAIL PROTECTED] Source from: ftp://prep.ai.mit.edu/pub/gnu Binaries from: ftp://sunsite.unc.edu/pub/Linux/libs Filename: libgdbm.so.1.7.3 soname: libgdbm.so.1 Building as a shared library: This patch, also included in the binary distribution. Notes: More information: Greetings, Ray -- POPULATION EXPLOSION Unique in human experience, an event which happened yesterday but which everyone swears won't happen until tomorrow. - The Hipcrime Vocab by Chad C. Mulligan
Re: origin and pronunciation of Debian
[ Note: I read this mailing list. There is no need to CC me on replies, unless it is _really_ urgent. I pay for my PPP connections. Thanks. ] Juergen Menden: rumours say its Deb-Ian, from Ian Murdock and his wife Deb. ;-) Is Ian pronounced ee-an or eye-an? My dictionary lists both ways... What does Ian M prefer?
Bug#3325: usr/include/bsd/signal.h:7: No include path in which to find signal.h
[EMAIL PROTECTED] wrote:
Package: libc5-dev
Version: 5.2.18-6
# cat test.c
#include bsd/signal.h
main() {}
# make test
cc test.c -o test
In file included from test.c:1:
/usr/include/bsd/signal.h:7: No include path in which to find signal.h
make: *** [test] Error 1
If you want to use BSD signals you should use #include signal.h
and compile the program with -I/usr/include/bsd.
Thanks,
Peter
--
Peter TobiasEMail:
Fachhochschule Ostfriesland [EMAIL PROTECTED]
Fachbereich Elektrotechnik und Informatik [EMAIL PROTECTED]
Constantiaplatz 4, 26723 Emden, Germany [EMAIL PROTECTED]
Re: 1.2 modem devices
CD Rasmussen wrote: This is an old issue for which we have not made a decision and written down as policy. The decision was to use cua* for minicom/dip etc.. (the decision was made about 2 years ago). I motion that all serial port modem traffic to be used on /dev/ttyS*. We need the consistency in the serial post lock names. There should be no problem if all programs use the ttyS* devices and the /var/lock directory. Thanks, Peter -- Peter TobiasEMail: Fachhochschule Ostfriesland [EMAIL PROTECTED] Fachbereich Elektrotechnik und Informatik [EMAIL PROTECTED] Constantiaplatz 4, 26723 Emden, Germany [EMAIL PROTECTED]
