Steve Langasek wrote:
> Is there a summary available of the upstream changes (in particular, any
> changes that aren't straightforward bugfixes)?
Since the current package is from more than one year ago, there surely
are.
> If there are non-bugfix changes here, why do these warrant a freeze
> exception?
The main reason is that the package was out of sync with Debian for a
while because it didn't work anymore with Ubuntu's xulrunner (which
doesn't allow xulrunner-stub to be symlinked) and hasn't been synced
anymore after that problem has been fixed in Debian in January.
I asked Alexander Sack several times since January to have a look at
this, but the only reply that I got was that the package may be kicked
out anyway due to Mozilla's new release policy. Maybe that's the
reason why nobody synced it earlier.
Steve Langasek wrote:
> Is there a summary available of the upstream changes (in particular, any
> changes that aren't straightforward bugfixes)?
Since the current package is from more than one year ago, there surely
are.
> If there are non-bugfix changes here, why do these warrant a freeze
> exception?
The main reason is that the package was out of sync with Debian for a
while because it didn't work anymore with Ubuntu's xulrunner (which
doesn't allow xulrunner-stub to be symlinked) and hasn't been synced
anymore after that problem has been fixed in Debian in January.
I asked Alexander Sack several times since January to have a look at
this, but the only reply that I got was that the package may be kicked
out anyway due to Mozilla's new release policy. Maybe that's the
reason why nobody synced it earlier.
Regards, Axel people. debian. org/~abe/
--
,''`. | Axel Beckert <email address hidden>, http://
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
`- | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5