Re: CC's on this mailing list

[Lars Wirzenius]

I wrote earlier:
> Indeed, but it's the principle that matters. Spam isn't costing me
> all that much either, but I still get furious when I get it.

Dirk pointed out that equating a couple of superfluous Cc's from 
debian-devel with spam isn't exactly polite. Sorry, I was writing too
quickly again.

Spam does make furious, extra Cc's from mailing lists don't. They
just annoy me (see signature), and in theory they do cost me a bit.
Not enough to make me worry about it, but enough to write kilobyte after
kilobyte about it.

I do wish that people wouldn't Cc me when I read the mailing list. I feel
that it is good netiquette not to do that.

This may be a mark that we or I don't think there is enough real problems
with Debian. Hm, perhaps the three month release schedule is one: we have
one month left for the next release, and we're just about to make a big
change in source packaging? Perhaps it would be better to wait an extra
month for this occasion only?

-- 
Rural sizes win <[EMAIL PROTECTED]> 
Please don't Cc: me when replying to my message on a mailing list.




pgpsddDgsmBLE.pgp
Description: PGP signature

Bug#4176: mkdosfs has file conflict with dosfstools

[Martin Schulze]

You write:

}Package: mkdosfs, dosfstools
}Version: 0.3b-1, 1.0-1

}Unpacking mkdosfs (from .../misc/mkdosfs_0.3b-1.deb) ...
}...
}dpkg - warning, overriding problem because --force enabled:
} trying to overwrite `/usr/man/man8/mkdosfs.8', which is also in package 
dosfstools

The package mkdosfs is the predecessor of dosfstools.  I have asked
Guy to remove the first one.  It seems that he has more important work
to do.

Regards,

Joey

PS: Guy, would you please remove mkdosfs from the archive and close
this bug.-- 
  / Martin Schulze  *  [EMAIL PROTECTED]  *  26129 Oldenburg /
 /  No question is too silly to ask, /
/but, of course, some are too silly to answer  -- perl book /

pixmap_2.6pl1-5 uploaded

[joost witteveen]

-BEGIN PGP SIGNED MESSAGE-

Date: 16 Aug 96 19:51 UT
Format: 1.6
Distribution: unstable
Urgency: Low
Maintainer: joost witteveen <[EMAIL PROTECTED]>
Source: pixmap
Version: 2.6pl1-5
Binary:  pixmap
Architecture:  i386 source
Description: 
 pixmap: A pixmap editor.
Changes:
 - Upstream maintainer now provided me with a propper patch for
   bug 4169, included in this version.
 - Bug 4100 may be due to a bug in XFree 3.1.2. My previous
   patch was a very buggy workaround for this, and my current
   patch for bug 4100 is a somewhat less (though still not good)
   workaround for this.
Files:
 627ba0d737d2ab206dfef06fd59a2261  228727  x11  -  pixmap_2.6pl1-5.tar.gz
 7aecf1b738640c482c33a73e2321f8d5  4010  x11  -  pixmap_2.6pl1-5.diff.gz
 8be83821f6b3407d5c8d37a70c427ea5  101912  x11  Optional  
pixmap_2.6pl1-5_i386.deb

-BEGIN PGP SIGNATURE-
Version: 2.6.2i

iQCVAwUBMhTShJNVaG8BiEBRAQHH5AQAg7LLzPZQ+2uY6+rAREmI0wxVT0U2W0TG
VCWNwvrE65HaJyyOY7cZ8YUZ7ZUrS7wovuqzf/clv5LFvf8lD78fEGiyr/1Nc9R3
coX/2KS8HgqhfALWHBDJPzKL9wdMk2UGGbUfO8BVwfH+dxFJ5ha/4Xe0ssZe1npi
UPTKxwRSs+I=
=q8nY
-END PGP SIGNATURE-

Uploaded: hfsutils 1.17b-1

[Rob Leslie]

Uploaded to master.debian.org.


-BEGIN PGP SIGNED MESSAGE-

Date: 16 Aug 96 18:21 UT
Format: 1.6
Distribution: unstable
Urgency: Low
Maintainer: Robert Leslie <[EMAIL PROTECTED]>
Source: hfsutils
Version: 1.17b-1
Binary:  hfsutils
Architecture:  i386 source
Description: 
 hfsutils: Tools for reading and writing Macintosh volumes.
Changes: 
 * New upstream version
Files:
 ad9a97b41d7c4aa743e807d2e72ed75e  106097  -   hfsutils_1.17b-1.tar.gz
 fc2789bff8a3bcaf0ef7e043a14d6b5d  1884  -   hfsutils_1.17b-1.diff.gz
 0c8552b06987454854b4b36cdbdc4573  114924  misc  extra  
hfsutils_1.17b-1_i386.deb

-BEGIN PGP SIGNATURE-
Version: 2.6.2

iQB1AwUBMhS8QQfFLymttX8tAQE5xQL+LZcLSyOc8d42WX9oP8uQXBGooV/2irxb
8TTz9gkEXqqMjfNvESQc6HFvQF9eCr81UVfMvg3j4G93vOWIcjHu7hLMNaGPfMz/
fy0JDGOX9Eex8Wu5n/V/gW9aKOcf2VeE
=MznW
-END PGP SIGNATURE-


-- 
Robert Leslie
[EMAIL PROTECTED]

Bug#4180: bash has duplicate examples

[Michael Meskes]

Package: bash
Version: 1.14.6-4

It seems some example files are installed twice:

$ ls -l /usr/doc/examples/bash /usr/doc/examples/bash/examples

/usr/doc/examples/bash:
total 7
-rwxr-xr-x   1 root root  742 Nov  2  1992 alias-conv.sh
drwxr-xr-x   5 root root 1024 Apr 10 16:41 examples
drwxr-xr-x   2 root root 1024 Apr 10 16:41 functions
drwxr-xr-x   2 root root 1024 Apr 10 16:41 scripts
drwxr-xr-x   2 root root 1024 Apr 10 16:41 startup-files
-rw-r--r--   1 root root 1458 Feb 28  1991 suncmd.termcap

/usr/doc/examples/bash/examples:
total 6
-rwxr-xr-x   1 root root  742 Nov  2  1992 alias-conv.sh
drwxr-xr-x   2 root root 1024 Apr 10 16:41 functions
drwxr-xr-x   2 root root 1024 Apr 10 16:41 scripts
drwxr-xr-x   2 root root 1024 Apr 10 16:41 startup-files
-rw-r--r--   1 root root 1458 Feb 28  1991 suncmd.termcap

Michael

-- 
Michael Meskes   |_  __  
[EMAIL PROTECTED] |   / ___// / // / / __ \___  __
[EMAIL PROTECTED]  |   \__ \/ /_  / // /_/ /_/ / _ \/ ___/ ___/
[EMAIL PROTECTED]|  ___/ / __/ /__  __/\__, /  __/ /  (__  )
Use Debian Linux!| //_/  /_/  //\___/_/  //

sudo_1.4.4-2

[Michael Meskes]

This one has to go into both releases as it fixes a security bug.

-BEGIN PGP SIGNED MESSAGE-

Date: 16 Aug 96 12:44 UT
Format: 1.6
Distribution: stable unstable
Urgency: High
Maintainer: Michael Meskes <[EMAIL PROTECTED]>
Source: sudo
Version: 1.4.4-2
Binary:  sudo
Architecture:  i386 source
Description: 
 sudo: Provides limited super user privileges to specific users.
Changes: 
 sudo (1.4.4-2) admin; urgency=HIGH
 .
* Fixed major security bug reported by Peter Tobias
  <[EMAIL PROTECTED]>
* Added dchanges support to debian.rules
Files:
 af241b6c40d130257a267d37bee3f533  186508  admin  -  sudo_1.4.4-2.tar.gz
 5d9cfbcb52bda23e5cf2be350c8df965  15996  admin  -  sudo_1.4.4-2.diff.gz
 378b7be8d30b7a2fbcd4b451c9d6c036  53556  admin  optional  sudo_1.4.4-2_i386.deb

-BEGIN PGP SIGNATURE-
Version: 2.6.2i

iQCVAwUBMhRtkipaNcQEtuj1AQExtQP+MTgeBEiqOG7x5LJM3sWP/DJcu+3IWOu0
dZsn2gQFvZ2rq4Gi9kTzJaDaeFCh6MUg2FatnZfrv7klxkspyNGANmWlSskbuI3p
dFYbUlf+eHKarohfOnEzgUaDYTV2HdhdjCJMrXYLkY02IlVriZFSKjNpzZhe2dBf
oMXwTo4n5F4=
=Szfa
-END PGP SIGNATURE-

-- 
Michael Meskes   |_  __  
[EMAIL PROTECTED] |   / ___// / // / / __ \___  __
[EMAIL PROTECTED]  |   \__ \/ /_  / // /_/ /_/ / _ \/ ___/ ___/
[EMAIL PROTECTED]|  ___/ / __/ /__  __/\__, /  __/ /  (__  )
Use Debian Linux!| //_/  /_/  //\___/_/  //

Bug#4178: silly problem with less

[Joey Hess]

Package: less
Version: 321-1

When I run less on a 0 byte file, it displays its help screen (same as
if you less a normal file and press 'h').

Example:

[EMAIL PROTECTED] ~/work>touch foo 
[EMAIL PROTECTED] ~/work>less foo

   SUMMARY OF LESS COMMANDS

  Commands marked with * may be preceded by a number, N.
  Notes in parentheses indicate the behavior if N is given.

  h  H Display this help.
  q  :q  Q  :Q  ZZ Exit.

  e  ^E  j  ^N  CR  *  Forward  one line   (or N lines).
...

I hesitate to report this as a bug, but it's really annoying me, as I
expect that if I look at a zero byte file, I'll just see 
"foo line 0/0 (END)". I do a double-take every time I look at some empty
log file and get the less help screen. I've used less in slackware,
redhat, etc, and those versions of less all work as I expect. Does anyone
know how to get the behavior I want with debian's less?

-- 
#!/usr/bin/perl -i=-/*/~%*~%/~~%/~~~-/*/_/=~~~-/~~!   [EMAIL PROTECTED]
$o=35;$_="$^I-*!=_!/";s/~/!*/g;s~%~-/ / ~g;$_.='---   Joey Hess
';s/=/__/g;y|*!| \\|;for(split/-/){print' 'x$o--."$_\n"}
  "How appropriate, you fight like a cow." - - Guybrush Threepwood

Bug#4179: can't use 'write' when su'd to root

[Joey Hess]

Package: bsdmainutils
Version: 3.1-0

[EMAIL PROTECTED] /tmp>su
Password:
[EMAIL PROTECTED] /tmp>write joey
write: joey is logged in more than once; writing to ttyp1
write: you are uid 0, but your login is as uid 500
[EMAIL PROTECTED] /tmp>

I don't know if this is meant to be a security feature of what, but I only
log in as root via su, and it is sometimes useful to write to people as
root. I've not seen write exhibit this behavior on other linux systems
(slackware, redhat). Can this check be turned off?

-- 
#!/bin/perl -sp0777i

Bug#4176: mkdosfs has file conflict with dosfstools

[Ian Jackson]

Package: mkdosfs, dosfstools
Version: 0.3b-1, 1.0-1

Unpacking mkdosfs (from .../misc/mkdosfs_0.3b-1.deb) ...
...
dpkg - warning, overriding problem because --force enabled:
 trying to overwrite `/usr/man/man8/mkdosfs.8', which is also in package 
dosfstools

Bug#4177: mkdosfs has file /usr/doc/copyright/debian.copyright

[Ian Jackson]

Package: mkdosfs
Version: 0.3b-1

Unpacking mkdosfs (from .../misc/mkdosfs_0.3b-1.deb) ...
dpkg - warning, overriding problem because --force enabled:
 trying to overwrite `/usr/doc/copyright/debian.copyright', which is also in 
package util-linux

Bug#4175: util-linux has file /usr/doc/copyright/debian.copyright

[Ian Jackson]

Package: util-linux
Version: 2.5-4

dpkg - warning, overriding problem because --force enabled:
 trying to overwrite `/usr/doc/copyright/debian.copyright', which is also in 
package util-linux

Bug#4174: Unable to use 'dc' fonts in latex2e

[Richard Kaszeta]

Package: latex
Version: 2e-7

The following input file fails with a 'cannot find dc1000.mf' error

\documentclass{article}
\usepackage[T1]{fontenc}

\begin{document}
Testing \LaTeX\ and trying to figure out font encodings.

\end{document}

Versions of my TeX installation:

ii  kpathsea2.6-2  Path searching for TeX & friends
ii  mfbin   2.71-4 Metafont - TeX's font engine
ii  mfnfss  2.1g-2 Use additional Metafont fonts with LaTeX
ii  mflib   1.0-8  Auxiliary files to run Metafont
ii  mfbasfnt1.0-4  TeX's default fonts and a few others.
ii  latex   2e-7   Write structured documents with TeX
ii  ltxmisc 1.0-1  Additional small styles for LaTeX
ii  ltxtool 1.0-3  Add on macro packages for LaTeX
ii  texbin  3.1415-5   TeX - The typesetting system
ii  texlib  1.0-4  Auxiliary Files to run TeX
ii  texpsfnt1.0-1  Virtual fonts and TFM's to use Postscript fo
ii  textfm  1.0-3  TeX standard font metric files



-- 
Richard W Kaszeta   Graduate Student/Sysadmin
[EMAIL PROTECTED]   University of MN, ME Dept
http://www.menet.umn.edu/~kaszeta

Re: mflib creates /var/spool/texmf/fonts/

[Nils Rennebarth]

On Thu, 11 Jul 1996, Erick Branderhorst wrote:
>I was wondering why the mflib postinst script creates directories:
...
>Isn't it better to include these in the directory structure of the package?
Didn't think of that. Yes. of course.

--
Coming again: Best quotes of the net. Today:  | Nils Rennebarth
Kristian Köhntopp <[EMAIL PROTECTED]| Schillerstr. 61 
>>I'd also be interested in the comparison [of Linux] | 37083 Göttingen
>>with a cisco router. I assume a factor of about ten.| ++49-551-71626
>What? faster or slower?  | http://www.nus.
Cheaper!  | de/~nils

Re: /usr/lib/locale and /usr/share/locale

[Miquel van Smoorenburg]

You (Christophe Le Bars) wrote:
>  > Doesn't glibc use /usr/share/locale, too?
> 
> Well, I don't know... 

I do. That's the reason I started this thread: should it or shouldn't it?
I've deciced it should, and I'm configuring glibc to use /usr/share.

Now should we move /usr/lib/zoneinfo too? What does the FHS say?

(Mind you I'm working on the Alpha port so I don't have a reason to
 desire backwards compatibility).

Mike.
-- 
  Miquel van| Cistron Internet Services   --Alphen aan den Rijn.
  Smoorenburg,  | mailto:[EMAIL PROTECTED]  http://www.cistron.nl/
[EMAIL PROTECTED] | Tel: +31-172-419445 (Voice) 430979 (Fax) 442580 (Data)

Re: Bug#4164: Ferret extended description has blank lines

[Dale Scheetz]

On Fri, 16 Aug 1996, Lars Wirzenius wrote:

> "Brian C. White":
> > By the way, for such tiny things, it's usually considered better
> > to just notify the maintainer instead of adding the overhead of
> > a full bug report.  
> 
> I disagree. 

We seem to be divided fairly evenly on this issue.

> The bug list is not a shame pole!

Objections to reporting something as a bug are not founded on this
concept. No one feels personaly "put down" by a bug report. Those of us
who object to "trivial" bug reports are more concerned about the
distribution's public perception. The new user is apt to see a "security"
bug and a "blanks in description" bug as having equal weight. Large
numbers of outstanding bugs also leave new users feeling uncertain.

> It's a trivial way for
> users to reach maintainers -- there's only one address to remember.

No, the trivial way to reach maintainers is to start with debian-user.
Case in point:
Recently a user reported smtp problems with pine. This problem turned out
to be a configuration issue, unrelated to any functional problems with the
pine software. By reporting the "bug" on debian-user first, a non-bug bug
report was avoided.

> The address in the package might be out of date.
> 
And it might not be...

> This has been discussed before, of course.
> 
And it seems we will continue to disagree. I see no harm in encouraging
users to talk to me first about problems with my packages, and I will
continue to do so. I see no reason for those who disagree with this
attitude to continue to point it out.

If we really need to grind on the differences in our personal philosophy
we should probably do it on debian-private (or maybe just private mail).

Luck,

Dwarf

  --

aka   Dale Scheetz   Phone:   1 (904) 877-0257
  Flexible Software  Fax: NONE 
  Black Creek Critters   e-mail:  [EMAIL PROTECTED]

 If you don't see what you want, just ask --

Bug#4169: pixmap dies

[joost witteveen]

> 
> Package: pixmap
> Version: 2.6pl1-2
> 
> Pixmap crashes when I try to save an icon (it works with
> some icons).


You've got a 8bpp display! 
(well, I just think you don't have a 16bpp display, as get
pixmap dump core upon loading your file)


Thanks for the bug-report, though. I've removed the
hints/comment write support in pixmap (at least that's
what I think it is), and your file seems to be saved
more or less correctly now (I can re-load, and it looks
the same. But the resuting file cannot anymore cause a
cordump with the old pixmap).

Because I am unsure I've done the right thing with the
patch, I don't want to upload the new pixmap to master.
I've put it on ftp://rulcmc.leidenuniv.nl/joost/pixmap_2.6pl1_4*
for you (and other interested parties) to try out, and
I've asked the pixmap mailinglist for more advice.

-- 
joost witteveen
[EMAIL PROTECTED]
  [EMAIL PROTECTED]
--
Use Debian/GNU Linux!

Returned mail: warning: cannot send message for 2 days (fwd)f

[Wichert Akkerman]

I've got a somewhat strange problem: I fixed a bug and tried to close
the bugreport, but somehow the message does seem to arrive at bugs.debian.org
The problem only occurs with this specific bug. Anyone got any ideas on
why this occurs on how it can be fixed?

Here is the message I got from sendmail:

Forwarded message:
> From [EMAIL PROTECTED]  Wed Aug 14 13:56:36 1996
> Date: Wed, 14 Aug 1996 13:56:36 +0200
> From: [EMAIL PROTECTED] (Mail Delivery Subsystem)
> Subject: Returned mail: warning: cannot send message for 2 days
> Message-Id: <[EMAIL PROTECTED]>
> To: 
> 
> **
> **  THIS IS A WARNING MESSAGE ONLY  **
> **  YOU DO NOT NEED TO RESEND YOUR MESSAGE  **
> **
> 
> The original message was received at Mon, 12 Aug 1996 13:00:55 +0200
> from [EMAIL PROTECTED] [132.229.128.7]
> 
>- The following addresses had delivery problems -
> <[EMAIL PROTECTED]>  (transient failure)
> 
>- Transcript of session follows -
> Warning: message still undelivered after 2 days
> Will keep trying until message is 5 days old
> 
>- Original message follows -
> Return-Path: 
> Received: from ipx206aa.wi.leidenuniv.nl ([EMAIL PROTECTED] [132.229.128.7])
>   by mailhost.wi.leidenuniv.nl (8.6.10a/SBH-1.20.1-M) with ESMTP id 
> NAA07808
>   for <[EMAIL PROTECTED]>;  Mon, 12 Aug 1996 13:00:55 +0200 (MET)
> From: wakkerma (Wichert Akkerman)
> Received: from  ([EMAIL PROTECTED])
>   by ipx206aa.wi.leidenuniv.nl (8.6.10a/FHM-1.01-S) id NAA12040
>   for [EMAIL PROTECTED];  Mon, 12 Aug 1996 13:03:40 +0200 (MET)
> Message-Id: <[EMAIL PROTECTED]>
> Subject: Re: grep description: no ext
> To: [EMAIL PROTECTED]
> Date: Mon, 12 Aug 1996 13:03:38 +0200 (MET DST)
> Organization: Zeilclub `Ten Onder!'
> Content-Type: text/plain; charset=US-ASCII
> X-Mailer: ELM [version 2.4 PL24 (modified)]
> Content-Type: text
> Content-Length: 196   
> 
> package: grep
> 
> The new grep_2.0-6 has completly revamped debian files which feature
> architecture-checking and an extended description. This should fix
> bugs #3595 and #3334.
> 
> Greetings,
>   Wichert.
> 

Bug#4173: xdm stop-script should use --pidfile

[Michael Gaertner]

Package: xbase
Version: 3.1.2-9

If you shutdown -r|h with running xdm-daemon you get:
"start-stop-daemon: warning: failed to kill xxx: No such process"
This is because start-stop-daemon kills xdm and the local
X-displayserver too - which gets killed by xdm. 

To get rid of this annoying message you should include in /etc/init.d/xdm
(sorry no diff):

stop)
start-stop-daemon --stop --verbose --pidfile /var/lib/xdm/xdm-pid \
  --exec /usr/bin/X11/xdm \
   \
# Attention: look at FSSTND, Chap. 5.3.5 "The xdm-pid file should___\
# be placed in /var/lib/xdm despite the existence of /var/run." 
# You must change in /etc/X11/xdm-config the resource 
# "DisplayManager.pidFile" to point to /var/lib/xdm-pid.
# If FHS rules this should be: /var/state/xdm/xdm-pid ???

BTW I won't discuss the mandated location per FSSTND or FHS - I don't know
the history. I also don't understand why you (here I don't mean YOU
personally) should use "xdm-pid" as it is clearly stated in both
"standards" you should use "packagename.pid".



Michael Gaertner <[EMAIL PROTECTED]>
Tel/Fax +49-761-32684

Re: fhs

[Richard Kettlewell]

Raul Miller writes:

>I think you should look at this issue a bit differently.  In one
>sense, both policies are broken -- delivering mail to a spool
>directory requires sgid programs for the user to read mail (in the
>usual sense).  A more secure and more robust solution would be to
>deliver mail directly into the user's home directory.  For example,
>  echo $HOME/Mailbox >$HOME/.forward

This is a bad idea if the home directory is NFS-mounted from a remote
system; IME file locking under NFS is very easy to get wrong.  (Not
that all mailers get locking right even on local file systems...)

Additionally, a system might well have different backup or quota
policies for mail and ordinary user data, which is a good reason to
keep them separate.

-- 
Richard Kettlewell  [EMAIL PROTECTED]  [EMAIL PROTECTED]
   http://www.elmail.co.uk/staff/richard/

Re: /usr/lib/locale and /usr/share/locale

[Christophe Le Bars]

  
 > Doesn't glibc use /usr/share/locale, too?

Well, I don't know... 

 > The only difference I'm aware of
 > is /usr/share/i18n instead of /usr/share/nls. But then this already holds
 > for libc5 starting with 5.4.0

The next wg15-locale package must provide a symbolic link then
 (/usr/share/i18n -> /usr/share/nls) .   



--
Christophe Le Bars - Email : [EMAIL PROTECTED], [EMAIL PROTECTED]
01001DEBIAN0LINUX0110ESPERANTO00101011ML1010010GNU0111
10111010010100011 Utilisez Linux Debian! 10010101001110010

Bug#4130: Old motif applications don't run

[Thomas Koenig]

[EMAIL PROTECTED] wrote:

>So you're right, one needs the environment variable. I guess the best place
>to put it would be /usr/local/bin/xmaple.

This would certainly fix the specific Maple problem, but I suspect
there may very well be more packages with the same problem.  It's
not Maple - specific; it could bite anything which uses the xcompat
package.

Either setting export XWINHOME=/usr/X11R6 in /etc/profile or
recompiling the old X libraries to use /usr/X11R6 if /usr/X386
isn't there should be the Right Thing.

I'll be reassigning this to the xcompat package, unless there are strong
objections.
-- 
Thomas Koenig, [EMAIL PROTECTED], [EMAIL PROTECTED]
The joy of engineering is to find a straight line on a double
logarithmic diagram.

Bug#4168: xemacs wants lock-dir under /usr

[Winfried Truemper]

On 16 Aug 1996, Darren/Torin/Who Ever... wrote:

torin> different systems here.  Can you check and see if /var/lib/xemacs/lock
torin> exists and is mode 1777?  Also, are you sure you're using the right

Oh, I'm so stupid. Of course /var/lib/xemacs/lock does not exist
because the package was installed on the NFS-Server and my poorly
maintained client does only mount /usr without updating the rest of
the system.

Time to set up rdist.

Sorry for the bug-report, it's superfluououous.


-Winfried

Re: libpaper 1.0 on master

[joost witteveen]

> 
> >Shouldn't the "paper size" be an attribute of a print queue, and not an
> >attribute of a machine?

Well, it could be argued that Yvess libppaper could look at
the current $PRINTER setting, and select the correct papersize
depending on the /etc/papersize.printer file or something. But
at the moment not very many programmes use libpaper or /etc/papersize,
so it's better to have them at least get to recognise a global
/etc/papersize than nothing.

> 
> Paper size effect more that just printers.  Previewers and tex tools
> come to mind, there may be others...
> 
> All I know is right now I've got to tweak quite a few things on a
> standard debian 1.1 system so that dvips, xdvi, genscript, and a few
> other programs work well and have the same idea of a default paper
> size.

Well, after you've done the tweaking, maybe it's worth the little
extra efford of mailing the patches to the maintainer/bug-system
and wait to see them included in the next release?
If you don't want to do that, could you send your patches to me,
so that try to handle it?

Thanks,

-- 
joost witteveen
[EMAIL PROTECTED]
  [EMAIL PROTECTED]
--
Use Debian/GNU Linux!

Re: fhs

[Dominik Kubla]

> Raul Miller writes:

[quotation removed]

> I think you should look at this issue a bit differently.  In one
> sense, both policies are broken -- delivering mail to a spool
> directory requires sgid programs for the user to read mail (in the
> usual sense).  A more secure and more robust solution would be to
> deliver mail directly into the user's home directory.  For example,
> echo $HOME/Mailbox >$HOME/.forward

That might work for you, but not for others: If your home directory
is located in an AFS volume, then you will either need to open the
directory to a certain pseudo-group/user for WRITES or your sendmail
(or whatever) will need to run with the CellAdministrator token.

Not good.

And /var/mail is standardized (to my knowledge) by SVID and XPG, so
why re-invent the wheel again?

Dominik
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Visit the FAN SITE of the WORLD LEAGUE OF AMERICAN FOOTBALL:
http://www.uni-mainz.de/~kubla/WLAF/Welcome.html>HTTP or
AFS
 file access.

Re: Releases other than by the package maintainert

[Bdale Garbee]

In article <[EMAIL PROTECTED]> you wrote:

: > When mainstream is updated, hello-1.3 -> hello-1.4
: > Non-usual-maintainer updates, hello-1.3-8 -> hello-1.4-0.1
: > Usual-maintainer updates, hello-1.3-8 -> hello-1.4-1
: > 
: > Usual-maintainer should never use -0 for revisions.
: 
: I think this seems reasonable.  I propose to mandate it.

Do it.

Bdale

Re: CC's on this mailing list

[Lars Wirzenius]

Bernd Eckenfels:
> umm... I'm not going to bring calculation examples.. usually you wont notice
> a few mails eighter in a uucp batch nor in ppp background transmission. 

Indeed, but it's the principle that matters. Spam isn't costing me
all that much either, but I still get furious when I get it.

-- 
Rural sizes win <[EMAIL PROTECTED]> 
Please don't Cc: me when replying to my message on a mailing list.




pgpCVLotWkwuy.pgp
Description: PGP signature

Re: Bug#4164: Ferret extended description has blank lines

[Lars Wirzenius]

"Brian C. White":
> By the way, for such tiny things, it's usually considered better
> to just notify the maintainer instead of adding the overhead of
> a full bug report.  

I disagree. The bug list is not a shame pole! It's a trivial way for
users to reach maintainers -- there's only one address to remember.
The address in the package might be out of date.

This has been discussed before, of course.

-- 
Rural sizes win <[EMAIL PROTECTED]> 
Please don't Cc: me when replying to my message on a mailing list.




pgpruuW5RWg3R.pgp
Description: PGP signature

Bug#2895: gnats passwd entry

[Brian C. White]

I'm starting to package the newest version of 'gnats' (currently in late
beta).  Could I get this resolved soon?

> The entry for the "gnats" userid is currently set to...
> gnats:*:21:100:uucp:/var/spool/uucp:/bin/sh
> 
> It should be...
> gnats:*:16:65534:Gnats Bug-Reporting System (admin):/var/gnats-db:/bin/sh
> 
> If the userid & group should be changed from what I have, please let me
> know.  The 'gnats' userid currently logs on with group "nobody" which
> should probably be changed -- maybe to "user"? "staff"? "root"? "gnats"?

Brian
   ( [EMAIL PROTECTED] )

---
In theory, theory and practice are the same.  In practice, they're not.

Bug#4159: xcoral dies

[Susan G. Kleinmann]

Raul Miller said:
> Package: xcoral
> Version: 2.5-1
> 
> Today, I decided to try xcoral.  The first operation I tried, upon
> starting it, was New.  This was sufficient to kill the program, with
> the error message:
> 
> X Error of failed request:  BadValue (integer parameter out of range for oper
ation)
>   Major opcode of failed request:  12 (X_ConfigureWindow)
>   Value in failed request:  0x0
>   Serial number of failed request:  924
>   Current serial number in output stream:  930
> 
> It may be relevant that I'm using 9wm.

To check whether 9wm might be relevant, I just tried xcoral under fvwm.
It seemed to work fine for me.

Susan Kleinmann

uploading pixmap_2.6pl1-3

[joost witteveen]

-BEGIN PGP SIGNED MESSAGE-

Date: 15 Aug 96 21:21 UT
Format: 1.6
Distribution: unstable
Urgency: Low
Maintainer: joost witteveen <[EMAIL PROTECTED]>
Source: pixmap
Version: 2.6pl1-3
Binary:  pixmap
Architecture:  i386 source
Description: 
 pixmap: A pixmap editor.
Changes: 
 - Fixed bug 4100, pixmap dumps core.
  (he says, while he bows deeply for the electric fence author (Bruce))
Files:
 599930c5caffba7af29481cd1d904de2  192987  x11  -  pixmap_2.6pl1-3.tar.gz
 ca8622d6f0d93e7f4619271812dde4c0  11769  x11  -  pixmap_2.6pl1-3.diff.gz
 987adbd583ba886e694d12f7579c4e04  101946  x11  Optional  
pixmap_2.6pl1-3_i386.deb

-BEGIN PGP SIGNATURE-
Version: 2.6.2i

iQCVAwUBMhOVlZNVaG8BiEBRAQEjvQQAlZQL4pxx5RlSaJBHF2NBkomfwCH4EV5q
WhXy9dKh0B22JA8MRk8yDl7FtHoKFtEhhNW2ee/R+ftjBnc+NnnmG7K5AzCUewVk
XGBrBw284PTtdmffbH8S5RdLdxHV2+obOX3MSY91h1CtrCpursjiRj7ZeCCaQa52
0wiiH4t0uEE=
=Tt2m
-END PGP SIGNATURE-