Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 0.3.0
Request #19299 Handle max + exclude version
Submitted: 2012-02-20 00:35 UTC
From: remicollet Assigned: doconnor
Status: Closed Package: PEAR_Command_Packaging (version 0.2.0)
PHP Version: 5.4 RC (specify # in Description) OS: GNU/Linux (Fedora 16)
Roadmaps: (Not assigned)    
Subscription  


 [2012-02-20 00:35 UTC] remicollet (Remi Collet)
Description: ------------ The package from horde channel comes with <package> <name>Horde_Translation</name> <channel>pear.horde.org</channel> <min>1.0.0</min> <max>2.0.0</max> <exclude>2.0.0</exclude> </package> The min is lost. The max + exclude should be handle as "<" instead of adding an awful Conflicts. Can you please consider the attached patch P.S. 1 line per requires seems more "legible" (as required by Guidelines) Test script: --------------- pear make-rpm-spec Horde_Exception-1.0.8.tgz Expected result: ---------------- Requires: php-pear(pear.horde.org/Horde_Translation) >= 1.0.0 Requires: php-pear(pear.horde.org/Horde_Translation) < 2.0.0 Requires: php-pear(PEAR) >= 1.7.0 Actual result: -------------- Requires: php-pear(pear.horde.org/Horde_Translation) <= 2.0.0, php-pear(PEAR) >= 1.7.0 Conflicts: php-pear(pear.horde.org/Horde_Translation) = 2.0.0

Comments

 [2012-02-20 00:35 UTC] remicollet (Remi Collet)
Added patch max-exclude.patch.
 [2012-04-01 19:16 UTC] doconnor (Daniel O'Connor)
So applying this breaks tests - http://test.pear.php.net:8080/job/PEAR_Command_Packaging/33/testReport/junit/(ro ot)/tests_/_var_lib_jenkins_workspace_PEAR_Command_Packaging_tests_make_rpm _spec_test_nodocs_dupdeps_phpt/
 [2012-04-01 19:17 UTC] doconnor (Daniel O'Connor)
(PS: feel absolutely free to send in pull requests)
 [2012-04-01 19:24 UTC] doconnor (Daniel O'Connor)
-Status: Open +Status: Closed -Assigned To: +Assigned To: doconnor
This bug has been fixed in SVN. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.