I found a late-breaking problem in the Insight system. The drupal6 RPM includes an hourly cron file in /etc/cron.hourly/drupal6 that points to the wrong URL. It's not something that should be tinkered with in the RPM, because the value could be perfectly reasonable for some installations.
Should I store an alternate copy in the puppet files/ for this module?
On Mon, 2011-03-21 at 15:49 -0400, Paul W. Frields wrote:
I found a late-breaking problem in the Insight system. The drupal6 RPM includes an hourly cron file in /etc/cron.hourly/drupal6 that points to the wrong URL. It's not something that should be tinkered with in the RPM, because the value could be perfectly reasonable for some installations.
Should I store an alternate copy in the puppet files/ for this module?
sure.
-sv
On Mon, Mar 21, 2011 at 03:57:45PM -0400, seth vidal wrote:
On Mon, 2011-03-21 at 15:49 -0400, Paul W. Frields wrote:
I found a late-breaking problem in the Insight system. The drupal6 RPM includes an hourly cron file in /etc/cron.hourly/drupal6 that points to the wrong URL. It's not something that should be tinkered with in the RPM, because the value could be perfectly reasonable for some installations.
Should I store an alternate copy in the puppet files/ for this module?
sure.
OK, I fixed this and also some other missing file definitions in the manifest. I think averi and I are going to need to run another test of the staging routine to make sure things are still working properly.
logistics@lists.fedoraproject.org