**On 30 Jul, In article Unanswered problem reports by maintainer and package,
** OBDO ([EMAIL PROTECTED]) writes:
OBDOThe following problem reports have not yet been marked as `taken up' by a
OBDOmessage to [EMAIL PROTECTED] or or `forwarded' by a
OBDOmessage to [EMAIL PROTECTED]
OBDO
Package: kbd
Version: 0.91-3
I wondered why the 'loadkeys' program didn't work as expected on m68k,
and then I found a little bug in src/getfd.c: It determines the keyboard
type via an ioctl (KDGKBTYPE) which returns a char on the kernel side, but
is put into a 'long' variable. This just
I took the freedom to make gopher bug free.
-BEGIN PGP SIGNED MESSAGE-
Date: 01 Aug 96 10:03 UT
Format: 1.6
Distribution: unstable
Urgency: Low
Maintainer: Ted Hajek [EMAIL PROTECTED]
Source: gopher
Version: 2.1.1-3
Binary: gopher-client gopherd
Architecture: i386 source
Description:
Well, it's been a while, so lets add:
imap-client and imap-server
to the virtual package names list.
On another note, is there an editor virtual package? Is there any interest
in adding one? It could be valuable to add Provides: editor to ae (and
others as well).
Thanks,
Dwarf
On Thu, 1 Aug 1996, Ian Jackson wrote:
Should we move the copyright file (and the examples directory) into
the per-package directory in /usr/doc ?
I don't think we should move the copyright file. Most people don't
ever need to look at them, so it's simpler if they're out of the way.
We
Christian Hudon writes (Re: Bug#3795: ae should not be essential):
Isn't it that some of the packages that look at EDITOR fall back to ae if
there are problems with EDITOR?
vipw and vigr do this. They're in passwd which is essential, but won't
be as soon as I upload a new version.
Guy
It's nice to have all these files in the same directory, but people
are starting to do things like having /usr/doc/foo/REAMDE be a link to
/usr/doc/copyright/foo or vice versa, and splitting the documentation
for a package up across several directories doesn't seem to work very
well.
This
-BEGIN PGP SIGNED MESSAGE-
Date: 31 Jul 96 09:22 UT
Format: 1.6
Distribution: unstable stable
Urgency: Low
Maintainer: Michael Meskes [EMAIL PROTECTED]
Source: lyx
Version: 0.10.0-1
Binary: lyx
Architecture: i386 source
Description:
lyx: High Level Word Processeor (BETA version)
Erick Branderhorst writes (use of /usr/share):
Perhaps this is a very sensitive subject but shouldn't architecture
independent things like man pages, info manuals, tex latex styles
and a lot of other things being put under a subdir of /usr/share?
The FSSTND people haven't really settled
Mr Stuart Lamble writes:
As of (at the latest) 2.0.0, /usr/include/scsi should be a symbolic link
to /usr/src/linux/include/scsi. Given that libc5 includes the kernel
I'll hopefully get time to fix this next week.
David
--
David EngelOptical Data Systems, Inc.
[EMAIL
Thanks for forwarding this note by Jim Meyerding. I like his ignoring of
/etc/DIR_COLORS, I always found that filename rather ugly and kept my own
file /usr/local/etc/colour-ls.rc for these colour settings.
IMHO, two things remain:
- the fileutils maintainer should patch dircolors so
Could you provide a reference to these benchmarks, and the compiler settings
they used? Or better yet, even run them? I don't really use fortran myself,
but link some of my C++ code with Fortran libraries that other folks have
done. But I could do with a speedup of factor 2 ...
see the
Ian Jackson wrote:
We only have room for one `extra' scripting language, besides the
usual sh, awk, sed, c, on the base disks.
Perl is widely known. It can solve most problems. There are problems
for which it is difficult to get it to work, but these don't often
occur at installation
13 matches
Mail list logo
