cvs commit: ports/ports-mgmt/portupgrade-devel Makefile
itetcu at FreeBSD.org
Tue Jul 1 15:51:12 UTC 2008
On Tue, 1 Jul 2008 14:02:54 +0000 (UTC)
Sergey Matveychuk <sem at FreeBSD.org> wrote:
> sem 2008-07-01 14:02:54 UTC
> FreeBSD ports repository
> Modified files:
> ports-mgmt/portupgrade-devel Makefile distinfo
> Removed files:
> ports-mgmt/portupgrade-devel/files patch-bin-portupgrade
> - Update to 2.4.4
> Revision Changes Path
> 1.259 +1 -2 ports/ports-mgmt/portupgrade-devel/Makefile
> 1.180 +3 -3 ports/ports-mgmt/portupgrade-devel/distinfo
> 1.18 +0 -23
> ports/ports-mgmt/portupgrade-devel/files/patch-bin-portupgrade (dead)
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 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:
NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_PACKAGE=yes.
The error which triggered this email is bellow followed by the link to the
full log and explanations about the testing process.
building portupgrade-devel-2.4.4 in directory /var/tinderbox/7-STABLE-FTP
maintained by: sem at FreeBSD.org
building for: 7.0-STABLE amd64
port directory: /usr/ports/ports-mgmt/portupgrade-devel
Makefile ident: $FreeBSD: ports/ports-mgmt/portupgrade-devel/Makefile,v 1.259 2008/07/01 14:02:53 sem Exp $
prefixes: LOCALBASE=usr/local X11BASE=usr/local
NO* env vars: NOPORTDOCS=yes NOPORTEXAMPLES=yes NOPORTDATA=yes
build started at Tue Jul 1 14:39:41 UTC 2008
====================<phase 7: make package>====================
===> Building package for portupgrade-devel-2.4.4
Creating package /tmp/packages/All/portupgrade-devel-2.4.4.tbz
Registering depends: ruby18-bdb-0.6.4 db41-4.1.25_4 perl-5.8.8_1 ruby-126.96.36.199_4,1.
Registering conflicts: portupgrade-[0-9]*.
Creating bzip'd tar ball in '/tmp/packages/All/portupgrade-devel-2.4.4.tbz'
=== Checking filesystem state
list of extra files and directories in / (not present before this port was installed but present after it was deinstalled)
15103531 4 drwxr-xr-x 4 root wheel 512 Jul 1 14:40 usr/local/share/examples/pkgtools
15103532 4 drwxr-xr-x 2 root wheel 512 Jul 1 14:40 usr/local/share/examples/pkgtools/bash
15103533 12 -r--r--r-- 1 root wheel 4499 Jul 1 14:40 usr/local/share/examples/pkgtools/bash/complete.sample
15103534 4 drwxr-xr-x 2 root wheel 512 Jul 1 14:40 usr/local/share/examples/pkgtools/tcsh
15103535 4 -r--r--r-- 1 root wheel 667 Jul 1 14:40 usr/local/share/examples/pkgtools/tcsh/complete.sample
build of /usr/ports/ports-mgmt/portupgrade-devel ended at Tue Jul 1 14:40:06 UTC 2008
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
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).
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:
Please use the right pairs like:
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 at FreeBSD.org, PGP Key ID 057E9F8B493A297B
More information about the cvs-ports