Strange upgrade logs showing after 10.13.66-9 upgrade

Just happened to take a quick peek at my update log and seeing some strangeness. You can see that on Feb 21 the 10.13.66-9 update completed successfully… but immediately thereafter it makes mention of the 6.12.65-27 update and has been popping that up by the looks of it at every weekly update check since. The system admin screen does still show that the system is on 10.13.66-9… but obviously something’s mucked up somewhere…

No update currently running. You may close this window.
•2016-02-21 02:08:11: (10.13.66-9) Starting stage 1
•2016-02-21 02:14:56: (10.13.66-9) Stage 1 complete
•2016-02-21 02:14:57: (10.13.66-9) Starting stage 2
•2016-02-21 02:23:09: (10.13.66-9) Stage 2 complete
•2016-02-21 02:23:09: (10.13.66-9) Starting stage 3
•2016-02-21 02:23:09: (10.13.66-9) Stage 3 complete
•2016-02-21 02:23:09: (10.13.66-9) Starting stage 4
•2016-02-21 02:23:36: (10.13.66-9) Stage 4 complete
•2016-02-21 02:23:36: (10.13.66-9) Starting stage 5
•2016-02-21 02:23:36: (10.13.66-9) Stage 5 complete
•2016-02-21 02:23:36: (10.13.66-9) Starting stage 6
•2016-02-21 02:23:36: (10.13.66-9) Stage 6 complete
•2016-02-21 02:23:36: (10.13.66-9) Upgrade script complete
•2016-02-21 02:23:36: (6.12.65-27) Upgrade process successfully completed!
•2016-02-28 02:08:02: () Update sequence initialized
•2016-02-28 02:08:02: (6.12.65-27) Upgrade process successfully completed!
•2016-03-06 02:08:02: () Update sequence initialized
•2016-03-06 02:08:02: (6.12.65-27) Upgrade process successfully completed!
•2016-03-13 03:00:02: () Update sequence initialized
•2016-03-13 03:00:02: (6.12.65-27) Upgrade process successfully completed!

Cheers,
Mike

I reported this back in November 2015. Until now I thought I was the only one. Can you please add your details here:

http://issues.freepbx.org/browse/FREEPBX-10749

eg What was the original version you updated to 10.13 from? When you did this? etc

I have the same issue. I specifically updated using every version update between the distro and the latest available update version:

No update currently running. You may close this window.

2016-05-13 04:00:13: () Update sequence initialized
2016-05-13 04:00:13: (6.12.65-27) Upgrade process successfully completed!
2016-05-20 04:00:10: () Update sequence initialized
2016-05-20 04:00:10: (6.12.65-27) Upgrade process successfully completed!
2016-05-27 04:00:06: () Update sequence initialized
2016-05-27 04:00:06: (6.12.65-27) Requesting updates
2016-05-27 04:00:07: (6.12.65-27) Processing update
2016-05-27 04:00:07: (10.13.66-12) Starting stage 1
2016-05-27 04:01:42: (10.13.66-12) Stage 1 complete
2016-05-27 04:01:42: (10.13.66-12) Starting stage 2
2016-05-27 04:05:24: (10.13.66-12) Stage 2 complete
2016-05-27 04:05:24: (10.13.66-12) Stage 3 complete
2016-05-27 04:05:24: (10.13.66-12) Starting stage 4
2016-05-27 04:05:25: (10.13.66-12) Stage 4 complete
2016-05-27 04:05:25: (10.13.66-12) Starting stage 5
2016-05-27 04:05:25: (10.13.66-12) Stage 5 complete
2016-05-27 04:05:25: (10.13.66-12) Starting stage 6
2016-05-27 04:05:26: (10.13.66-12) Stage 6 complete
2016-05-27 04:05:26: (10.13.66-12) Upgrade script complete
2016-05-27 04:05:26: (6.12.65-27) Upgrade process successfully completed!

Please add your details to this bug that has been raised for this issue:

http://issues.freepbx.org/browse/FREEPBX-10749

So far I’m the only one to provide any details on the issue so I doubt it is going to get any attention unless others such as yourself provide some information so the devs can track down what is causing it.