teTeX and no_x11

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

teTeX and no_x11

f.holop
hi there,

i have upgraded my production server to 3.8 release.
i have no X there, but as in my previous post about the new
rrdtools i sense some shift in what actually no_x11 means
or will mean in the future.

please note that i am describing a 3.8 release situation,
if this is fixed in current, disregard it.

first of all here's the log of installing tetex no_x11:

integer> sudo pkg_add teTeX_base-3.0p1-no_x11
teTeX_base-3.0p1-no_x11:png-1.2.8: complete
teTeX_base-3.0p1-no_x11:t1lib-5.0.0: complete
teTeX_base-3.0p1-no_x11:ghostscript-fonts-6.0: complete
Can't install ghostscript-7.05p6: lib not found ICE.8.0
Even by looking in the dependency tree:
        ghostscript-fonts-6.0, png-1.2.8
Maybe it's in a dependent package, but not tagged with @lib ?
(check with pkg_info -K -L)
If you are still running 3.6 packages, update them.
Can't install ghostscript-7.05p6: lib not found SM.8.0
Can't install ghostscript-7.05p6: lib not found X11.9.0
Can't install ghostscript-7.05p6: lib not found Xext.9.0
Can't install ghostscript-7.05p6: lib not found Xt.9.0
teTeX_base-3.0p1-no_x11:teTeX_texmf-3.0: complete
teTeX_base-3.0p1-no_x11:texi2html-1.64: complete
Can't install teTeX_base-fmt-3.0: can't resolve ghostscript-7.05p6
Can't install teTeX_base-3.0p1-no_x11: can't resolve teTeX_base-fmt-3.0
You may wish to update your font path for /usr/local/share/ghostscript/fonts
Can't exec "/usr/X11R6/bin/mkfontdir": No such file or directory at /usr/libdata/perl5/OpenBSD/Error.pm line 30.
system(/usr/X11R6/bin/mkfontdir, /usr/local/share/ghostscript/fonts) failed: -1
Can't exec "/usr/X11R6/bin/fc-cache": No such file or directory at /usr/libdata/perl5/OpenBSD/Error.pm line 30.
system(/usr/X11R6/bin/fc-cache, /usr/local/share/ghostscript/fonts) failed: -1
--- ghostscript-fonts-6.0 -------------------
To install these fonts for X11, just make sure that the fontpath
lists the 75dpi or 100dpi bitmap fonts before the ghostscript fonts,
and make sure you have the string ":unscaled" appended to the bitmap
font's fontpath. This way, the bitmap fonts will be used if they
match, and the Type 1 versions will be used if the font needs to be
scaled. Below is the relevant section from a typical xorg.conf file.

   FontPath   "/usr/X11R6/lib/X11/fonts/misc/"
   FontPath   "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
   FontPath   "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
   FontPath   "/usr/local/lib/X11/fonts/ghostscript/"
   FontPath   "/usr/X11R6/lib/X11/fonts/Type1/"





the problem obviously starts with ghostscript, which i think
should rather be ghostscript-7.05p6-*no_x11 ... if needed,
but i am not even sure that it is needed for teTeX, is it really?

so i added ghostscript-7.05p6-*no_x11 myself.  at this point
i have the following installed:

ghostscript-7.05p6-a4-no_x11 GNU PostScript interpreter
ghostscript-fonts-6.0 35 standard PostScript fonts with Adobe name aliases
png-1.2.8           library for manipulating PNG images
t1lib-5.0.0         Type 1 rasterizer library for UNIX/X11
teTeX_texmf-3.0     TeX distribution, common support files
texi2html-1.64      texinfo to HTML converter

so i tried

integer> sudo pkg_add teTeX_base-3.0p1-no_x11
Can't install teTeX_base-fmt-3.0: lib not found ICE.8.0
Even by looking in the dependency tree:
        t1lib-5.0.0, ghostscript-7.05p6-a4-no_x11, ghostscript-fonts-6.0, png-1.2.8, texi2html-1.64, teTeX_texmf-3.0
Maybe it's in a dependent package, but not tagged with @lib ?
(check with pkg_info -K -L)
If you are still running 3.6 packages, update them.
Can't install teTeX_base-fmt-3.0: lib not found SM.8.0
Can't install teTeX_base-fmt-3.0: lib not found X11.9.0
Can't install teTeX_base-fmt-3.0: lib not found Xaw.11.0
Can't install teTeX_base-fmt-3.0: lib not found Xext.9.0
Can't install teTeX_base-fmt-3.0: lib not found Xmu.9.0
Can't install teTeX_base-fmt-3.0: lib not found Xp.9.0
Can't install teTeX_base-fmt-3.0: lib not found Xpm.7.0
Can't install teTeX_base-fmt-3.0: lib not found Xt.9.0
Can't install teTeX_base-3.0p1-no_x11: can't resolve teTeX_base-fmt-3.0


and that is because teTeX_base-fmt-3.0 has no no_x11.  i went
and looked at INDEX (cutting the long line):

teTeX_base-fmt-3.0|print/teTeX/base,-fmt|/var|format files|print/teTeX/base/pkg/
teTeX_base-fmt-3.0|print/teTeX/base,-fmt,no_x11|/var|format files|print/teTeX/ba

and as you can see, there is no no_x11 flavour.
also further down the line the line which contains the string no_x11
has no ghostscript-* in it while the other yes, so i guess this
explains the ghostscript dependency.


is my analysis correct?

could this be fixed for 3.8 release?

-f
--
between two evils, always pick the one you never tried before.

Reply | Threaded
Open this post in threaded view
|

Re: teTeX and no_x11

steven mestdagh
On Fri, Nov 25, 2005 at 03:00:44PM +0100, frantisek holop wrote:

> hi there,
>
> i have upgraded my production server to 3.8 release.
> i have no X there, but as in my previous post about the new
> rrdtools i sense some shift in what actually no_x11 means
> or will mean in the future.
>
> please note that i am describing a 3.8 release situation,
> if this is fixed in current, disregard it.
>
> first of all here's the log of installing tetex no_x11:
>
> integer> sudo pkg_add teTeX_base-3.0p1-no_x11
> teTeX_base-3.0p1-no_x11:png-1.2.8: complete
> teTeX_base-3.0p1-no_x11:t1lib-5.0.0: complete
> teTeX_base-3.0p1-no_x11:ghostscript-fonts-6.0: complete
> Can't install ghostscript-7.05p6: lib not found ICE.8.0
> Even by looking in the dependency tree:
>         ghostscript-fonts-6.0, png-1.2.8

this has been fixed in -current, see cvs logs.

> could this be fixed for 3.8 release?

no, only security/reliability issues are fixed in -stable.
you can try to backport the fixes from current, if you really need this.
that is not supported, however.

Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm

Reply | Threaded
Open this post in threaded view
|

Re: teTeX and no_x11

f.holop
hmm, on Fri, Nov 25, 2005 at 03:30:26PM +0100, steven mestdagh said that

> On Fri, Nov 25, 2005 at 03:00:44PM +0100, frantisek holop wrote:
> > hi there,
> >
> > i have upgraded my production server to 3.8 release.
> > i have no X there, but as in my previous post about the new
> > rrdtools i sense some shift in what actually no_x11 means
> > or will mean in the future.
> >
> > please note that i am describing a 3.8 release situation,
> > if this is fixed in current, disregard it.
> >
> > first of all here's the log of installing tetex no_x11:
> >
> > integer> sudo pkg_add teTeX_base-3.0p1-no_x11
> > teTeX_base-3.0p1-no_x11:png-1.2.8: complete
> > teTeX_base-3.0p1-no_x11:t1lib-5.0.0: complete
> > teTeX_base-3.0p1-no_x11:ghostscript-fonts-6.0: complete
> > Can't install ghostscript-7.05p6: lib not found ICE.8.0
> > Even by looking in the dependency tree:
> >         ghostscript-fonts-6.0, png-1.2.8
>
> this has been fixed in -current, see cvs logs.
>
> > could this be fixed for 3.8 release?
>
> no, only security/reliability issues are fixed in -stable.
> you can try to backport the fixes from current, if you really need this.

isn't this reliability?
it's not the problem of the actual software but the port.

and 3.8 will be supported for 12 months from now on....

-f
--
many would be cowards if they had enough courage.

Reply | Threaded
Open this post in threaded view
|

Re: teTeX and no_x11

steven mestdagh
On Fri, Nov 25, 2005 at 03:56:15PM +0100, frantisek holop wrote:

> hmm, on Fri, Nov 25, 2005 at 03:30:26PM +0100, steven mestdagh said that
> > On Fri, Nov 25, 2005 at 03:00:44PM +0100, frantisek holop wrote:
> > > hi there,
> > >
> > > i have upgraded my production server to 3.8 release.
> > > i have no X there, but as in my previous post about the new
> > > rrdtools i sense some shift in what actually no_x11 means
> > > or will mean in the future.
> > >
> > > please note that i am describing a 3.8 release situation,
> > > if this is fixed in current, disregard it.
> > >
> > > first of all here's the log of installing tetex no_x11:
> > >
> > > integer> sudo pkg_add teTeX_base-3.0p1-no_x11
> > > teTeX_base-3.0p1-no_x11:png-1.2.8: complete
> > > teTeX_base-3.0p1-no_x11:t1lib-5.0.0: complete
> > > teTeX_base-3.0p1-no_x11:ghostscript-fonts-6.0: complete
> > > Can't install ghostscript-7.05p6: lib not found ICE.8.0
> > > Even by looking in the dependency tree:
> > >         ghostscript-fonts-6.0, png-1.2.8
> >
> > this has been fixed in -current, see cvs logs.
> >
> > > could this be fixed for 3.8 release?
> >
> > no, only security/reliability issues are fixed in -stable.
> > you can try to backport the fixes from current, if you really need this.
>
> isn't this reliability?

has your system become less reliable due to this? i think not.
there is simply no time to fix all little port mistakes in the -stable trees.

> it's not the problem of the actual software but the port.
>
> and 3.8 will be supported for 12 months from now on....

uhu, and in about 5 months, there will be 3.9 with the fix included.

--
steven

Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm

Reply | Threaded
Open this post in threaded view
|

Re: teTeX and no_x11

Nikolay Sturm-2
In reply to this post by f.holop
* frantisek holop [2005-11-25]:
> > > could this be fixed for 3.8 release?
> >
> > no, only security/reliability issues are fixed in -stable.
> > you can try to backport the fixes from current, if you really need this.
>
> isn't this reliability?

In principal we only backport security fixes. If sth else breaks due to
this, we fix those ports as well. AFAIK there was only one exception to
these rules and that was a port which was completely unusable.

Now for your problem, you can just pull the -current port's Makefile to
your 3.8 machine and it should work. Furthermore it is consensus among
porters that installing xbase on a machine is not a problem, so the
broken FLAVOR is a nuisance, nothing more.

Feel free to execrate me for not fixing the problem before 3.8 tree
freeze.

Nikolay

Reply | Threaded
Open this post in threaded view
|

Re: teTeX and no_x11

f.holop
hmm, on Sat, Nov 26, 2005 at 01:45:45PM +0100, Nikolay Sturm said that
> Now for your problem, you can just pull the -current port's Makefile to
> your 3.8 machine and it should work. Furthermore it is consensus among
> porters that installing xbase on a machine is not a problem, so the
> broken FLAVOR is a nuisance, nothing more.

that is of the other issues i wanted to talk about later.
call me old fashioned but no_x11 for me means not havint to
install any x*.tgz sets.  now, of course it's not a huge problem
for me to install xbase, it's just that this "consensus" was
never really publicized here before, at least i haven't seen.
maybe it's just me, i was making incorrect assumptions about
what no_x11 means.

and if this is the way it will be, wouldn't it be a good idea
to make an xlib38.tgz which would hold only the libs and nothing
else, after all, isn't it the security mantra that don't install
anything you won't use, and xbase is full of binaries which
will be never used on a firewall?

> Feel free to execrate me for not fixing the problem before 3.8 tree
> freeze.

no need to get angry, it was just a matter of interpreting
'reliability'.

-f
--
a war put off is not a war avoided. -- c. heston

Reply | Threaded
Open this post in threaded view
|

Re: teTeX and no_x11

Nikolay Sturm-2
* frantisek holop [2005-11-26]:
> call me old fashioned but no_x11 for me means not havint to
> install any x*.tgz sets.

That's the idea.

> now, of course it's not a huge problem for me to install xbase, it's
> just that this "consensus" was never really publicized here before, at
> least i haven't seen.

We don't write reports. I think Alek and Matthieu mentioned it recently
as well.

> maybe it's just me, i was making incorrect assumptions about
> what no_x11 means.

Your assumptions are correct. teTeX_base,no_x11 is broken in that regard
and installing xbase is a workaround.

> and if this is the way it will be, wouldn't it be a good idea to make
> an xlib38.tgz which would hold only the libs and nothing else, after
> all, isn't it the security mantra that don't install anything you
> won't use, and xbase is full of binaries which will be never used on a
> firewall?

If you have enough disk space on your firewall/server, just install
xbase and be done. If you don't have the space, you are on your own
anyways and can just as well pull tetex/base/Makefile from -current and
build your own package with a correct no_x11 FLAVOR.
 
Now I need to get back to porting...

Nikolay

Reply | Threaded
Open this post in threaded view
|

Re: teTeX and no_x11

f.holop
hmm, on Sat, Nov 26, 2005 at 10:45:06PM +0100, Nikolay Sturm said that

> > maybe it's just me, i was making incorrect assumptions about
> > what no_x11 means.
>
> Your assumptions are correct. teTeX_base,no_x11 is broken in that regard
> and installing xbase is a workaround.
>
> > and if this is the way it will be, wouldn't it be a good idea to make
> > an xlib38.tgz which would hold only the libs and nothing else, after
> > all, isn't it the security mantra that don't install anything you
> > won't use, and xbase is full of binaries which will be never used on a
> > firewall?
>
> If you have enough disk space on your firewall/server, just install
> xbase and be done. If you don't have the space, you are on your own
> anyways and can just as well pull tetex/base/Makefile from -current and
> build your own package with a correct no_x11 FLAVOR.

you put it as if teTeX was(before being fixed) the only case..
and of course teTeX is not really a firewall "required" program.

when i said firewall, i rather meant packages like
rrdtools (which at one point also need xbase)
or other reporting tools needing x11 libs but
really needing x11.

-f
--
sex is not the answer.  sex is the question.  "yes" is the answer.