Re: Automatic check for bodhi updates not to break RPM dependencies

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Miro Hrončok wrote:
> this is not the first time I saw a bodhi update that breaks dozens of
> dependencies, goes unnoticed for a week and is automatically pushed
> stable, only to discover many packages fail to install.

The most important measure would be to abolish automatic pushes. This update 
was automatically pushed after 7 days with no feedback whatsoever. Promoting 
an update to stable should require a human to explicitly click a "push to 
stable" button, thereby acknowledging the lack of feedback.

> How come we don't have an automatic check for this? What can be done?

I also do not understand why the gating stuff that was recently added does 
not complain about this.

        Kevin Kofler
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux