Bug 21173

Summary:	lilypond doesn't emerge with old metafont(tetex)
Product:	Gentoo Linux	Reporter:	Thomas Raschbacher <lordvan>
Component:	New packages	Assignee:	Text-Markup Team (OBSOLETE) <text-markup+disabled>
Status:	RESOLVED INVALID
Severity:	major	CC:	mike
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Thomas Raschbacher gentoo-dev

2003-05-17 17:06:06 UTC

hi!
i couldn't emerge lilypond iwth tetex 1.x .. worked fine with 2.0.2 maybe the
dep should be updated [didn't want to mess with it myself ..]

regards

Comment 1 Michael Ossmann 2003-05-25 19:13:08 UTC

Works for me with tetex-1.0.7-r12.  Have you tried the lilypond-1.6.9 ebuild?

Comment 2 Mike Gardiner (RETIRED) gentoo-dev

2003-09-20 00:14:53 UTC

if the case is that lilypond-1.6.9 needs tetex-1, and higher than than could have tetex-2 or higher, we'll just sharpen up the dependencies.

Comment 3 Mike Gardiner (RETIRED) gentoo-dev

2003-10-08 04:20:03 UTC

Mike I think you were our resident lilypond'er, any chance you could take
a quick look at this ? thanks.

Comment 4 Michael Ossmann 2003-10-08 12:39:09 UTC

Hmmm.  I'm pretty certain this bug was against lilypond-1.6.6.ebuild which
is still the current ebuild in the tree although it is getting pretty old.
 I just tried "ebuild lilypond-1.6.6.ebuild compile" and it worked fine twice.
 I tried it once with tetex-2.0.2-r1 and once with tetex-1.0.7-r13.  It also
worked for me with tetex-1.0.7-r12 back in May.

I think we can chalk this one up to a quirk of the reporter's system unless
Thomas or anyone else can provide us with more information (output from failure,
emerge info, etc.) about the bug.  Anyone?

Comment 5 Mike Gardiner (RETIRED) gentoo-dev

2003-10-08 19:54:33 UTC

I think unfortunately it ended up going dormant, and without more info there's
not much we can do. Mike, thanks for your time, we appreciate you being able
to look at this stuff, so thankyou.