[OT]Re: feta20.enc not found

2004-04-10 Thread Han-Wen Nienhuys
[EMAIL PROTECTED] writes: > > > Now, I understand enough about this (I think) that this is a safegaurd > against overwriting some configuration files. I don't recall having > done anything to these config files so is it probably safe to remove the > '.rpmnew' and append '.old' on the old files?

[OT]Re: feta20.enc not found

2004-04-10 Thread David Bobroff
On Sat, 2004-04-10 at 19:56, Han-Wen Nienhuys wrote: > [EMAIL PROTECTED] writes: > > > your best bet would be the tetex from Fedora core 1, because it is > > > closest related to RH9. > > > > Ok, do I need anything other than the obvious (obvious = tetex-*)? > > no, probably not. Han-Wen/Jan, T

Re: feta20.enc not found

2004-04-10 Thread Han-Wen Nienhuys
[EMAIL PROTECTED] writes: > > your best bet would be the tetex from Fedora core 1, because it is > > closest related to RH9. > > Ok, do I need anything other than the obvious (obvious = tetex-*)? no, probably not. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen

Re: feta20.enc not found

2004-04-10 Thread David Bobroff
On Sat, 2004-04-10 at 19:12, Han-Wen Nienhuys wrote: > [EMAIL PROTECTED] writes: > > It's a bit annoying that RedHat hasn't seen fit to update this package in > > their distribution. Then again, RedHat 9 will see no more updates/errata > > fixes after the end of this month anyway so maybe I should

Re: feta20.enc not found

2004-04-10 Thread Han-Wen Nienhuys
[EMAIL PROTECTED] writes: > It's a bit annoying that RedHat hasn't seen fit to update this package in > their distribution. Then again, RedHat 9 will see no more updates/errata > fixes after the end of this month anyway so maybe I should look for a > different distribution. Before I do that (and

Re: feta20.enc not found

2004-04-10 Thread David Bobroff
At 07:15 PM 4/7/2004 +0200, you wrote: >David Bobroff writes: > >>> kpsewhich f7b6d320.enc >> >> Nothing, I'm just returned to the prompt. > >> tetex-1.0.7-66 > >Ouch, in three weeks that will be four years old. Would it be >acceptable to ask for an upgrade? Ouch, indeed. I checked around an

Re: feta20.enc not found

2004-04-07 Thread Jan Nieuwenhuizen
David Bobroff writes: >> kpsewhich f7b6d320.enc > > Nothing, I'm just returned to the prompt. > tetex-1.0.7-66 Ouch, in three weeks that will be four years old. Would it be acceptable to ask for an upgrade? I'm a bit reluctant to include missing tetex files into lilypond, just to be compat

Re: feta20.enc not found

2004-04-07 Thread David Bobroff
On Wed, 2004-04-07 at 16:12, Jan Nieuwenhuizen wrote: > David Bobroff writes: > > > Apparently not. This is what I get now: > > > > Calculating line breaks... warning: kpathsea can not find file: > > `f7b6d320.enc' > > error: can't find file: `f7b6d320.enc' > > Strange. What does: > > kpse

Re: feta20.enc not found

2004-04-07 Thread Jan Nieuwenhuizen
David Bobroff writes: > Apparently not. This is what I get now: > > Calculating line breaks... warning: kpathsea can not find file: > `f7b6d320.enc' > error: can't find file: `f7b6d320.enc' Strange. What does: kpsewhich f7b6d320.enc say? What version of tetex do you have? Jan. -- Jan

Re: feta20.enc not found

2004-04-07 Thread David Bobroff
On Wed, 2004-04-07 at 16:00, Jan Nieuwenhuizen wrote: > > If you don't understand, you probably don't need this (no offence > intended). > > There are two supported ways to run lilypond, the usual way is: > >./configure; make; make install; cd ~; lilypond > > but you can also omit the `make

Re: feta20.enc not found

2004-04-07 Thread Jan Nieuwenhuizen
David Bobroff writes: >> That depends on how you run LilyPond. If you run from the build >> directory, you can try: >> >> rm -rf share >> make >> >> which should fix it. If you install and then run, lilypond won't look >> in the original source dir, of course. >> > > I'm not sure I en

Re: feta20.enc not found

2004-04-07 Thread David Bobroff
On Wed, 2004-04-07 at 15:06, Jan Nieuwenhuizen wrote: > That depends on how you run LilyPond. If you run from the build > directory, you can try: > > rm -rf share > make > > which should fix it. If you install and then run, lilypond won't look > in the original source dir, of course. >

Re: feta20.enc not found

2004-04-07 Thread David Bobroff
On Wed, 2004-04-07 at 15:06, Jan Nieuwenhuizen wrote: > David Bobroff writes: > > > Interpreting music... warning: kpathsea can not find file: `feta20.enc' > > error: can't find file: `feta20.enc' > > > > Yet it is located in > > > > /usr/src/lilypond/mf/out/feta20.enc > > > > Is this where it sh

Re: feta20.enc not found

2004-04-07 Thread Jan Nieuwenhuizen
David Bobroff writes: > Interpreting music... warning: kpathsea can not find file: `feta20.enc' > error: can't find file: `feta20.enc' > > Yet it is located in > > /usr/src/lilypond/mf/out/feta20.enc > > Is this where it should be? Should it have been moved somewhere else? That depends on how y

feta20.enc not found

2004-04-07 Thread David Bobroff
I posted something about this on the user list a bit earlier today. I think there is something amiss with the current CVS (ChangeLog 1.2033). I get: Interpreting music... warning: kpathsea can not find file: `feta20.enc' error: can't find file: `feta20.enc' Yet it is located in /usr/src/lily