Date: Wed, 9 Jun 2004 11:55:46 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: Drew Tomlinson <drew@mykitchentable.net> Cc: webmaster@lightningfire.net Subject: Re: AWSTATS Error & Resolution Message-ID: <20040609105545.GC12520@happy-idiot-talk.infracaninophile.co.uk> In-Reply-To: <40C63F38.903@mykitchentable.net> References: <40C63F38.903@mykitchentable.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--jy6Sn24JjFx/iggw
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, Jun 08, 2004 at 03:35:36PM -0700, Drew Tomlinson wrote:
> After upgrading perl from 5.8.2 to 5.8.4, following the instructions in=
=20
> /usr/ports/UPDATING, I found awstats-6.0_1 no longer worked. I ran=20
> awstats.pl interactively and received the following error:
>=20
> Bizarre copy of ARRAY in aassign at /path/to/awstats.pl line 8707
>=20
> After some checking, I found this issue was fixed in awstats.pl revision=
=20
> 1.747. I downloaded the most current revision (1.755) and replaced the=
=20
> revision that's included with the port. This seems to solve the=20
> problem. YMMV.
>=20
> Is it appropriate to send a problem report about this? I've never sent=
=20
> one so I want to be sure before bugging someone.
>=20
> Hopefully this post will save others from having to research and resolve=
=20
> this issue.
You aren't the only one to notice this: it's being discussed over on
freebsd-ports@... at the moment. See the thread that starts with:
http://lists.freebsd.org/pipermail/freebsd-ports/2004-June/013104.html
which generally means a fix will soon be forthcoming.
Generally in these sort of cases your first point of contact should be
the port's maintainer. Find that by:
% cd /usr/ports/www/awstats
% make -V MAINTAINER
Now just sending an e-mail to the maintainer usually suffices, and
most maintainers will be happy to fix things and help you out
generally.
However, if the maintainer has an @FreeBSD.org address (including
various mailing list addresses like x11@FreeBSD.org, perl@FreeBSD.org,
ports@FreeBSD.org) then you can use send-pr(1) to send in a bug report
- preferably including a fix. If the port is unmaintained
(ie. maintainer is ports@FreeBSD.org) then you may well get asked to
become the maintainer... Also use send-pr(1) if e-mail to the
maintainer bounces or you get no reply after a reasonable time
(ie. two weeks) -- mention the problem in the PR you send. See
http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/makef=
ile-maintainer.html
Cheers,
Matthew
--=20
Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks
Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614 Bucks., SL7 1TH UK
--jy6Sn24JjFx/iggw
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)
iD8DBQFAxuyxiD657aJF7eIRAngMAJ9Ye/s2UrX5gYwNQik0ouju5sGZrgCfZG5U
IAojP6oFJmZvvkJUC4XHZw8=
=yLvK
-----END PGP SIGNATURE-----
--jy6Sn24JjFx/iggw--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040609105545.GC12520>