> Is there any reason this couldn't land in Ubuntu proper (throug the SRU
> process)?
I've verified that this bug is present in released images of both hardy
and intrepid. On the intrepid image, i did an
apt-get install launchpad-client
there were no updates available.
I think we really need to pursue proper (SRU) updates for this, and stop
maintaining/using ppa builds of landscape-client in our ec2/uec images. I
apologize for anything I said previously that implied anything else.
One other thing to note, this is fairly easily worked around by a
user-data script (or other post-boot configuration).
I verified that 'sudo /etc/cron.hourly/landscape-client' is functional on
a system after booting with:
xc2-run-instances --user-data-file=user-data.sh ami-5059be39
and 'user-data.sh' as below.
--- user-data.sh ---
#!/bin/sh
RUN=""
conf=/etc/default/landscape-client
. ${conf}
if [ -n "${RUN}" ]; then
echo "run set to ${RUN} in ${conf}"
else
echo "fixing ${conf}, setting RUN=1"
echo "RUN=1" >> ${conf} ||
{ echo "failed."; exit 1; }
echo "updated ${conf}"
fi
--- end user-data.sh ---
--
landscape-client cron job is broken
https://bugs.launchpad.net/bugs/421707
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
