Initially we mentioned we would not try and support upgrades from the historical, PiRogue-based approach to the new pirogue-admin/ViRogue-based approach.
That would probably mean using different repositories, having the risk of users still pointing to the old/current ones and never getting any upgrades.
It seems feasible to try and support that upgrade in best effort mode, with at least a couple of glitches spotted with a first attempt:
pirogue-ap and pirogue-networking have files in common, a Conflicts is needed.- A few things happened in the
debian-12 branch that need to be merged/cherry-picked into the virogue one (e.g. in deb-packages, for the pirogue-archive-keyring addition).
- The
--redeploy cannot work when existing packages (e.g. pirogue-dashboard, pirogue-eve-collector, pirogue-flow-inspector) get upgraded: the config file is very likely to be missing at this point.
- And
pirogue-base.postinst only does autodetection on initial installation. It should also do it when upgrading from an “historical” version.
Quick comments/ideas:
- Is probably trivial.
- Will need to be seriously investigated when we get closer to a first release.
- Is probably easily addressed by turning the hard failure into a warning (I wanted to notice if things went KO, but making the upgrade smoother is a good reason to revisit this initial decision).
- Is probably easy as I decided to go for 1.2.* versions in the
virogue branch while 1.1.* versions are used in the debian-12 branch. Version comparison will let us know if we're upgrading from an “historical, PiRogue-based” setup.
Initially we mentioned we would not try and support upgrades from the historical, PiRogue-based approach to the new
pirogue-admin/ViRogue-based approach.That would probably mean using different repositories, having the risk of users still pointing to the old/current ones and never getting any upgrades.
It seems feasible to try and support that upgrade in best effort mode, with at least a couple of glitches spotted with a first attempt:
pirogue-apandpirogue-networkinghave files in common, aConflictsis needed.debian-12branch that need to be merged/cherry-picked into thevirogueone (e.g. indeb-packages, for thepirogue-archive-keyringaddition).--redeploycannot work when existing packages (e.g.pirogue-dashboard,pirogue-eve-collector,pirogue-flow-inspector) get upgraded: the config file is very likely to be missing at this point.pirogue-base.postinstonly does autodetection on initial installation. It should also do it when upgrading from an “historical” version.Quick comments/ideas:
viroguebranch while 1.1.* versions are used in thedebian-12branch. Version comparison will let us know if we're upgrading from an “historical, PiRogue-based” setup.