in the bump (from a fl:2 user point of view when updating) python changes and conary changes and toolchain changes, at same time,... i just want to avoid that for the common case the probabilities of ppl getting stuck in a state where they can't neither rollback nor mv forward are absolutely minimal. (i do know that some bugs related to this were identified and fixed in both sides (conary and us). want us to be absolutely positive that it is enough)
all the best, António Meireles, aka doniphon On 03/25/2011 11:20 AM, Jesse Zhang wrote: > On Fri, Mar 25, 2011 at 7:08 PM, Alexandre Franke > <alexandre.fra...@gmail.com> wrote: >>> Instead of releasing 2.5 from fl:2-qa, the >>> other option is to push to fl:2, release from there (as in the past), >>> and (possibly) break the upgrade path for those users. >> Sorry for being naive, but I don't see why this will break upgrade >> path. Can you expand on this? > I don't actually know. That's just what I heard. Maybe because of too > old conary? > > jesse > _______________________________________________ > Foresight-devel mailing list > Foresight-devel@lists.rpath.org > http://lists.rpath.org/mailman/listinfo/foresight-devel _______________________________________________ Foresight-devel mailing list Foresight-devel@lists.rpath.org http://lists.rpath.org/mailman/listinfo/foresight-devel
