discuss.answer
So I haven't gotten a solution but I have an explanation.
When you search for a package locally, it's added to the DB in a table called modx_transport_package. In the table the version major, minor and patch are stored as separate columns ... each with a type of tinyint(4) which wouldn't be able to store a timestamp anyway.
As a result timestamps are stored as 255 (all of them) ... so according to MODx there isn't a new version. If you use values that fit in there ... things should work, don't see why not.
This seems like the best bet to me:
awesome-2.16.1383991111-pl
BTW, this is the "massaging" I mentioned, in case it helps, though I don't think it would affect what you're doing:
public function getComparableVersion() {
$v = explode('-',$this->get('signature'));
array_shift($v);
$v = implode('-',$v);
$v = str_replace('-ga','-pl',$v);
return $v;
}
Yes, I missed your message above when I wrote that because it was on a new page. The Tinyint deal is obviously the problem.
You could make a feature request to change the type of the patch field.
