Il 06/12/19 07:34, Johannes Lips ha scritto: > Hi all, > > I was recently bit by a bug, which was caused by a mismatch between texlive-biblatex and biber. The technical side is not so important, only so much that they need each other in a pretty specific version, which is not reflected on the rpm level. > What I found weird is that you can't comment on an update, which is already pushed to stable. A lot of users are only hit by a bug, once it reaches stable and then you don't have any possibility to highlight a bug report or an issue with this update. I would like to have the possibility to add such an information to an update, which introduced the issue. That was requested and discussed long time ago in https://github.com/fedora-infra/bodhi/issues/2050 The rationale behind this was about the nonsense to have users commenting on an already pushed update, since this cannot be undone. My opinion is that once an update is pushed to stable, new bugs should be reported in Bugzilla, not as comments in Bodhi. However there's an open discussion about restoring the previous behavior: https://github.com/fedora-infra/bodhi/issues/3748 > Also I would like to ask if it is possible for important updates, like the texlive one to increase the stable karma. It really depends which mirrors you are using and if you are unlucky the updates get pushed to stable, before it reaches updates-testing for you and then again there's nothing to add, once it's pushed. > The stable-karma and stable-days parameters can be set by the user in the web form or by CLI. By default stable-karma is set to 3, but it can be changed when creating the update. Mattia _______________________________________________ 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
