On Nov 11, 2015 11:34 PM, "Petr Pisar" <ppisar@xxxxxxxxxx> wrote:
>
> On 2015-11-11, Kevin Fenzi <kevin@xxxxxxxxx> wrote:
> > The best thing we can do about these cases right now is for maintainers
> > to PAY ATTENTION. If you have multiple updates in flight for the same
> > package, please make sure they don't both go stable at the same time.=20
> >
> That's ridiculous. Should I request for stable in one branch, then wait
> few days until the packages is actually pushed, and then request for
> stable into older Fedora?
>
> The serialization should be handled by releng's tool that do the push.
>
> > Failing that, when you notice these issues after the fact, file a
> > releng ticket and we can retag things in the right order so it gets
> > fixed.
> >
> In otherwords always disable autokarma. I push builds into testing and
> sombody raises karma over a weekend and when I come to the mailbox
> later, I only see F22 was pushed into stable before F23. There is
> nothing a mainter can do besides disabling default Bodhi features.
This is very much related to a thread I started a couple weeks ago. I really think that Bodhi should be able to understand that a pair of updates to different branches match and to push them together.
Also, compose should maybe learn to do branches together - right now I have a broken upgrade path just because F22 finished its push while my F23 push is still pending.
--Andy
>
> -- Petr
>
> --
> devel mailing list
> devel@xxxxxxxxxxxxxxxxxxxxxxx
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
