On Tue, May 08, 2012 at 02:23:43PM +0100, Steven Hardy wrote:
> Hi Jan,
>
> Thanks for the reply:
>
> On Mon, May 07, 2012 at 12:54:32PM +0200, Jan Pazdziora wrote:
> > > Testing on satellite shows that the API provided issue_date is not offset
> > > aware, so the comparison works.
> > >
> > >
Hi Jan,
Thanks for the reply:
On Mon, May 07, 2012 at 12:54:32PM +0200, Jan Pazdziora wrote:
> > Testing on satellite shows that the API provided issue_date is not offset
> > aware, so the comparison works.
> >
> > I was going to implement a workaround in spacewalk-clone-by-date, but first
>
On Tue, Mar 20, 2012 at 11:03:40AM +, Steven Hardy wrote:
> Hi All,
>
> I've been testing some spacewalk-clone-by-date patches on both satellite
> (5.4.1) and spacewalk (nightly, postgresql), and I noticed the following on
> spacewalk:
>
> [root@fedora_satellite utils]# ./spacewalk-clone-b
Hi All,
I've been testing some spacewalk-clone-by-date patches on both satellite
(5.4.1) and spacewalk (nightly, postgresql), and I noticed the following on
spacewalk:
[root@fedora_satellite utils]# ./spacewalk-clone-by-date --to_date 2007-03-03
-u rhn-admin -l rhel-x86_64-server-5 zzerrtest2