kstars move and epoch

[Rik Mills]

On 13/01/18 23:57, Scarlett Clark wrote:
> Hello,
> Recently kstars moved to their own release schedule away from
> applications. With this move they changed version numbers.. 2.9.0 from a
> much higher application version..
> The application version already had a 4: epoch... so the way I
> understand epochs, I need a higher epoch for it to be effective. I tried
> 5:2.9.0 and I get this failure:
> 
> https://build.neon.kde.org/job/xenial_stable_applications_kstars_src/116/console
> 
> Am I misunderstanding something? Thanks,
> Scarlett

>From the tooling changelog;

apachelogger committed on 16 Feb 2016
add new version enforcer tech to prevent epoch changes without noticing
this makes sourcer build fall over if epochs are being changed. the only
way to get an epoch change is to remove a marker file in the workspace