Hi Luke, On Saturday 29 November 2008 01:42, Luke Faraone wrote: > As I've said, it's been fixed in those packages, we're just awaiting a > release. > Moreover, the fix was made to the older upstream version in git, > so new-upstream-version isn't a problem, we just need a @debian to upload.
the subject says "in git"...
$ rmadison sugar
sugar | 0.81.4-1 | testing | source, all
sugar | 0.82.8-3 | unstable | source, all
In git for which version did you fix it?
> I see no reason why a new package release in lenny should be a problem;
New upstream versions are (normally) not accepted during a freeze, and we are
in a freeze.
To fix those issues for the version in lenny, 0.81 packages need to be
uploaded to testing-proposed-updates (and not to unstable, like normal
uploads). For this, you need preapproval from the release team, which you
will only get if a.) the upload fixes stuff which is really wanted to have in
lenny (this is usually determined with a bug, currently only one such bug
(this) is filed against sugar, but not against the other activities) and b.)
when you asked for it showing the full diff.
Thats why I suggested to clone this bug several times and reassign these
clones to the various activity packages...
regards,
Holger
P.S.: I'm subscribed to the sugar packages and to the debian-olpc list, not
being cc:ed makes me smile.
I'm also a @debian.org and can upload :)
pgpXtt9bcZ2YJ.pgp
Description: PGP signature
