Bug 157406

Comment 1 Mark Linimon 2011-05-30 00:29:12 UTC

Responsible Changed
From-To: freebsd-doc->doceng

This is really a port owned by doceng.

Comment 2 Marc Fonvieille 2011-06-02 10:47:15 UTC

On Sun, May 29, 2011 at 10:39:01PM +0000, J. Altman wrote:
> 
> 
> >Description:
> First, please see my query to -questions for some more background:
> 
> http://lists.freebsd.org/pipermail/freebsd-questions/2011-May/230423.html
> 
> This is the content of my last message to -questions, in which I outline where I think the problems are for the handbook only:
> 
> After reading the thread referenced above, and looking at the output
> of my build, I noticed that the build was failing in different areas.
> So I decided to run make on the port multiple times, and eventually
> the port installed successfully. However, the port in my tree (dated #
> $FreeBSD: ports/misc/freebsd-doc-en/Makefile,v 1.36 2011/05/22
> 14:28:49 blackend Exp $) in a fresh tree made only through
> 2010, according to the copyright at the top of the
> handbook. Individual files in that doc tree were variously dated; the
> newest being 8/2010.
> 
> So I ran make, multiple times, on the source; and that gave me a doc
> tree dated 2011. Most of the files there were dated 5/29/11. A few
> exceptions were found in image files dated 3/2010, which all loaded in
> SeaMonkey, except for some files in: advanced-networking, security,
> vinum, geom. I may have missed others in other books.
> 
> To summarize:
> 
> 1) It appears that make is, in this case, a hammer that must be
> applied more than once to either the source or the port.
> 
> 2) Not all images are seen as valid, and according to make may have
> bad magic numbers. If building from source is used on a fresh tree, it
> may be possible to have make ignore all the errors by using the -k
> flag.
> 
> 3) I have no idea how things will go with an upgrade to the doc
> source; I normally use portupgrade, so I suppose I will find out
> later.
>

Sorry I have problem to understand what you really mean.
I tried to build last misc/freebsd-doc-en multiple times and it never
failed.
The fact some files appear to be from 2010 or older is normal since
files are not always modified between two or more new port release.
Each port is based on a specific distfile (see
misc/freebsd-doc-en/distinfo) it's impossible (or quite) to get
different files each time you try to build a port.

So we need more details, a full output of the whole operation:

- uname -a
- pkg_delete docproj\*
- full deletion of your current ports tree;
- csup a new ports tree;
- cd /usr/ports/misc/freebsd-doc-en && make install clean

-- 
Marc

NB: I apologize for the lateness of my reply; but I needed to think
about your request.

On Thu, Jun 02, 2011 at 11:47:15AM +0200, Marc Fonvieille wrote:
> 
> Sorry I have problem to understand what you really mean.

Don't be sorry; I find it to be a bit odd and convoluted as well.

> So we need more details, a full output of the whole operation:
> 
> - uname -a
> - pkg_delete docproj\*
> - full deletion of your current ports tree;
> - csup a new ports tree;
> - cd /usr/ports/misc/freebsd-doc-en && make install clean

I've thought about this; and feel I cannot do it. I spent a
non-trivial amount of time just getting a local copy of the
documentation, and don't want to spend several hours doing it again.

I regret not being able to help, but I feel it's more than I can do
right now.

However, if I encounter more problems (for instance, if an upgrade to
the documentation tree fails) then I will do what you ask and follow
up via the bug reporting system.

So I suppose this current ticket should be closed.

Thanks for your help, and best regards,

Joe

I ran into this bug with a fresh install of the 8.2 Release on the Sparc64
platform.

 

Steps leading to this occurring:

 

1)       Minimal install from CD

2)       Used sysinstall to add some utilities (nano and bash) and the docs

3)       Found the "Using the Ports Collection" section of the handbook and
decided to use portmaster on this server.

4)       Installed and ran portsnap and portaudit without issue (did this on
June 9, 2011)

5)       Did portmaster -a which needed to run a couple times (bash and
freebsd-doc-en needed updated, freebsd-doc required additional dependencies)

6)       Ran into this problem and attempted multiple "corrections" (make
-k, repeat multiple makes, etc) that were suggested in similar problem
scenarios without a change until I was able to get past it with the method
below

 

What corrected it:

1)       Reran portsnap yesterday (June 13, 2011)

2)       Found additional upgrades for packages ghostscript, tatex, tiff,
and 1 or 2 more that I don't recall (all of the 4 or 5 ports were installed
as requirements for freebsd-doc-en upgrade that was ran on the 9th and into
the 10th.)

3)       Ran portmaster -ai and skipped the freebsd-doc-en install (I didn't
the first time as portmaster aborted after doing this one first) and
completed the additional upgrades that were found.

4)       Ran portmaster -ai again and upgraded freebsd-doc-en without
additional issues.

 

Unfortunately I was not capturing the session output and I do not have the
details that you'll likely require.  Hopefully this is of assistance to
someone.

 

Mike

 

Comment 5 Hiroki Sato 2011-06-15 16:32:09 UTC

State Changed
From-To: open->closed

Seems this was a temporary problem.