No autocomplete for new package in bodhi 2.0?

[Dave Johansen]

I just finished the review for cppformat (
https://bugzilla.redhat.com/show_bug.cgi?id=1216279 ) and went to submit
the updates. I noticed that bodhi 2.0 won't autocomplete the names of
updates. I believe that would happen before the update to 2.0.
Is this a known issue? I didn't find it when looking through the list at
https://github.com/fedora-infra/bodhi/issues
Thanks,
Dave

[Haïkel]

There's autocompletion on package name, but looks like bodhi
autocompletion database was not refreshed.


H.

[Kevin Fenzi]

On Sat, 12 Sep 2015 16:15:24 -0700
Dave Johansen <davejohansen(a)gmail.com&gt; wrote:

>  I just finished the review for cppformat (
>  https://bugzilla.redhat.com/show_bug.cgi?id=1216279 ) and went to
>  submit the updates. I noticed that bodhi 2.0 won't autocomplete the
>  names of updates. I believe that would happen before the update to
>  2.0. Is this a known issue? I didn't find it when looking through the
>  list at https://github.com/fedora-infra/bodhi/issues 
Not fully sure what you mean here... 

If you are submitting a new update you should be able to enter the name
of the package in the "Packages" area, select the package name and then
hit return and it should populate candidate builds and related bugs. 

So, that works for you, but not on cppformat? or breaks somewhere else?

kevin

[Tom Hughes]

On 13/09/15 19:02, Kevin Fenzi wrote:
>  On Sat, 12 Sep 2015 16:15:24 -0700
>  Dave Johansen <davejohansen(a)gmail.com&gt; wrote:
>
> > I just finished the review for cppformat (
> > https://bugzilla.redhat.com/show_bug.cgi?id=1216279 ) and went to
> > submit the updates. I noticed that bodhi 2.0 won't autocomplete the
> > names of updates. I believe that would happen before the update to
> > 2.0. Is this a known issue? I didn't find it when looking through the
> > list at https://github.com/fedora-infra/bodhi/issues
>
>  Not fully sure what you mean here...
>
>  If you are submitting a new update you should be able to enter the name
>  of the package in the "Packages" area, select the package name and then
>  hit return and it should populate candidate builds and related bugs. 
Normally you're right, but if the package has only just been created 
then it doesn't work. I assume bodhi catches up eventually but there is 
definitely a delay when a new package is created during which bodhi 
won't find it and you have to enter the build name instead.

Tom

-- 
Tom Hughes (tom(a)compton.nu)
http://compton.nu/

[Michael Catanzaro]

On Sun, 2015-09-13 at 19:28 +0100, Tom Hughes wrote:
>  Normally you're right, but if the package has only just been
> created 
>  then it doesn't work. I assume bodhi catches up eventually but there
>  is 
>  definitely a delay when a new package is created during which bodhi 
>  won't find it and you have to enter the build name instead. 
I gave up trying to edit an update last week, because the new Bodhi
wouldn't autocomplete the build name, and I couldn't enter it manually
either. This was ridiculously hard to do in the old Bodhi, though, to
the point where I would normally give up and use fedpkg, so it's not
really a regression....

Michael