In my Hierarchical Select module, some submodules have not yet been ported to Drupal 7. Hence, I've explicitly disabled them, by stating that in hierarchical_select/modules/hs_menu.info (as well as in another submodule).

In git, HS 7.x-3.x:

name = Hierarchical Select Menu
description = Use Hierarchical Select for menu parent selection.
dependencies[] = hierarchical_select
dependencies[] = menu
package = Form Elements
core = 6.x

In the tarball:

name = Hierarchical Select Menu
description = Use Hierarchical Select for menu parent selection.
dependencies[] = hierarchical_select
dependencies[] = menu
package = Form Elements
core = 6.x

; Information added by drupal.org packaging script on 2011-07-11
version = "7.x-3.0-alpha2"
core = "7.x"
project = "hierarchical_select"
datestamp = "1310423216"

Hence, d.o's packaging scripts are to blame for the ability to enable the module.

The solution is simple: if a core = something line is detected in a .info file, don't override it.

Comments

Berdir’s picture

Subscribe, I have the same problem with http://drupal.org/project/userpoints_contrib

That project is a collection of separate but userpoints related modules, I haven't ported all of them yet, but I'm getting regular bug reports about them being broken.

Since the core = x.x is pretty much required, as you need it to be able to install the module from git, it would really make sense if this is supported.

marcingy’s picture

Another issue related to util module was raised against core #1730866: D7.14 allowed modules marked as "core = 6.x" to be enabled

lizzjoy’s picture

Project:Drupal.org webmasters» Drupal.org infrastructure
Component:Project problem» Packaging
Issue summary:View changes
drumm’s picture

Project:Drupal.org infrastructure» Drupal.org customizations
Version:» 7.x-3.x-dev
Component:Packaging» Code

drupalorg_project/plugins/release_packager/DrupalorgProjectPackageRelease.class.php has the code which makes this addition.