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

webernet’s picture

Status: Active » Fixed

Yes - If a release or module exists, but is unpublished, it is flagged as revoked.

dww’s picture

Title: Module has been revoked? » Ignore new release nodes that are unpublished
Project: Drupal core » CVS deploy
Version: 6.0-rc2 » 6.x-1.x-dev
Component: update.module » Code
Category: support » feature
Priority: Normal » Minor
Status: Fixed » Active

The 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.

nancydru’s picture

Okay, 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.

dww’s picture

Status: Active » Closed (won't fix)

Great. So be it. ;)

nancydru’s picture

Yes, the message went away when the new release rolled.