On Fri, Jul 16, 2010 at 8:41 AM, Michael K. Johnson <johns...@rpath.com> wrote:
> On Fri, Jul 16, 2010 at 02:31:02PM +0100, António Meireles wrote:
>> b) regarding fl:2. the problem isn't what is in 2-devel (and 2-qa now),
>> is the update path.
>>     fl:2 has a too old conary (with known issues and PackageKit). So at
>> the time of a promote
>>     from 2-qa  to it, groups pre-update scripts need to be wired to (at
>> least) erase existing
>>     PackageKit there (or at least blocking  its ability to initiate
>> updates) and get some way to
>>     notify  users to do an 'updateall'. mkj do you volunteer for this ?
>
> So old PackageKit does not put itself into the critical update?

the old packagekit update using update-system. Yes use the critical update first

> Does it even put conary per se into the critical update?
Yes

Only i need confirm looking the code on packagek...@fl:2
> _______________________________________________
> 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

Reply via email to