Recently, we (ports) committers are keep receiving kris(bot) mailS. These mails are about build errors.

One of them is ‘fail of german/BBBike’, and inside the mail, the problem is not BBBike itself. So, I’m not the maintainer, why I received it? Because BBBike depends on p5-Text-Balanced, which was just upgraded to 2.0.0 by me. And in the Makefile I add
BUILD_DEPENDS= ${SITE_PERL}/${PERL_ARCH}/version.pm:${PORTSDIR}/devel/p5-version
These causes the dependent ports (BBBike) error, because it still need version.pm in run-time. Thus, I add
RUN_DEPENDS= ${BUILD_DEPENDS} to avoid the problem.

Add to del.icio.us - Digg this article

Today’s best News

The winner is ‘HEADS UP: FreeBSD 4.11, 6.0 EoLs coming soon‘.

I just felt frustrated when dealing with something 4.x….

Add to del.icio.us - Digg this article

mx1 dead again?

Enough… Let’s take a break….

Dec 29 16:56:42 xxxxxxx postfix/smtp[53186]: A20932874D: to=, relay=none, delay=22077, delays=22047/0.06/30/0, dsn=4.4.1, status=deferred (connect to mx1.freebsd.org[ip.you.do.nt.know]: Operation timed out)

As a ports committer, that means I have to commit myself instead of taking(or submitting) new PRs. Hmm… that’s not that bad ;)

Add to del.icio.us - Digg this article

The best reference is always PR.
Let’s take a look at ports/96304.
See the “post-patch:” section:
post-patch:

@${PERL} -pi -e 's/^our (Ww+);/use vars q($$1);/o;' -e 's/^ours+(Ww+)(?!;)/use vars q($$1); $$1/o;' -e 'undef $$_ if /^s*(no|use) warnings/o;' files_you_need_to_patch_for_perl_5.00503
Okay, that should fix lots of ports which broken in perl 5.00503. Examples of error like:

Could not eval ’

package ExtUtils::MakeMaker::_version; no strict; local $VERSION; $VERSION=undef; do { our $VERSION = “0.003”; }; $VERSION ’ in lib/XXX/YYY.pm: Can’t modify subroutine entry in scalar assignment at (eval 6) line 7, at EOF

But the best way, IMHO, is mark IGNORE and encourage users to upgrade their perl version to latest one :)

Add to del.icio.us - Digg this article

[ports] devel/porttools

I just wondering why some people don’t like to use devel/porttools to generate ports/ PRs and use devel/portlint to test your ports. I’m not talking about those who didn’t know about devel/porttools or devel/portlint.

Just install it. Type ‘man port’ and ‘man portlint’, you will know how they help you (to generate qualified PR).
The most used commands:
port test
port diff
port submit

Try it, please.

Add to del.icio.us - Digg this article

ProblemReport 100,000

It’s a doc/ PR, good. And that’s what I want :)

Continue reading ‘ProblemReport 100,000’
Add to del.icio.us - Digg this article

I’ve made top with jail id support. I start to think adding similar functions to other programs.

fstat is the victim. I decide to let fstat can accept jid and then display active files according to the specified jid.

Here comes the patch.

To apply this patch, you must rebuild your kernel.

% cd /usr/src; patch < patch_fstat_jid
% make kernel
...reboot with new kernel
% cd /usr/src/lib/libkvm; make clean install clean
% cd /usr/src/usr.bin/fstat; make clean install clean
... to make other program sync
% cp -f /usr/src/sys/sys/sysctl.h /usr/include/sys/

If you see any error appear, please inform me :)

How to use?

% fstat -j

NOTE, this patch will be send-pr-ed sooner or later. But I need your test first. :)

UPDATE 2006/06/12: Thanks to Roberto Lima for ‘cp -f /usr/src/sys/sys/sysctl.h /usr/include/sys/’ :)
UPDATE 2006/06/30: pr is here.

Add to del.icio.us - Digg this article

Daniel Gerzo asked if top can have a column to display jid last week. So I spend my lovely weekend wink to do the job.

Here is the patch. How to apply?

% cd /usr/src
% patch < patch_top_jid2
% cd /usr/src/usr.bin/top; make clean install clean

Then try either
% top -j
or toggle with ‘j’ when you’re using top.

NOTE: since this patch is not committed (yet), there is no documentation describe about that. :)

Add to del.icio.us - Digg this article

Just as what ports/97985 said, serveral gnome-related ports renamed. How it caught my attention is the renaming from pkgconfig to pkg-config, since my tinderbox reported lots of error. But fine, now I solve it (by simply rebuild them all).

A question arised. Why these changes didn’t mention in ports/UPDATING?

Add to del.icio.us - Digg this article

Hurry Porter Project

Don’t follow me? Read this.

Add to del.icio.us - Digg this article