Orphaning ftnchek and ratfor77.

Hi, After some years in the Debian project, although not so active as I wished, I do not have the time and the motivation anymore to maintain my packages: * ftnchek: A semantic checker for Fortran 77 programs. Good shape. Just needs to be upgraded to newest upstream version

Re: Re^2: Documentation Policy

> "MB" == Marco Budde <[EMAIL PROTECTED]> writes: MB> Why should we ship info files? HTML is better format. The most MB> system will use HTML as their help system in the future. KDE for MB> example uses HTML. The Info format is a lot better, tecnically, than HTML. That's what I've heard. Mayb

Bug#4570: xview-clients without owplaces

> "SR" == Sven Rudolph <[EMAIL PROTECTED]> wrote: >> Package: xview-clients >> Version: 3.2p1.2-1 >> >> The "Save workspace" internal command of olwm requires >> olwplaces (which often uses xtoolwait). olwplaces and >> xtoolwait are not available in the package. SR> Are these programs part o

Bug#4551: xautolock and xtrlock conflict on screensaver

> "DH" == Dave Holland <[EMAIL PROTECTED]> wrote: DH> xautolock should check to see if the display is already locked DH> before attempting to run the locker program. No, this is what xlock should do. xautolock, despite of its name, does not know it will run a lock program. xautolock is a gene

Bug#4392: xfishtank coredumps at 16bpps

> "HX" == Herbert Xu <[EMAIL PROTECTED]> wrote: HX> Package: xfishtank HX> Version: 2.2-1 HX> As the subject says, xfishtank dumps core at 16 bpp. It HX> works fine at 8 bpp, at least on my machine. There is a version of xfishtank in sunsite.unc.edu that was patched to work in "truecolor" m

Bug#4376: vm doesn't use /etc/emacs/site-start.d

> "RK" == Richard Kettlewell <[EMAIL PROTECTED]> wrote: RK> Package: vm RK> Version: 5.95beta-2 RK> ... VM maintainer, when fixing this bug, it would also be a good idea to upgrade to 5.96beta. Kind regards, Emilio. -- Emilio C. Lopes

Bug#4269: xosview has only XOSView as application resource file

> "jw" == joost witteveen <[EMAIL PROTECTED]> wrote: jw> do you want me to jw> 1 move xosview to 'contrib', and stop maintaining it jw> 2 just go on maintaining a broken xosview? IMHO, you should stick with 1. There are other things that may do the same thing xosview is supposed to do.

Re: Bug#4261: Ghostview -- needs MIME entry

> "BCW" == Brian C White <[EMAIL PROTECTED]> wrote: BCW> I suggest making ghostview "Recommends: mime-support". I don't see why this is necessary. "mime-support" brings no extra capabilities to ghostview, AFAIK. Ciao, Emilio. -- Emilio C. Lopes

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

Hi, this is not a bug. Due to copyright reasons the dc fonts, which use the T1 encoding, are no more in the mflib package. You got to get the package "mfdcfnt_1.0-1_all.deb"; It's on "Incoming/" right now (at least in our mirror here). Ciao, Emilio. > "RK" == Richard Kaszeta <[EMAIL PROTECT

Re: CC's on this mailing list

> "IJ" == Ian Jackson <[EMAIL PROTECTED]> wrote: >> It would be nice also to not have long messages fully quoted :-( IJ> Right, this is going into the policy manual. Please put also something about long signatures (> 4 lines) or signatures whose first line is not "-- ". Ciao, Emilio. --

Re: site-start.el and lout-mode.el

> "eichin" == eichin <[EMAIL PROTECTED]> wrote: eichin> If someone wants to write an "install-elisp" (there have been eichin> some quite clever suggestions here) some time this week, I'll eichin> try and include it in the 19.32-1 package. I like the way is done in w3: all the commands necess

Re: Emacs per-package startup files

> "EB" == Erick Branderhorst <[EMAIL PROTECTED]> wrote: EB> How will these files be read. In alphabetical or fileposition order? EB> Some scripts written in these might work only properly if some other EB> script is executed first. I can't come up with some proper example EB> but I can imag

Re: Emacs per-package startup files

> "EB" == Erick Branderhorst <[EMAIL PROTECTED]> wrote: EB> How will these files be read. In alphabetical or fileposition order? EB> Some scripts written in these might work only properly if some other EB> script is executed first. I can't come up with some proper example EB> but I can imag

Re: Documentation formats

> "LW" == Lars Wirzenius <[EMAIL PROTECTED]> wrote: LW> Ian Jackson (after my deletions): >> * GNU Texinfo ... HTML. >> * The Linux FAQ ... HTML ... >> * The Linux HOWTOs ... HTML ... >> * My new dpkg manuals ... HTML ... >> * The Perl documentation ... HTML LW> I think I see a trend here. Wh

Re: Emacs per-package startup files

> "IJ" == Ian Jackson <[EMAIL PROTECTED]> wrote: IJ> /etc/emacs/site-start.d ? There would be something else inside /etc/emacs or just site-start.d? If not, it seems we need a better name. /etc/site-start.d? /etc/emacs.d? /etc/emacs-start.d? /etc/emacs-lisp.d? Yes, I know would nice to have

Re: uploaded babel 3.6-4 to master

> "MM" == Michael Meskes <[EMAIL PROTECTED]> wrote: >> What is wrong with >> >> \usepackage[latin1]{inputenc} MM> Note that as my fault. I've been using latin1.sty for so long I MM> didn't even realize that this was a possibility. Sorry for that. MM> But I still think we should keep latin1

Re: IP-aliasing

> "CS" == Craig Sanders <[EMAIL PROTECTED]> wrote: CS> I'd like to see a bourne-like shell with perl-like regexp stuff CS> (mainly sed & grep) built in - i'd switch to that in a flash. People may say it's called ksh93. IMHO, it may seem somewhat interesting, but I really don't like it. Look l

Bug#4000: emacs can't initialize x window

> "EB" == Erick Branderhorst <[EMAIL PROTECTED]> wrote: EB> I load hilit19.el in my .emacs but when not under X this error occurs. EB> Loading hilit19... EB> Error in init file: error: "X windows are not in use or not initialized" Maybe that's why the documentation at the beggining of hilit1

Re: uploaded babel 3.6-4 to master

> "EB" == Erick Branderhorst <[EMAIL PROTECTED]> wrote: EB> babel: Support for multilingual typesetting with (La)TeX EB> Changes: EB> Fri Aug 2 13:21:27 1996 Erick Branderhorst <[EMAIL PROTECTED]> EB> . EB> * debian.rules: changed for processing in subdir babel EB> * add

Re: Name clash in prospective package

> "BCW" == Brian C White <[EMAIL PROTECTED]> wrote: BCW> I don't see a problem with packages creating directories and BCW> other necessary framework in /usr/local. In some cases, this can BCW> be quite complex and without which it isn't possible for there to BCW> be "local" extensions. Besid

Re: Questions about LClint package I am creating.

> "DM" == Dale Miller <[EMAIL PROTECTED]> wrote: DM> Secondly, the LClint package provides some .el and .elc files DM> to allow access to LClint through emacs. I noticed a directory DM> under /usr/lib/emacs named site-lisp. Is this an appropriate DM> place to install these files or does that d

Re: Better Xdm logo screen (Re: Doubts building a new package...)

> "LW" == Lars Wirzenius wrote: LW> For those of you who have some free time, perhaps designing a flashy LW> xdm login screen would be a better project. That is, something more LW> sexy than the default criss-cross background with a dull, white LW> "login:/Password:" window in the middle. It

Re: uploaded dvi2tty_5.1-6_i386.deb to chiark

> "Engel" == David Engel <[EMAIL PROTECTED]> wrote: Engel> Guy Maor writes: >> To guarantee that the changes file is uncorrupted? Nothing for >> now. After 1.1 is released, I'll start requiring all changes files >> to be pgp signed. That will guarantee their sanctity. Engel> Can you sugges

Re: Doubts building a new package...

> "AD" == Austin Donnelly <[EMAIL PROTECTED]> wrote: AD> I'm not convinced we need the package at all. AD> After all, you get the image with the kernel sources anyway. Sure? I didn't know that. It's really hidden in that "Documentation" dir... Anyway, maybe someone who does not want the sou

Doubts building a new package...

Hi, I'm planning to do a package, erh, hm, ... it's the Linux-2.0 Logo package :-). But I have some doubts: 1- There is some trouble with dpkg naming it linux-2.0-logo_1.0-0.all.deb? 2- The logo itself is a gif file. Is it non-free? I can convert it to a jpeg file if needed. 3- Where should