On 08/20/2015 12:00 PM, Paul Howarth wrote:
On 20/08/15 10:28, Ralf Corsepius wrote:
On 08/20/2015 09:51 AM, Milan Crha wrote:
On Wed, 2015-08-19 at 21:45 -0600, Kevin Fenzi wrote:
There will likely be oddities and bugs. Please file them in github so
we can prioritize them and get them fixed up.
https://github.com/fedora-infra/bodhi/issues
Hi,
I do not have a github account, and I'm currently not going to create
any (github is not my favorite site), thus I'm writing here instead
(after all, Fedora infrastructure issue => Fedora bugzilla, no?).
I share this view. I refuse to create a github account and do not
consider using any external account resources for Fedora to be
acceptable.
I tried to submit an update for Fedora 22 and it just tells me that it
wasn't able to submit it with absolutely no reason. My values are:
And this as well. I just tried to create an update for F23 and was just
told "unable to create update".
So be it, ... give me a ping when you think bodhi is ready for public
usage. ATM it definitely is not.
I had the same issue trying to create an update for F23. I was able to
manage it eventually by using "fedpkg update", once I'd updated
python-fedora from F21 updates-testing.
However, I later needed to edit that update to change the build, and the
result is an update with no builds that I can't even access any more.
https://github.com/fedora-infra/bodhi/issues/202
Looks like you need to hit "enter" after typing/pasting in the package
NVR into the "Candidate Builds" field, which was not at all obvious to me.
Aha ;()
I just somehow managed to push an update - No idea how.
While filling out the update form for a second time (The first try had
failed with the error above), out of a sudden a large number of popups
with checkboxes inside popped up.
After checking some of them, the update was reported to have been
pushed, except that the BZ, I had added manually seems to have been
ignored - Seems to me, as is this popup is not offering BZ's which have
been "closed rawhide" but require further action for fc23.
BTW: Something with time stamps of the rpmlint/taskotron checks seem to
be wrong, as well. I my case rpmlint reported to have checked the
package hours ago, while I had commited the package into git ca. 1/2
hour ago and submitted it minutes ago.
Ralf
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
