Bug #12589
Modules have checksum for empty metadata file
| Status: | Closed | Start date: | 02/12/2012 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Kelsey Hightower | % Done: | 0% | |
| Category: | - | Spent time: | - | |
| Target version: | - | |||
| Keywords: | Affected URL: | |||
| Branch: | ||||
Description
From Kelsey:
I have chased down a wired bug that prevented the uninstall command from uninstalling modules. It was always reporting local changes no matter what. This is now fixed by not generating a metadata.json file during the module bootstrapping process. Not sure how far this issue goes back, but most of the modules I have tested on the forge see to have this issue. We need to ensure we call this out in the docs. For now users can get around the issue by using the —force flag during uninstalls.
There’s a patch in for the builder tool, but the modules in the database have this problem still. We need to open up the metadata files and remove checksum entries for the metadata file itself.
History
#1
Updated by Matt Robinson about 1 year ago
- Assignee set to Matt Robinson
This should already be taken care of since the moduletool will ignore the metadata.json file when checksumming. I will verify and close if that’s the case.
#2
Updated by Matt Robinson about 1 year ago
Verified that this is the case. Uninstall ignores the metadata.json entry when checksumming.
#3
Updated by Matt Robinson about 1 year ago
- Status changed from Accepted to Merged - Pending Release
#4
Updated by Daniel Pittman about 1 year ago
- Assignee changed from Matt Robinson to Kelsey Hightower
#5
Updated by Ken Barber 7 months ago
- Status changed from Merged - Pending Release to Closed