Yves Arrouye:
> I remember that a long time ago it was said that it was okay to gzip
> manual pages because the manual reader did handle them nicely?
Our man seems to handle them OK. Since there can be tens of megabytes of
manual pages (I have 18 MB), I think compressing them would be a good idea
Date: Tue, 20 Aug 96 08:19 PDT
From: [EMAIL PROTECTED] (Bruce Perens)
Reply-To: Bruce Perens <[EMAIL PROTECTED]>
From: Patrick Weemeeuw <[EMAIL PROTECTED]>
> The big question is: is PAM ready for integration in the distribution?
I agree that it sounds like a better way to do th
Patrick Weemeeuw writes:
> Thinking things over again, and considering that the shadow support
> for Debian is almost finished (as far as I know, only xdm and a few
> small utilities such as vipw have to be adapted for shadow support), I
The actual situation is that we have to make xdm and adduser
-BEGIN PGP SIGNED MESSAGE-
Date: 21 Aug 96 11:30 UT
Format: 1.6
Distribution: unstable
Urgency: Low
Maintainer: Erick Branderhorst <[EMAIL PROTECTED]>
Source: id-utils
Version: 3.2-1
Binary: id-utils
Architecture: i386 source
Description:
id-utils: Fast, high-capacity, identifier data
I did a quick scan through the archive and found at least two (well that is
four) packages in an incorrect location. The way I understand it all
packages including a motif binary (statically or dynamically linked) belong
into contrib since there's no way for me (as normal user) to recompile them.
T
Patrick Weemeeuw writes:
> For general information, see http://www.redhat.com/linux-info/pam/
> and for Linux-PAM: http://gluon.physics.ucla.edu/~morgan/pam/
Got it. Thanks.
> But to answer your question in short: PAM (which stands for pluggable
> authentication modules) is an API that encapsula
Package: xonix
Version: 1.4-3
By default, xonix can't write to its highscore file.
As a remedy, I'd suggest
chgrp games /usr/games/xonix
chmod 2755 /usr/games/xonix
chgrp games /var/lib/games/xonix
chmod 775 /var/lib/games/xonix
--
Thomas Koenig, [EMAIL PROTECTED], [EMAIL PROTECTED]
The joy of
I've just uploaded the first version of the new (almost final) shadow
packages to my ftp site. Please test them as much as possible. They are
under:
ftp://feivel.informatik.rwth-aachen.de/pub/debian.local/binary-i386/shadow-*
I devided shadow into three packages:
1) shadow-passwd which is thought
-BEGIN PGP SIGNED MESSAGE-
Date: 21 Aug 96 07:36 UT
Format: 1.6
Distribution: unstable
Urgency: Low
Maintainer: Michael Meskes <[EMAIL PROTECTED]>
Source: fdutils
Version: 4.3-4
Binary: fdutils
Architecture: i386 source
Description:
fdutils: Floppy utitlities
Changes:
fdutils (4.3-4)
From: Michael Meskes <[EMAIL PROTECTED]>
Date: Tue, 20 Aug 1996 18:25:36 +0200 (MET DST)
[...]
What exactly does it offer that shadow doesn't?
For general information, see http://www.redhat.com/linux-info/pam/
and for Linux-PAM: http://gluon.physics.ucla.edu/~morgan/pam/
But to answe
Patrick Weemeeuw writes:
> I have the feeling that an awful lot of work is being duplicated here.
But then almost the complete work has already been done.
> All of the work being done to support shadow password files, will have
> to be done over again to support PAM. Also, IMHO the PAM framework
From: Dan Stromberg <[EMAIL PROTECTED]>
> 1) Have you switched up to a 28.8kbps modem yet, or at least a 14.4kbps
> modem?
We may be a bit spoiled here in the U.S.
Some people have to buy their net service from a government-mandated
monopoly, and pay by the packet. 28.8 modems are _illegal_ in so
Package: inn
Version: 1.4unoff4-1
deimos:~:[2]# dpkg --purge inn
(Reading database ... 20824 files and directories currently installed.)
Removing inn ...
Trying to stop INN..
Removing crontab for news..
Removing files in /var/log/news and /var/run/innd..
dpkg - warning: while removing inn, directo
I hadn't realized this arch independence stuff would take so much time
when I originally agreed to be the maintainer and I still don't see
the end of the tunnel, so if anyone wants to let me know.
Thanks,
Leland
__ Y_ a_ m_ b_ o_ | The leanest, meanest, fightinest sweet tater on Earth!
oo
I've now implemented the shared library scheme as described earlier.
I don't expect to make any further significant changes to the new
source package format and building scheme. I shall finalise this in a
week unless there are significant complaints. So: please download
these and look at them an
Note: I'm copying this to debian-devel to get feedback on my response
to Philippe's question #3. If you do respond, please include a direct
response to me in addition to the list. I was inadvertantly dropped
from debian-devel three weeks ago and no amount of trying on my or
Bruce's parts has been
The following problem reports have not yet been marked as `taken up' by a
message to [EMAIL PROTECTED] or or `forwarded' by a
message to [EMAIL PROTECTED]
The maintainer listed against each package is derived from the Maintainer
field of the package as found in the development tree; there is an ov
Package: doc-debian
Version: 1.0-3
In /usr/doc/debian/bug-reporting.txt.gz:
HOW TO REPORT A BUG IN DEBIAN
Send mail to [EMAIL PROTECTED], as described below.
However, according to:
http://www.cl.cam.ac.uk/users/iwj10/debian
> Package: libpaper
> Version: 1.0-1
>
> The package contains:
> -r--r--r-- root/root 718 Aug 13 18:04 1996 usr/man/man1/paper.1.gz
>
> 2. Either it should not be compressed (see the guidelines) or we
> should mandate compressed manpages.
I remember that a long time ago it was said that i
> Package: libpaper
> Version: 1.0-1
>
> The package contains /etc/papersize as a dpkg-handled conffile, but
> this file is also modified by many packages' maintainer scripts
> (including those of libpaper).
>
> This is forbidden. See the dpkg programmers' manual.
As I said before, this will b
I've noticed that version 2.0.7 of the kernel packages, i.e.,
kernel-headers, kernel-image, and kernel-source, for the i386 have
been sitting in Incoming for about a month. There are no .changes
files for these packages, which is probably the reason that they have
not been transferred out of the I
Yves Arrouye Email : [EMAIL PROTECTED]
7, avenue Leon Bollee Web : http://www.fdn.fr/~yarrouye/
75013 ParisWork : +33 53 61 09 55
France Home : +33 45 95 64 59
On Tue, 20 Aug 1996, D
**On 19 Aug, In article "Bug#4159: xcoral dies ",
** RTMUE ([EMAIL PROTECTED]) writes:
RTMUE>Christophe Le Bars writes:
RTMUE> >Yes, I have never seen this error message with fvwm...
RTMUE> >I will reassign this bug...
RTMUE>Please don't do this.
Sorry, too late... But, I'll repair this...
R
Package: cron
Version: 3.0pl1-33
Here is what I get:
marin13# dpkg -i cron_3.0pl1-33.deb
(Reading database ... 0 files and directories currently installed.)
Preparing to replace cron (using cron_3.0pl1-33.deb) ...
start-stop-daemon: unable to stat executable `/usr/sbin/cron': No suc
marin66# dpkg -i bind_4.9.3-P1-3.deb
(Reading database ... 22241 files and directories currently installed.)
Preparing to replace bind (using bind_4.9.3-P1-3.deb) ...
start-stop-daemon: unable to stat executable `/usr/sbin/named': No such file or
directory
dpkg: error processing bind_4.9.3-P1-3.d
Package: sendmail
Version: 8.7.5-4
marin38# dpkg -i sendmail_8.7.5-4.deb
(Reading database ... 4 files and directories currently installed.)
Preparing to replace sendmail (using sendmail_8.7.5-4.deb) ...
start-stop-daemon: unable to stat executable `/usr/sbin/sendmail': No such file
or direc
>These problems with the unpacked (preinstalled configured) latex (and
>related) packages has been noticed earlier but was never dealed with.
>Anyone having a mail adress at hand for contacting the latex3 team?
The 'Latex3 Home Page',
http://homepage.cistron.nl/~jlbraams/ltx3/latex3.html,
says th
Apparently, dpkg decided to rename /usr/lib to /usr/lib.dpkg-tmp
and only removed a few files from it. Moving the directory
back again, I got a few errors such as perl being unable to find
libgdbm and libdb.
This appears to conform to warnings such as
dpkg - warning, overriding problem because -
Storing one thing in one place is an excellent goal.
Treating multiple things as tho they were one thing (EG "all printers
use the same paper) can be troublesome.
Ideal: keep the option of an /etc/papersize, but allow a user to
override /etc/papersize if desired, thru ~/papersize or environment
v
Package: dpkg
Version: 1.2.11
In trying to make a Debian package, I managed to create a regular
file in debian-tmp/usr/lib (a wrong flag with install).
When I tried to test-install the package, there were a few warnings,
but dpkg happily overwrote /usr/lib with that particular text file.
I'll eag
-BEGIN PGP SIGNED MESSAGE-
Date: 20 Aug 96 17:28 UT
Format: 1.6
Distribution: unstable
Urgency: Low
Maintainer: joost witteveen <[EMAIL PROTECTED]>
Source: gsfonts
Version: 4.01-2
Binary: gsfonts
Architecture: all source
Description:
gsfonts: Fonts for the ghostscript interpreter
Chang
Mr Stuart Lamble wrote:
> All very nice, but it dodges the major reason for people disliking duplicate
> copies of messages: they pay for their PPP link (or UUCP feed, or whatever).
> Identifying duplicates by their message IDs means that you have to download
> both messages, unless you can do the
Sorry for the long delay. I'm uploading 2.5-5 now which has your m68k
patches, among other things.
Date: 20 Aug 96 16:57 UT
Format: 1.6
Distribution: unstable
Urgency: Low
Maintainer: Guy Maor <[EMAIL PROTECTED]>
Source: util-linux
Version: 2.5-5
Binary: util-linux
Architecture: i386 source
De
Daniel Quinlan writes:
> Use geteuid(2) and/or use a configuration file that says who has
> access. Using permissions alone to dictate who has access to
> *running* the binary is bad, IMHO, and I think the Debian package
> guidelines agree (unless they've been changed). Even worse, it's a
> `4750
On Tue, 20 Aug 1996 09:51:39 CDT David Engel ([EMAIL PROTECTED])
wrote:
> Note: I'm copying this to debian-devel to get feedback on my response
> to Philippe's question #3. If you do respond, please include a direct
> response to me in addition to the list. I was inadvertantly dropped
> from d
35 matches
Mail list logo
