> But shouldn't xbase then replace and conflict with xterm-color?
Yes, it probably should have done that a long time ago. Go ahead and
file a bug report so I remember to get that in.
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mai
I'm moving this over to debian-devel. Hope that's OK.
Joey Hess <[EMAIL PROTECTED]> writes:
> The real reason I'm replying to this: I wonder what the other developers
> think about bug reports that just say a new version is available (as opposed
> to, a new version is available, and fixes this
hmm. xnest should work fine with xfs (I'd used it that way under
3.1.2, when I was developing the gzipped font stuff) but note that the
very end of the man page has some warnings about how xnest actually
*fakes* all of it's font handling. (Rather than repeat it here, look
near the end of man Xnes
> Joey Hess <[EMAIL PROTECTED]> writes:
> > The real reason I'm replying to this: I wonder what the other developers
> > think about bug reports that just say a new version is available (as opposed
> > to, a new version is available, and fixes this nasty bug).
> I think it's a good idea. I don'
[EMAIL PROTECTED] (Bruce Perens) writes:
> I think you have to tell dselect where non-free and contrib are so that it
> can find their Packages files. It asks about this when you choose an access
> method.
yes, that's right. I've checked the directories again. Dselect finds
the apropritiate Packa
Good morning Enrique and others!
> > > Perhaps the `bug' package should be priority standard? It does make
> > > bug reporting much easier.
> >
> > Yes, and when it installs itself, from `deity', it should stop with a
> > message to be read, (any key to continue) which advertises `bug's
> > p
> Perhaps you could think over the whole thing and how we could arrange
> to have an installation without the need to answer questions.
The main thing to do is to separate the question asking from the other scripts.
SVR4's package system does this by having a request script for each package
that
Update on the packages I checked:
ssh does _not_ use the libc functions when compiled with libc5.
So ssh will corrupt the utmp file if used with hamm.
Helmut
--
Helmut Geyer[EMAIL PROTECTED]
public PGP key available : finger [EMAIL PROTECTED]
Hi,
I'm working on the xdaliclock package, and I will take it to libc6. I have
merely recompiled it, and all has worked fine, except perhaps some warning
(perhaps present with libc5: I have not installed alt-libc5 as yet). This is
suspect to me, because my X libs are compiled with libc5, and in thi
I've recompiled some programs that use X with libc6 and they run like a
charm. A few minutes ago I recompiled the latest procps suite for
testing purposes. For instance xload:
gauss:meskes 113) ldd /usr/X11R6/bin/xload
libXaw.so.6 => /usr/X11R6/lib/Xaw95/libXaw.so.6 (0x4001)
li
Francesco Tapparo <[EMAIL PROTECTED]> writes:
> I'm working on the xdaliclock package, and I will take it to libc6. I have
> merely recompiled it, and all has worked fine, except perhaps some warning
> (perhaps present with libc5: I have not installed alt-libc5 as yet). This is
> suspect to me, be
On Jun 11, Guy Maor wrote
> > I'm working on the xdaliclock package, and I will take it to libc6. I
> > have merely recompiled it, and all has worked fine, except perhaps some
> > warning (perhaps present with libc5: I have not installed alt-libc5 as
> > yet). This is suspect to me, because my X li
> On Jun 11, Guy Maor wrote
> > > I'm working on the xdaliclock package, and I will take it to libc6. I
> > > have merely recompiled it, and all has worked fine, except perhaps some
> > > warning (perhaps present with libc5: I have not installed alt-libc5 as
> > > yet). This is suspect to me, becau
[EMAIL PROTECTED] (J.H.M.Dassen) writes:
> No. The surprising thing is that it _does_ work. (e.g. take the DDD source
> in a libc6 environment, with libc6 libg++272, libc5 ncurses, X etc. It
> compiles and works).
Yes, Helmut just told me the same - that H.J. Lu and XFree86 team
worked together t
When will we get libc6 X packages ?
Phil.
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
On Jun 11, Michael Meskes wrote
> I've recompiled some programs that use X with libc6 and they run like a
> charm. A few minutes ago I recompiled the latest procps suite for
> testing purposes. For instance xload:
>
> gauss:meskes 113) ldd /usr/X11R6/bin/xload
> libXaw.so.6 => /usr/X11R6/l
Christian Leutloff <[EMAIL PROTECTED]> writes:
> --pgp-sign-Multipart_Tue_Jun_10_23:52:51_1997-1
> Content-Type: text/plain; charset=US-ASCII
>
> [EMAIL PROTECTED] (Bruce Perens) writes:
>
> > I think you have to tell dselect where non-free and contrib are so that it
> > can find their Packages
Mark Baker:
>
> In article <[EMAIL PROTECTED]>,
> Joey Hess <[EMAIL PROTECTED]> writes:
>
> > version is available. I volenteered some time ago on the debian-qa list to
> > do this, and I have scripts that look at the LSM files on sunsite, and
> > automatically give me a list of out of date
> When will we get libc6 X packages ?
probably in the next week or two (I'll try to push out a 3.3-2 with
the dependency problems and XF86Setup problem fixed this weekend, and
then convert my stock-1.3 build machine into a mixed-mode machine and
work forward from there...)
--
TO UNSUBSCRIBE FROM
[EMAIL PROTECTED] (Philip Hands) wrote on 11.06.97 in <[EMAIL PROTECTED]>:
> The problems that need to be solved are:
> unpacking all the request scripts early enough to run them all before the
> first pre-inst;
> and making the request scripts able to diagnose what questions to ask,
> wh
On Jun 11, Ricardas Cepas wrote
> Package: svgatextmode
> Version: 1.5-1
>
> get/setVGAreg is missing,
They are missing because they are described by the author as "hacker" programs,
not necessary for the functioning of the svgatextmode itself. The comment in
the source implies that you must
On 11 Jun 1997, Kai Henningsen wrote:
> [EMAIL PROTECTED] (Philip Hands) wrote on 11.06.97 in <[EMAIL PROTECTED]>:
>
> > The problems that need to be solved are:
> > unpacking all the request scripts early enough to run them all before the
> > first pre-inst;
> > and making the request scr
pgpGAtHFNd8a1.pgp
Description: PGP message
pgp5giZfsgbKh.pgp
Description: PGP message
24 matches
Mail list logo
