[SOLVED] Pacmanager error after uuid update

I have been using pacmanager for awhile and have had no issues with updates to its dependencies. Today an update to uuid came and I started getting errors when trying to start pacmanager. So I went to the AUR page noticed someone previously had the same issue and they solved by rebuilding the AUR packages that were dependencies. I went through that and did not getting any further in the solving of the problem, also tried rebuilding all the dependencies as well as the main package after they were rebuilt still to no avail. Can anyone shed some light on what I am missing here, I feel like it should be obvious but for some reason is evading me.

So as you see it seems to not being able to find something from uuid. Thanks for any help or smacking me to realize what I am missing here. Also I did verify what it is looking for does not exist on my system.

EDIT:While trying to still sort this out I have run into something that seems "weird" to me I was looking over the uuid package just a moment ago, and the AUR page stats it was uploaded first today, yet it has been installed on my box before today? I know the package I maintain on AUR actually shows when it was first submitted normally. How could this have been used as a dependency before this but was initially submitted the 8th yesterday? It may be nothing just seems strange to me, also if it was submitted on the 8th its all ready been orphaned.

EDIT2:Well after lots of tinkering around I cloned the AUR repo to get the -8 version of uuid to see if I could notice what had changed through the update. I noticed that configure was missing the --with-perl call which is why I was missing the file that I was. But the part that I still do not get is how can an unmaintained packaged get updated, and with major changes. It got a new patch and a new PKGBUILD between -8 and -9. I am trying to sort through what the actual differences are with the patches as time permits for me, if I can confidently say why the changes took place I will take over the package as well, but honestly at this point I am at a loss for why the changes that were done took place on the 8th.