Re: time for perl 5.10.x in devel?

2007-11-28 Thread Jan Pazdziora
On Tue, Nov 27, 2007 at 05:16:49PM -0500, Tom spot Callaway wrote:
 
 Tom Callaway (aka, no one asked for it explicitly)
 
   * perl-Alien-wxWidgets -- Building, finding and using wxWidgets
 binaries
   * perl-AppConfig -- Perl module for reading configuration files
   * perl-Array-Compare -- Perl extension for comparing arrays
   * perl-Cairo -- Perl interface to the cairo library
   * perl-Carp-Assert -- Executable comments
   * perl-Carp-Assert-More -- Convenience wrappers around
 Carp::Assert
   * perl-Config-IniFiles -- A module for reading .ini-style
 configuration files
   * perl-Data-Compare -- Compare perl data structures
   * perl-DBD-XBase -- Perl module for reading and writing the dbf
 files 

Ummm -- I've asked for perl-DBD-XBase ...

-- 
Jan Pazdziora
Satellite Engineering, Red Hat

--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list


Re: time for perl 5.10.x in devel?

2007-11-28 Thread Tom spot Callaway

On Wed, 2007-11-28 at 03:58 +0100, Ralf Corsepius wrote:

 Seems to me, as if Fedora doesn't support collective maintainership ://

Its a technicality. There is no difference in rights or permissions
between primary maintainers and comaintainers, except that the packagedb
requires there be a primary.

~spot

--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list


Re: time for perl 5.10.x in devel?

2007-11-28 Thread Patrice Dumas
On Wed, Nov 28, 2007 at 07:40:15AM -0500, Tom spot Callaway wrote:
 
 On Wed, 2007-11-28 at 03:58 +0100, Ralf Corsepius wrote:
 
  Seems to me, as if Fedora doesn't support collective maintainership ://
 
 Its a technicality. There is no difference in rights or permissions
 between primary maintainers and comaintainers, except that the packagedb
 requires there be a primary.

I think that Ralf point is not about having many comaintainers, but
group comaintainers. Looks like the packagedb doesn't allow that. 

--
Pat

--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list


Re: time for perl 5.10.x in devel?

2007-11-28 Thread Ralf Corsepius

On Wed, 2007-11-28 at 14:05 +0100, Patrice Dumas wrote:
 On Wed, Nov 28, 2007 at 07:40:15AM -0500, Tom spot Callaway wrote:
  
  On Wed, 2007-11-28 at 03:58 +0100, Ralf Corsepius wrote:
  
   Seems to me, as if Fedora doesn't support collective maintainership ://
  
  Its a technicality. There is no difference in rights or permissions
  between primary maintainers and comaintainers, except that the packagedb
  requires there be a primary.
 
 I think that Ralf point is not about having many comaintainers, but
 group comaintainers. Looks like the packagedb doesn't allow that. 
Almost. 

What I wanted to find is how Fedora supports and destinguishes:

a) a principal w/ several co-maintainers under his directions
b) free for a specific group with changing members 
  e.g. free for perl-sig, free for FPG, free for sponsors.
c) free for anybody (free for any Fedora all CLA-signors) 
d) orphaned

My understanding of what Spot wrote is: Fedora doesn't support b) and
c). He can't avoid folding them into a).

IMO, this lets appear collective maintainership as a closed
group/intriguing circle, because doesn't let appear such packages as
open for interested volunteers, but implies explicit appointment and
explict knowledge about how somebody made it into such a circle.

Or differently: one year ahead, nobody will remember these packages are
open, because they can't be distinguished from the usual closed
circles maintaining packages otherwise.

Ralf



--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list


Re: time for perl 5.10.x in devel?

2007-11-28 Thread Patrice Dumas
On Wed, Nov 28, 2007 at 02:26:38PM +0100, Ralf Corsepius wrote:
 
 What I wanted to find is how Fedora supports and destinguishes:
 
 a) a principal w/ several co-maintainers under his directions
 b) free for a specific group with changing members 
   e.g. free for perl-sig, free for FPG, free for sponsors.
 c) free for anybody (free for any Fedora all CLA-signors) 
 d) orphaned
 
 My understanding of what Spot wrote is: Fedora doesn't support b) and
 c). He can't avoid folding them into a).

c) is technicaly possible, it corresponds with 
'group members can commit?'
selected. However, in general, having this selected doesn't mean that
the maintainer is really willing to let everybody touch the package.

 Or differently: one year ahead, nobody will remember these packages are
 open, because they can't be distinguished from the usual closed
 circles maintaining packages otherwise.

Right.

Maybe the solution could simply be to be able to add some comments in the
pacakgedb, telling who is really allowed to touch the package?
and select 'group members can commit?'.

--
Pat

--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list


Re: time for perl 5.10.x in devel?

2007-11-28 Thread Ralf Corsepius

On Wed, 2007-11-28 at 14:35 +0100, Patrice Dumas wrote:


 Maybe the solution could simply be to be able to add some comments in the
 pacakgedb, telling who is really allowed to touch the package?
 and select 'group members can commit?'.

IMO, the easiest approach would be to use perl-sig or similar (eg. an
email alias or a packagedb alias (should such thing exist)) as
owner ;)

Ralf


--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list


Re: time for perl 5.10.x in devel?

2007-11-28 Thread Ralf Corsepius

On Wed, 2007-11-28 at 09:25 -0500, Tom spot Callaway wrote:
 On Wed, 2007-11-28 at 14:46 +0100, Ralf Corsepius wrote:
  On Wed, 2007-11-28 at 14:35 +0100, Patrice Dumas wrote:
  
  
   Maybe the solution could simply be to be able to add some comments in the
   pacakgedb, telling who is really allowed to touch the package?
   and select 'group members can commit?'.
  
  IMO, the easiest approach would be to use perl-sig or similar (eg. an
  email alias or a packagedb alias (should such thing exist)) as
  owner ;)
 
 Which, we can't do, without dirty hacks, currently.
 
 You should talk to Toshio about this.
Me? I don't have a problem when the packagedb stuff denotes you to
maintain all these packages all alone, because nobody can distinguish
them from true Spot packages nor when these packages doen't receive
cpancheck from because of this.

This is solely your problem - Sooner or later.

Ralf



--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list


Re: time for perl 5.10.x in devel?

2007-11-28 Thread Tom spot Callaway

On Wed, 2007-11-28 at 15:41 +0100, Ralf Corsepius wrote:
 On Wed, 2007-11-28 at 09:25 -0500, Tom spot Callaway wrote:
  On Wed, 2007-11-28 at 14:46 +0100, Ralf Corsepius wrote:
   On Wed, 2007-11-28 at 14:35 +0100, Patrice Dumas wrote:
   
   
Maybe the solution could simply be to be able to add some comments in 
the
pacakgedb, telling who is really allowed to touch the package?
and select 'group members can commit?'.
   
   IMO, the easiest approach would be to use perl-sig or similar (eg. an
   email alias or a packagedb alias (should such thing exist)) as
   owner ;)
  
  Which, we can't do, without dirty hacks, currently.
  
  You should talk to Toshio about this.
 Me? I don't have a problem when the packagedb stuff denotes you to
 maintain all these packages all alone, because nobody can distinguish
 them from true Spot packages nor when these packages doen't receive
 cpancheck from because of this.
 
 This is solely your problem - Sooner or later.

I don't have any problem with this. They'll show up in cpancheck as
packages that I need to fix. You're the one who is getting worked up
over technical limitations.

~spot

--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list


Re: time for perl 5.10.x in devel?

2007-11-28 Thread Steven Pritchard
On Wed, Nov 28, 2007 at 09:46:32AM -0500, Tom spot Callaway wrote:
 I don't have any problem with this. They'll show up in cpancheck as
 packages that I need to fix. You're the one who is getting worked up
 over technical limitations.

And where would one find this cpancheck that knows how to check the
packagedb?  :-)

Steve
-- 
Steven Pritchard - KS Pritchard Enterprises, Inc.
Email: [EMAIL PROTECTED] http://www.kspei.com/
Phone: (618)624-4440   Mobile: (618)567-7320

--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list


Re: time for perl 5.10.x in devel?

2007-11-28 Thread Ralf Corsepius

On Wed, 2007-11-28 at 09:22 -0600, Steven Pritchard wrote:
 On Wed, Nov 28, 2007 at 09:46:32AM -0500, Tom spot Callaway wrote:
  I don't have any problem with this. They'll show up in cpancheck as
  packages that I need to fix. You're the one who is getting worked up
  over technical limitations.
 
 And where would one find this cpancheck that knows how to check the
 packagedb?  :-)

Yet another individual facing this regression?

Am using a script to restore a local owners.list from the packagedb and
than run a slight modified derivative of a very early version of your
script.

snip
#!/bin/sh

owners=$(HOME)/src/fedora/local

lftp -c get
https://admin.fedoraproject.org/pkgdb/acls/bugzilla?tg_format=plain; \
-o $owners/owners.list.raw

cat $owners/owners.list.raw | grep '^Fedora|' 
$owners/owners.fedora.list
snip

As my local cpancheck only checks for packages being maintained by
me, ... it will not check spots packages.

So be it - He receives what he wants.

Collective maintainership has failed due to infrastructural defects -
period.

Ralf
 

--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list


Re: time for perl 5.10.x in devel?

2007-11-28 Thread Chris Weyl
On Nov 28, 2007 6:25 AM, Tom spot Callaway [EMAIL PROTECTED] wrote:
 On Wed, 2007-11-28 at 14:46 +0100, Ralf Corsepius wrote:
  On Wed, 2007-11-28 at 14:35 +0100, Patrice Dumas wrote:
   Maybe the solution could simply be to be able to add some comments in the
   pacakgedb, telling who is really allowed to touch the package?
   and select 'group members can commit?'.
 
  IMO, the easiest approach would be to use perl-sig or similar (eg. an
  email alias or a packagedb alias (should such thing exist)) as
  owner ;)

 Which, we can't do, without dirty hacks, currently.

 You should talk to Toshio about this.

I'm unfamiliar with the limitations of the accounts/grouping/packagedb
system, but if we can have the accounts system enforce a requirement
that members of one group must be a subset of another group (e.g.
perl-sig group members must be members of the cla-done group), would
this satisfy the requirement that all package owners have signed
CLA's?  Can we have a group own a package?

I'm buying what Ralf is saying here: to attempt to have collective
ownership via individual ownership and extensive co-maintainers is
another variant of dirty hacks.

Of course, I may be totally misunderstanding how the systems work
together here :)

   -Chris
-- 
Chris Weyl
Ex astris, scientia

--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list


Re: time for perl 5.10.x in devel?

2007-11-28 Thread Tom spot Callaway

On Wed, 2007-11-28 at 08:09 -0800, Chris Weyl wrote:
 I'm buying what Ralf is saying here: to attempt to have collective
 ownership via individual ownership and extensive co-maintainers is
 another variant of dirty hacks.
 
 Of course, I may be totally misunderstanding how the systems work
 together here :)

The perl-SIG is not a user, hence it cannot own packages.

Reference:

Note: You may be asked to CC fedora-perl-devel-list on a perl package.
This can be done with the username perl-sig. This is presently a user,
not a group so it cannot be used as an owner or comaintainer, only for
CC.

http://fedoraproject.org/wiki/CVSPrivate

Any more than that, I do not know, and you should be talking to Toshio
about making possible improvements. Please do not shoot the
messenger. :)

~spot

--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list


[Bug 401941] EPEL Branch Request

2007-11-28 Thread bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: EPEL Branch Request


https://bugzilla.redhat.com/show_bug.cgi?id=401941


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |CLOSED
 Resolution||NEXTRELEASE




--- Additional Comments From [EMAIL PROTECTED]  2007-11-28 12:14 EST ---
Branched and built successfully

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are on the CC list for the bug, or are watching someone who is.

--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list


Re: time for perl 5.10.x in devel?

2007-11-28 Thread Tom spot Callaway

On Wed, 2007-11-28 at 09:22 -0600, Steven Pritchard wrote:
 On Wed, Nov 28, 2007 at 09:46:32AM -0500, Tom spot Callaway wrote:
  I don't have any problem with this. They'll show up in cpancheck as
  packages that I need to fix. You're the one who is getting worked up
  over technical limitations.
 
 And where would one find this cpancheck that knows how to check the
 packagedb?  :-)

http://fedoraproject.org/wiki/PackageMaintainers/UsefulScripts

That cpancheck seems fully capable of checking the packagedb.

~spot

--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list


Fwd: time for perl 5.10.x in devel?

2007-11-28 Thread Chris Weyl
Looks like this didn't make it :)


-- Forwarded message --
From: Toshio Kuratomi [EMAIL PROTECTED]
Date: Nov 28, 2007 9:21 AM
Subject: Re: time for perl 5.10.x in devel?
To: Chris Weyl [EMAIL PROTECTED], fedora-perl-devel-list@redhat.com


Chris, if this bounces from the list, feel free to forward it there.

Chris Weyl wrote:
 On Nov 28, 2007 6:25 AM, Tom spot Callaway [EMAIL PROTECTED] wrote:
 On Wed, 2007-11-28 at 14:46 +0100, Ralf Corsepius wrote:
 On Wed, 2007-11-28 at 14:35 +0100, Patrice Dumas wrote:
 Maybe the solution could simply be to be able to add some comments in the
 pacakgedb, telling who is really allowed to touch the package?
 and select 'group members can commit?'.
 IMO, the easiest approach would be to use perl-sig or similar (eg. an
 email alias or a packagedb alias (should such thing exist)) as
 owner ;)
 Which, we can't do, without dirty hacks, currently.

 You should talk to Toshio about this.

 I'm unfamiliar with the limitations of the accounts/grouping/packagedb
 system, but if we can have the accounts system enforce a requirement
 that members of one group must be a subset of another group (e.g.
 perl-sig group members must be members of the cla-done group), would
 this satisfy the requirement that all package owners have signed
 CLA's?

Yes, this part is currently possible.  We're changing over to an LDAP
backend and better web frontend in a few months, though, so I don't know
the limitations and abilities of that system.

One other thing is that people would need to be a member of cvsextras as
well as cla_done in order to login to the cvs server.

 Can we have a group own a package?

Not currently.  Pseudo groups like the current perl-sig can own a
package but a real group cannot.  This requires a bit of recoding in
order to change.

OTOH, letting a group be comaintainer (equivalent rights to owner) of a
package is fairly complete (there are a few places where we are
currently checking for cvsextras explicitly, but we can change those to
list other groups without much difficulty.

The biggest area where group ownership won't work precisely right at
this time is in the webUI.  cvsextras is our only current group and we
aren't showing all the acls for it, just the commit acl.  For the
perl-sig, I imagine that you'll want to have at least commit,
watchbugzilla, and watchcommits set.  I can code this into the
commandline tool admins are using to set permissions but doing the same
for the webUI will require some rethinking of what it should look like
and how complex it should be.

 I'm buying what Ralf is saying here: to attempt to have collective
 ownership via individual ownership and extensive co-maintainers is
 another variant of dirty hacks.

Agreed.  If you want to move forward with getting this working in the
packagedb you should open a ticket[1]_, we can try and record all the
changes we need in the packagedb and account system to enable the
change.  Then I can talk to the FAS2 author to be sure it won't cause
him any grief when we migrate and we can code something up.

We're shooting to deploy FAS2 in February.  So if there are
interdependencies between FAS and pkgdb that should wait on that
deployment we would do so after that.

.. _[1]: https://hosted.fedoraproject.org/projects/packagedb/newticket
-Toshio



-- 
Chris Weyl
Ex astris, scientia

--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list


[Bug 250873] Please rebuild perl-MLDBM for EPEL 4 and 5

2007-11-28 Thread bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Please rebuild perl-MLDBM for EPEL 4 and 5


https://bugzilla.redhat.com/show_bug.cgi?id=250873


[EMAIL PROTECTED] changed:

   What|Removed |Added

 AssignedTo|[EMAIL PROTECTED]|[EMAIL PROTECTED]




-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are on the CC list for the bug, or are watching someone who is.

--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list


Re: time for perl 5.10.x in devel?

2007-11-28 Thread Steven Pritchard
On Wed, Nov 28, 2007 at 01:05:45PM -0500, Tom spot Callaway wrote:
 http://fedoraproject.org/wiki/PackageMaintainers/UsefulScripts
 
 That cpancheck seems fully capable of checking the packagedb.

I'll be damned.  So it does.

Isn't collaborative development great?  ;-)

Steve
-- 
Steven Pritchard - KS Pritchard Enterprises, Inc.
Email: [EMAIL PROTECTED] http://www.kspei.com/
Phone: (618)624-4440   Mobile: (618)567-7320

--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list


[Bug 250873] Please rebuild perl-MLDBM for EPEL 4 and 5

2007-11-28 Thread bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Please rebuild perl-MLDBM for EPEL 4 and 5


https://bugzilla.redhat.com/show_bug.cgi?id=250873





--- Additional Comments From [EMAIL PROTECTED]  2007-11-28 17:10 EST ---
So someone has already built this, and we can close the ticket, correct?

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are on the CC list for the bug, or are watching someone who is.

--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list


[Bug 250873] Please rebuild perl-MLDBM for EPEL 4 and 5

2007-11-28 Thread bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Please rebuild perl-MLDBM for EPEL 4 and 5


https://bugzilla.redhat.com/show_bug.cgi?id=250873





--- Additional Comments From [EMAIL PROTECTED]  2007-11-28 18:03 EST ---
I see perl-MLDBM-2.01-5.el5 in the epel-5 testing repo, built on Nov 17th. 

I don't see any build yet for epel-4. 

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are on the CC list for the bug, or are watching someone who is.

--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list


[Bug 392341] missing perl-Test-MinimumVersion

2007-11-28 Thread bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: missing perl-Test-MinimumVersion


https://bugzilla.redhat.com/show_bug.cgi?id=392341





--- Additional Comments From [EMAIL PROTECTED]  2007-11-28 20:32 EST ---
perl-Algorithm-Dependency-1.104-2.fc8 has been pushed to the Fedora 8 stable 
repository.  If problems still persist, please make note of it in this bug 
report.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are on the CC list for the bug, or are watching someone who is.

--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list


[Bug 250873] Please rebuild perl-MLDBM for EPEL 4 and 5

2007-11-28 Thread bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Please rebuild perl-MLDBM for EPEL 4 and 5


https://bugzilla.redhat.com/show_bug.cgi?id=250873





--- Additional Comments From [EMAIL PROTECTED]  2007-11-28 20:40 EST ---
(In reply to comment #10)
 I see perl-MLDBM-2.01-5.el5 in the epel-5 testing repo, built on Nov 17th. 
 
 I don't see any build yet for epel-4. 

Weird.  I don't know what I thought I saw.  I've updated the spec to match the
devel branch and fired off EL-4 and EL-5 builds.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are on the CC list for the bug, or are watching someone who is.

--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list


[Bug 392331] missing perl-Test-MinimumVersion

2007-11-28 Thread bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: missing perl-Test-MinimumVersion


https://bugzilla.redhat.com/show_bug.cgi?id=392331





--- Additional Comments From [EMAIL PROTECTED]  2007-11-28 20:44 EST ---
perl-Class-Autouse-1.29-2.fc8 has been pushed to the Fedora 8 stable 
repository.  If problems still persist, please make note of it in this bug 
report.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are on the CC list for the bug, or are watching someone who is.

--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list


[Bug 389741] perl-Crypt-OpenSSL-AES-0.02 is available

2007-11-28 Thread bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: perl-Crypt-OpenSSL-AES-0.02 is available


https://bugzilla.redhat.com/show_bug.cgi?id=389741





--- Additional Comments From [EMAIL PROTECTED]  2007-11-28 20:35 EST ---
perl-Crypt-OpenSSL-AES-0.02-1.fc8 has been pushed to the Fedora 8 testing 
repository.  If problems still persist, please make note of it in this bug 
report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update perl-Crypt-OpenSSL-AES'

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are on the CC list for the bug, or are watching someone who is.

--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list


[Bug 392301] missing perl-Test-MinimumVersion

2007-11-28 Thread bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: missing perl-Test-MinimumVersion


https://bugzilla.redhat.com/show_bug.cgi?id=392301


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |CLOSED
   Fixed In Version||0.31-2
 Resolution||CURRENTRELEASE




--- Additional Comments From [EMAIL PROTECTED]  2007-11-28 23:10 EST ---
updates pushed for FC-7, FC-8 and rawhide

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are on the CC list for the bug, or are watching someone who is.

--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list


[Bug 398451] missing perl-Test-MinimumVersion

2007-11-28 Thread bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: missing perl-Test-MinimumVersion


https://bugzilla.redhat.com/show_bug.cgi?id=398451


Bug 398451 depends on bug 392291, which changed state.

Bug 392291 Summary: Review Request:  perl-Test-MinimumVersion - Check whether 
your code requires a newer perl
https://bugzilla.redhat.com/show_bug.cgi?id=392291

   What|Old Value   |New Value

 Status|ASSIGNED|CLOSED
 Resolution||CURRENTRELEASE



-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are on the CC list for the bug, or are watching someone who is.

--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list


[Bug 237197] perl-File-Slurp: EL-4, EL-5 branches?

2007-11-28 Thread bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: perl-File-Slurp: EL-4, EL-5 branches?


https://bugzilla.redhat.com/show_bug.cgi?id=237197


[EMAIL PROTECTED] changed:

   What|Removed |Added

Product|Fedora Extras   |Fedora

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |NEEDINFO
   Flag||needinfo?([EMAIL PROTECTED]
   ||edu)




--- Additional Comments From [EMAIL PROTECTED]  2007-11-28 23:43 EST ---
Ping? 

Chris, please feel free to take over for EPEL.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are on the CC list for the bug, or are watching someone who is.

--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list


[Bug 230689] Missing config.h

2007-11-28 Thread bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Missing config.h


https://bugzilla.redhat.com/show_bug.cgi?id=230689


[EMAIL PROTECTED] changed:

   What|Removed |Added

   Priority|normal  |medium
Product|Fedora Extras   |Fedora

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |CLOSED
 Resolution||ERRATA




--- Additional Comments From [EMAIL PROTECTED]  2007-11-28 23:39 EST ---
Seems as if this bug did resolve automagically ;)

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are on the CC list for the bug, or are watching someone who is.

--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list