Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 UTC on 18 March 2024, to get $100 off your ticket.
There were several issues with the project release packaging that have been reported in various queues, please check the list below before opening new issues.
- Problems with supported/recommended/snapshot -dev releases not showing up on project pages should be resolved. If the release exists and is published, but still isn't showing up on your project page, you need to regenerate Downloads table. To do so try disabling and re-enabling a supported release or recommended version (saving in between the disable/enable, of course)
- The problem with beta releases being shown in the Downloads table along with the final releases should be resolved. If you still see a beta release in the table, try re-save it (simply edit and save).
- If 'Add new release' page shows 'no valid branches/tags', even though the tags exist within the repository browser:
- click "View all releases" link at the bottom of your project page. You might find that releases for all valid branches/tags exist, just unpublished. Try edit and save the release node to get the release packaged and published.
- If there are no unpublished releases, delete and re-create tag or branch you have troubles with.
e.g.:git tag -d 7.x-1.3 git push --delete origin 7.x-1.3 git tag 7.x-1.3 git push origin 7.x-1.3
Related issue #2132327: Can't create release: git repository tag appears in repo browser, but not vcs tables
- If you previously edited a release and it isn't showing up in the Downloads table since then, edit it one more time and save.
Current known problems
- Can't create release: "Version already exists for [modulename].
Issue #2132351: Project_release node validation shouldn't fire when selecting git tag/branch - Distribution releases which include insecure modules aren't being shown in the Downloads table on the project page.
So far this is by design, discussion is here: #2137095: Should supported releases be shown on downloads table even if it contains insecure modules? If so, how?.
Comment | File | Size | Author |
---|
Comments
Comment #1
kreynen CreditAttribution: kreynen commentedComment #2
jthorson CreditAttribution: jthorson commentedThere are currently 371 "full" projects in the database which do not have releases enabled (while all full projects should have releases enabled by default).
I think the first step will be to expose the releases checkbox for certain admin roles, so that we can manually correct these as they appear.
Comment #3
hass CreditAttribution: hass commentedIs there an issue somewhere about DEV versions that are not updated? Last update was before the upgrade :-(
See D8 core: https://drupal.org/node/572834
Comment #4
kreynen CreditAttribution: kreynen commented@hass The code dev snapshots are being packaged. The dates are not updating
See #2125973: Repackaging dev release should update field_release_file's timestamp
Comment #5
kscheirerUpdated #2132003: Unable to enable releases for Full Projects with 'project_has_releases' = FALSE, this seems to be affecting old sandboxes that were promoted after the D7 upgrade.
Comment #6
eliza411 CreditAttribution: eliza411 commentedComment #7
dsnopekAdded issue which covers prod_check and comment_alter.
Comment #8
pixelwhip CreditAttribution: pixelwhip commentedComment #9
jthorson CreditAttribution: jthorson commentedComment #10
jthorson CreditAttribution: jthorson commentedComment #11
jthorson CreditAttribution: jthorson commentedComment #12
jthorson CreditAttribution: jthorson commentedComment #13
jthorson CreditAttribution: jthorson commentedComment #14
jthorson CreditAttribution: jthorson commentedComment #15
jthorson CreditAttribution: jthorson commentedComment #16
jthorson CreditAttribution: jthorson commentedComment #17
gisleComment #18
smoothify CreditAttribution: smoothify commentedI had an issue about creating a release closed as duplicate for panels_bootstrap_styles.
#2126953: Unable to create release for panels_bootstrap_styles
One thing missing from that last comment, is what i can/should I do about it. Do i need to wait for this all to be fixed, or can i request someone to publish that release (i get an error when i try to edit)?
Comment #19
kreynen CreditAttribution: kreynen commented@smoothify, if I'm reading that correctly your issue is now requires #2127315: Unable to see unpublished releases to be resolved.
Comment #20
rfayThe project_release_nodes table was dumped in the D7 model. This affects quite a lot of existing code. Seems like the postcard about this got lost in the mail.
The table was obsoleted in http://drupalcode.org/project/project.git/blob/HEAD:/release/project_rel...
Comment #21
kreynen CreditAttribution: kreynen commentedadded links to various queues users continue to post issues about their specific projects and issues @jthorson added to https://drupal.org/project/drupalorg to help track progress
Comment #22
jthorson CreditAttribution: jthorson commentedComment #23
jthorson CreditAttribution: jthorson commentedComment #24
kreynen CreditAttribution: kreynen commented@jthorson #8160969 still isn't a node. Is that a comment id?
Comment #25
jthorson CreditAttribution: jthorson commentedLol ... Yup!
Comment #26
kreynen CreditAttribution: kreynen commentedComment #27
kreynen CreditAttribution: kreynen commentedComment #28
kreynen CreditAttribution: kreynen commentedComment #29
kreynen CreditAttribution: kreynen commentedComment #30
kreynen CreditAttribution: kreynen commentedRemoved duplicates and issues are now sorted and added links to additional related issues from https://drupal.org/project/drupalorg
Would really like to see something done w/ #2134179: Remove message on project and release nodes about the current status of project packaging
Comment #31
drummComment #32
drummI fixed up a few issues today, so we should be getting closer to normal. Thanks for the issue summary updates!
Comment #33
kreynen CreditAttribution: kreynen commented@drumm thanks for all your effort on this, but what do maintainers need to do to get their projects "closer to normal"? It's still unclear what should be working and what isn't.
https://drupal.org/project/views_share the new, 1.0 tag isn't showing up on the project page.
https://drupal.org/project/performance still has both it's -2.0 and -2.0-beta1 releases.
https://drupal.org/project/civicrm_starterkit the latest tag of the supported branch (4.4-rc4) caused all supported downloads to be removed.
https://drupal.org/project/commerce_kickstart only show the supported 2.x branch
https://drupal.org/project/mollom has a release from Nov-10, but dev snapshot still shows date of Oct-30.
It looks like @tvn is going to do something about #2134179: Remove message on project and release nodes about the current status of project packaging
It would be great to get a handle on what should be working and the steps (if there are any) a maintainer who had release issues can take to resolve them.
Comment #34
tvn CreditAttribution: tvn commentedkreynen, I totally agree with you. We still need to do some more investigation to be able to determine that. So far problems seem to affect not all the projects but some of them, fairly randomly. I hope we'll be able to publish something of that sort soon enough.
Comment #35
tvn CreditAttribution: tvn commentedComment #36
tvn CreditAttribution: tvn commentedComment #37
tvn CreditAttribution: tvn commentedComment #38
tvn CreditAttribution: tvn commentedComment #39
jthorson CreditAttribution: jthorson commentedJust incase it went unnoticed, tvn has updated the issue summary with a list of what has and has not been fixed to date. ;)
Comment #40
behestee CreditAttribution: behestee commentedI have created a release for official release, but it doesn't show on project page. Though it is showing in view all releases page where no downloadable file are seen. If I try to edit this node then it shows an error message. Now, what can I do? Is there anyone who can publish my release node or take necessary action so that releases shows in my project page?
Here is my project: https://drupal.org/project/remember_me_in_ip_range
Comment #41
jthorson CreditAttribution: jthorson commentedLooks like https://drupal.org/comment/8174337#comment-8174337 will solve both outstanding issues listed in #1.
Comment #42
jthorson CreditAttribution: jthorson commentedComment #43
jthorson CreditAttribution: jthorson commented#40: The 'unable to edit unpublished releases' issue is at #2127373: EntityMetadataWrapperException when trying to edit an unpublished release node, and has a patch pending. Your node is not published due to some failure of the packaging script; and publishing it manually now will not help, as we need the packaging script to generate the tarballs. (Unfortunately, I'm a little green on the behind-the-scenes operation of the packaging script, so that's as much as I can tell you at the moment.)
Comment #44
gisleI do not believe the analysis is #43 is correct. All my releases has had its tarball generated in a timely manner. The problem is that these tarballs (or the dates they are generated in the case of dev-releases) are not listed on the project page where users usually look for them.
For instance take a look at this tagged release: Notify 7.x-1.0-alpha3. The tarball is there all right on the release page. However, there is no sign of it on the Notify project page (nor does it appear on the Administer releases page).
It is the same with dev-releases. Look at this dev-release: Flexi Access 7.x-1.x-dev. The tarball is there, generated by the packaging script yesterday (Nov 13). However, the date listed on the Flexi Access project page is stuck on Oct 01 2013.
Comment #45
jthorson CreditAttribution: jthorson commented#44: There are multiple issues at play here, and the analysis in #43 is not intended to explain all of them ... just the case in #40, which was backed up through direct analysis of the DB.
I was able to resolve the Flexi-Access example with the workaround posted at the top of this issue (i.e. Re-editing and saving a release triggers regeneration of the download table).
Comment #46
jthorson CreditAttribution: jthorson commentedAdditional fuel for the troubleshooting fire, from watchdog logs (appearing multiple times):
git binary was not found on the $PATH, try to manually set the absolute path to the git binary at configuration
Event with elid = 819781 from repository 1497344 (35852) reached the limit of retries. Please perform a full syncronization on it.
Invocation of 'mv '/var/git/repositories/project/utm_source.git' '/var/git/repositories/project/utm_source.git'' exited with return code 1, emitting stdout: and stderr: mv: cannot move `/var/git/repositories/project/utm_source.git' to a subdirectory of itself, `/var/git/repositories/project/utm_source.git/utm_source.git'
No makefile for devshop-6.x-1.x-dev profile, skipping extended packaging.
Comment #47
Elijah LynnI just pushed a new tag to https://drupal.org/project/sticky_edit_actions, 7.x-1.1 to be precise and when I go to add a new release I am cannot see it and get the "No valid branches or tags found." message. The new tag is in the repository viewer.
Comment #48
Elijah LynnComment #49
TR CreditAttribution: TR commentedI created a new -dev release on a new branch of one of my projects last night, but the release didn't show up so I followed the instructions in this issue summary that say to edit/save the release node.
But every time I try to edit the node, by visiting https://drupal.org/node/2135639/edit , I get a 500 server error "The website encountered an unexpected error. Please try again later.".
The release did show up immediately after I first visited that page, despite the error, but I still can't edit that release node.
Comment #50
jthorson CreditAttribution: jthorson commentedTR: The workaround should be good when you edit/save any release node (maybe only on the same major branch).
The error you're getting on edit is this: #2127373: EntityMetadataWrapperException when trying to edit an unpublished release node.
Comment #51
jyokum CreditAttribution: jyokum commentedRegarding Marketo MA (marketo_ma) project, I attempted to create a release for tag 7.x-1.2-beta3 and ran into the issue described "'Add new release' page shows 'no valid branches/tags', even though the tags exist". After a couple of times deleting and re-pushing the tag got frustrated and gave up.
Since my 1.2 release was nearly ready anyway, I finished the last change and pushed up a 7.x-1.2 tag. I was able to find this tag on the Add new release page and successfully create a release. The 7.x-1.2 release now shows up properly on my project page however an older release 7.x-1.2-beta2 is still there as well. I expected this older beta release to be removed when I pushed up the new release.
Comment #52
TravisCarden CreditAttribution: TravisCarden commentedI created a release for Checklist API (checklistapi 7.x-1.1). It was successfully published and packaged. It appears on the releases view, and
drush pm-releases
correctly identifies it as the current supported, recommended release... but it doesn't appear on the project page. The project page only shows the previous version, 7.x-1.0.Comment #53
tvn CreditAttribution: tvn commentedTravisCarden, can you try to edit and save the release node?
Comment #54
Anonymous (not verified) CreditAttribution: Anonymous commentedI spoke with @jthorson on IRC... also seen this bug in action on my first commit to commerce_migrate_ubercart module.
The first (ever - for this project) action I have taken was to create 7.x-2.x branch per the instructions and push that, then I attempted to make one commit. Commits show in the drupalcode site, and git clones are possible. No sign of 7.x-2.x with the project nodes, no commits in the log on drupal.org. No items in the releases pages. Hope this helps!
Comment #55
ajosephau CreditAttribution: ajosephau commentedI wanted to post up my experiences creating releases on my project Site Banner (https://drupal.org/project/site_banner): apologies in advance if I'm missing something - I got priviliges to promote sandbox projects to full projects a little while after this bug was filled.
I followed the instructions on creating a project release (https://drupal.org/node/1068944), creating an official release. I noticed an official build at https://drupal.org/node/2105389/release but no download link on the main project page. I created a development release too but now I have a "recommended download" on the main project page but no links to the builds.
A more concerning issue was that when I go to the "edit" link for the recommended release (https://drupal.org/node/2134787/edit?destination=node/add/project-releas...) I get a Drupal "The website encountered an unexpected error. Please try again later." error.
If I can provide any more information to help replicate this, please feel free to ask.
Comment #56
swim CreditAttribution: swim commentedI experienced a similar situation as #54 when creating the new project branch (7.x-1.x in my case). Commits were visible via drupalcode.org, including downloading the snapshot from the repository viewer but they did not become visually packaged on the project page.
Comment #57
sdboyer CreditAttribution: sdboyer commentedok so, yeah, we clearly have a major issue here. i'm going to be digging in properly this weekend. can't promise i'll be able to fix everything, but there are definitely some root issues down in the git code that need resolving.
Comment #58
tyler.frankenstein CreditAttribution: tyler.frankenstein commentedPossible related issue:
Comment #59
iamEAP CreditAttribution: iamEAP commentedCommenting about an issue I've had on https://drupal.org/project/project_src_github.
Trying to get it to run automated tests, but it won't rebuild its dependencies. Not only that, but it also seems to not be able to find the project / release itself.
See
Comment #60
DanChadwick CreditAttribution: DanChadwick commentedI'm the (new) co-maintainer for Views Crosstab. I have been having the problem that when I push a dev release with git, the project page was not updated even after 24 hours. This includes the list of commits, the committers, and the release packages, as well as the commits shown on my profile page. The project's repository viewer shows the commits.
I tried editing the release node for the 7.x-1.x branch, as well as editing the releases page. The updated date on the 7.x-1.x branch did update, but the package hasn't been rebuilt.
However now when I try to edit any of the three release nodes, I get a fatal error:
Fatal error: Call to undefined method EntityStructureWrapper::count() in /var/www/drupal.org/htdocs/sites/all/modules/versioncontrol_project/versioncontrol_release/versioncontrol_release.module on line 998
This seems to be a different (but perhaps related) issue from #2127373: EntityMetadataWrapperException when trying to edit an unpublished release node, the fix for which has been deployed and I'm still getting the error.
Any help or advise is welcome. I have a security-related commit that I'm anxious to get published.
Comment #61
jthorson CreditAttribution: jthorson commentedDanChadwick: Thanks for the report ... that looks like a new bug introduced by the fix you referenced.
Comment #62
DanChadwick CreditAttribution: DanChadwick commentedjthorson: Thx. I reopened #2127373: EntityMetadataWrapperException when trying to edit an unpublished release node for regression with the same bug-reproduction info.
Relative to the current issue, my project (views_crosstab) is still not updating despite a release node edit/save. Maybe it will provide some clues to the git / packaging problem.
Comment #63
TravisCarden CreditAttribution: TravisCarden commented@tvn, re #53: Yikes! When I go to the edit URL for the release node, I get this beauty:
Fatal error: Call to undefined method EntityStructureWrapper::count() in /var/www/drupal.org/htdocs/sites/all/modules/versioncontrol_project/versioncontrol_release/versioncontrol_release.module on line 998
Comment #64
gcassie CreditAttribution: gcassie commentedHere's my experience - hopefully it aids in debugging.
I created the first two release tags for https://drupal.org/project/acquia_cloud_sticky_sessions today around 12:30 PM Eastern. When I visit https://drupal.org/node/add/project-release/1698144 I can see only the branches which have existed for several months, not the new tags. Both tags show up in http://drupalcode.org/project/acquia_cloud_sticky_sessions.git however.
Comment #65
jthorson CreditAttribution: jthorson commented#53 ... that's been resolved, but the fix for the edit->releases table has also been deployed.
The caveat on the second fix is that something needs to change on that table to trigger the rebuild ... so I removed the supported release and then re-added it, and your download table now looks correct.
Comment #66
jthorson CreditAttribution: jthorson commentedNOTE: Issues related to the 'edit->releases' table on a project (and related issues about supported/recommended/snapshot releases not showing up on your project page) should now be resolved. The new download table will only be regenerated if something changes on that table, so try disabling and re-enabling a supported release or recommended version (saving inbetween the disable/enable, of course).
Comment #67
jthorson CreditAttribution: jthorson commentedComment #68
jthorson CreditAttribution: jthorson commentedComment #69
jthorson CreditAttribution: jthorson commentedComment #70
jthorson CreditAttribution: jthorson commentedComment #71
DanChadwick CreditAttribution: DanChadwick commented#62 is resolved for views_crosstab.
Disabling and re-enabling a release caused the -dev releases to be redisplayed on the project page.
However, I tagged the 6.x-1.x branch with 6.x-1.0-alpha2 and pushed the tag, which I see in the repro browser. However, I cannot add this release, nor do I see any of the commits in the View Commits list, nor do I see me in the View All Commiters list, nor do I see them in my profile.
Comment #72
tvn CreditAttribution: tvn commentedupdating current problems and notes
Comment #73
tvn CreditAttribution: tvn commentedComment #74
pounardOn the Redis project https://drupal.org/project/redis I have the following bugs:
Comment #75
tvn CreditAttribution: tvn commentedComment #76
tvn CreditAttribution: tvn commentedComment #77
tvn CreditAttribution: tvn commentedComment #78
tvn CreditAttribution: tvn commentedComment #79
maximpodorov CreditAttribution: maximpodorov commentedhttps://drupal.org/project/ctools_entity_exists doesn't show files to download (but shows the release itself in the table).
Comment #80
Anonymous (not verified) CreditAttribution: Anonymous commentedI posted earlier in #54 and applied the recommended changes in #66. The action did not work at first and I was not able to find my 7.x-2.x dev branch, "No valid branches or tags found."
I added a tag to my repo and pushed that. Now I am able to get to the "create release" page. I put in the info, hit submit, and it waited a long time. Eventually the page showed an error (sorry I did not copy it, long enough that safe to assume it was a timeout). I reloaded the page to resubmit the form and it said the release already exits.
I went back to the "create release" page... once again "No valid branches or tags found."
HOWEVER, the release was created and shows on the "view all releases" and "administer releases" pages.
...so it is "working" but I still cannot create a dev branch and my 7.x-2.x branch is "invisible".
Comment #81
Anonymous (not verified) CreditAttribution: Anonymous commentedFurther to #80, I made the mistake of checking of "snapshot release" when trying to set the default and now the downloads have disappeared. I set it back to unchecked, but the downloads are no longer there.
Comment #82
hatuhay CreditAttribution: hatuhay commentedhttps://drupal.org/project/bootstrap_barrio
When first created dev release, drupal.org crashed, no dev version shown, after disabling and enabling show release but do not show files to download.
Comment #83
rfayAlso, the unfollow on issues is broken :-) Since I unfollowed this one and still get all notifications. I searched and didn't find a related issue. If somebody can mention where I should post about unfollow being broken I will.
Comment #84
kreynen CreditAttribution: kreynen commented@rfay #2135397: Unable to unfollow issues after Drupal.org D7 upgrade exists, but should get a better title and more detail. In addition to not being able to unfollow issues, I don't get email updates to the issues I create.
Comment #85
jkuma CreditAttribution: jkuma commentedI've got an issue on one of my project: https://drupal.org/project/commerce_futurepay
The commit page doesn't list the correct amount of commits https://drupal.org/node/2110073/commits
Indeed, If you go on that page http://drupalcode.org/project/commerce_futurepay.git, you'll notice that the commit "Add support of customer registration." is not listed on the module commit page.
This happens to me when Drupal.org website has been updated.
Comment #86
sdboyer CreditAttribution: sdboyer commentedso we figured out one major issue that accounts for a lot of the intermittent "branches/tags/commits aren't showing up". we'll be able to put up a fix for it presently, but that will only resolve things going forward; it won't fix existing issues.
to fix the existing issues, the easiest thing SHOULD be for people to just re-push another commit, and the syncer will bring things up to date. (if you try that and it doesn't work, give it until Sunday or so, and try again, please). i'd love to be able to just do that for everyone who's having an issue here, but the command i've historically used to magically heal these problems was broken in the d7 upgrade. we're working on fixing that, too.
more updates as things progress.
Comment #87
tvn CreditAttribution: tvn commentedpounard, re #74, I see now 7.x-2.5 on the project page and it has files.
Comment #88
pounard@tvn nice, is that a bugfix or just a very long delay?
Comment #89
tvn CreditAttribution: tvn commentedAdded a list of projects with releases without files.
Comment #90
tvn CreditAttribution: tvn commentedpounard, jthorson fixed your release but forgot to comment.
Comment #91
mkalkbrennerhttps://drupal.org/project/themekey
Release of ThemeKey 7.x-3.0-rc1 is still unpublished:
https://drupal.org/node/2136813
Comment #92
jthorson CreditAttribution: jthorson commentedThemeKey is in the list of unpublished release nodes ... which I don't believe has yet been resolved. (For -dev releases, it can be resolved with a new commit ... but obviously this isn't a solution for static releases. I do believe, however, that pushing another tag and creating an -rc2 would now work.)
Comment #93
jyokum CreditAttribution: jyokum commentedMarketo MA https://drupal.org/project/marketo_ma
Release 7.x-1.2 is published but has no files for download
Additionally, 7.x-1.2-beta2 is still shown in the releases table and should have been removed when 7.x-1.2 was published.
Comment #94
smoothify CreditAttribution: smoothify commentedComment #95
jyokum CreditAttribution: jyokum commentedComment #96
iamEAP CreditAttribution: iamEAP commentedAdding a note regarding my experience in #59: I can't manually trigger a branch test because it doesn't appear under the "automated testing" tab.
Image here: http://www.privatepaste.com/download/2696163499
Comment #97
pounard@tvn #8 for the record, this release was created after the migration.
Comment #98
infojunkie CreditAttribution: infojunkie commentedThis release I made ~40 mins ago has no files. Not sure if I have to wait longer for them to appear or the bug applies here as well.
Comment #99
mkalkbrennerThe release from #91 is now published. It took a long time and I edited and saved the node multiple times as described at #2134505: Release not being published.
And I had to "administer releases" to get the download files table up-to-date.
Comment #100
abhishek.kumar CreditAttribution: abhishek.kumar commentedProject statistics not updated on project page.
Comment #101
moshe weitzman CreditAttribution: moshe weitzman commentedUpdate on 11/16 : 8.x is now valid but 7.x still failing.
For Drupal core, the Update XML has proper dates now, but I am still seeing an MD5 mismatch between the tarball and the Update XML. To see this, you can do
drush dl drupal-8.x --no-cache -v
ordrush dl drupal-7.x --no-cache -v
.I tried some workarounds to isolate the problem like adding a random querystring for the update XML and fetching the tarball from drupal.org instead of ftp.drupal.org. Neither made a difference.
Comment #102
drummI un-stuck the packager and updated the download table views to close out #2127355: Supported release not showing on project page for distributions, #2132353: Beta releases being shown in Downloads table along with final releases, and #2134505: Release not being published.
Comment #103
japerryAdding discussion of #2137095: Should supported releases be shown on downloads table even if it contains insecure modules? If so, how? since its relevant to distribution maintainers.
Comment #104
tvn CreditAttribution: tvn commentedUpdating to reflect current status.
Comment #105
Danny EnglanderI'm not sure if I should be reporting "me too" here but I made a new release for my project, Gratis, about 12 hours ago and it still has no files and is therefore unpublished. The odd part is that I made a release a few days ago and that one published right away and that was post D7 upgrade. In addition, the dev release on my project page seems stuck at October 31st. The other factor is that some aspects of the UI / UX seems confusing with the D7 upgrade so perhaps I am not making a release in the proper manner?
Comment #106
mikeytown2 CreditAttribution: mikeytown2 commentedThings are really broken
#2137285: Different code branches being packaged up in a release.
Comment #107
drumm#2137285: Different code branches being packaged up in a release. was a simple typo while tagging.
Comment #108
tvn CreditAttribution: tvn commentedComment #109
drummEverything from #2 in the issue summary at this time is resolved.
Comment #110
mikeytown2 CreditAttribution: mikeytown2 commentedThanks for pointing out the typo. Anyway we could prevent creating a release if the tag doesn't match the branch, or at least warn?
Got a minor one.. pushed out advagg-7.x-2.3 and the download links aren't there. So I just hit #2. Files do exist though so I linked to them in the release notes. Feel free to remove the links in the notes once that node is fixed.
https://drupal.org/node/2137351
Comment #111
mikeytown2 CreditAttribution: mikeytown2 commentedComment #112
DanChadwick CreditAttribution: DanChadwick commentedComment #113
jthorson CreditAttribution: jthorson commentedCurrently, package_release-run-queue is choking while trying to package advagg ... there appears to be some issue with the field_release_files field on one of the releases.
However, I wasn't able to reproduce the error when executing the same code in a standalone script file, so I'm at a bit of a loss as to what's happening.
Comment #114
drummThe field cache inconsistency from #2125703: Issue list not up-to-date struck again because I didn't make the bin changes on util. I made those and it went right through. That should fix all sorts of occasional random problems.
And I think I fixed #101 with http://drupalcode.org/project/project.git/commit/160883a
Comment #115
cheatlex CreditAttribution: cheatlex commentedI'm trying to create the first release on my project and still get no files ?
https://drupal.org/project/economic
Have saved and enabled the release form a bunch of times now - nothing changes when added the "Show snapshot release" the download links is still not there.
Comment #116
Perignon CreditAttribution: Perignon commented#115 @cheatlex I am in the same boat. The release finally published but it was several hours for me.
Comment #117
jyokum CreditAttribution: jyokum commentedComment #118
smoothify CreditAttribution: smoothify commentedComment #119
jthorson CreditAttribution: jthorson commented#115 (chetlex):
For the -dev release to appear in the download table, you'll need to check the 'Show snapshot release' checkbox.Also, I believe that -dev release snapshots can take up to 12 hours (at least, prior to the upgrade, they were processed at 12:00 and 24:00), so if you make any new commits, it may correct itself on the next build.Edit: Sorry, misunderstood the comment.
Comment #120
jthorson CreditAttribution: jthorson commentedComment #121
muneeba CreditAttribution: muneeba commentedI am having trouble with devel themer as I installed it in module it says simplehtmldom (missing) due to this issue it is disabled and not working
Comment #122
jthorson CreditAttribution: jthorson commented#121 If you are having troubles with a specific module, please open a ticket in the queue for that project.
Comment #123
mr.york CreditAttribution: mr.york commentedI'm trying to create the first releases on my project.
https://drupal.org/project/views_calc_filter
The releases is unpublished:
https://drupal.org/node/2135679/release
Comment #124
fgiasson CreditAttribution: fgiasson commentedHi,
I created a new project called OSF a few weeks ago. Last Friday, I created the first DEV release. However, it is not yet visible as a downloadable package here (after 3 days):
And here is the release:
Thanks,
Fred
Comment #125
tvn CreditAttribution: tvn commented#123 fixed by re-saving release nodes.
Comment #126
tvn CreditAttribution: tvn commented#124 fixed as well.
Comment #127
gcassie CreditAttribution: gcassie commentedAs a follow-up to #64, I deleted and re-created the 6.x-1.0 release tag today. Doing so caused both tags to show up in the select box on https://drupal.org/node/add/project-release/1698144 . Picked 6.x-1.0, entered an initial release message, and submitted. Form hung for a while then returned:
"Error
The website encountered an unexpected error. Please try again later."
It looks like the release was created but when I try to download the archives I get a "File not found" error - https://drupal.org/node/2138309 . I waited 15 minutes after creating the release and still getting "file not found".
Haven't tried the 7.x-1.0 release yet.
Comment #128
mr.york CreditAttribution: mr.york commentedThank you tvn.
Comment #129
ttwhyz CreditAttribution: ttwhyz commentedAfter upgrading drupal I also get an error with ubercart 7x.3.4
this is the error.
Fatal error: Cannot redeclare class UcOrderController in /home/myserver/public_html/sites/all/modules/ubercart/uc_order/uc_order.controller.inc on line 60.
Comment #130
pounard#129 post your issue on the ubercart issue queue please.
Comment #131
drummI'm still seeing orphaned file and field collection entities, which are the cause of all the packaging problems I've seen since #114. I can query to find all of these after #2136119: Text search on issue queues is slow and sometimes WSODs is addressed. In the meantime, I can fix individual releases as I see them.
This was the problem for https://drupal.org/project/economic, and is now fixed. All the others since #115 look okay now.
On scheduling - normally, all releases should be packaged within 10 minutes, now including dev. (Once packaged, it does take up to 30 minutes for file to sync out to ftp.drupal.org, that's not a new thing, #106399: Release link present, file not found.)
However, drush make for distributions tends to hang on git clone sometimes. This is killed after 30 minutes and releases continue to be packaged. And what happened over the weekend is that the queue got stuck on a couple releases, preventing processing of anything in the queue.
Comment #132
drummWhat I'm doing to fix orphaned entities is running:
sudo -u bender -i drush -v -r /var/www/drupal.org/htdocs php-script ~drumm/fix-release.php {project_short_name}
And
fix-release.php
is currently:I expect this won't be needed for anything created after #114.
Comment #133
fgiasson CreditAttribution: fgiasson commented@tvn: thanks for fixing #124!
Comment #134
mradcliffeI am also experience trouble getting Automated Tests available for my module regarding Comment #96. It says use the "Test Additional Branches" form, but that form is not displayed at all.
I don't see any follow-up from comment #96 so I guess a new issue should be created.
Edit: for grammar
Edit 2: Issue posted #2139251: "Test Additional Branches" form is missing on Automated Testing page.
Comment #135
Miszel CreditAttribution: Miszel commentedI am not able to make a release for my module
- release tag is not available in the dropdown on the Create Release page.
- new commits do not show up on the commits page
[edit] It started working after I did this: https://drupal.org/comment/8187901#comment-8187901
Comment #136
SteveMushynsky CreditAttribution: SteveMushynsky commentedProject page at https://drupal.org/project/SideShare shows no downloadable files
Comment #137
jthorson CreditAttribution: jthorson commented#136: That's because there are no supported/snapshot releases selected on the administer releases page, at https://drupal.org/node/2111905/edit/release.
Comment #138
theohawse CreditAttribution: theohawse commentedPlease close these issues for me when this is all resolved.. Haven't been able to build a new drupal 7 platform for 2 weeks now...
Superfish Wrong md5 checksum
Navbar Wrong md5 checksum
Comment #139
tvn CreditAttribution: tvn commentedAdded instructions for missing tags/branches from #2132327: Can't create release: git repository tag appears in repo browser, but not vcs tables.
Comment #140
btopro CreditAttribution: btopro commentedBuilt https://drupal.org/node/2139689 last night as a 7.x-4.0 release. Project page still says 7.x-4.0-beta1 is the prefered version. Beta seems to have priority over the 7.x-4.0-rc1 and 2 that I had in there as well as the full 4.0 release node. drush dl textbook also fetches 7.x-4.0-beta1. Don't know if this is related to packaging but figured I'd mention it.
Comment #141
znerol CreditAttribution: znerol commented@btopro: see #2137201: [META] Regressions in project_release handling of version element fields and release-history XML
Comment #142
jthorson CreditAttribution: jthorson commentedFixed #140 by disabling/re-enabling support for the 4.x branch, using the administer releases form.
Comment #143
xiukun.zhou CreditAttribution: xiukun.zhou commentedHi guys,
I'm not entirely sure if this issue could be related with the latest upgrade of DO to Drupal 7, but I would like to report an issue I encountered while creating a new release for a project I currently help maintaining:
Project: Views Slideshow
New Release: views_slideshow 7.x-3.1 (currently unpublished)
GIT Tag: 7.x-3.1: http://drupalcode.org/project/views_slideshow.git/commit/d1d7371
The release creation process went just fine and I can correctly see the new release as well as code packages.
However, it has been unpublished for already a month and nothing seems to have changed, when there seems to be an increasing demand for a new release at #1677426: Roll 7.x-3.1 release of Views Slideshow.
Previously, I recall creating new releases for other projects and they would be automatically published, in general, within 48 hours....
I would greatly appreciate if a site admin could potentially help me take a closer look at this release and potentially help me publishing it.
Feel free to let me know if you would have any questions or would need any additional information on this particular project and release package, I would surely be glad to explain in more details.
Thanks in advance for your feedback, comments and replies.
Comment #144
dww@xiukun.zhou re #143: That's because you tagged it as a "Security update" release. In that case, the release isn't published until a member of the security team manually intervenes and publishes the release (at the same time as publishing a security announcement about it). There used to be a warning to this effect whenever you tried to create a release with this tag, not sure if that code got lost during the D7 port of d.o. Anyway, if you tagged it a security release, you were supposed to be in touch with the security team about it.
Cheers,
-Derek
Comment #145
xiukun.zhou CreditAttribution: xiukun.zhou commentedHi Derek,
Thank you very much for your kind and clear reply.
Since my problem doesn't seem to be directly related with this issue, I'll try to stay brief:
For some reason, I still can't see or have access to the field Release Type on the Edit page of the release views_slideshow 7.x-3.1 (neither can I see the link
What is a release type?): Screenshot of what I can see.
Now, that's perhaps due to limited maintainer's permissions for the Views Slideshow module or because I'm still not a fully vetted GIT user (application in process at #2128839: [D7] Baidu Map) or maybe because there would be some specific handling for releases tagged Security.... I'm not sure at all...
In any case, I'm finding myself stuck in a situation where I was able to create a new release, mistakenly selected Security for the Release type, when this should actually be Bug fixes and now, I'm unable to edit and change this value.
I'm not sure exactly how this issue could be assessed in order to avoid such a situation in the future, but for the time being, I would greatly appreciate if somebody (with sufficient permissions) could help me to edit this release page and change the Release type to Bug fixes, which would allow "unlocking" the release to be published and accessible to all users without any potentially required approval.
Feel free to let me know if you would have any questions or would need any additional information on this rather "awkward" situation, I would surely be glad to explain in more details.
Thanks in advance for your feedback, comments and replies.
Comment #146
dww#145 is now fixed. I removed the Security update term, published the release, and rebuilt the XML release history feed: http://updates.drupal.org/release-history/views_slideshow/7.x
Comment #147
xiukun.zhou CreditAttribution: xiukun.zhou commentedThank you so much Derek for your understanding and really prompt reply.
It looks all good now!! On my way to mark #1677426: Roll 7.x-3.1 release of Views Slideshow as fixed!
I'll certainly pay more attention to the Release type in the future to try to avoid ending up stuck again....
Thanks a lot for the great support and feedback.
Cheers!
Comment #148
kreynen CreditAttribution: kreynen commentedThings are looking much better, but there are still issues.
I got the Website had Unexpected Error when creating the 1.0-beta1 release of https://drupal.org/project/profile_status_check this morning, but the release node was still created and showed up on the project page. Not sure if it matters, but that was the first supported release.
I was able to successfully update the https://drupal.org/project/civicrm_starterkit distribution on Drupal.org with the security updates released yesterday despite getting errors about the supported versions and md5 hash when I tried to test the drush make locally.
Finally, the issue related to 0 usage is back this week.
#2128619: Project usage/download/install statistics not being generated in a timely manner
And the usage on the project pages is still using the number from mid October.
#2129811: Reported install usage statistics count on the project page is not being updated
It looks like the usage issues will persist until #2133385: project_generate_download() query needs porting to D7 structure is resolved.
Comment #149
japerryUpdated to add the packaging errors that multiple distributions are having trying to package today. It seems the packager runs out of memory after 8mb?
Comment #150
japerryComment #151
jthorson CreditAttribution: jthorson commentedBased on what I'm being told regarding testbot behaviour the last day or so, there's some bug inside D8 core which is causing memory issues.
Comment #152
Elijah LynnThere is a problem with *.info files in the latest 7.24 release. I am not sure it is related or not but I think it is.
#2141481: All *.info files - Message 'Information added by packaging script on 2013-11-20' is missing 'Drupal.org'
Comment #153
Yasmina7575 CreditAttribution: Yasmina7575 commentedSince I have upgraded Drupal to 7.24 yesterday it asks me to update Entity Reference which I did twice already. What is the pb here ?
Comment #154
kreynen CreditAttribution: kreynen commented@Yasmina7575 trying to figure out if your issue is related to packaging, Entity Reference, or is site specific. Are you saying that you are now running Entity Reference 1.1, but it is still showing up on admin/modules/update as requiring a security update?
Comment #155
Yasmina7575 CreditAttribution: Yasmina7575 commentedIt asks me three times today. Every time I updated it and i did the update.php and it is ok for a few hours and then it ask me again ! And yes it is the 1.1 version
Comment #156
jthorson CreditAttribution: jthorson commentedYasmina7575: Can you open a new issue for that specific problem?
Comment #157
Owen Barton CreditAttribution: Owen Barton commentedLooks like https://drupal.org/project/spark (not my project) has missing 7.x release packages
Comment #158
webchickHm. Weird. We haven't committed to that, nor created any releases, since before the d.o D7 upgrade.
Comment #159
manuelBS CreditAttribution: manuelBS commentedJust to leave a note: At ERPAL we had our new Alpha6 version the last 5 days but from yesterday it disappearded again.
Comment #160
hass CreditAttribution: hass commenteddrush up
still says Core 7.23 is latest. What's wrong here? I cleared all caches several times.Comment #161
jthorson CreditAttribution: jthorson commented#159: You'll need to update your project so that it depends on the latest release of core, after Wednesday's security updates.
Comment #162
jstollerI just had
drush up
fail with the error:File addressfield-7.x-1.x-dev.tar.gz_date=1384470205 is corrupt (wrong md5 checksum).
A couple days ago the same thing happened when using Drush to update Drupal core to 7.24. That was a different site, on a different computer.
Comment #163
rumenyordanov CreditAttribution: rumenyordanov commentedThere are currently problems with all Aegir 1.x. installation as for some of the modules the key for release history is wrong i.e. https://drupal.org/project/multiform, the key for release history is 1.x. and not 1.0. There is an issue posted here:
https://drupal.org/node/2141641
Comment #166
japerryComment #167
jstollerIs the checksum error I described in #162 actually part of this issue? I was referred here, but it isn't mentioned in the issue summary and I'm a little unclear. If so, then what is actually causing this error and is there another sub-issue I should be following?
Comment #168
jsacksick CreditAttribution: jsacksick commentedHi, I just tried to create a new release of Commerce Kickstart and it didn't work, I got a big error message, See http://cl.ly/image/1g2C2u2n0v2o, I have no idea what's wrong and what to do about it.
Comment #169
kreynen CreditAttribution: kreynen commented@jsacksick do you have the full error? It's really the end of the error that contains the good|bad stuff. There are still reports of MD5 issues when using drush make locally, but in #166 @japerry removed the links to #2141559: Better Error Reporting when packager fails from the issue summary...
My guess is another patching race condition, but that's just a guess.
Comment #170
jsacksick CreditAttribution: jsacksick commentedThe error doesn't say anything, I tried to scroll down to the end of the message, there's nothing special in it.
Comment #171
jsacksick CreditAttribution: jsacksick commentedHere is a link to the full error message : http://pastebin.com/80EzuM0j
Comment #172
jonathan1055 CreditAttribution: jonathan1055 commentedDoes anyone mind if we get the comment #171 deleted? It's ridiculously long and just makes the thread hard to use. Write to https://drupal.org/node/2144827 if there is something useful in #171 otherwise lets get it removed.@jsacksick Thanks!
Comment #173
kreynen CreditAttribution: kreynen commentedSorry if I contributed to that by not being specific about how to share the full error, but the error is hardly spam. A much more constructive way to fix that would be to ask @jsacksick if he could edit his own comment and replace the full error w/ a link to http://pastebin.com/ or http://dropbucket.org/
All we really needed was the...
It's sad that the issue this is related to is about the fact that drush is throwing these ridiculously long errors when failing to package distributions #2141559: Better Error Reporting when packager fails.
Comment #174
generalconsensus CreditAttribution: generalconsensus commentedSorry Jon, I agree.
vote_up(Delete #171)++
Comment #175
kreynen CreditAttribution: kreynen commentedEnough about #171 already. Commerce Kickstart is the most popular Drupal distribution after core. The data about an issue that prevents security updates from being packaged into a distribution used by almost 9,000 sites is FAR more important than how this issue displays.
Anyone really this upset about the way this makes the thread display should put some effort into a patch that would proactively prevent extremely long comments like that from ever being posted. It should be a pretty simple validation to check the length of the post and encourage the user to post a link to a paste bin.
Otherwise just wait for @jsacksick to correct his mistake.
Comment #184
Anonymous (not verified) CreditAttribution: Anonymous commentedComment #185
Anonymous (not verified) CreditAttribution: Anonymous commented@gisle (re #180)... I agree. It is not ideal having people come here with unrelated support issues. I added a warning in the issue description to help people identify if they are part of the target audience for this thread. I think the issue is that we're interrupting workflow with a big notice on every page and people are just tempted to use it... probably thinking the infrastructure issues are way bigger than they actually are.
Comment #186
jonathan1055 CreditAttribution: jonathan1055 commentedYes, it is because there is a link at the top of each project page, directly to this issue. I know why that was put there, but it is making things worse, so really it might be better to remove it. Otherwise we will continue to get unrelated problems posted here.
Comment #187
webchickEither that or maybe limit the message visibility only to those with Git permissions, since they are the only people this realistically affects, and are also a lot less likely to post off-topic support requests here. :)
Comment #188
jonathan1055 CreditAttribution: jonathan1055 commentedPerfect solution. I have requested it on comment 18 in #2134179: Remove message on project and release nodes about the current status of project packaging
Comment #191
tvn CreditAttribution: tvn commentedI unpublished a bunch of unrelated comments. The message will be removed from the project pages later today.
Comment #192
Scyther CreditAttribution: Scyther commentedModule Author Pane (https://drupal.org/project/author_pane) has the problem that the date for the Development releases is not update but the file in the package is updated.
Comment #193
manuelBS CreditAttribution: manuelBS commentedCurrently on the new ERPAL from today with the latest core version I see http://screencast.com/t/Vsvrx8hMt4 but I there is no error written so I dont know how to fix it.
Comment #194
znerol CreditAttribution: znerol commentedTrying to release Authcache 7.x-2.0-beta1 today after 7.x-2.0-alpha5 (November 7th).
Quoting from the issue summary:
7.x-2.0-beta1 is not showing up in the release table on the project page after triggering a regeneration with this method.
Resaving the release notes of 7.x-2.0-beta1 did not work, resaving 7.x-2.0-alpha5 actually caused that now an even older version is shown on the release table on the project page, i.e. 7.x-2.0-alpha4. Additionally the 7.x-2.0-alpha5 release vanished from the project XML feed.
Comment #195
znerol CreditAttribution: znerol commentedMore of the same Taxonomy Term Status has 7.x-1.0 release, however on the project page only the dev-release is shown. Same story in the project XML feed.
However I did not edit any release nodes over at that project recently. 7.x-1.0 is from November 6th.
Comment #196
webchickNavbar https://drupal.org/project/navbar has the same issue. beta1 is the latest at https://drupal.org/node/1728538/release, but alpha10 is the one listed on https://drupal.org/project/navbar and also at https://drupal.org/node/1728538/edit/releases.
...aaaaaand by re-submitting the releases form it picked it up.
Comment #197
znerol CreditAttribution: znerol commentedThis does not work over here. Is this a permission-problem?
Comment #198
znerol CreditAttribution: znerol commentedFor the moment I've placed a note at the project page. I still hope that someone with superpowers comes along and rescues me out of maintainers hell where release numbers are moving backwards.
Comment #199
mitchell CreditAttribution: mitchell commentedI have a similar problem to #194. In my project's case, the beta release showed up fine, but then I edited the release node to add more notes. This caused the beta release to no longer show up as recommended. I tried to resave it, but it didn't help. Then I tried to resave the alpha release that came back to recommended, and now it no longer shows up either.
Comment #200
kreynen CreditAttribution: kreynen commentedI'm really at a loss about what to do at this point as well.
The reason I started this issue was I couldn't package updates to a distribution. It's been over a month since the D7 update and we still can't reliably package distributions. At this point the packaging errors are preventing security updates from being applied to sites using a distribution.
I do not understand why a consistent message about the issue was removed from the project pages other than it was really making the D.A. look bad. Now individual project maintainers are left to explain why releases aren't showing up again. The benefit? Newbie users don't mistakenly post to the wrong queue?!?
I'm posting a message to distributions I'm involved with explaining the situation. I'm also emailing the users I know who are using the distribution asking them to post here. If enough users complain that the issue is preventing them from applying security updates, maybe this will actually get resolved.
Several distributions have reported similar errors to what we're seeing w/ https://drupal.org/project/cm_starterkit_easy...
https://drupal.org/comment/8233333#comment-8233333
https://drupal.org/comment/8215399#comment-8215399
But then somehow the error is resolved and the distribution is packaged. Unfortunately there has been more time spent complaining about how posting these drush errors impacts the formatting of this issue than documenting how to resolve it.
#2141559: Better Error Reporting when packager fails was listed in the issue summary at one point (https://drupal.org/node/2132659/revisions/6723061/view), but was removed and is no longer considered related to the D7 update of Drupal.org.
I'm not entirely sure if that error is the cause of the memory errors in the drush error or a symptom of some other issue.
One thing I learned today is it doesn't matter who commits the change to the .make, only the owner of the release (I think?) can see that packaging error. When I go to https://drupal.org/project/cm_starterkit_easy and click on Notes, I see one of the now really common, ridiculously long drush errors. It was...
http://pastebin.com/1FRAdSnM
Now after making some mirror changes and committing again, it's now...
http://pastebin.com/wXyrCixh
When @jdcreativity goes to that Notes link, never sees the error.
From what I can make out, this is part of the errors is normal...
DRUSH_BACKEND:{"type":"debug","message":"Library whitelist loaded from http:\/\/drupal.org\/packaging-whitelist\/json:\narray (\n 0 => '^http:\/\/arshaw\\\\.com\/fullcalendar\/downloads\/fullcalendar.+$',\n 1 => '^http:\/\/jqueryui\\\\.com\/download\/.+$',\n 2 => '^http:\/\/jquery-
...
^https:\/\/github\\\\.com\/Modernizr\/Modernizr\/.+$',\n 264 => '^https:\/\/github\\\\.com\/Modernizr\/Modernizr\/+$ ',\n)","timestamp":1386187715.9202,"memory":8666720,"error":null,"packet":"log"}
I don't even know if that's an error. The Modernizr Whitelist entry was the most recent entry to be approved #2133407: Add Modernizr. I'm guessing when I whitelist the requests that have been RBTC in https://drupal.org/project/issues/drupalorg_whitelist, Leaflet.js, Holder.js, and JQuery UI Multiselect will make up item 265, 266, and 267 in the "error" array.
I think these are the actual errors in the first error...
This distribution doesn't even use jquery.cycle or fullcalendar?!?!
What I know is that this distribution packaged before the D7 update of Drupal.org. Error messages related to attempting to package a URL that wasn't whitelisted was relatively easy for a human being to decipher. The distribution does not package now. Several distributions have reported similar error messages, but it is unclear what (if anything) was done to resolve the issue or if the issue is even related to the project where it is being displayed and isn't just a timing issue really caused by the testbot and just happens to show up in packaging...
https://drupal.org/comment/8201245#comment-8201245
Attempting to package a supported "7.x-2.0-alpha4" release results in the same error https://drupal.org/node/2150167
Comment #201
moshe weitzman CreditAttribution: moshe weitzman commentedAs you suggested, these Drush log messages have ""error":null" which says that they are not error messages. These are just debug messages. I don't see any Drush errors in the pastebins. I don't know why the packaging script declares a fail. I'll offer my assistance at #2141559: Better Error Reporting when packager fails. Hopefully someone more knowledgeable can help here.
Comment #202
Damien Tournoud CreditAttribution: Damien Tournoud commentedThere are definitely hidden errors. Updating Drush would be a good first step (as it will include my concurrency fix that removes those backend packets from the update).
Comment #203
moshe weitzman CreditAttribution: moshe weitzman commentedAgree with damz - first try running with modern Drush.
If the problem turns out to be 'out of memory' and you don't want to simply allocate more, we made an optimization 3 weeks ago in make. That fix will be in 6.2.0 which is coming out in the next few days.
Comment #204
jdcreativity CreditAttribution: jdcreativity commentedI am one of the users who helps to co-maintain a distribution. Since I am the co-maintainer and not the primary person responsible to packaging the distribution I have been completely in the dark regarding these failures to package. I don't even get the error messages on the project release page after a commit.
I want to echo the need to get these resolved. I also want to acknowledge how exceptionally complex this upgrade must be to those on the inside.
Comment #205
znerol CreditAttribution: znerol commentedSeparate issue for releases disappearing after saving release notes over at the Project project #2150865: Saving release notes makes release disappear from project feed and project page release table.
Comment #206
dwwRe: #200 -- I understand your frustration. I can't answer everything, but a few quick replies:
(and also comment #204).
Project release only shows packaging errors to maintainers who have the 'administer releases' project permission. Looking at https://drupal.org/node/1475580/maintainers I see that kreynen is currently the only maintainer of that project with that permission. If you don't think that's reasonable, let's discuss further in a separate issue, but I consider the current behavior "by design".
Re: #2141559: Better Error Reporting when packager fails -- I didn't realize that was in the critical path for trying to fix this bug. It seemed like a good idea, but not something uniquely broken by the d.o D7 upgrade. So I was just trying to clean out the queue to help us keep the focus on the actual regressions. Apologies if I made the wrong call -- we're all human and make (plenty of) mistakes.
Re:
We don't need crowd-sourced noise to convince anyone this is a critical bug. "We" know there are some critical regressions related to release packaging, and we're trying to make progress on this (along with many other bugs). I was hoping #2137201: [META] Regressions in project_release handling of version element fields and release-history XML would clean up a lot of the remaining problems, but apparently there are still some lingering bugs that haven't been killed by that META and all the subtasks we did solve. Adding to the frustration is that some of the code that appears to be failing on production seems to be working on the d.o dev sites, so it's not as simple as finding broken code and fixing it. Instead, we're in the realm of "WTF is going wrong with the production DB that these queries don't work as expected?".
Anyway, there's probably more to say, but I'm going to keep trying to fix what remains broken... :/
Sorry,
-Derek
Comment #207
kreynen CreditAttribution: kreynen commented@dww Thanks for taking the time to respond. I've changed @jdcreativity's permissions on project and updated https://drupal.org/node/1432190 to include the information about needing the 'administer releases' project permission.
Individual projects posting their own "warnings" pointing end users to this issue to explain why they can't update seems like the only logical thing to do after #2134179: Remove message on project and release nodes about the current status of project packaging.
If the situation is really to a "WTF is going wrong with the production DB that these queries don't work as expected?" state, isn't that the type of thing that deserves some type of notification?
Comment #208
dwwGlad I shut up and started debugging. ;) I think I just discovered (and have a relatively sane proposal to fix) the root of many (most?) of our remaining bugs:
#2150865-2: Saving release notes makes release disappear from project feed and project page release table
Stay tuned...
Thanks/sorry,
-Derek
Comment #209
stefanwray CreditAttribution: stefanwray commentedI'm the General Manager at channelAustin. We run www.channelaustin.org and community.channelaustin.org. I'm also the co-maintainer of the Community Media Difficult Starter Kit https://drupal.org/project/cm_starterkit_difficult. As @jdcreativity has indicated I feel very powerless in this current situation with the packaging not working properly. I've been involved with the Drupal community for more than 6 years and this is worst problem that I've ever experienced.
We are stuck. We cannot move forward. And it has been this way for a month now.
We've gotten used to the fact that things don't always work properly and there is a need for bug fixes. But we're in a situation now where the bugs can be fixed. But they just can't be applied
And now I'm finding out that due to this we not be able to upgrade to the latest Drupal version.
I hope this gets addressed soon.
I just don't understand why more people haven't been working on this to solve it faster. It seems to be a universal problem that impacts the entire Drupal community.
This doesn't reach the level of the White House's health care web site debacle, but for Drupal users and Drupal developers this has not been good at all.
Comment #210
jthorson CreditAttribution: jthorson commentedI just want to re-iterate ... crowd-sourced noise does nothing to help us track down the root cause of the issues, and the warning was causing all sorts of non-package related noise in this thread - to the extent that people started reporting totally unrelated user problems with various modules *here*, because it was a nice convenient link on the project page.
Personally, I feel the 8-10 issues we tracked down and solved in this META thread are enough to close it off; and chase the one remaining item in a dedicated issue; which would make it much easier to filter what's remaining (at a glance!) and focus more attention on solving the issue than sorting through 200+ comments to try and identify it.
Hopefully dww's discovery in #208 will let us put this to bed without having to go to that extent. :)
Comment #211
dwwOkay, #2150865: Saving release notes makes release disappear from project feed and project page release table is now fixed and deployed live. The release history feeds are rebuilding. I think that should repair most of the distro packaging badness (and all of the project page badness for the modules themselves).
Seems like for the distro project pages themselves, we need to focus on #2137095-9: Should supported releases be shown on downloads table even if it contains insecure modules? If so, how?.
There are a few other follow-up child issues here, but honestly, this particular issue is so confusing and unwieldy (and getting emotionally charged) that I think the best thing would be to close it and just focus on the remaining bugs as separate issues instead of pinging 90+ people for every comment in here about every issue.
Comment #212
tvn CreditAttribution: tvn commentedRe #192 Scyther, please make another commit to https://drupal.org/project/author_pane. It seems last commit happened before we fixed that issue. New commit should refresh the date.
Comment #213
tvn CreditAttribution: tvn commentedRe #199, mitchell, please edit the release you have trouble with one more time, it should work now since #2150865: Saving release notes makes release disappear from project feed and project page release table is fixed.
Comment #214
webchickThe 7.x-1.0-alpha9 release of Spark (which was tagged/released before the D7 upgrade and somehow disappeared since then) did not automatically show up at https://drupal.org/project/spark. Do project owners need to do something manual for the new logic to kick in? Is there a way to automate this process across all of contrib, since there are likely tons of other projects who do not closely follow their own projects' download tables?
Comment #215
tvn CreditAttribution: tvn commentedAdded a note about the latest fix deployed.
Comment #216
tvn CreditAttribution: tvn commented@webchick, I was just adding that info to the summary when you commented. Project owners need to edit the release in question, and it will be back in the table. We'll work on fixing all the projects, dww is opening follow up issue right now. We just wanted to deploy the fix asap to stop this from happening to more and more projects.
Comment #217
dww@webchick Re #214 - Right. tvn wanted me to ship the fix now, instead of waiting for writing an update to automatically repair everything. For now, editing any release of Spark should fix everything (except rebuilding the release feeds, which is happening automatically). Automatic cleanup now lives at #2151555: Write a drush command to check release status for projects.
Comment #218
dww@webchick: whoops, sorry. I assumed this was a module. It's a distro. Therefore, it's probably not showing up due to #2137095-9: Should supported releases be shown on downloads table even if it contains insecure modules? If so, how? not because of the recent fixes I deployed.
Comment #219
webchickOh, shoot. I also forgot it was a distro. LOL :D Ok I'll go over there, thanks.
Comment #220
sylus CreditAttribution: sylus commentedPackaging was working for me for the last few weeks but as of today I am now getting:
>> Whitelist download from http://drupal.org/packaging-whitelist/json failed: not found [error]
Comment #221
tvn CreditAttribution: tvn commentedSylus, which release are you talking about? wetkit 7.x-1.0 seems fine now.
Comment #222
dww#2137095: Should supported releases be shown on downloads table even if it contains insecure modules? If so, how? is now fixed. There are two follow-ups for it if anyone's interested:
#2151555: Write a drush command to check release status for projects has a patch that's (IMHO) ready to deploy so we can repair any lingering projects that were effected by #2150865: Saving release notes makes release disappear from project feed and project page release table.
This issue seems like an extremely unwieldy way to resolve individual support requests with various projects and releases.
I'd vote to just close this one now and handle any remaining issues as separate follow-ups.
Thanks,
-Derek
Comment #223
sylus CreditAttribution: sylus commentedYeah, my issue with whitelist failing to download is resolved must have been a temporary issue. :)
Comment #224
jthorson CreditAttribution: jthorson commentedI second the "close this issue" sentiment. :)
Comment #225
kreynen CreditAttribution: kreynen commentedSince there haven't been any new reports of issues at the module or theme level since the latest fixes were pushed and the distribution issues seem to be random w/ error messages that have nothing to do with the actual problems at this point, I've gone ahead and closed the issue.
Comment #226
Perignon CreditAttribution: Perignon commentedOddly enough this came up again today. However my scenario is different. I pushed a tag with the improper naming. I deleted the tag locally and remotely. I created a new one, pushed it, but not showing up. Through my searching I ended up here.
Here is the repo. The tag in question I cannot seem to access is 7.x-2.0-beta3
http://cgit.drupalcode.org/commerce_rules_extra/refs/?id=3780721
Comment #227
DamienMcKenna@Perignon: You mean "7.x-2.1-beta3"?
Comment #228
Perignon CreditAttribution: Perignon commented@DamienMcKenna Yup... typo!
7.x-2.1-beta3
Comment #229
drumm@Perignon I re-synced your repo and you can now make this release.
Comment #230
drummFor any additional issues - please file a new infrastructure issue, rather than commenting on this old issue.
Comment #231
Perignon CreditAttribution: Perignon commented@drumm Thank you. Noted for the future.