"Gimp-manual-ps" removal enables "make INDEX" to work (was: "make INDEX" broken this morning?")

"Gimp-manual-ps" removal enables "make INDEX" to work (was: "make INDEX" broken this morning?")

Post by Young Coo » Thu, 20 Feb 2003 12:12:05



Hello again -

I've started a fresh thread on this one because it's a fresh take on my
earlier post.

After four separate downloads of INDEX, and having each "make" fail, I
finally looked at the resulting INDEX file (what I should have done in the
first instance) and found it to be about 760K instead of the 3Megs it had
been after download.  The error listed at the top of the file had to do
with the port "gimp-manual-ps", saying that the "PS" was not a  recognized
document type, that only HTML and PDF were recognized document types (I
know, I should have saved that exact message but it's vapor now).  After
CVSUP-ing again, and then placing "gimp-manual-ps" in the trash, I was then
able to do a typically clean make of the index.  No problems.

Now here's the question: if this "gimp-manual-ps" port is not new, then how
is it that the document type is not recognized now when it was just a
couple of days ago?  I don't know where the change has occurred, whether it
was in one of the supporting ports or whether it's in my system somewhere.
I'm currently going on the assumption that it's in my system, but I don't
really know where to look right now.

That's my workaround anyway - to delete the "gimp-manual-ps" port before
making the index.

Anyone else seen this?

YC

 
 
 

"Gimp-manual-ps" removal enables "make INDEX" to work (was: "make INDEX" broken this morning?")

Post by Young Coo » Fri, 21 Feb 2003 16:18:46


This is an addendum to my last message on this topic: I was able to get the
error to appear again, and I'm posting the relevant part of the resulting
"INDEX" file, at the top:

*** Error code 1|||||||
ERROR: invalid value for DOCFORMAT: "PS"|||||||
Possible values are: HTML, PDF.|||||||
Stop in /usr/ports/graphics.|||||||
Stop in /usr/ports.|||||||
Stop.

At the end of this file, the last item in the generated index is
"gimp-manual-pdf".

Again - without the "gimp-manual-ps" port the index compiles OK, and if the
offending port is there the index barfs at the same spot.  And that's since
Monday the 17th.

YC


Quote:> Hello again -

> I've started a fresh thread on this one because it's a fresh take on my
> earlier post.

> After four separate downloads of INDEX, and having each "make" fail, I
> finally looked at the resulting INDEX file (what I should have done in the
> first instance) and found it to be about 760K instead of the 3Megs it had
> been after download.  The error listed at the top of the file had to do
> with the port "gimp-manual-ps", saying that the "PS" was not a  recognized
> document type, that only HTML and PDF were recognized document types (I
> know, I should have saved that exact message but it's vapor now).  After
> CVSUP-ing again, and then placing "gimp-manual-ps" in the trash, I was
> then
> able to do a typically clean make of the index.  No problems.

> Now here's the question: if this "gimp-manual-ps" port is not new, then
> how is it that the document type is not recognized now when it was just a
> couple of days ago?  I don't know where the change has occurred, whether
> it was in one of the supporting ports or whether it's in my system
> somewhere. I'm currently going on the assumption that it's in my system,
> but I don't really know where to look right now.

> That's my workaround anyway - to delete the "gimp-manual-ps" port before
> making the index.

> Anyone else seen this?

> YC


 
 
 

"Gimp-manual-ps" removal enables "make INDEX" to work (was: "make INDEX" broken this morning?")

Post by Kris Kennawa » Sat, 22 Feb 2003 12:00:02



> *** Error code 1|||||||
> ERROR: invalid value for DOCFORMAT: "PS"|||||||
> Possible values are: HTML, PDF.|||||||
> Stop in /usr/ports/graphics.|||||||
> Stop in /usr/ports.|||||||
> Stop.

Hmm.  Looks like INDEX is indeed broken..my tinderbox noticed this, but
I think the failure mail was being bounced by freebsd.org because it was
too big :(

I've mailed the committer who broke this.

Kris

 
 
 

"Gimp-manual-ps" removal enables "make INDEX" to work (was: "make INDEX" broken this morning?")

Post by Young Coo » Sat, 22 Feb 2003 13:45:34


Thanks, Kris, for the ack.

I monitor both the "freebsd-ports" and the "freebsd-stable" mailing lists on
their respective web pages
for news; I've elected to not subscribe at this time as I get enough e-mail
already, though I'm wondering how much faster this would have been picked up
if I had written about it there?

YC



> > *** Error code 1|||||||
> > ERROR: invalid value for DOCFORMAT: "PS"|||||||
> > Possible values are: HTML, PDF.|||||||
> > Stop in /usr/ports/graphics.|||||||
> > Stop in /usr/ports.|||||||
> > Stop.

> Hmm.  Looks like INDEX is indeed broken..my tinderbox noticed this, but
> I think the failure mail was being bounced by freebsd.org because it was
> too big :(

> I've mailed the committer who broke this.

> Kris

 
 
 

"Gimp-manual-ps" removal enables "make INDEX" to work (was: "make INDEX" broken this morning?")

Post by Kris Kennawa » Sat, 22 Feb 2003 15:00:02



> Thanks, Kris, for the ack.

> I monitor both the "freebsd-ports" and the "freebsd-stable" mailing lists on
> their respective web pages
> for news; I've elected to not subscribe at this time as I get enough e-mail
> already, though I'm wondering how much faster this would have been picked up
> if I had written about it there?

It would have been quicker.  Most FreeBSD committers don't read this
newsgroup.  If I hadn't been reading it, chances are your report would
never have reached the appropriate person.

Kris

 
 
 

"Gimp-manual-ps" removal enables "make INDEX" to work (was: "make INDEX" broken this morning?")

Post by Young Coo » Mon, 24 Feb 2003 04:58:36


I thank you for that: next time I'll go straight there.

YC

Earlier in the linear time track, on Thursday 20 February 2003 10:00 pm,


> It would have been quicker.  Most FreeBSD committers don't read this
> newsgroup.  If I hadn't been reading it, chances are your report would
> never have reached the appropriate person.

> Kris