Re: [Spacewalk-devel] rpmbuild directories in git
On Thu, Jan 15, 2009 at 03:27:23PM -0500, Jesus M. Rodriguez wrote: Any reason we checked in rpmbuild-perl-DBD-Oracle-git* directories? I've removed them now. I've also changed Makefile.tag-release not to do git add . so they should not be added in the future. I've checked that rel-eng/lib/spacewalk/releng/tagger.py already does not have it either. -- Jan Pazdziora Satellite Engineering, Red Hat ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] perl-DBD-Oracle build without tag
Jan Pazdziora wrote: % Hello Dennis, % % I can see that you manually (?) bumped version of perl-DBD-Oracle in % commit 659586abd2a5ab66aed83dd8eed54d997864dee0 and built the result, % without using make tag-minor-release to keep the information in % rel-eng in a sane state. Thus, koji-missing-builds.pl then reports % extra build perl-DBD-Oracle-1.22-6.el5 and missing build % perl-DBD-Oracle-1.22-5. % % May I suggest you re-read % https://fedorahosted.org/spacewalk/wiki/ReleaseProcess % for the steps that need to be done. Hello Dennis, I noticed that you fixed the problem and tagged new commit 001c4ac - Automatic commit of package [perl-DBD-Oracle] [1.22-6]. Unfortunately there is no tag perl-DBD-Oracle-1.22-6 in the git repo. You probably forgot to 'git push --tags'. Please fix the problem above by extra git push --tags. -- Michael Mráka Satellite Engineering, Red Hat ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Is Spacewalk Proxy rawhide supposed to work?
Jan, did you ever get this to work? It's been a while since I tried getting proxy up and running (probably shortly after the 0.3 release) but I never got it to work properly. I'd be interested to know if you have any success. -R On Thu, Jan 15, 2009 at 2:54 PM, Jan Pazdziora jpazdzi...@redhat.com wrote: On Mon, Jan 12, 2009 at 05:55:52PM +0100, Miroslav Suchý wrote: That is long story. If you want just short answer - yes, it is working. But it is winter time and you may want to read some story during long evenings. So make yourself some hot tee and sit down comfortably. This is story about chicken and egg... In Satellite you have proxy packages in Proxy channel and since we wanted to created command line installer (CLI) for proxy and only possible way to make proxy channel available from command line is rhn-proxy-activate and since this command is in Proxy channel ... you are busted. So I have to cut this circle somewhere and I decided to move rhn-proxy-activate to separate package (in spacewalk spacewalk-proxy-installer) and it is available in RHN Tools channel. So if you install spacewalk-proxy-installer you will only install packages needed for installer run. So, rhncfg, rhncfg-actions, rhncfg-client, and rhncfg-management are really all needed to run the installer and activate the proxy? And httpd? -- Jan Pazdziora Satellite Engineering, Red Hat ___ 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
Re: [Spacewalk-devel] Moving content of satellite/ around: proposal 1
Jan Pazdziora wrote: % in the satellite/ directory, we have the following packages: % % $ find satellite -name '*.spec' % satellite/admin/spacewalk-admin.spec % satellite/certs/spacewalk-certs-tools.spec % satellite/config/spacewalk-config.spec % satellite/install/Spacewalk-Setup/spacewalk-setup.spec % satellite/schema/schema.spec % satellite/spacewalk.spec % % The name of the directory (satellite) is misleading, so I plan to % rename it to ... let's see ... spacewalk? Hello Jan, this is one of things on my todo list so I completely agree. % Packages spacewalk-admin, spacewalk-certs-tools, and spacewalk-config % are OK, except for certs which could have certs-tools in the directory % name to match the package name. Yes. % The satellite/install/ directory contains a lot of code that we do not % use in Spacewalk -- the original Satellite installer. I'd like to % remove it as well but we shall see what the layout of the Satellite % repo will be. In any case, I propose moving % satellite/install/Spacewalk-Setup/ up, away from that directory. % % The satellite/schema/schema.spec is a rhns-schema-tools package which % was never tagged or built in Spacewalk, so I propose to remove it % completely. Again agree with purging unused code. % The problem with satellite/spacewalk.spec being on this level is that % % git-untagged-commits.pl % % will show % % spacewalk-0.4.2-3..HEAD: % d7f34f039f8334a8ef173367a124ad3d8ecf Automatic commit of package [spacewalk-setup] release [0.4.23-1]. % 8aeb652ed014e2721406ccb9cf0eef72cb1a4981 remove legacy satellite upgrade message (not required in Spacewalk) % aebb69c70457c7231a958aeebfa6b03bb84acbe0 don't setup monitoring during upgrade (it's already configured) % e6bf13edf49a724c97b89e9e8b80561c2b823eca run ssl virtual host configuration even for upgrades % 104bbdd663aca0cc72ccc9ed5c24a227dc28757f Automatic commit of package [spacewalk-config] release [0.4.24-1]. % ce0b2bcb362d7d0b85bdbedd120f54ab5f1f85e7 480095 - old package name. % [...] % % even if those commits belong to packages stored in subdirectories of % satellite/ -- git-untagged-commits.pl does not know that the % spacewalk package is only about the spacewalk.spec file and nothing % else. We might try to do some changes to the git-untagged-commits.pl % but I'd prefer to find new home for the spacewalk package, where it % will not have anything underneath it. And what about merging spacewalk and spacewalk-setup packages (whatever new name will be)? If you configure a package via spacewalk-setup you definitely need all that packge installed so it sould be required by spacewalk-setup package. The rest of packages should be installed as dependencies of those first level packages. % So sum up, I plan to do the following changes: % % satellite/admin/ = spacewalk/admin/ % satellite/certs/ = spacewalk/certs-tools/ % satellite/config/ = spacewalk/config/ % satellite/install/Spacewalk-Setup/ = spacewalk/setup/ remove the rest of satellite/install/* % remove satellite/schema/ % satellite/spacewalk.spec = spacewalk/package/spacewalk.spec % satellite/Makefile = spacewalk/package/Makefile Couple of other things: * gzipstream/ contains zlib-python interface so we should move gzipstream/ = spec-tree/python/gzipstream/ * projects/cobbler/ - no spec there. I can see cobbler-setup there but there is another cobbler-setup in satellite/install/Spacewalk-Setup/bin/. Should be projects/cobbler safely removed? * projects/ssl-cert-check/ - what about moving projects/ssl-cert-check/ = spacewalk/ssl-cert-check/ where people expects spacewalk-* packages? % Please raise your objections, And we should not forget to tag moved packages so rel-eng/packages/* point to right location. -- Michael Mráka Satellite Engineering, Red Hat ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Is Spacewalk Proxy rawhide supposed to work?
On Fri, Jan 16, 2009 at 11:12:05AM +, Rob James wrote: Jan, did you ever get this to work? It's been a while since I tried getting proxy up and running (probably shortly after the 0.3 release) but I never got it to work properly. I'd be interested to know if you have any success. Yes, Spacewalk Proxy 0.4 works fine for me. -- Jan Pazdziora Satellite Engineering, Red Hat ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] Re: Spacewalk 0.4 is here!
On Thu, Jan 15, 2009 at 05:43:23PM -0500, Jesus M. Rodriguez wrote: * SELinux support added: https://fedorahosted.org/spacewalk/wiki/Features/SELinux I've now updated that page with a short list of hints about how to spot a problem on Spacewalk with SELinux enabled and what could be done about it, as well as list of SELinux-related rpms and expected types for running processes. Comments welcome, -- Jan Pazdziora Satellite Engineering, Red Hat ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] Re: [Spacewalk-list] Spacewalk 0.4 is here!
Jesus M. Rodriguez wrote: The Spacewalk team is happy to announce the release of Spacewalk 0.4. In a few hours, the repos will be accessible and you can install 0.4 and try it out. FYI: Freshmeat page updated: http://freshmeat.net/projects/spacewalk/?branch_id=76942release_id=292281 -- Miroslav Suchy RHN Satellite Engineering, Red Hat ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Re: Spacewalk 0.4 BRANCHED
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 16 Jan 2009 11:07:46 +0100 Michael Mraka michael.mr...@redhat.com wrote: Jesus M. Rodriguez wrote: % master = spacewalk 0.5 % SPACEWALK-0.4 = spacewalk 0.4 Why 0.4 branch is called SPACEWALK-0.4 while we have RELEASE-0.2 and RELEASE-0.3 branches? I asked Jesus to change the naming for clarity with the Satellite git repo. (SPACEWALK-0.4 and SATELLITE-5.3 instead of RELASE-X.Y for both) We could quite easily push those old RELEASE-0.2 to RELEASE-0.3 branches with a new name to make them conform if you'd like. Cheers, Devan - -- Devan Goodwin dgood...@redhat.com Software Engineer Spacewalk / RHN Satellite Halifax, Canada 650.567.9039x79267 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAklwjVwACgkQAyHWaPV9my42YgCfQz+DV/hEdBmezgzB1HosKowp LXIAoI5h7ohY0tAhqjIqE4yEeHhGyjWR =d42C -END PGP SIGNATURE- ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Re: [Spacewalk-list] Spacewalk 0.4 is here!
Miroslav Suchý wrote: % E. The builds failed: % GenericError: Unable to complete build: release mismatch (build: 1.el5, % rpm: 1) % % Dennis, is it possible that you removed buildsys-macros from % dist-5E-sw-0.4-candidate ? IMO this is a very good reason not to move packages between tags but have them tagged to more locations simultaneously. Dennis, please could you tell me the reason why do you insist on moving them? (Other than We always do it this way in Fedora because it isn't a reason.) -- Michael Mráka Satellite Engineering, Red Hat ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Which jabberd in Spacewalk?
On Tue, Jan 13, 2009 at 10:22:08AM +0100, Miroslav Suchý wrote: Jan Pazdziora wrote: page. However, jabberd is *not* in EPEL. What are our plans with that thing? Let assume that it is rhetorical question. Rhetorical answer: Upgrade to 2.2.4 and ask maintainer if he can build jabberd for EPEL? FYI: I've tried to poke the jabberd maintainer, in the end I've asked for jabberd in EPEL via bugzilla 480335. -- Jan Pazdziora Satellite Engineering, Red Hat ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Re: [Spacewalk-list] Spacewalk 0.4 is here!
On Friday 16 January 2009 08:47:19 am Michael Mraka wrote: Miroslav Suchý wrote: % E. The builds failed: % GenericError: Unable to complete build: release mismatch (build: 1.el5, % rpm: 1) % % Dennis, is it possible that you removed buildsys-macros from % dist-5E-sw-0.4-candidate ? IMO this is a very good reason not to move packages between tags but have them tagged to more locations simultaneously. Dennis, please could you tell me the reason why do you insist on moving them? (Other than We always do it this way in Fedora because it isn't a reason.) I move packages because they are no longer candidates they are now released the tags reflect such. buildsys-macros is not and has never been in dist-5E- sw-0.4-candidate or any tag that it inherits from. it gets inherited in dist-5E-sw-0.4-build from dist-5E-sw-0.3-build, dist-5E-sw-0.4-build is used to populate the buildroots. it seems that the inheritance was removed. ive now fixed that up. once https://koji.rhndev.redhat.com/koji/taskinfo?taskID=4579 is complete you will be able to build. Dennis signature.asc Description: This is a digitally signed message part. ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] Re: Spacewalk 0.4 BRANCHED
Michael Mraka wrote: Jesus M. Rodriguez wrote: % master = spacewalk 0.5 % SPACEWALK-0.4 = spacewalk 0.4 Why 0.4 branch is called SPACEWALK-0.4 while we have RELEASE-0.2 and RELEASE-0.3 branches? -- Michael Mráka Satellite Engineering, Red Hat As part of the on going Spacewalk to Satellite process. We've decided to rename it. It makes the Satellite portion easier :) -- jesus m. rodriguez| jes...@redhat.com sr. software engineer | irc: zeus rhn satellite spacewalk | 919.754.4413 (w) rhce # 805008586930012| 919.623.0080 (c) +---+ | Those who cannot learn from history | | are doomed to repeat it. | | -- George Santayana | +---+ ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] PGPORT (installation issue using make)
On Fri, Jan 16, 2009 at 05:25:39PM +0530, tushar ahuja wrote: 2)I have installed 0.3.version of spacewalk Spacewalk 0.4 was released yesterday. Could you maybe move over to that version, so see if it fixes the issue you see? -- Jan Pazdziora Satellite Engineering, Red Hat ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] PGPORT (installation issue using make)
thanks Jan. Sure I will try to upgrade 0.3 to 0.4 .and let you know the result. i am just wondering is this a known issue ,has someone already encountered with this problem ? or i am doing something wrong ? as i am not able to find any thread against this issue at spacewalk-devel list. -- regards,tushar Member Technical Staff RD Group Enterprisedb ,visit us at :- http://enterprisedb.com On 1/17/09, Jan Pazdziora jpazdzi...@redhat.com wrote: On Fri, Jan 16, 2009 at 05:25:39PM +0530, tushar ahuja wrote: 2)I have installed 0.3.version of spacewalk Spacewalk 0.4 was released yesterday. Could you maybe move over to that version, so see if it fixes the issue you see? -- Jan Pazdziora Satellite Engineering, Red Hat -- -- regards, tushar ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
