When you write "the same spacewalk-clone-by-date command" I assume you did update the "--to-date" parameter? If you leave that out or change it to the day you synced the additional packages on it *should* sync those.
That said I am still waiting on RH dev to report back why spacewalk-clone-by-date synced some packages but missed several dependencies resulting in a repo in a "broken" state. HTH Bram On Wed, Oct 23, 2013 at 6:44 AM, Lupin Deterd <[email protected]> wrote: > > Hi, > > I have created a cloned channel. > > spacewalk-clone-by-date --channels=centos6-x86_64-updates > dev-centos6-x86_64-updates --to_date=2013-10-24 -a > centos6-x86_64 centos6-x86_64-updates -u satadmin > > So I ended up with following source channel, > ->centos6-x86_64 - base > -> centos6-x86_64-updates - 1392pkgs > > and cloned channel. > ->dev-centos6-x86_64 > -> dev-centos6-x86_64-updates - 1367pkgs > > When I updated/sync my source centos6-x86_64-updates it's having a > new/updated 25 packages that differ from dev-centos6-x86_64-updates, now I > wanted sync my cloned repo to be in-sync with the source but invoking the > same "spacewalk-clone-by-date" command I used earlier to create it but it > doesn't sync the packages differences. > > I don't want to merge the packages using the UI, could it be done on cli? > > Thanks, > lupin > > _______________________________________________ > Spacewalk-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-list >
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
