Re: Iceweasel/Icedove ESR and Whezzy
Hi, On Sun, 14 Oct 2012 21:56:02 +0200 Alexander Wirt 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 -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130105110602.8b045bb857833a7cd7505...@debian.or.jp
Re: Iceweasel/Icedove ESR and Whezzy
On Sun, 14 Oct 2012, David Prévot wrote: > [ Maybe a -backports list would be a better place to discuss this issue > than -release ] > > Hi, > > Le 14/10/2012 03:41, Mike Hommey a écrit : > > > 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. Alex -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121014195602.ga5...@snow-crash.org
Re: Iceweasel/Icedove ESR and Whezzy
[ Maybe a -backports list would be a better place to discuss this issue than -release ] Hi, Le 14/10/2012 03:41, Mike Hommey a écrit : > 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. 1: $ cat /etc/apt/preferences.d/iceweasel Package: iceweasel Pin: release a=squeeze-backports Pin-Priority: 500 Regards David signature.asc Description: OpenPGP digital signature
Re: Iceweasel/Icedove ESR and Whezzy
On Sat, Oct 13, 2012 at 02:19:25PM +0200, Julien Cristau wrote: > On Sat, Oct 13, 2012 at 09:43:48 +0200, Mike Hommey wrote: > > > Or maybe it would be a good idea to add the working pinning setup to the > > iceweasel package itself, so that people that add backports source will > > automatically get proper upgrades? Or maybe not, I'm just throwing an > > idea. > > > What does that even mean? 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. Mike -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121014074143.ga24...@glandium.org
Re: Iceweasel/Icedove ESR and Whezzy
On Sat, Oct 13, 2012 at 09:43:48 +0200, Mike Hommey wrote: > Or maybe it would be a good idea to add the working pinning setup to the > iceweasel package itself, so that people that add backports source will > automatically get proper upgrades? Or maybe not, I'm just throwing an > idea. > What does that even mean? Cheers, Julien signature.asc Description: Digital signature
Re: Iceweasel/Icedove ESR and Whezzy
On 13.10.2012 09:43, Mike Hommey wrote: > That being said, I think we should actively advise people to use > backports for iceweasel. Making that statement part of the release notes > might be a good idea. Possibly with a working pinning setup. > > Or maybe it would be a good idea to add the working pinning setup to the > iceweasel package itself, so that people that add backports source will > automatically get proper upgrades? Or maybe not, I'm just throwing an > idea. Sounds interesting. I'd love to see ESR 17 (or any later ESR version) easily accessible in wheezy. Maybe d-i could even generate a proper backports configuration in sources.list but commented out by default? Seeing that backports are now an official part of the archive and promoted more actively, that would make sense imo. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: Iceweasel/Icedove ESR and Whezzy
On Sat, Oct 13, 2012 at 09:41:08AM +0200, Mike Hommey wrote: > On Sat, Oct 13, 2012 at 07:13:08AM +0900, Hideki Yamane wrote: > > Hi, > > > > Thank you for maintaining Iceweasel/Icedove. > > > > Now I have a question about its release/update schedule. > > As http://www.mozilla.org/en-US/firefox/organizations/faq/ says, they'll > > terminate Firefox 10.0.x ESR and move forward to 17.0.x. And its date > > seems to be around Wheezy release. It means Iceweasel/Icedove will be > > EOL before/after soon Wheezy release. > > > > Will Iceweasel/Icedove be upgrade to 17.0.x after 10.0.x EOL? > > No. It has too many reverse dependencies for this to be possible, even > if it were allowed (Debian doesn't usually bump software versions on a > stable release) > > That being said, 17 is going to be released in 6 weeks, so presumably, > one would think it's possible to push it for wheezy. But really, it's > not. First, because of the same reverse dependencies. I doubt many of > them would survive the version bump. Another problem is that it won't > reach a releaseable state in a short time frame. Look at the build logs > of iceweasel 16: > https://buildd.debian.org/status/package.php?p=iceweasel&suite=experimental > Besides actual code problems on kfreebsd, it crashes on armel, ia64, > powerpc, s390, and sparc. 17 is likely to break in other ways (for > instance, ia64 just broke on 16, it was ok on 15). There are also a lot > of failures in the test suites that need to be addressed (there are also > such failures on 10, but there are less of them) That being said, I think we should actively advise people to use backports for iceweasel. Making that statement part of the release notes might be a good idea. Possibly with a working pinning setup. Or maybe it would be a good idea to add the working pinning setup to the iceweasel package itself, so that people that add backports source will automatically get proper upgrades? Or maybe not, I'm just throwing an idea. Mike -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121013074348.gc9...@glandium.org
Re: Iceweasel/Icedove ESR and Whezzy
On Sat, Oct 13, 2012 at 07:13:08AM +0900, Hideki Yamane wrote: > Hi, > > Thank you for maintaining Iceweasel/Icedove. > > Now I have a question about its release/update schedule. > As http://www.mozilla.org/en-US/firefox/organizations/faq/ says, they'll > terminate Firefox 10.0.x ESR and move forward to 17.0.x. And its date > seems to be around Wheezy release. It means Iceweasel/Icedove will be > EOL before/after soon Wheezy release. > > Will Iceweasel/Icedove be upgrade to 17.0.x after 10.0.x EOL? No. It has too many reverse dependencies for this to be possible, even if it were allowed (Debian doesn't usually bump software versions on a stable release) That being said, 17 is going to be released in 6 weeks, so presumably, one would think it's possible to push it for wheezy. But really, it's not. First, because of the same reverse dependencies. I doubt many of them would survive the version bump. Another problem is that it won't reach a releaseable state in a short time frame. Look at the build logs of iceweasel 16: https://buildd.debian.org/status/package.php?p=iceweasel&suite=experimental Besides actual code problems on kfreebsd, it crashes on armel, ia64, powerpc, s390, and sparc. 17 is likely to break in other ways (for instance, ia64 just broke on 16, it was ok on 15). There are also a lot of failures in the test suites that need to be addressed (there are also such failures on 10, but there are less of them) Mike -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121013074108.gb9...@glandium.org
Iceweasel/Icedove ESR and Whezzy
Hi, Thank you for maintaining Iceweasel/Icedove. Now I have a question about its release/update schedule. As http://www.mozilla.org/en-US/firefox/organizations/faq/ says, they'll terminate Firefox 10.0.x ESR and move forward to 17.0.x. And its date seems to be around Wheezy release. It means Iceweasel/Icedove will be EOL before/after soon Wheezy release. Will Iceweasel/Icedove be upgrade to 17.0.x after 10.0.x EOL? -- Regards, Hideki Yamane henrich @ debian.or.jp/org http://wiki.debian.org/HidekiYamane -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121013071308.2404ce6a7a4ed2aead3e3...@debian.or.jp
