It's OK with me if the guidelines specify that shared libraries be
stripped.
Thanks
Bruce
Ok. I will try to get it to run with 16bpp. Everybody seemed just to run
8bpp. Perhaps I am not current.
On Wed, 4 Sep 1996, James A. Robinson wrote:
jimr
jimr Its not compiled for 16bpp.
jimr
jimrCould such programs then have a note telling us about that in the
jimrdescription? It looks bad
Its not compiled for 16bpp.
Could such programs then have a note telling us about that in the
description? It looks bad when one downloads software and gets a core
dump trying to run it. I think many people are running 16bpp, and
many more will be running it as 2meg become the default -- is
After getting pgp up and running, I only had to try dpkg-buildpackage
about 4 times before I got it right. (That's actually very easy) At each
step of the way the errors were informative enough to get me down the
road.
I got several errors about the failure of getpwd to return a path.
Diff -u
package: fsp
version: 2.71-3
[If I just hit return, it spews; if I actually hit n, it seems to do
the right thing fix is probably to change the
$input = y
to something like
$input = y
so they don't vanish...
Setting up fsp (2.71-3) ...
If you want, I can configure FSP so
From: Dale Scheetz [EMAIL PROTECTED]
I got several errors about the failure of getpwd to return a path.
One of the directories above the current directory is not readable?
Bruce
I know one can have a big file containing customization for all the X apps,
but I'd like to be able to modify the app-defaults/xxx file for the xxx
app. without having it being overwritten when a new release of xxx is
available? Is this a bad idea?
YA.
--
Yves Arrouye
On Aug 28, 11:56pm, Bdale Garbee wrote:
} Subject: Re: BSD lpr vs. LPRng
} In article [EMAIL PROTECTED] you wrote:
} :
} : The only incompatibility is that you might have to add a :bk: entry to
} : the printcap in order to print to a BSD-lpd-based network printer.
}
} I care a lot about
Package: aout-svgalib
Version: 1.28-6
This package installs its libraries in
/usr/i486-linuxaout/lib
But all the other aout libraries seem to be in
/usr/lib/i486-linuxaout/lib
Unfortunately /usr/i486-linuxaout/lib is not present by default
in /etc/ld.so.conf, and so the libraries cannot been
Package: boot1440-1
Version: buzz-fixed
I need to use the custom boot disks (custom no 1) to start my installation
process. However, the modules.tgz file is broken (unexpected EOF during the
detar process). I looked at the other boot disks, but all the modules.tgz files
seem to be in the same
Package: kernel-image
Version: 2.0.5-1
The post-install seems to look for /vmlinuz, and since I don't have one of
those it dies off rather quickly! All my kernels are in the /boot directory,
as this is a partition on my IDE drive, and / is on a SCSI drive (which
would be difficult to boot from).
Package: at
Version: 2.9b-1
at is not an essential base package, so it should not use Pre-Depends.
Ian.
On Wed, 4 Sep 1996, Bruce Perens wrote:
From: Dale Scheetz [EMAIL PROTECTED]
I got several errors about the failure of getpwd to return a path.
One of the directories above the current directory is not readable?
By root? Pwd works ok. I'll keep an eye out. Next time I see these errors,
Package: setserial
Version: 2.10-8
setserial should not be an essential base package, so it should not
use Pre-Depends.
Ian.
[EMAIL PROTECTED]'s mail:
Bibtex has nothing to do with TEXINPUTS. As you can see here from the file
/usr/lib/texmf/web2c/texmf.cnf, bibtex is supposed to listen to its own
variables:
[...]
Then the kpathsea doku is wrong and the bug should be reassigned to
kpathsea (I think it should be
Package: setserial
Version: 2.10-8
setserial should not be an essential base package, so it should not
use Pre-Depends.
Ian.
I have just checked out the bugs web site, and notice that I have quite
a few outstanding reports on setserial. I will try and update it, but
a lot of changes
Ian Jackson and I have had several exchanges by private email
having to do with the dependencies in dpkg, following my bug reports:
#4262 (dpkg-source requires cpio) and #4263 (dpkg-source requires patch).
We have now come to an impasse. Ian suggested if I were to bring this
to debian-devel
I have read your bug report regarding setserial... are you
still having problems? As far as I know, no other person
is having similar problems setserial...
If you are still having problems, could you get back to
me within the next few days, otherwise I will consider the
bug report closed.
Thanks
Owen Dunn:
I'm currently trying to clear some of Steve Early's backlog of X
package bugs; this'll be among them (though it may be a while longer
before the packages get converted to the new source format.)
Thanks. One suggestion: this particular bug is a quite serious
one (uid 0 exploit for
Is the essentialness of a package a sufficient condition for using
pre-depends?
Guy
Package: rxvt
Version: 2.14
Doing cut and paste from rxvt to anything will discard empty lines.
The lines get lost in the cut.
Guy
On Thu, 5 Sep 1996, Susan G. Kleinmann wrote:
Ian Jackson and I have had several exchanges by private email
having to do with the dependencies in dpkg, following my bug reports:
#4262 (dpkg-source requires cpio) and #4263 (dpkg-source requires patch).
We have now come to an impasse. Ian
'Michael Meskes wrote:'
[EMAIL PROTECTED] writes:
I have argued before that a2ps and a2gs are effectively replaced by
genscript, and that we should remove them. I think a similar case could be
made for xosview as we now have procmeter.
Opinions?
Remove them.
Move them to project/obsolete
Package: gwm
Version: 1.8c-3
gwm's source tree has a comprehensive doc/ directory, but it's not
installed. It should be in /usr/doc/gwm, or if trying to keep the
package size down, in a gwm-doc package which gwm Suggests:.
--
Shields, CrossLink.
24 matches
Mail list logo