On Wed, 2009-08-12 at 18:01 -0500, Justin Sherrill wrote:
> I think re-running this sql script will fix all the currently broken
> channels, but you'll have to rerun it to fix newly created channels
> every time (until a permanent fix gets created):
> 
> SQL> UPDATE rhnChannel SET
>        checksum_type_id = (select id
>                             from rhnChecksumType
>                            where LABEL = 'sha1')
>     WHERE checksum_type_id is null;
> 
> 
> 
> -Justin

Hi Team,

I hate to kick a dying horse... but I tried this.  Updating the database
directly did indeed update the record for the channel I just cloned,
however, I think because I've added the check that Prad suggested to the
webform, it's keeping me from being able to edit anything about this
channel.  After making the SQL change, when I try to edit the cloned
channel it shows SHA-256.. because of the minor check that I added:

-            form.set("checksum", c.getChecksum().getLabel());
+            if (!c.isCloned()) {
+                form.set("checksum", c.getChecksum().getLabel());
+            }

I think that field isn't getting set in the form.  So, while displaying
the webform works (and that field defaults to SHA-256) trying to edit it
without having anything in that field causes it to bork?

I'm really not sure here... 

Thoughts?
-- 
Andy Speagle

"THE Student" - UCATS
Wichita State University

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
Spacewalk-devel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-devel

Reply via email to