Hi Michael again after longer time,
I have finally decided to look over your response and using spacecmd
(within spacewalk 2.0) try to d) way:
> d) associate a repo with the cloned channel (the same external repo
which is associated with the original channel) and set exclude filters
for it > (API channel.software.addRepoFilter()). Just be aware of the
fact that even package excluded via filter can be pulled into channel if
it's
> Adependency of a different package. (Spacewalk-repo-sync does
dependency transitive closure.)
> I cloned existing channel with:
spacecmd {SSM:0}> softwarechannel_clone
Select source channel: centos6-x86_64-alt-ru
Channel Name: CentOS 6 ALT.ru Custom (x86_64)
Channel Label: centos6-x86_64-alt-ru-cust
Select Parent [blank to create a base channel]: centos6-x86_64
Copy source channel GPG details? [y/N]: y
Original State (No Errata) [y/N]: y
Now I listed existing filters on original repo:
spacecmd {SSM:0}> repo_listfilters "External yum repo - CentOS 6 ALT.ru
x86_64"
spacecmd {SSM:0}>
And now I wanted to add filter:
spacecmd {SSM:0}> repo_addfilters
repo_addfilters: Add filters for a user repo
usage: repo_addfilters repo <filter ...>
The problem is that I don't know the exact syntax for <filter>. If I can
use include filter or exclude filter as well. With googling I have just
found corresponding commit of filter implementation for spacecmd, but no
documentation.
Please can you point me to that documentation or a bit explain how
filter can be used?
In principle I wanted to exclude some packages from specifed repo,
because they are in conflict (modifed versions of existing packages)
with packages in existing CentOS base/updates/epel repos.
thank you!
michal
On 18. 4. 2013 14:40, Michael Mraka wrote:
Michal Bruncko wrote:
% Hi Michael,
%
% thanks for response. I've created clone of selected repository and
% removed unnecessary packages as you told. But the question is how
% this cloned channel stay up-to-date with original channel? I mean
% when there will be new packages/versions synced within original
% channel, how the synchronization will work with cloned channel now?
% As I can see currently no repository is selected within cloned
% channel - but how to keep up-to-date this cloned channel with some
% excluded packages?
Hi Michal,
there are couple of ways:
a) You can add new packages to cloned channel manually on
Channels > Manage Software Channels > Packages > Add
or
b) automate above via API calls
channel.software.listLatestPackages() and channel.software.addPackages()
or
c) automate via API channel.software.mergeErrata() if your workflow is
errata oriented
or
d) associate a repo with the cloned channel (the same external repo
which is associated with the original channel) and set exclude filters for
it (API channel.software.addRepoFilter()). Just be aware of the fact
that even package excluded via filter can be pulled into channel if it's
Adependency of a different package. (Spacewalk-repo-sync does dependency
transitive closure.)
Regards,
--
Michael Mráka
Satellite Engineering, Red Hat
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
--
Ing. Michal Bruncko, PhD., CCNP, RHCSA™
IT systems and network administrator
Coupled school of business and services Ruzomberok
Slovak Republic
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
