Dear Maintainer, I was migrating a very old Cacti server to a new one. The upgrade process stopped at version 1.0.4 and then failed with a database migration error. The issue was caused by a bug in the migration file for version 1.0.5. The related GitHub issue is: https://github.com/Cacti/cacti/issues/5527 . After replacing the distribution migration file with the upstream version (1_0_5.php), the migration completed successfully and the Cacti upgrade finished without problems. It looks like the migration file in the package needs to be synchronized with the upstream version.
Hi Michal, Thanks for reporting issues you encounter. That change supposedly went into 1.2.26 and indeed I see it in the Debian package currently in stable: 1.2.30+ds1-1: https://sources.debian.org/src/cacti/1.2.30%2Bds1-1/install/upgrades/1_0_5.php Can you show the difference between your downloaded file and the original. I didn't change the file, so if it's different than needed, it's a delta that's already present in the upstream tar ball. I don't understand how the situation you describe could have happened. Paul
Hi, if you compare the debian package https://sources.debian.org/src/cacti/1.2.30%2Bds1-1/install/upgrades/1_0_5.php with the upstream file https://github.com/Cacti/cacti/blob/develop/install/upgrades/1_0_5.php you can notice that there is a difference on line 35. Lines 35 - 40 should just fix a bug that was in the original migration and was causing problems when upgrading from a very old version. The bug was not fixed by the new migration, but by fixing the existing migration. Michal.
Control: tags -1 - moreinfo Contrary to the upstream bug report, that change was only made last November [1], so it hasn't been part of any upstream cacti release. Paul [1] https://github.com/Cacti/cacti/commit/81f2dd52b80e39ca0142eb8defc8a497791879dd
I completely missed this fact. Sorry for the unnecessary bug report :/ Thanks for response.