Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 8 Jun 2008 02:55:20 +0300
From:      "QA Tindy (Ion-Mihai Tetcu)" <itetcu@FreeBSD.org>
To:        Mark Linimon <linimon@FreeBSD.org>
Cc:        cvs-ports@FreeBSD.org, Mark Linimon <linimon@FreeBSD.org>, cvs-all@FreeBSD.org, ports-committers@FreeBSD.org
Subject:   Re: cvs commit: ports/ports-mgmt/portmk/Mk bsd.port.mk
Message-ID:  <20080608025520.6fd285ae@it.buh.tecnik93.com>
In-Reply-To: <200806072351.m57Np0lS088942@repoman.freebsd.org>
References:  <200806072351.m57Np0lS088942@repoman.freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 7 Jun 2008 23:51:00 +0000 (UTC)
Mark Linimon <linimon@FreeBSD.org> wrote:

> linimon     2008-06-07 23:51:00 UTC
> 
>   FreeBSD ports repository
> 
>   Modified files:
>     ports-mgmt/portmk/Mk bsd.port.mk 
>   Log:
>   Catch up with master 1.593.
>   
>   Revision  Changes    Path
>   1.73      +9 -1      ports/ports-mgmt/portmk/Mk/bsd.port.mk
> 
Hi,


You receive this email if you are either the maintainer of the port or if you
recently committed to it. If the error is already fixed please ignore this
email; if you submit a PR to fix it CC me and I'll commit it ASAP.

The error which triggered this email is bellow followed by explanations about
the testing process.


====================<phase 6: make install>====================
add_pkg
===>  Installing for portmk-0.1.1
===>   Generating temporary packing list
===>  Checking if ports-mgmt/portmk already installed
Port ports-mgmt/portmk has been successfully installed.

To activate the alternate bsd.port.mk version, do

  cd /usr/ports/ports-mgmt/portmk; make activate

To build a port with the classic bsd.port.mk version, do

  omake <... other args ...>

Documentation is available at

  /usr/local/share/doc/portmk/ReadMe

===>   Registering installation for portmk-0.1.1
================================================================
====================<phase 7: make package>====================
===>  Building package for portmk-0.1.1
Creating package /tmp/packages/All/portmk-0.1.1.tbz
Registering depends:.
Creating bzip'd tar ball in '/tmp/packages/All/portmk-0.1.1.tbz'
Deleting portmk-0.1.1
================================================================

=== Checking filesystem state
list of extra files and directories in / (not present before this port was installed but present after it was deinstalled)
15167895        4 drwxr-xr-x    2 root             wheel                 512 Jun  7 23:52 usr/local/share/doc/portmk
15167897        4 -r--r--r--    1 root             wheel                1362 Jun  7 23:52 usr/local/share/doc/portmk/ReadMe
15167899        4 -r--r--r--    1 root             wheel                  94 Jun  7 23:52 usr/local/share/doc/portmk/ChangeLog
15167901        8 -r--r--r--    1 root             wheel                2851 Jun  7 23:52 usr/local/share/doc/portmk/Features
15167904        4 -r--r--r--    1 root             wheel                  93 Jun  7 23:52 usr/local/share/doc/portmk/KnownIssues
================================================================
build of /usr/ports/ports-mgmt/portmk ended at Sat Jun  7 23:52:29 UTC 2008


http://t64.tecnik93.com/errors/7-STABLE-FTP/portmk-0.1.1.log


These emails are generated in one of the following cases:
- an automated build was scheduled because the port was touched in CVS
- the periodic QA build has reached it.
- the port was scheduled because it is a dependency of a port from the cases
above.
There is no fixed interval for this; if other ports depend on it you will
receive this emails more often since testing those other ports is made
impossible by this port being broken. Efforts are made to restrict the number
of outgoing emails to one/port/week for QA or dependency builds (but not for
commit-triggered builds; if you commit 3 times in 5 minutes to the same port
and the first 2 versions fail you'll receive 2 emails).

The builds are done under tinderbox-2.4.3, on 7-STABLE on amd64, with
tinderd_flags="-nullfs -plistcheck -onceonly" and ccache support, with the
official up-to-date Ports Tree (for commit-triggered builds the files are
fetched via CVSWeb), with the following vars set:
FORCE_PACKAGE=yes, NOPORTDOCS=yes,  NOPORTEXAMPLES=yes, NOPORTDATA=yes.

When you fix install/plist errors please bear in mind that each of the 3 NO*
vars controls the installation of different type of files, so constructs like:
.ifndef NOPORTDOCS
        @${MKDIR} ${DATADIR}
        ...
.endif
        or
%%PORTDOCS%%%%EXAMPLESDIR%%/some_example_file
are WRONG.
Please use:
%%PORTDOCS%%%%DOCSDIR%%
%%PORTEXAMPLES%%%%EXAMPLESDIR%%
%%PORTDATA%%%%DATADIR%%


Thanks for your work on making FreeBSD better,

-- 
IOnut - Un^d^dregistered ;) FreeBSD "user"
  "Intellectual Property" is   nowhere near as valuable   as "Intellect"
FreeBSD committer -> itetcu@FreeBSD.org, PGP Key ID 057E9F8B493A297B



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080608025520.6fd285ae>