On Mon, Nov 10, 2008 at 5:31 AM, Jan Pazdziora <[EMAIL PROTECTED]> wrote: > On Sat, Nov 08, 2008 at 10:34:11AM +0100, Jan Pazdziora wrote: >> On Fri, Nov 07, 2008 at 04:38:43PM -0500, Clifford Perry wrote: >> > >> > Just to follow up quickly - issue was because of previous upgrade from >> > 0.1 -> 0.2 - we attempt to create a duplicate entry. Gave a short term >> > work around solution on IRC. We need to address/fix code for the >> > /usr/bin/spacewalk-schema-upgrade command to not attempt to create >> > duplicate 'schema-from' entries in the DB, but maybe delete the old >> > upgrade entry or sequentially bump them up. >> >> Umm, I'm pretty sure that I was checking the schema and I did not >> see that unique constraint on label when I did write >> spacewalk-schema-upgrade. So the idea was to have multiple >> schema-from records, to hold the full schema upgrade history. >> >> I'll have to investigate some more. > > So it looks like I missed the unique key. > > I've filed bugzilla for the problem now: > > https://bugzilla.redhat.com/show_bug.cgi?id=470791 > > Zeus, asking for approval to fix this in RELEASE-0.3 and get the new > spacewalk-schema for the 0.3 release out. > > Alternatively we can tell people how to delete the original record > before upgrading from 0.2 to 0.3 (if they rpeviously upgraded from 0.1 > to 0.2) and only fix this for 0.4. >
Sure fix it in RELEASE-0.3 and master, and build the pkg. Once it's done I can upload to the repo. jesus _______________________________________________ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
