On 17 May 2015, at 22:47, Mihai Moldovan <io...@ionic.de> wrote: >> On 17 May 2015, at 22:09, Mihai Moldovan <io...@macports.org> wrote: >>> Have you looked at https://trac.macports.org/changeset/136285? Did I miss >>> anything? >> >> Ahhh, there it is! Sorry for the buzz. I saw the rev-upgrade build, and >> looked for the cause. > > Well, no, it's legitimate. I rev-bumped all dependent ports I could find right > after the ghostscript update. Given the commits were close together, users > shouldn't see any ports listed in rev-upgrade when ran after upgrade outdated. > Maybe I missed some? Or they failed to build on the build slaves?
I saw this with ImageMagick, which was rev bumped, but (1) the upgrade order has some influence, and (2) I have an non-default variants installation so I need to build anyway from source. I guess, all is okay. I just missed the second changeset. ~petr _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
