While testing the upgrading of rex to hamm I have discovered
several problems or possible bugs. I will post each of these as
separate messages, and ask if anyone else has encountered them, and if
they should be reported as bugs.
The perl system contained login 1.45a-3, which was replace
While testing the upgrading of rex to hamm I have discovered
several problems or possible bugs. I will post each of these as
separate messages, and ask if anyone else has encountered them, and if
they should be reported as bugs.
The rex system had e2fsprogs v1.06-3 installed, and versio
OOPS - staring at this console too long!
I ([EMAIL PROTECTED] (Robert D. Hilliard)) wrote:
> The perl system contained login 1.45a-3 . . .
__ should read "rex system"
Bob
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED]
While testing the upgrading of rex to hamm I have discovered
several problems or possible bugs. I will post each of these as
separate messages, and ask if anyone else has encountered them, and if
they should be reported as bugs.
During the installation, dselect stopped with the followin
While testing the upgrading of rex to hamm I have discovered
several problems or possible bugs. I will post each of these as
separate messages, and ask if anyone else has encountered them, and if
they should be reported as bugs.
Timezone:
Version 7.48-3 of timezone was installed and tim
> "Bart" == Bart Schuller <[EMAIL PROTECTED]> writes:
Bart> Particularly if they happened to have a fully unpacked and
Bart> configured kernel source tree in /usr/src/linux .
Bart> * Poof *
Perhaps the `kernel-headers' install script ought to look for an
existing /usr/src/linux
Given that the current build constructs either libc6-only (for some
non-x86 ports) or libc6+altdev-libc5 trees, arranging it to build for
1.3.1 would be a fair amount of painful work. Someone else may be
willing to do this. However, I think the effort is better spent
actually getting Debian 2.0 o
I've got a package version 1.5.0-1 that I've already packaged.
There is a new upstream release 1.5.1.
Should the new package be named 1.5.1-1 or 1.5.1-2 or is it up to
my discretion.
Since it's an entirely new source tree it would make sense
to use 1.5.1-1. Are there any official policies on thi
On Sat, 20 Dec 1997, Radu Duta wrote:
> I've got a package version 1.5.0-1 that I've already packaged.
> There is a new upstream release 1.5.1.
> Should the new package be named 1.5.1-1 or 1.5.1-2 or is it up to
> my discretion.
>
> Since it's an entirely new source tree it would make sense
> to
I am in the process of upgrading my system to run current with hamm and
had a problem with the libmime-perl pkg relating to the libwww-perl pkg
that prevented both pkgs from configuring.
First libwww-perl requires libmime-base64-perl which does not exist. I
figured that libmime-perl provided this
On Fri, Dec 19, 1997 at 09:29:17AM -0800, [EMAIL PROTECTED] wrote:
>1) Once all packages are selected, be able to dump the selections to
>a file that could be later read in for subsequent identical
>installations.
There is a twist to this. Allong with all the installed packages will
com
Hi,
>>"Karl" == Karl M Hegbloom <[EMAIL PROTECTED]> writes:
> "Bart" == Bart Schuller <[EMAIL PROTECTED]> writes:
Bart> Particularly if they happened to have a fully unpacked and
Bart> configured kernel source tree in /usr/src/linux .
Bart> * Poof *
No it does not! Would you please l
The web pages should all be utilizing Captain Blue-Eye
in a reasonably good way right now. The changes ended
up occurring sooner than I'd hoped so I had to rush.
I'm pretty sure all the major problems are fixed, but
I'd appreciate it if people could thoroughly look
through the pages and report any
>> Radu Duta writes:
RD> On Fri, Dec 19, 1997 at 09:29:17AM -0800, [EMAIL PROTECTED] wrote:
>> 1) Once all packages are selected, be able to dump the selections to
>> a file that could be later read in for subsequent identical
>> installations.
RD> There is a twist to this. Allong with all the
On Sat, Dec 20, 1997 at 12:15:29AM -0800, [EMAIL PROTECTED] wrote:
>>> Radu Duta writes:
>
>RD> On Fri, Dec 19, 1997 at 09:29:17AM -0800, [EMAIL PROTECTED] wrote:
>> dpkg --get-selections
>> dpkg --set-selections
I noticed; well it's a start, that's for sure. There is a lot of info
missing from t
On Dec 20, Manoj Srivastava wrote
> > "Bart" == Bart Schuller <[EMAIL PROTECTED]> writes:
> Bart> Particularly if they happened to have a fully unpacked and
> Bart> configured kernel source tree in /usr/src/linux .
>
> Bart> * Poof *
>
> No it does not! Would you please look at what the
Hi,
I'm going home for a week or more, if any serious[1] bugs in my
packages come up, please feel free to do non-maintainer uploads of
them.
Happy Christmas and all that larky.
[1] And, please, I do mean serious, i.e. not whether /x/y/z should or
shouldn't be a conffile.
--
James
--
TO UNSUB
Hi,
I intend to package a program called synaethesia. It is a cd player with
graphical effects, and is quite compact. The license is GPL, the section
would be hamm/sound.
Martin.
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-
I've created a directory "/usr/X11R6/icons" for my own use. I think
that we need to have something like that, and a keeper of the icons.
All of the mini icons and whatnot from the various packages ought to
be consolidated into one icon package. I think it should be someone
who likes to draw
Manoj Srivastava writes:
> Error configuring $package: /usr/src/linux-$version does not seem to
> be a symbolic link, possibly from an old package or a left-over
> from a user installed kernel. Please remove
> /usr/src/linux-$version and try to reconfigure $package.
I suggest you
On Sat, 20 Dec 1997, Tim Ferrell wrote:
> I am in the process of upgrading my system to run current with hamm and
> had a problem with the libmime-perl pkg relating to the libwww-perl pkg
> that prevented both pkgs from configuring.
>
> First libwww-perl requires libmime-base64-perl which does no
On Thu, Dec 18 1997 12:16 CST Rob Browning writes:
> /* On GNU/Linux systems, both methods are used by various mail
> programs. I assume that most people are using newer mailers that
> have heard of flock. Change this if you need to. */
>
> #define MAIL_USE_FLOCK
>
> And here's th
Tim> I am in the process of upgrading my system to run current with hamm
Tim> and had a problem with the libmime-perl pkg relating to the
Tim> libwww-perl pkg that prevented both pkgs from configuring.
"Hm, not good" says the libmime-perl maintainer (that would be me :-( )
Tim> First
I was just trying to compile `browser-history', and the following
thing happened:
make[1]: Entering directory `/usr/src/debian/Work/browser-history'
gcc -ansi -O -Wall browser-history.c -o browser-history \
-L/usr/X11R6/lib -lXmu -lX11
ld: warning: libc.so.5, needed by /usr/lib/libc5-compat
I find that if you put:
.EXPORT_ALL_VARIABLES:
... into debian/rules, the DH_VERBOSE=1 starts to function.
Also, to put a version string into a program, I use:
VERSION=$(shell dpkg-parsechangelog 2>/dev/null
\
| gawk -F:
I'm planning to package `cvsweb-1.0'.
Q: Where does it go? Experimental, or unstable/web?
Here's the README, the copyright follows.
README
Description: Binary data
# Copyright (C) 1996
# William C. Fenner. All rights reserved.
#
# Redistribution and use in source and binary forms, w
It occurs to me that the menu files ought to have fields for:
Xresources to get `xrdb -merge'd when the program is launched. (lazy eval)
(and removed perhaps, on the delete window hook? Does the X server gc?)
Menu font, color, icon, a predicate for when it's greyed off (think scwm)
XTerm
I remember reading here that even Redhat is not really in favor of kde
because of it's non free componente - Qt. Is this really documented
anywhere? Other than by the fact that it hasn't been included:-)?
Thanks,
--
David Welton http://www.efn.org/~davidw
Debi
David Welton <[EMAIL PROTECTED]> writes:
> I remember reading here that even Redhat is not really in favor of kde
> because of it's non free componente - Qt. Is this really documented
> anywhere? Other than by the fact that it hasn't been included:-)?
Some Redhat developer stated this policy in
29 matches
Mail list logo
