[macports-ports] branch master updated: jasper: needs a revbump

[Marko Käning]

Hi Joshua,

On 31 Oct 2016, at 18:04 , Joshua Root <jmr at macports.org> wrote:
> Why?

because I ran into this:
---
$ port dir jasper
/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/graphics/jasper
$ sudo port upgrade outdated
--->  Computing dependencies for jasper
--->  Fetching archive for jasper
--->  Attempting to fetch jasper-1.900.16_0.darwin_13.x86_64.tbz2 from http://nue.de.packages.macports.org/jasper
--->  Attempting to fetch jasper-1.900.16_0.darwin_13.x86_64.tbz2.rmd160 from http://nue.de.packages.macports.org/jasper
--->  Installing jasper @1.900.16_0
--->  Cleaning jasper
--->  Computing dependencies for jasper
--->  Deactivating jasper @1.900.5_0
--->  Cleaning jasper
--->  Activating jasper @1.900.16_0
--->  Cleaning jasper
--->  Uninstalling jasper @1.900.5_0
--->  Cleaning jasper
--->  Computing dependencies for py27-pycparser
--->  Fetching archive for py27-pycparser
--->  Attempting to fetch py27-pycparser-2.17_0.darwin_13.noarch.tbz2 from http://nue.de.packages.macports.org/py27-pycparser
--->  Attempting to fetch py27-pycparser-2.17_0.darwin_13.noarch.tbz2.rmd160 from http://nue.de.packages.macports.org/py27-pycparser
--->  Installing py27-pycparser @2.17_0
--->  Cleaning py27-pycparser
--->  Computing dependencies for py27-pycparser
--->  Deactivating py27-pycparser @2.16_1
--->  Cleaning py27-pycparser
--->  Activating py27-pycparser @2.17_0
--->  Cleaning py27-pycparser
--->  Uninstalling py27-pycparser @2.16_1
--->  Cleaning py27-pycparser
--->  Computing dependencies for py27-setuptools
--->  Fetching archive for py27-setuptools
--->  Attempting to fetch py27-setuptools-28.7.0_0.darwin_13.noarch.tbz2 from http://nue.de.packages.macports.org/py27-setuptools
--->  Attempting to fetch py27-setuptools-28.7.0_0.darwin_13.noarch.tbz2.rmd160 from http://nue.de.packages.macports.org/py27-setuptools
--->  Installing py27-setuptools @28.7.0_0
--->  Cleaning py27-setuptools
--->  Computing dependencies for py27-setuptools
--->  Deactivating py27-setuptools @28.5.0_0
--->  Cleaning py27-setuptools
--->  Activating py27-setuptools @28.7.0_0
--->  Cleaning py27-setuptools
--->  Uninstalling py27-setuptools @28.5.0_0
--->  Cleaning py27-setuptools
--->  Computing dependencies for py34-setuptools
--->  Fetching archive for py34-setuptools
--->  Attempting to fetch py34-setuptools-28.7.0_0.darwin_13.noarch.tbz2 from http://nue.de.packages.macports.org/py34-setuptools
--->  Attempting to fetch py34-setuptools-28.7.0_0.darwin_13.noarch.tbz2.rmd160 from http://nue.de.packages.macports.org/py34-setuptools
--->  Installing py34-setuptools @28.7.0_0
--->  Cleaning py34-setuptools
--->  Computing dependencies for py34-setuptools
--->  Deactivating py34-setuptools @28.5.0_0
--->  Cleaning py34-setuptools
--->  Activating py34-setuptools @28.7.0_0
--->  Cleaning py34-setuptools
--->  Uninstalling py34-setuptools @28.5.0_0
--->  Cleaning py34-setuptools
--->  Computing dependencies for py35-setuptools
--->  Fetching archive for py35-setuptools
--->  Attempting to fetch py35-setuptools-28.7.0_0.darwin_13.noarch.tbz2 from http://nue.de.packages.macports.org/py35-setuptools
--->  Attempting to fetch py35-setuptools-28.7.0_0.darwin_13.noarch.tbz2.rmd160 from http://nue.de.packages.macports.org/py35-setuptools
--->  Installing py35-setuptools @28.7.0_0
--->  Cleaning py35-setuptools
--->  Computing dependencies for py35-setuptools
--->  Deactivating py35-setuptools @28.5.0_0
--->  Cleaning py35-setuptools
--->  Activating py35-setuptools @28.7.0_0
--->  Cleaning py35-setuptools
--->  Uninstalling py35-setuptools @28.5.0_0
--->  Cleaning py35-setuptools
--->  Updating database of binaries
--->  Scanning binaries for linking errors
--->  Found 5 broken file(s), matching files to ports    
--->  Found 1 broken port(s), determining rebuild order
--->  Rebuilding in order
     jasper @1.900.16 
--->  Computing dependencies for jasper
--->  Cleaning jasper
--->  Scanning binaries for linking errors
--->  Found 5 broken file(s), matching files to ports    
--->  Found 1 broken port(s), determining rebuild order
--->  Rebuilding in order
     jasper @1.900.16 
--->  Computing dependencies for jasper
--->  Fetching distfiles for jasper
--->  Attempting to fetch jasper-1.900.16.tar.gz from http://nue.de.distfiles.macports.org/jasper
--->  Attempting to fetch jasper-1.900.16.tar.gz from https://distfiles.macports.org/jasper
--->  Attempting to fetch jasper-1.900.16.tar.gz from http://lil.fr.distfiles.macports.org/jasper
--->  Attempting to fetch jasper-1.900.16.tar.gz from http://mse.uk.distfiles.macports.org/sites/distfiles.macports.org/jasper
--->  Attempting to fetch jasper-1.900.16.tar.gz from http://osl.no.distfiles.macports.org/jasper
--->  Attempting to fetch jasper-1.900.16.tar.gz from http://fco.it.distfiles.macports.org/mirrors/macports-distfiles/jasper
--->  Attempting to fetch jasper-1.900.16.tar.gz from http://ykf.ca.distfiles.macports.org/MacPorts/mpdistfiles/jasper
--->  Attempting to fetch jasper-1.900.16.tar.gz from http://www.ece.uvic.ca/~mdadams/jasper/software/
--->  Verifying checksums for jasper                                                 
--->  Extracting jasper
--->  Applying patches to jasper
--->  Configuring jasper
--->  Building jasper
--->  Staging jasper into destroot
--->  Unable to uninstall jasper @1.900.16_0, the following ports depend on it:
--->  	OpenSceneGraph @3.4.0_4+qt5
--->  	libraw @0.17.2_0
--->  	gdk-pixbuf2 @2.36.0_0
--->  	kf5-digikam-devel @5.1.0.133_2+qt5kde
--->  	opencv @3.1.0_4+contrib+qt5
Warning: Uninstall forced.  Proceeding despite dependencies.
--->  Deactivating jasper @1.900.16_0
--->  Unable to deactivate jasper @1.900.16_0, the following ports depend on it:
--->  	OpenSceneGraph @3.4.0_4+qt5
--->  	libraw @0.17.2_0
--->  	gdk-pixbuf2 @2.36.0_0
--->  	kf5-digikam-devel @5.1.0.133_2+qt5kde
--->  	opencv @3.1.0_4+contrib+qt5
Warning: Deactivate forced.  Proceeding despite dependencies.
--->  Cleaning jasper
--->  Uninstalling jasper @1.900.16_0
--->  Cleaning jasper
--->  Computing dependencies for jasper
--->  Installing jasper @1.900.16_0
--->  Activating jasper @1.900.16_0
--->  Cleaning jasper
--->  Updating database of binaries
--->  Scanning binaries for linking errors
--->  No broken files found.
---

Doesn’t the second build of jasper justify the revbump, or should we simply ignore this and let rev-upgrade take care of it??

Greets,
Marko