[Spacewalk-devel] Advanced Yum Repo Question
Hello everyone,
I'm working on building a yum repo generator from Spacewalk sources.
It will function like this:
Jump into the Spacewalk API, snag all the packages. Build them into a list.
Insert all the data into a sqlite database (easiest way to power this
type of project I think, no I don't want to hook into the life DB
either, it should be DB free imo).
Download metadata for each package, insert into the sqlite database.
Build various files {other,primary,filelists}.xml
Now here's my question. Before I get to involved in something that may
or may not work, from my understanding
can point to a full URL correct? As in
"http://spacewalk/bla/bla/bla/something.rpm";?
If not, the only other solution I can think of is writing an apache
mod_rewrite rule for each package. This repo is ideally going to sit
on the Spacewalk server, so doing some rewrites isn't that big of a
deal. Considering the goal is to simply create yum repos from
Satellite packages and channels I think these are logically my best
two options without entering the database.
My reasons for not entering the database are the following:
1. Security policies in the office.
2. My Oracle-fu sucks.
So if someone says that I should be pulling the DB directly and can
give me a few good reasons, and possibly be willing to let me bounce
some queries off them, I would be more than happy to do it that way.
It would be quicker after all.
--
Steven Crothers
steven.croth...@gmail.com
___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] Submission of a script I would like to contribute
Hello every one I have created a Perl script to update and list the default channel map in spacewalk via the XMLRPC API and my current employer who shall remain nameless has authorized me to share it under the terms of the GPL. This is a partial workaround to https://bugzilla.redhat.com/show_bug.cgi?id=786705 "reactivation key do not preserve my custom base channel" Since this script uses the XMLRPC API unlike the method mentioned in the ticket this script should work for PostgreSQL and Oracle however I've only tested it against PostgreSQL. There is also a man page embedded in the script in POD format so the pod2(man|text|html|etc...) tools can be used to extract it. it depends on the following Perl modules strict Frontier::Client Getopt::Long Pod::Usage Term::ReadKey Note: This script does NOT do the more controversial part of the workaround namely dropping the constraint on the description field in the rhnserverhistory table which may or may not be a PostgreSQL specific bug. I hope people find it useful enough to add into the git repository Thank You Paul Robert Marino spacewalk-dist-channel-map.pl Description: Binary data ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Status of Debian support in Spacewalk
> > I'm also interested, we have some Debian 5 machines here in our > environment and a healthy Debian following. > > Where can I sign up? Where is your existing work at, and notes if you have > them? > Steven, I'll try to summarize where the available readings about Debian support lies. Page about registering Debian clients to the Spacewalk. - https://fedorahosted.org/spacewalk/wiki/RegisteringClients#Debian Overall status and a few outdated examples. - https://fedorahosted.org/spacewalk/wiki/Deb_support_in_spacewalk Current deb packaging repository, including apt-spacewalk sources - http://git.fedorahosted.org/git/?p=spacewalk.git;a=tree;f=client/debian Currently opened bugs: - https://bugzilla.redhat.com/show_bug.cgi?id=703834 - https://bugzilla.redhat.com/show_bug.cgi?id=703838 A few threads on Spacewalk mailinglist (keywords: debian, apt) Additionally, there are two whitepapers about Debian support: - http://www.fit.vutbr.cz/study/DP/DP.php?id=8013&y=2009 - http://www.fit.vutbr.cz/study/DP/BP.php?id=12397&y=2010 If I can I would suggest 'Chapter 5 - Conclusion' of the latter. Finally, I and Mirek will be happy to answer any questions. Best regards, -- Simon Lukasik ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Status of Debian support in Spacewalk
Mirek, That was the best email I've read all day. Thank you. I'm also interested, we have some Debian 5 machines here in our environment and a healthy Debian following. Where can I sign up? Where is your existing work at, and notes if you have them? On Thu, Mar 29, 2012 at 2:35 AM, Miroslav Suchy wrote: > On 28.3.2012 21:29, Eduardo Bergavera wrote: >> >> Hi, >> >> What necessary skills to become a volunteer in this effort? > > > Ability to read, write. Ability to thinking and knowledge of command line is > advance, but not strictly required. :) > > You will have to read through: > > http://www.google.com/search?q=how%20to%20build%20debian%20package&hl=cs&lr= > http://www.debian.org/doc/manuals/maint-guide/index.en.html > > Then follow what is written in those article. Then write various rules file. > E.g. you will learn that in RPM world we write: > Build-Requires: python > while in DEB world they write: > Build-Depends: python > etc. Very rarely you will have to use git, tar or make. But only in entry > level knowledge, which you can gain after reading some basic tutorial for 30 > minutes (unless you already know it). > > To summarize it - when you wrote this email you already proved that you have > all required skills. Now you have to decide if you want to dedicate your > time to this. > > Mirek > > > ___ > Spacewalk-devel mailing list > Spacewalk-devel@redhat.com > https://www.redhat.com/mailman/listinfo/spacewalk-devel -- Steven Crothers steven.croth...@gmail.com ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] [PATCH] Naming of cloned errata
On 03/07/2012 11:57 AM, Johannes Renner wrote: > On 03/06/2012 05:42 PM, Johannes Renner wrote: >> Hey, >> >> I want to propose a change concerning the names of cloned errata. >> Currently, names of cloned errata are generated like this: >> >> String clonedAdvisoryName = "CL" + published.getAdvisoryName().substring(3); >> String clonedAdvisory = "CL" + published.getAdvisory().substring(3); >> >> The reason for doing it like this might have been a small sized field in the >> database, but AFAIK we already upstreamed a patch to enlarge the respective >> field. Since cloned errata currently end up with rather strange names, I >> would like to propose to do the naming like this instead: >> >> String clonedAdvisoryName = "CL-" + published.getAdvisoryName(); >> String clonedAdvisory = "CL-" + published.getAdvisory(); >> >> Even the classification used for the Red Hat patches (E, S and B) gets lost >> when removing the first 3 characters, since names start with RH(E|S|B). So >> please tell me if I am missing any reason to keep the old naming scheme. >> >> Attached please find my proposed patch for spacewalk master. > > Of course this algorithm is duplicated in the perl parts of Spacewalk ;-) > Patch is attached. Just reactivating/raising this thread on the list since there is no comments yet, and I'm curious if you will accept the proposed changes or not. Thanks, Johannes -- SUSE LINUX Products GmbH, HRB 16746 (AG Nürnberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] [PATCH] Checkstyle 4.1 vs. 4.3
On Friday 30 of March 2012 10:44:19 Johannes Renner wrote:
> Hey,
>
> You are using checkstyle 4.1 it seems, while we use version 4.3.
> Our version seems to need the lib directory jars to be contained
> in the classpath for finding exception classes the are referenced
> by @throws clauses. Otherwise we get a lot of these errors:
>
> ./code/src/com/redhat/rhn/common/hibernate/HibernateFactory.java:0: Got an
> exception - java.lang.RuntimeException: Unable to get class information for
> @throws tag 'HibernateException'.
Since the change does not break our checkstyle, and fixes yous :-), applying
as: 894008bb9d1dd94b8c3677bfe01c57812c75e881
>
> Also 4.3 doesn't like the @{inherit-doc} for methods that are not
> actually overrides, like the constructor in ScapActionDetails.java:
>
> ./code/src/com/redhat/rhn/domain/action/scap/ScapActionDetails.java:33:5:
> Invalid use of the {@inheritDoc} tag.
Right, you're correct. Applied as: 1608dcf63390c62b2acf62476ba8040a7b9d799a
>
> Just in case you are planning to upgrade or want to fix anyways.
>
> Regards,
> Johannes
Thank you, Johannes!
Regards,
--
Tomas Lestach
RHN Satellite Engineering
___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] [PATCH] Checkstyle 4.1 vs. 4.3
Hey,
You are using checkstyle 4.1 it seems, while we use version 4.3.
Our version seems to need the lib directory jars to be contained
in the classpath for finding exception classes the are referenced
by @throws clauses. Otherwise we get a lot of these errors:
./code/src/com/redhat/rhn/common/hibernate/HibernateFactory.java:0: Got an
exception -
java.lang.RuntimeException: Unable to get class information for @throws tag
'HibernateException'.
Also 4.3 doesn't like the @{inherit-doc} for methods that are not
actually overrides, like the constructor in ScapActionDetails.java:
./code/src/com/redhat/rhn/domain/action/scap/ScapActionDetails.java:33:5:
Invalid use of the
{@inheritDoc} tag.
Just in case you are planning to upgrade or want to fix anyways.
Regards,
Johannes
--
SUSE LINUX Products GmbH, HRB 16746 (AG Nürnberg)
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer
>From 0bcacfc4bbc032c17263198f5bc8dde4ec000aef Mon Sep 17 00:00:00 2001
From: Johannes Renner
Date: Fri, 30 Mar 2012 10:26:25 +0200
Subject: [PATCH] Add lib directory to checkstyle classpath
---
java/spacewalk-java.spec |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/java/spacewalk-java.spec b/java/spacewalk-java.spec
index 2fc7361..7ae7c45 100644
--- a/java/spacewalk-java.spec
+++ b/java/spacewalk-java.spec
@@ -327,7 +327,7 @@ ant -Dprefix=$RPM_BUILD_ROOT init-install compile
%if 0%{?run_checkstyle}
echo "Running checkstyle on java main sources"
-export CLASSPATH="build/classes"
+export CLASSPATH="build/classes:build/build-lib/*"
export BASE_OPTIONS="-Djavadoc.method.scope=public \
-Djavadoc.type.scope=package \
-Djavadoc.var.scope=package \
--
1.7.7
>From 2b57a83dd3346dcaeff55586cacc13e5728e3d38 Mon Sep 17 00:00:00 2001
From: Johannes Renner
Date: Thu, 29 Mar 2012 16:10:13 +0200
Subject: [PATCH] Fix checkstyle error (invalid use of the {@inheritDoc} tag)
---
.../rhn/domain/action/scap/ScapActionDetails.java |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/java/code/src/com/redhat/rhn/domain/action/scap/ScapActionDetails.java b/java/code/src/com/redhat/rhn/domain/action/scap/ScapActionDetails.java
index 7c34c49..885da51 100644
--- a/java/code/src/com/redhat/rhn/domain/action/scap/ScapActionDetails.java
+++ b/java/code/src/com/redhat/rhn/domain/action/scap/ScapActionDetails.java
@@ -28,7 +28,7 @@ public class ScapActionDetails extends ActionChild {
private byte[] parameters;
/**
- * {@inheritDoc}
+ * Default constructor.
*/
public ScapActionDetails() {
super();
--
1.7.7
___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel
