Hi, The patch is actually as trivial as I expected - Inlining it here:
diff --git a/modules/update/update.fetch.inc b/modules/update/update.fetch.inc
index 22db6e8..136a500 100644
--- a/modules/update/update.fetch.inc
+++ b/modules/update/update.fetch.inc
@@ -86,6 +86,9 @@ function _update_refresh() {
*/
function _update_build_fetch_url($project, $site_key = '') {
$default_url = variable_get('update_fetch_url', UPDATE_DEFAULT_URL);
+ if ($project['name'] == 'drupal') {
+ $project['name'] = 'debian-uses-own-updates';
+ }
if (!isset($project['info']['project status url'])) {
$project['info']['project status url'] = $default_url;
}
I feel this has the best of both worlds, and no advantages. Why?
• It allows administrators to keep the (very useful) update_status
module enabled, alerting them of any new versions of
locally-installed packages
• Drupal6 core should be updated together with the full system —
Responsible administrators will keep the whole system up to date via
apt-get/aptitude/…
• While this patch will ignore any modules built by dh-make-drupal,
those packages are not officially provided by Debian, and alerting
about updates is IMHO adequate.
--
Gunnar Wolf - gw...@debian.org - (+52-55)5623-0154 / 1451-2244
PGP key 1024D/8BB527AF 2001-10-23
Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF
signature.asc
Description: Digital signature
