[Bug 838679] perl-Plack: EL-6 build

[bugzilla at redhat.com]

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

--- Comment #4 from Jose Pedro Oliveira <jpo at di.uminho.pt> ---
(In reply to comment #2)
> Thanks for the comprehensive summary. Looks like this will be a though one.
> About the missing PPC64 packages, this is a pain, but that can be dealt with.

This problem appears to be the easiest to fix.

> About the test suites, I think it should be acceptable to selectively
> disable tests that are failing because of the unmet dependencies. What do
> you think ?

I'm with Ralf on this one: we should strive to successfully run all the module
tests.


In order to have perl-Plack in EPEL-6 we need to accomplish the following
steps:


 1) perl-Crypt-PasswdMD5 needs to be in the EPEL-6 PPC64 repositories

    Action:
    import and build perl-Crypt-PasswdMD5 for EPEL-6 with a lower release 
    than the one existing in the RHEL channels. TODO: check if there are 
    modules missing in the PPC64 repos.

    RHEL 6.x SRPM:
   
ftp://ftp.redhat.com/pub/redhat/linux/enterprise/6Server/en/os/SRPMS/perl-Crypt-PasswdMD5-1.3-6.el6.src.rpm


  2) perl-Devel-StackTrace needs to be updated to a more recent version
     (at least version 1.23)

     RHEL 6.x SRPM:
    
ftp://ftp.redhat.com/pub/redhat/linux/enterprise/6Server/en/os/SRPMS/perl-Devel-StackTrace-1.22-4.el6.src.rpm


  3) perl-Test-Simple (Test::More) needs to be updated to a more recent version
     (ideally from version 0.92 to 0.98)

     Caveats:
     The update must be done to the perl package;
     a patch - perl-update_Test-Simple.patch - needs to added

     RHEL 6.x SRPM:
    
ftp://ftp.redhat.com/pub/redhat/linux/enterprise/6Server/en/os/SRPMS/perl-5.10.1-127.el6.src.rpm


Although only the first two steps are really mandatory, the third is also
highly recommend due to the complexity and security problems of the Plack stack
(as Ralf pointed in the previous comment): several modules may need to be
updated regularly and some of these updates will need a more recent version of
Test::More.

I believe the first step can be performed by us. The second and the third steps
will need to be performed by Red Hat packagers and most likely in sync with
major RHEL releases.

/jpo

-- 
You are receiving this mail because:
You are on the CC list for the bug.