On Fri, Nov 28, 2008 at 19:32, Holger Levsen <[EMAIL PROTECTED]> wrote:
> (*) of course, we could also try to persuade the release team that new > upstream versions of sugar are desirable for lenny. I'm not sure I agree. > (And new upstream versions are per default a "no" in a freeze, there are > exceptions, but..) 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. All I did was to run a regexp replacing the old path with the new one. I see no reason why a new package release in lenny should be a problem; this is a packaging fix that does not modify any sugar code as far as I am aware. -lf
