From owner-freebsd-questions Wed May 15 16:25:47 2002 Delivered-To: freebsd-questions@freebsd.org Received: from thick.mail.pipex.net (thick.mail.pipex.net [158.43.192.95]) by hub.freebsd.org (Postfix) with SMTP id 1473B37B40C for ; Wed, 15 May 2002 16:25:34 -0700 (PDT) Received: (qmail 11573 invoked from network); 15 May 2002 22:36:17 -0000 Received: from userhh092.dsl.pipex.com (HELO ThisAddressDoesNotExist) (62.190.215.92) by smtp-3.dial.pipex.com with SMTP; 15 May 2002 22:36:17 -0000 Subject: Re: pkg_version -v returns: succeeds port for pdksh-5.2.14 From: "S. Roberts" Reply-To: sroberts@dsl.pipex.com To: Erik Trulsson Cc: FreeBSD-Questions In-Reply-To: <20020515223605.GA23652@student.uu.se> References: <1021497989.41001.27.camel@Demon.Strobe.org> <20020515222341.GA23483@student.uu.se> <1021501417.41001.38.camel@Demon.Strobe.org> <20020515223605.GA23652@student.uu.se> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-MSObnpp9OGx6eR94fv23" X-Mailer: Ximian Evolution 1.0.5 Date: 15 May 2002 23:34:47 +0100 Message-Id: <1021502087.41001.41.camel@Demon.Strobe.org> Mime-Version: 1.0 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --=-MSObnpp9OGx6eR94fv23 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Good deal. If its appeared already, I'll just hang tight for a bit and see if it gets sorted in the meanwhile. If not, I'll try sending an e-mail off to him. Thanks again for the assistance and information. Stacey On Wed, 2002-05-15 at 23:36, Erik Trulsson wrote: > On Wed, May 15, 2002 at 11:23:36PM +0100, S. Roberts wrote: > > Hey Erik, > > Thanks for the quick feedback. I was beginning to worry about havin= g > > to re-run something or the other. > >=20 > > So following on from "not worrying about this", does this anomaly get > > sorted out by itself at some point? Meaning.., should I be thinking of > > contacting the port maintainer so as to alert them to this ocurence? >=20 > It gets sorted out when the version number of the pdksh port is bumped > to something which pkg_version considers as newer than 5.2.14 > (5.2.14p2 could be a good new version number.) > If he is not already aware of this, then contacting the port maintainer > might be a good idea, yes. > (I saw a report about this on the freebsd-ports list before, so the > maintainer might already be aware of this.) >=20 > >=20 > > Just meaning to help 'em out in any way I can for now. > >=20 > > Stacey > >=20 > > On Wed, 2002-05-15 at 23:23, Erik Trulsson wrote: > > > On Wed, May 15, 2002 at 10:26:29PM +0100, S. Roberts wrote: > > > > Hi There, > > > > Strange one here for me. > > > >=20 > > > > I've just cvsup'd my ports tree and then ran pkg_version -v and got= this > > > > for one of my installed ports: > > > >=20 > > > > pdksh-5.2.14 > succeeds port (port has 5.2.1= 4.p2) > > > >=20 > > > > Never seen that before! Could someone who know more about this give= an > > > > explanation, please? Man pkg_version says this about that string re= sult: > > > >=20 > > > > > The installed version of the package is newer than the current > > > > version.This situation can arise with an out-of-date index fil= e, or > > > > when testing new ports. > > > >=20 > > > > Taking both explanations for this case: > > > > 1] I always run portsdb -Uu after cvsup'ing the ports tree, I would= n't > > > > have thought that my Index file was out-of-date. > > > > 2] Not sure about the "testing nrew ports" either, I'm not (oknowin= gly) > > > > actively testing new ports. > > > >=20 > > > > Suggestions? > > >=20 > > > Nothing to worry about. > > >=20 > > > The problem is simply that the version number for the newest version = of > > > the pdksh port (5.2.14.p2) is counted as "older" than the old version > > > number (5.2.14) by pkg_version. > > >=20 > > > So the bug is in the version number given to the latest update of the > > > pdksh port and not in anything you did. > > >=20 > > >=20 > > >=20 > > > --=20 > > > > > > Erik Trulsson > > > ertr1013@student.uu.se > > --=20 > > Stacey Roberts B.Sc. (HONS) Computer Science > > Network Systems Engineer >=20 >=20 >=20 > --=20 > > Erik Trulsson > ertr1013@student.uu.se >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message --=20 Stacey Roberts B.Sc. (HONS) Computer Science Network Systems Engineer --=-MSObnpp9OGx6eR94fv23 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Good deal. If its appeared already, I'll just hang tight for a bit and see if it gets sorted in the meanwhile. If not, I'll try sending an e-mail off to him. Thanks again for the assistance and information. Stacey On Wed, 2002-05-15 at 23:36, Erik Trulsson wrote: > On Wed, May 15, 2002 at 11:23:36PM +0100, S. Roberts wrote: > > Hey Erik, > > Thanks for the quick feedback. I was beginning to worry about havin= g > > to re-run something or the other. > >=20 > > So following on from "not worrying about this", does this anomaly get > > sorted out by itself at some point? Meaning.., should I be thinking of > > contacting the port maintainer so as to alert them to this ocurence? >=20 > It gets sorted out when the version number of the pdksh port is bumped > to something which pkg_version considers as newer than 5.2.14 > (5.2.14p2 could be a good new version number.) > If he is not already aware of this, then contacting the port maintainer > might be a good idea, yes. > (I saw a report about this on the freebsd-ports list before, so the > maintainer might already be aware of this.) >=20 > >=20 > > Just meaning to help 'em out in any way I can for now. > >=20 > > Stacey > >=20 > > On Wed, 2002-05-15 at 23:23, Erik Trulsson wrote: > > > On Wed, May 15, 2002 at 10:26:29PM +0100, S. Roberts wrote: > > > > Hi There, > > > > Strange one here for me. > > > >=20 > > > > I've just cvsup'd my ports tree and then ran pkg_version -v and got= this > > > > for one of my installed ports: > > > >=20 > > > > pdksh-5.2.14 > succeeds port (port has 5.2.1= 4.p2) > > > >=20 > > > > Never seen that before! Could someone who know more about this give= an > > > > explanation, please? Man pkg_version says this about that string re= sult: > > > >=20 > > > > > The installed version of the package is newer than the current > > > > version.This situation can arise with an out-of-date index fil= e, or > > > > when testing new ports. > > > >=20 > > > > Taking both explanations for this case: > > > > 1] I always run portsdb -Uu after cvsup'ing the ports tree, I would= n't > > > > have thought that my Index file was out-of-date. > > > > 2] Not sure about the "testing nrew ports" either, I'm not (oknowin= gly) > > > > actively testing new ports. > > > >=20 > > > > Suggestions? > > >=20 > > > Nothing to worry about. > > >=20 > > > The problem is simply that the version number for the newest version = of > > > the pdksh port (5.2.14.p2) is counted as "older" than the old version > > > number (5.2.14) by pkg_version. > > >=20 > > > So the bug is in the version number given to the latest update of the > > > pdksh port and not in anything you did. > > >=20 > > >=20 > > >=20 > > > --=20 > > > > > > Erik Trulsson > > > ertr1013@student.uu.se > > --=20 > > Stacey Roberts B.Sc. (HONS) Computer Science > > Network Systems Engineer >=20 >=20 >=20 > --=20 > > Erik Trulsson > ertr1013@student.uu.se >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message - --=20 Stacey Roberts B.Sc. (HONS) Computer Science Network Systems Engineer -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.8 iQA/AwUBPOLihfdn4A8qiCO5EQLfgwCcDrFONZs5EAwJV1RVtj/Ra9XoxyAAoI3J Rd7MudM/234Z5u0SVv5Iq88o =mlC2 -----END PGP SIGNATURE----- --=-MSObnpp9OGx6eR94fv23-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message