Mattia Verga

> > About the Koji issue, we should find why installing koji from Fedora package it is not found: [ff5cc1d](https://github.com/fedora-infra/bodhi/commit/ff5cc1d6e097acb96ea0ea9132bcd68d9c8caeea) > > I am sure I saw an official issue...

I have removed the lorax build from the Update in Bodhi backend, not sure about the db error... in a local test environment, adding and removing builds with testcases works...

I have been thinking about this in the past. It's not a simple task, though: we currently emit the messages through a javascript that cannot survive upon page refresh, so...

It seems more like an error during installation: `error: urllib3 1.26.1 is installed but urllib3!=1.25.0,!=1.25.1,=1.21.1 is required by {'requests'}` however, trying in a local virtualenv works: `Requirement already satisfied: urllib3=1.21.1...

Hi. We have a setting for this in Bodhi config: if a user is in one of the defined `admin_packager_groups` the ACL validation mechanism is bypassed and there's no need...

> Hi! Packit lead here. > > We discussed this during the today's team meeting and I have a few notes to this to push this forward: > > *...

> @mattiaverga Thanks for the answer and sorry for being out for a few days. > > > Bodhi relies on permissions set in DistGit, if a user has commit...

> What about also allowing users with the `ticket` ACL to submit Bodhi updates? The `ticket` ACL isn't currently used for anything in src.fp.o (that instance disables Pagure's built in...

> @mattiaverga: > > > Note that the package mainatainer needs to set [bodhi_update](https://packit.dev/docs/configuration/#bodhi_update) config in the **DistGit located** `.packit.yml` file first ([example](https://src.fedoraproject.org/rpms/packit/blob/8421ca4a11d473539ac6d04261aa65b7e657ad18/f/.packit.yaml#_96)) - which is an equivalent security measure...

There has been an infrastructure glitch in past days, can you check if it's still an issue for you now?