drush_4.4-1~bpo50+1_amd64.changes is NEW
(new) drush_4.4-1~bpo50+1.diff.gz optional php
(new) drush_4.4-1~bpo50+1.dsc optional php
(new) drush_4.4-1~bpo50+1_all.deb optional php
command line shell and Unix scripting interface for Drupal
drush is a command line shell and Unix scripting interface for Drupal, a
veritable Swiss Army knife designed to make life easier for those of us
who spend some of our working hours hacking away at the command prompt.
.
Drush core ships with lots of useful commands for interacting with code
like modules/themes/profiles. Similarly, it runs update.php, executes
sql queries and DB migrations, and misc utilities like run cron or clear
cache.
Changes: drush (4.4-1~bpo50+1) lenny-backports-sloppy; urgency=low
.
* Rebuild for lenny-backports-sloppy.
.
drush (4.4-1) unstable; urgency=low
.
* New upstream minor release to fix .info file.
.
drush (4.3-1) unstable; urgency=low
.
* New upstream release, see http://drupal.org/node/1091572
* Changed git repos to be the upstream repos, which have accepted that
the Debian branch live upstream. Upstream (msonnabaum) has also
manifested interest in maintaining the Debian/Ubuntu packages.
.
drush (4.2-1) unstable; urgency=low
.
* New upstream release
* Updated manpage (Closes: #595908)
* Forgot to mention that the upstream release fixed the vget bug
(Closes: #595772)
.
drush (4.1-1) unstable; urgency=low
.
* New upstream release (Closes: #609362)
This branch (4.x) is likely to live only in sid considering upstream
is already considering a 5.x release. In general, the release cycle of
Debian and Drush are incompatible, the latter being roughly every 6
months. I will try to keep sid (and therefore testing) up to date with
the upstream stable and people will be free to use 3.3 (in squeeze or
lenny-backports) or whatever the latest stable upstream is (in sid or
testing).
.
* standards upgrade to 3.9.1 - no change
* update table.inc to follow upstream
Override entries for your package:
Announcing to debian-backports-changes@lists.debian.org
Your package contains new components which requires manual editing of
the override file. It is ok otherwise, so please be patient. New
packages are usually added to the override file about once a week.
You may have gotten the distribution wrong. You'll get warnings above
if files already exist in other distributions.
l get warnings above
if files already exist in other distributions.
Reply to: