Iceweasel/Icedove ESR and Whezzy

[Hideki Yamane]

Hi,

On Sun, 14 Oct 2012 21:56:02 +0200
Alexander Wirt <formorer at formorer.de> wrote:
> > > When you have backports in your sources.list, you don't automatically
> > > get your upgrades from there. Once you do install one for the first
> > > time, subsequent upgrades come from backports. But in the case of
> > > iceweasel, version bumps also require new packages for xulrunner and
> > > libmozjs, and that prevents automatic upgrades: iceweasel's is kept
> > > back by apt. Default apt preferences for the iceweasel packages would
> > > ensure stable users that use backports sources will always get the
> > > latest.
> > 
> > You may wish to include an /etc/apt/preferences.d/iceweasel [1] file in
> > your backported software, but I wonder if that would be a really good
> > idea, if that would be enough to achieve your purpose, and if that would
> > be safe of unwanted side effects.
> Wrong, not in the backported one. In the stable one. If a package is
> installed from bpo the file isn't needed.

 Do we have any conclusion for this issue?

 - Mozilla upstream will terminate 10.0.x ESR update in 19th Febrary,
   then will switch to 17.0.x.
 - Wheezy seems to be released after above.
 - It means that iceweasel/icedove maintainers should work hard if we'll
   maintain 10.0.x in Wheezy.
 - If we just would encourage users to migrate 17.0.x in backports via 
   release note, it's easy but it will be significant trouble for average
   users, IMHO.
 - Just bump Iceweasel/Icedove up is difficult due to reverse dependency.

 Q: can we provide updated Iceweasel/Icedove in stable-updates channel?


-- 
Regards,

 Hideki Yamane     henrich @ debian.or.jp/org
 http://wiki.debian.org/HidekiYamane