> On Oct 9, 2014, at 3:26 AM, lar...@macports.org wrote: > > Revision > 126395 > Author > lar...@macports.org > Date > 2014-10-09 01:26:13 -0700 (Thu, 09 Oct 2014) > Log Message > > py25-boto: Replace with py27-boto
> Modified: trunk/dports/python/py-boto/Portfile (126394 => 126395) > --- trunk/dports/python/py-boto/Portfile 2014-10-09 08:26:10 UTC (rev > 126394) > +++ trunk/dports/python/py-boto/Portfile 2014-10-09 08:26:13 UTC (rev > 126395) > @@ -8,7 +8,7 @@ > set real_name boto > epoch 1 > version 2.8.0 > -python.versions 25 26 27 > +python.versions 26 27 > maintainers nomaintainer > license MIT > supported_archs noarch > Modified: trunk/dports/python/py-graveyard/Portfile (126394 => 126395) > --- trunk/dports/python/py-graveyard/Portfile 2014-10-09 08:26:10 UTC (rev > 126394) > +++ trunk/dports/python/py-graveyard/Portfile 2014-10-09 08:26:13 UTC (rev > 126395) > @@ -35,6 +35,7 @@ > antlr3 3.1.3_1 25 > aspects 1.3_1 25 > blessings 1.5_1 25 31 32 > +boto 2.8.0_1 25 > buzhug 1.8_1 25 > cherrypy3 3.2.0_1 24 25 > dap 2.2.6.7_1 24 25 py-graveyard doesn't seem to be taking the epoch into account. Note that before, py25-boto was epoch 1 version 2.8.0 revision 0, and now it's epoch 0 version 2.8.0 revision 1. I don't understand why it nevertheless seems to be working: $ port install py25-boto ---> Computing dependencies for py25-boto ---> Fetching distfiles for py25-boto ---> Verifying checksums for py25-boto ---> Extracting py25-boto ---> Configuring py25-boto ---> Building py25-boto ---> Staging py25-boto into destroot ---> Installing py25-boto @2.8.0_0 ---> Activating py25-boto @2.8.0_0 ---> Cleaning py25-boto $ port sync ---> Updating the ports tree $ port outdated py25-boto The following installed ports are outdated: py25-boto 2.8.0_0 < 2.8.0_1 $ _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
