I couple of observations after recently submitting some buildroot overrides and updates: Buildroot overrides: 1. The new auto-search with partial build names is nice but clicking on the builds it findes has no effect. 2. When I manually paste in a full build name it says "No results" but works when submitted.

Updates: 1. Preview for the update notes is completely broken.

Hi, On 6/22/20 9:53 AM, Clement Verna wrote: > Hi all, > > I have just deployed Bodhi 5.4.0 > (https://github.com/fedora-infra/bodhi/releases) in production. We > were running 5.2.2 so that deployment brings the improvement and bug > fixes from 5.3.0 and 5.4.0 (see release notes) > > One high level feature worth noting : > > * you can now associate BZ tickets to the automatically created > rawhide updates. The bugs mentioned with the format "fix(es)|close(s) > (fedora|epel|rh|rhbz)#BUG_ID"  in the changelog will be associated to > the update and automatically closed.

> More info > https://github.com/fedora-infra/bodhi/blob/develop/docs/user/automatic_up... I tried using this: https://bodhi.fedoraproject.org/updates/FEDORA-2020-21cac06005 And the bug got associated with the update in bodhi, but the bug did not get closed when the update hit stable ?

Regards, Hans _______________________________________________ devel mailing list -- devel(a)lists.fedoraproject.org To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org 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@lists.fedoraproject.org

On Tue, 23 Jun 2020 at 12:32, Vít Ondruch <vondruch(a)redhat.com <mailto:vondruch@redhat.com>> wrote: Dne 23. 06. 20 v 9:23 Hans de Goede napsal(a): > Hi, > > On 6/22/20 9:53 AM, Clement Verna wrote: >> Hi all, >> >> I have just deployed Bodhi 5.4.0 >> (https://github.com/fedora-infra/bodhi/releases) in production. We >> were running 5.2.2 so that deployment brings the improvement and bug >> fixes from 5.3.0 and 5.4.0 (see release notes) >> >> One high level feature worth noting : >> >> * you can now associate BZ tickets to the automatically created >> rawhide updates. The bugs mentioned with the format "fix(es)|close(s) >> (fedora|epel|rh|rhbz)#BUG_ID"  in the changelog will be associated to >> the update and automatically closed. It should also support "Resolves": https://github.com/fedora-infra/bodhi/commit/f2f8413ffcb749fff512f226b0bc... >> More info >> https://github.com/fedora-infra/bodhi/blob/develop/docs/user/automatic_up... > > I tried using this: > > https://bodhi.fedoraproject.org/updates/FEDORA-2020-21cac06005 > > And the bug got associated with the update in bodhi, but the bug > did not get closed when the update hit stable ? It does not appear to work: https://bodhi.fedoraproject.org/updates/FEDORA-2020-08b74be230 The update is not referenced in BZ as the F32 update: https://bodhi.fedoraproject.org/updates/FEDORA-2020-5dd98b41e7 https://bugzilla.redhat.com/show_bug.cgi?id=1849708#c2 Yeah this is similar to Fabio's case and having a ":"  in the string.

  Vít > > Regards, > > Hans > _______________________________________________ > devel mailing list -- devel(a)lists.fedoraproject.org <mailto:devel@lists.fedoraproject.org> > To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org <mailto:devel-leave@lists.fedoraproject.org> > 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@lists.fedoraproject.org _______________________________________________ devel mailing list -- devel(a)lists.fedoraproject.org <mailto:devel@lists.fedoraproject.org> To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org <mailto:devel-leave@lists.fedoraproject.org> 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@lists.fedoraproject.org _______________________________________________ devel mailing list -- devel(a)lists.fedoraproject.org To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org 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@lists.fedoraproject.org

Hi all, I have just deployed Bodhi 5.4.0 (https://github.com/fedora-infra/bodhi/releases) in production. We were running 5.2.2 so that deployment brings the improvement and bug fixes from 5.3.0 and 5.4.0 (see release notes) One high level feature worth noting : * you can now associate BZ tickets to the automatically created rawhide updates. The bugs mentioned with the format "fix(es)|close(s) (fedora|epel|rh|rhbz)#BUG_ID" in the changelog will be associated to the update and automatically closed. More info https://github.com/fedora-infra/bodhi/blob/develop/docs/user/automatic_up...

One high level feature worth noting : * you can now associate BZ tickets to the automatically created rawhide updates. The bugs mentioned with the format "fix(es)|close(s) (fedora|epel|rh|rhbz)#BUG_ID"  in the changelog will be associated to the update and automatically closed. More info https://github.com/fedora-infra/bodhi/blob/develop/docs/user/automatic_up...

Il 09/07/20 15:12, Miro Hrončok ha scritto: > > Finally I got to testing this. > > The bugzilla was added to the update: > > https://bodhi.fedoraproject.org/updates/FEDORA-2020-c1be13ded8 > > But it was not closed: > > https://bugzilla.redhat.com/show_bug.cgi?id=1851519 > > Should I report this as a bug or am i doing something wrong? The commit is: > > https://src.fedoraproject.org/rpms/python-tox/c/d154cf5aabe445914123b4123... > > But the build was done from one clenaup commit above this. Is that relevant? > The feature is not completely working in Bodhi 5.4.0, a fix is ready [1] and it will be deployed with the next bugfix (probably 5.4.1) Mattia [1] https://github.com/fedora-infra/bodhi/pull/4068