Please sync sugar 0.81.4-1 from Debian unstable (main)
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| sugar (Ubuntu) |
Won't Fix
|
Wishlist
|
Unassigned | ||
Bug Description
Binary package hint: sugar
Hi all,
Debian has sugar 0.81.4-1
This is from the Debian changelog
http://
sugar (0.81.4-1) unstable; urgency=low
* New upstream release.
* Disable (but keep in source) patch 2003 (refactored upstream).
* Tighten dependency on python-
moved).
* Update local cdbs snippets:
+ Relax copyright-check to only warn about its discoveries. Closes:
bug#486984.
+ Update dependency cleanup to strip cdbs 0.4.27 (not 0.4.27-1).
* Update debian/copyright (new files, same owners and licenses).
Update debian/
* Semi-auto-update debian/control to update build-dependencies:
-- Jonas Smedegaard <email address hidden> Fri, 20 Jun 2008 23:11:55 +0200
sugar (0.81.2-1) unstable; urgency=low
* New upstream Release.
-- Jonas Smedegaard <email address hidden> Mon, 26 May 2008 10:06:47 +0200
sugar (0.81.1-1) unstable; urgency=low
* New upstream release.
+ Merge activities.default into favorites. Closes: bug#480856.
* Unfuzz patches.
* Update debian/copyright and debian/
same licenses).
* Rewrite debian/copyright to only mention each licensing string once.
-- Jonas Smedegaard <email address hidden> Sat, 24 May 2008 22:31:14 +0200
sugar (0.79.4-2) unstable; urgency=medium
* Update cdbs tweaks:
+ Strip any non-printable characters in copyright-check.mk.
* Update danish l10n.
* Raise to urgency=medium, as these are small changes that shouldn't
delay the earlier large changes reaching Lenny.
-- Jonas Smedegaard <email address hidden> Tue, 29 Apr 2008 15:29:41 +0200
| Changed in sugar: | |
| importance: | Undecided → Wishlist |
| Emmet Hikory (persia) wrote | #1 |
| Luke Faraone (lfaraone) wrote | #2 |
| Changed in sugar: | |
| status: | New → Won't Fix |
Apologies, but the sponsors were unable to get to this request prior to feature freeze. It appears that this update will require a feature-freeze exception. If you are sure that this is not the case, please resubscribe the sponsors queue. If it is the case, please work with the MOTU Release team to get this update approved.