This is related to [https://fedorahosted.org/bodhi/ticket/235 Bodhi Ticket #235].
I tried to file updates for gimp-2.6.4-{1,2}.fc{9,10} which contained an extensive notes text (see my comment in the Bodhi ticket, I copied over large parts of it from the [http://developer.gimp.org/NEWS-2.6 GIMP 2.6 NEWS file].
Besides the apparent bugs in the Bodhi code, the database seems to be inconsistent: when I try to file updates for the same n-v-r, I e.g. get a "gimp-2.6.4-2.fc10 update already exists!" error, but if I follow the link it gives me "There are no updates for gimp-2.6.4-2.fc10". From the outside, this looks like a referential integrity problem in the DB schema.
I'd really like to file these updates, so I'd appreciate any help and would also be willing to get my hands dirty... I'm a member of the non-specific "sysadmin" group, but haven't decided yet what specific subgroup to apply for first. Perhaps sysadmin-web would be a good start, then I could tackle this problem on my own (with a bit of guidance).
I've applied for sysadmin-web membership.
Yep, this is related to the unicode issue described in bug #235, as well as [https://fedorahosted.org/bodhi/ticket/288 #288]. It seems that it is creating the PackageBuild objects, without the PackageUpdate. I went ahead and deleted the stray builds from the database, which should allow you to submit the update. However, it will still choke on non-ascii characters at the moment. I'm thinking that this may be an issue with SQLObject, or the postgres bindings -- because this code hasn't changed in a long time, and used to work fine with unicode characters. I added a test_unicode_fail unit test to bodhi's test suite, which can reproduce the problem; now we just need to figure out how to fix it :)
I believe to have fixed this issue, and just pushed the fix into production. Please re-open this ticket if you still experience this problem, thanks.
Login to comment on this ticket.