Re: [Spacewalk-devel] Automating Oracle-xe Setup
On Wed, Feb 18, 2009 at 11:30:30AM -0800, Mike McCune wrote: >> >> % And the creation of the spacewalk user / permissions? >> >> su - oracle -c 'sqlplus / as sysdba' <> create user spacewalk identified by spacewalk default tablespace users; >> grant dba to spacewalk; >> alter system set processes = 400 scope=spfile; >> alter system set "_optimizer_filter_pred_pullup"=false scope=spfile; >> alter system set "_optimizer_cost_based_transformation"=off >> scope=spfile; EOS > > we should consider adding the user creation steps to spacewalk-setup Do you mean spacewalk-setup the package, or spacewalk-setup the file in /usr/bin? -- Jan Pazdziora Satellite Engineering, Red Hat ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] Important Git Guide Updates
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Made some updates this morning to the Git Guide in a number of areas, most importantly I've changed the example workflow to (a) avoid the "goto master, pull, goto branch, rebase, goto master, merge, push" dance and (b) discuss just working in master for those who do not like or understand the use of local branches, while still avoiding those cursed "merge" commits that pollute our history. All of this is made possible by git pull --rebase which I wasn't even aware of when I wrote the first draft of the guidelines. I've been using it myself lately and find it much simpler. Sections also added for understanding branches, resolving conflicts, and the difference between merge and rebase. PLEASE read these carefully if you are having problems with git, and I cannot recommend these resources enough: http://book.git-scm.com/ http://www.kernel.org/pub/software/scm/git/docs/user-manual.html The first is the happy magical sugar git introduction, the second is much more in depth and suitable for drilling into specific topics. Hoping to get a git lunch and learn or something like that set up for next Wednesday. Cheers, Devan - -- Devan Goodwin Software Engineer Spacewalk / RHN Satellite Halifax, Canada 650.567.9039x79267 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkmdfLUACgkQAyHWaPV9my5zJQCggXuum2drh7C62mmSHcLZBH6p 8q4Ani+bx26ADzdBGBjafNevk/MbXIHh =ddta -END PGP SIGNATURE- ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Important Git Guide Updates
Thanks Devan! Devan Goodwin wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Made some updates this morning to the Git Guide in a number of areas, most importantly I've changed the example workflow to (a) avoid the "goto master, pull, goto branch, rebase, goto master, merge, push" dance and (b) discuss just working in master for those who do not like or understand the use of local branches, while still avoiding those cursed "merge" commits that pollute our history. All of this is made possible by git pull --rebase which I wasn't even aware of when I wrote the first draft of the guidelines. I've been using it myself lately and find it much simpler. Sections also added for understanding branches, resolving conflicts, and the difference between merge and rebase. PLEASE read these carefully if you are having problems with git, and I cannot recommend these resources enough: http://book.git-scm.com/ http://www.kernel.org/pub/software/scm/git/docs/user-manual.html The first is the happy magical sugar git introduction, the second is much more in depth and suitable for drilling into specific topics. Hoping to get a git lunch and learn or something like that set up for next Wednesday. Cheers, Devan - -- Devan Goodwin Software Engineer Spacewalk / RHN Satellite Halifax, Canada 650.567.9039x79267 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkmdfLUACgkQAyHWaPV9my5zJQCggXuum2drh7C62mmSHcLZBH6p 8q4Ani+bx26ADzdBGBjafNevk/MbXIHh =ddta -END PGP SIGNATURE- ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] PGPORT: empty_blob() Commit For Review
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ran into an issue in satCerts.py with the use of empty_blob(), being used to insert into a table with a blob column which has a not null constraint. In PostgreSQL this column becomes a "bytea". First tried changing it to just '' but this breaks for Oracle as it evaluates to NULL. Thought briefly about changing it to nonsense like "nothingyet" but then decided to try a postgresql compatibility function. http://git.fedorahosted.org/git/?p=spacewalk.git;a=blob;f=schema/spacewalk/postgresql/procs/empty_blob.sql;h=4af10bf12c8d483bdc0606395c8e346ef2423d88;hb=ad648496420396db183fa6433628ab17f8d9fd0b Look ok? Thanks, Devan - -- Devan Goodwin Software Engineer Spacewalk / RHN Satellite Halifax, Canada 650.567.9039x79267 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkmdts0ACgkQAyHWaPV9my4LtwCgzh5bvmMkZJg/VthSJ9uPm/X0 CtUAn2iAj+zPZWkilVB4lgZN8/pgopkw =ig80 -END PGP SIGNATURE- ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] Re: build.py + dist-cvs update
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 thirdparty.git available at: git clone git+ssh://yourlo...@git.rhndev.redhat.com/scm/git/thirdparty.git oracle-instantclient is the only package there now. I brought the spec over from svn, removed the reverences to "sources" and "version" files, and fixed any issues with build.py. I see that we don't bother tracking sources for this project in source control (and rightly so given their size), is this something we should apply to all our third party libraries? Or do we wish to continue doing so if the .tar.gz is small enough? (how small?) It's probably still a little rough around the edges but if anyone wants to test feel free to clone and try: build.py --tag-release build.py --cvs-release Should look something like: Checking for tag [oracle-instantclient-10.2.0-36] in git repo [git+ssh://dgood...@git.rhndev.redhat.com/scm/git/thirdparty.git] Building release from CVS... Checking out cvs module [oracle-instantclient] Creating oracle-instantclient-10.2.0.tar.gz from git tag: fbd8da9d1c28045ea5e9f3a542c8acfa1baeaa55... Preparing to commit [/tmp/spacewalk-build/cvswork/oracle-instantclient] Switch terminals and run cvs diff in this directory to examine the changes. Do you wish to proceed with commit? [y/n] y Proceeding with commit. Creating CVS tags... (cd ../common && cvs update) cvs update: Updating . cvs update: Updating devel cvs tag -c oracle-instantclient-10_2_0-36_el4sat cvs tag: Tagging . T .cvsignore T Makefile T branch T oracle-instantclient.spec T sources T version Tagged with: oracle-instantclient-10_2_0-36_el4sat (cd ../common && cvs update) cvs update: Updating . cvs update: Updating devel cvs tag -c oracle-instantclient-10_2_0-36_el5sat cvs tag: Tagging . T .cvsignore T Makefile T branch T oracle-instantclient.spec T sources T version Tagged with: oracle-instantclient-10_2_0-36_el5sat Submitting CVS builds... (cd ../common && cvs update) cvs update: Updating . cvs update: Updating devel Created task: 1700283 Task info: http://brewweb.devel.redhat.com/brew/taskinfo?taskID=1700283 (cd ../common && cvs update) cvs update: Updating . cvs update: Updating devel Created task: 1700285 Task info: http://brewweb.devel.redhat.com/brew/taskinfo?taskID=1700285 If run on something that's already been tagged, it will have nothing to commit for the spec file and die trying to run make tag. (this behavior seems ok to me) Next stage will be moving the existing projects left in svn, as well as those under spec-tree/ in git into thirdparty. This will have implications in that the build-missing* scripts will not catch them anymore, but this seems to be only a marginal concern considering the projects will be built from binary packed source. (and rarely at that) Hopefully we can keep thirdparty as just a master branch, but if necessary we can create branches to track spacewalk and satellite releases. Cheers, Devan - -- Devan Goodwin Software Engineer Spacewalk / RHN Satellite Halifax, Canada 650.567.9039x79267 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkmeLFUACgkQAyHWaPV9my6NaQCcCsB42Pnq/VZtt3O7j08eohfK zjwAnRAHR7TjMIi6FNZ96ezMkhRgdT1W =/cKX -END PGP SIGNATURE- ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
