<p dir="ltr"><br>
On Nov 12, 2015 6:39 AM, "Reindl Harald" <<a href="mailto:h.reindl@thelounge.net">h.reindl@thelounge.net</a>> wrote:<br>
><br>
><br>
><br>
> Am 12.11.2015 um 15:34 schrieb Andrew Lutomirski:<br>
>><br>
>> On Nov 11, 2015 11:34 PM, "Petr Pisar" <<a href="mailto:ppisar@redhat.com">ppisar@redhat.com</a><br>
>> > In otherwords always disable autokarma. I push builds into testing and<br>
>> > sombody raises karma over a weekend and when I come to the mailbox<br>
>> > later, I only see F22 was pushed into stable before F23. There is<br>
>> > nothing a mainter can do besides disabling default Bodhi features.<br>
>><br>
>> This is very much related to a thread I started a couple weeks ago. I<br>
>> really think that Bodhi should be able to understand that a pair of<br>
>> updates to different branches match and to push them together<br>
><br>
><br>
> who says you that a update for F22 would behave identical on F23 or the other direction when half of the OS has different versions of libraries and the whole userland?<br>
><br>
> it may often work that way but to assume it is so by definition is a dangerous game, i saw enough Fedora bugs the past 8 years after dist-upgrades where the affected application had exactly the same version as before the upgrade and behaved wrong or failed completly<br>
></p>
<p dir="ltr">I said no such thing. (Can you please try to stop being combative by default?)</p>
<p dir="ltr">I think that Bodhi should arrange, at least by default, to push things in the correct order. Whether that means that karma is required separately for each branch is an orthogonal issue, except insofar as allowing karma from one branch to carry over to another would also require Bodhi to track that two updates are the same thing but just to different branches.</p>
<p dir="ltr">At the very least, Bodhi should *not* push to F22 due to autokarma until F23 stable is requested.</p>
<p dir="ltr">--Andy</p>