The cronscript has been running every minute for a few weeks now:
{{{
2010-10-20 00:03:05 INFO Creating lockfile: /var/lock/launchpad-generate-ppa-htaccess.lock
2010-10-20 00:03:15 INFO Starting the PPA .htaccess generation
2010-10-20 00:03:15 INFO Committing transaction...
2010-10-20 00:03:15 INFO Finished PPA .htaccess generation
2010-10-20 00:03:24 DEBUG Removing lock file: /var/lock/launchpad-generate-ppa-htaccess.lock
2010-10-20 00:04:04 DEBUG Cronscript control file not found at file:cronscripts.ini
2010-10-20 00:04:04 INFO Creating lockfile: /var/lock/launchpad-generate-ppa-htaccess.lock
2010-10-20 00:04:14 INFO Starting the PPA .htaccess generation
2010-10-20 00:04:14 INFO Committing transaction...
2010-10-20 00:04:14 INFO Finished PPA .htaccess generation
2010-10-20 00:04:23 DEBUG Removing lock file: /var/lock/launchpad-generate-ppa-htaccess.lock
2010-10-20 00:05:04 DEBUG Cronscript control file not found at file:cronscripts.ini
2010-10-20 00:05:04 INFO Creating lockfile: /var/lock/launchpad-generate-ppa-htaccess.lock
2010-10-20 00:05:14 INFO Starting the PPA .htaccess generation
2010-10-20 00:05:15 INFO Committing transaction...
2010-10-20 00:05:15 INFO Finished PPA .htaccess generation
2010-10-20 00:05:24 DEBUG Removing lock file: /var/lock/launchpad-generate-ppa-htaccess.lock
}}}
So I assume this bug is fix released (as in users should no-longer see a 401 when the repository is accessed after a successful purchase). Soyuz would still like to work on a better long-term fix (removing the need for a cron-job).
The cronscript has been running every minute for a few weeks now:
{{{ launchpad- generate- ppa-htaccess. lock launchpad- generate- ppa-htaccess. lock s.ini launchpad- generate- ppa-htaccess. lock launchpad- generate- ppa-htaccess. lock s.ini launchpad- generate- ppa-htaccess. lock launchpad- generate- ppa-htaccess. lock
2010-10-20 00:03:05 INFO Creating lockfile: /var/lock/
2010-10-20 00:03:15 INFO Starting the PPA .htaccess generation
2010-10-20 00:03:15 INFO Committing transaction...
2010-10-20 00:03:15 INFO Finished PPA .htaccess generation
2010-10-20 00:03:24 DEBUG Removing lock file: /var/lock/
2010-10-20 00:04:04 DEBUG Cronscript control file not found at file:cronscript
2010-10-20 00:04:04 INFO Creating lockfile: /var/lock/
2010-10-20 00:04:14 INFO Starting the PPA .htaccess generation
2010-10-20 00:04:14 INFO Committing transaction...
2010-10-20 00:04:14 INFO Finished PPA .htaccess generation
2010-10-20 00:04:23 DEBUG Removing lock file: /var/lock/
2010-10-20 00:05:04 DEBUG Cronscript control file not found at file:cronscript
2010-10-20 00:05:04 INFO Creating lockfile: /var/lock/
2010-10-20 00:05:14 INFO Starting the PPA .htaccess generation
2010-10-20 00:05:15 INFO Committing transaction...
2010-10-20 00:05:15 INFO Finished PPA .htaccess generation
2010-10-20 00:05:24 DEBUG Removing lock file: /var/lock/
}}}
So I assume this bug is fix released (as in users should no-longer see a 401 when the repository is accessed after a successful purchase). Soyuz would still like to work on a better long-term fix (removing the need for a cron-job).