Hello,
when you change the Oracle-specific SQL schema sources
(schema/spacewalk/oracle), please make sure from now on to also
commit the equivalent change to the PostgreSQL side
(schema/spacewalk/postgres). After you do so, please mark the Oracle
version on which the PostgreSQL is based by putting the SHA1 of
the Oracle source file to the first line of the PostgreSQL source.
If you don't do this, the spacewalk-schema rpm will not build, so
please keep in mind to do it from now on. Of course, you also
need to add Oracle schem upgrade script -- that stays the same.
For example, the file
schema/spacewalk/postgres/procs/lookup_package_arch.sql
now starts with
-- oracle equivalent source sha1
ff037ec343dd654b470e32c119fbf596c669364e
When you change schema/spacewalk/oracle/procs/lookup_package_arch.sql
and commit the change to the PostgreSQL file, put the new SHA1
(use the sha1sum command) to the PostgreSQL source instead of that
ff037... string.
Well, the file
schema/spacewalk/postgres/procs/lookup_package_arch.sql
actually starts with
-- oracle equivalent source sha1
ff037ec343dd654b470e32c119fbf596c669364e
-- retrieved from
./1235730481/28a92ec2f6056ccc56e0bc4b0da3630def22548f/schema/spacewalk/rhnsat/procs/lookup_package_arch.sql
because I've just spent some time to find the old matching Oracle
versions and I've retrofitted the SHA1 to our PostgreSQL code, so
please remove the second line at the same time because it will
no longer be true.
--
Jan Pazdziora
Principal Software Engineer, Satellite Engineering, Red Hat
_______________________________________________
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel
