Re: Bodhi 5.4.0 in production

2020-07-24 Thread Miro Hrončok 

On 09. 07. 20 21:08, Mattia Verga via devel wrote:

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/d154cf5aabe445914123b41239243811eeac93b7?branch=master

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


It worked this time, thanks!

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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

Re: Bodhi 5.4.0 in production

2020-07-09 Thread Mattia Verga via devel 
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/d154cf5aabe445914123b41239243811eeac93b7?branch=master
>
> 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

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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

Re: Bodhi 5.4.0 in production

2020-07-09 Thread Miro Hrončok 

On 22. 06. 20 9:53, Clement Verna wrote:


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_updates.rst#associate-bugs-to-automatic-updates


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/d154cf5aabe445914123b41239243811eeac93b7?branch=master

But the build was done from one clenaup commit above this. Is that relevant?

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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

Re: Bodhi 5.4.0 in production

2020-06-24 Thread Vít Ondruch 

Dne 23. 06. 20 v 15:08 Clement Verna napsal(a):
>
>
> On Tue, 23 Jun 2020 at 12:32, Vít Ondruch  > 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/f2f8413ffcb749fff512f226b0bcee9182a969be
>
>
> >> More info
> >>
> 
> https://github.com/fedora-infra/bodhi/blob/develop/docs/user/automatic_updates.rst#associate-bugs-to-automatic-updates
> >
> > 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.


Hm, I thought that the `(?:\:)` part of RegExp would accept ":"? But I
might read it wrong.


Vít


>  
>
>
>
>
> Vít
>
>
> >
> > Regards,
> >
> > Hans
> > ___
> > devel mailing list -- devel@lists.fedoraproject.org
> 
> > To unsubscribe send an email to
> devel-le...@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@lists.fedoraproject.org
> 
> To unsubscribe send an email to
> devel-le...@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@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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

Re: Bodhi 5.4.0 in production

2020-06-23 Thread Clement Verna 
On Tue, 23 Jun 2020 at 12:32, Vít Ondruch  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/f2f8413ffcb749fff512f226b0bcee9182a969be
>
>
> >> More info
> >>
> https://github.com/fedora-infra/bodhi/blob/develop/docs/user/automatic_updates.rst#associate-bugs-to-automatic-updates
> >
> > 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@lists.fedoraproject.org
> > To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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

Re: Bodhi 5.4.0 in production

2020-06-23 Thread Clement Verna 
On Tue, 23 Jun 2020 at 12:11, Fabio Valentini  wrote:

> On Mon, Jun 22, 2020 at 9:58 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_updates.rst#associate-bugs-to-automatic-updates
>
> Uh well, I managed to screw this up at my first try. I guess the regex
> used to detect this doesn't like the ":" in there (which is what most
> projects use for automations like this?) ...
> https://bodhi.fedoraproject.org/updates/FEDORA-2020-0523158a04


Yeah that is not supported (the ":") in the default regex expression if you
look at the documentation you have examples [0]. Supporting that case
should not be too hard tho, we just need to update the config with the
right regex :-)

[0] -
https://github.com/fedora-infra/bodhi/blob/develop/docs/user/automatic_updates.rst#associate-bugs-to-automatic-updates

>
>
> Fabio
>
> > Also there were no changes on the client side.
> >
> > Thanks all
> > Clément
> > ___
> > devel mailing list -- devel@lists.fedoraproject.org
> > To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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

Re: Bodhi 5.4.0 in production

2020-06-23 Thread Clement Verna 
On Tue, 23 Jun 2020 at 09:24, Hans de Goede  wrote:

> 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_updates.rst#associate-bugs-to-automatic-updates
>
> 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 ?
>

Hum yeah the closing of bugs is actually done during the daily push for
normal releases, this does not happen for rawhide so that needs to be
integrated in the rawhide workflow. I have opened
https://github.com/fedora-infra/bodhi/issues/4067


>
> Regards,
>
> Hans
>
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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

Re: Bodhi 5.4.0 in production

2020-06-23 Thread Vít Ondruch 

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/f2f8413ffcb749fff512f226b0bcee9182a969be


>> More info
>> https://github.com/fedora-infra/bodhi/blob/develop/docs/user/automatic_updates.rst#associate-bugs-to-automatic-updates
>
> 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


Vít


>
> Regards,
>
> Hans
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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

Re: Bodhi 5.4.0 in production

2020-06-23 Thread Fabio Valentini 
On Mon, Jun 22, 2020 at 9:58 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_updates.rst#associate-bugs-to-automatic-updates

Uh well, I managed to screw this up at my first try. I guess the regex
used to detect this doesn't like the ":" in there (which is what most
projects use for automations like this?) ...
https://bodhi.fedoraproject.org/updates/FEDORA-2020-0523158a04

Fabio

> Also there were no changes on the client side.
>
> Thanks all
> Clément
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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

Re: Bodhi 5.4.0 in production

2020-06-23 Thread Hans de Goede 

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_updates.rst#associate-bugs-to-automatic-updates


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@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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

Re: Bodhi 5.4.0 in production

2020-06-22 Thread Richard Shaw 
Just submitted another set of updates and it worked as expected. Not sure
if it was an infra issue or maybe there was something / a character in the
notes it just didn't like.

Thanks,
Richard

>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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

Re: Bodhi 5.4.0 in production

2020-06-22 Thread Richard Shaw 
On Mon, Jun 22, 2020 at 11:16 AM Mattia Verga via devel <
devel@lists.fedoraproject.org> wrote:

> Il 22/06/20 17:42, Richard Shaw ha scritto:
> > I couple of observations after recently submitting some buildroot
> > overrides and updates:
> >
> > Updates:
> > 1. Preview for the update notes is completely broken.
> Everything works fine for me and the update form hasn't been touched in
> the update from 5.2.2.
> Can you check in the browser console if any error is displayed when
> opening the preview popup?
>

It either said something to the effect of "Preview Failed" or just stalled.

Thanks,
Richard
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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

Re: Bodhi 5.4.0 in production

2020-06-22 Thread Mattia Verga via devel 
Il 22/06/20 17:42, Richard Shaw ha scritto:
> 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.
Yeah, this is not working as expected. Also, the search query should use 
a prefix, not the full package name, so that definitively needs a fix.
>
> Updates:
> 1. Preview for the update notes is completely broken.
Everything works fine for me and the update form hasn't been touched in 
the update from 5.2.2.
Can you check in the browser console if any error is displayed when 
opening the preview popup?

Mattia

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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

Re: Bodhi 5.4.0 in production

2020-06-22 Thread Richard Shaw 
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.

Thanks,
Richard
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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