public inbox for gentoo-perl@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Cummings <mcummings@gentoo.org>
To: gentoo-perl@lists.gentoo.org
Subject: Re: [gentoo-perl] Perl ebuilds needing updates (19)
Date: Mon, 23 Jan 2006 08:08:46 -0500	[thread overview]
Message-ID: <1138021726.3161.14.camel@localhost> (raw)
In-Reply-To: <20060123073931.E838F14C@gnosis.datanode.net>

[-- Attachment #1: Type: text/plain, Size: 1241 bytes --]

For what it's worth, I've got a new version of the script that generates
this in the works. Of those reported here:

On Mon, 2006-01-23 at 07:39 +0000, Michael Cummings wrote:
>       AxKit      1.6.2      1.62
Same version, this particular script just isn't smart enough to see
it :)

>       Gnome2      1.00      1.023
Not sure - we have gnome2-perl-1.023 in the tree

>       Net::SNMP      5.2.0      v5.2.0
silly script

>       RPC::XML      0.58      1.35
The mysterious one - not sure where it's getting 1.35 from, 0.58 is
really the current one...

>       Test::Builder::Tester      1.01      1.02

misleading - Test::Builder::Tester was re-encapsulated in Test-Simple
recently, so although there is a newer version of the module, its
actually part of the Test-Simple dist.

>       Unix::Syslog      0.100      0.99
Oddly enough, cpan doesn't report the 0.100 version even though it's
there...

>       Video::Info      0.993      0.999
0.999 was sent out without most of the module's contents - 0.993 is
actually the last good copy of it.

> Total packages suspected as outdated: 19
Really packages suspected as outdated: 12. Still, better than the 100+
from a week or so ago :)

~mcummings

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2006-01-23 13:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-23  7:39 [gentoo-perl] Perl ebuilds needing updates (19) Michael Cummings
2006-01-23 13:08 ` Michael Cummings [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1138021726.3161.14.camel@localhost \
    --to=mcummings@gentoo.org \
    --cc=gentoo-perl@gentoo.org \
    --cc=gentoo-perl@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox