Closed (won't fix)
Project:
CVS deploy
Version:
6.x-1.x-dev
Component:
Code
Priority:
Minor
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
25 Jan 2008 at 19:07 UTC
Updated:
26 Jan 2008 at 03:21 UTC
I just submitted a D6 version of the Faq_Ask module so it has, obviously, not rolled a tarball from HEAD yet. But Update is telling me that the module has been revoked. Is this just because it hasn't rolled yet?
Comments
Comment #1
webernet commentedYes - If a release or module exists, but is unpublished, it is flagged as revoked.
Comment #2
dwwThe release is unpublished. update_status has no way to know if it's unpublished because it was just created, or unpublished because it was revoked. This is why the 'revoked' stuff is sort of a hack, and we should just be marking projects as 'insecure' instead of unpublishing them.
I *suppose* we could put in some special case hackery that if the release is unpublished but there's no file information in the XML file, we assume it's a release that was just created, not unpublished later. However, this seems like a hack and extra bloat/complication for a pretty unimportant edge case. Not many people are going to be deploying from CVS before release nodes exist for something. We could solve this in cvs_deploy, in fact, using hook_update_status_alter(), if we really cared.
Anyway, yes, it'll all be happy once the packaging scripts run again and publish your release.
Comment #3
nancydruOkay, that's pretty much what I thought. I don't see any reason why you need to worry about coding for this. I'd be happy marking this "by design" and let it go.
Comment #4
dwwGreat. So be it. ;)
Comment #5
nancydruYes, the message went away when the new release rolled.