>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #2675892. --> Reported by: [mariagwyn](https://www.drupal.org/user/14363) >>> <p>Running<br> <code>drush ups</code><br> on any D6 site now returns this:</p> <pre>Name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Installed Version&nbsp;&nbsp;&nbsp; Proposed version&nbsp;&nbsp;&nbsp;&nbsp; Message<br> Drupal&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 6.37&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 6.37&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Installed version not supported<br> Acquia agent (acquia_connector)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 6.x-2.17&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 6.x-2.17&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Installed version not supported<br> Administration menu (admin_menu)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 6.x-1.8&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 6.x-1.8&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Installed version not supported<br> Backup and Migrate (backup_migrate)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 6.x-2.8&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 6.x-2.8&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Installed version not supported<br>...</pre><p>This means that drush cannot detect nor update any remaining module updates, nor can it apply the current core update. While D6 is deprecated, turning off this functionality seems hasty until updates can be reasonably applied.</p> <h3>Proposed resolutions</h3> <p>From comment <a href="https://www.drupal.org#comment-10911548">#32</a>:</p> <blockquote><p> Based on the discussion last night, looks like what is going to happen is (please correct me if I am wrong or expand if I missed something):</p> <p>- Update status information on drupal.org will be different based on reporting Drupal 6 version, so we can tell pre 6.38 users to update to 6.38. The standard "unsupported" marking affected all versions, so we cannot use that, manual changes are needed. This resolves the immediate concern with the incorrect information.<br> - We may release Drupal 6.39 with better messaging in place of update status' reporting which points people to a landing page on drupal.org to figure out their further options. There was no firm decision on this point AFAIR. </p></blockquote> <p>The issue to discuss a proposed Drupal 6.39:</p> <p><span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-5"><a href="https://www.drupal.org/project/drupal/issues/2678882" title="Status: Closed (won't fix)">#2678882: Release to improve LTS messaging in Update status</a></span></p> <p>David Rothstein suggested some alternative approaches in <a href="https://www.drupal.org#comment-10913202">#36</a>.</p> <p>And an update status alternative from one of the Drupal 6 LTS vendors in <a href="https://www.drupal.org#comment-10932563">#41</a>:</p> <blockquote><p> We've finally (sorry for the delay) published our alternative to the 'update' module (it's a fork):</p> <p><a href="https://www.drupal.org/project/mydropwizard">https://www.drupal.org/project/mydropwizard</a></p> <p>It does two main things:</p> <ol> <li>It still shows security updates if a module is unsupported, so you'll know about security updates you haven't applied, regardless, and</li> <li>It uses an alternate data source that reports whether a module is supported by the Drupal 6 Long-Term Support (LTS) vendors, so you'll know if it'll be getting security updates going foward</li> </ol> <p>While it uses a different data source, it continues to report usage information back to Drupal.org, so the community won't lose that valuable resource. </p></blockquote> > Related issue: [Issue #2678882](https://www.drupal.org/node/2678882)