I see why. The vlconfig2 package has made it to it's 10th release, so the full package name is "vlconfig2-7.0-noarch-10vl70". I Again, this goes back the usual (and IMO wrong) way of doing these packages. You see, I know we have not had 10 releases of this package since 7.0 went out. So, with each release, the package VERSION should change, and not the RELEASE number.
VL-6.0 = vlconfig2-6.0-noarch-1vl70
VL-7.0 = vlconfig2-7.0-noarch-1vl70
VL-8.0 = vlconfig2-8.0-noarch-1vl70
Release numbers should only be incremented for (very unlikely) patches made to this package between releases. The only scenario I can think of that would require this would be doing a 7.1 release after 7.0 of course.
So, in short, to stay consistent with our build system, I think the release number of the package needs to be fixed, otherwise, you have to fix a ton of slackbuilds for the 64b build