Il 26/02/2018 09:25, Artur Iwicki ha scritto:
As far as I can see, previously this wasn't an issue, since joost (fpc & lazarus maintainer) didn't usually perform FPC & Lazarus updates, preferring to build new versions in Rawhide / early branched and have them roll out with the next Fedora release.
_______________________________________________
I would say that Joost was too conservative (very poor communication and
very long time between the release of a FPC or Lazarus stable release
and when they were built in Fedora), but now we're on the other side: I
would have expected FPC 3.0.4 and Lazarus 1.8.0 to be released only on
Rawhide and F28, not also in F27 and F26.
Since many packages depends on FPC and Lazarus, pushing new releases on
older Fedora branches throws in some risks about breaking dependent
package builds. If this is not needed to fix some urgent bug, it's
better not to do so.
Anyway, the process to avoid a broken Lazarus to enter in repositories is:
build FPC for the desired branch -> create a buildroot override in bodhi
for the new FPC build -> wait for the overrided package to become active
-> build Lazarus -> push a cumulative update for both packages
Regards
Mattia
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
