Hideki Yamane schrieb:
> Hi,
>
> On Fri, 18 May 2018 10:29:03 +0200
> Moritz Mühlenhoff wrote:
>> > Does it fail like in bug #858153 (which has a patch) or in a different way?
>>
>> That bug is a year old and for 0.19, not sure if it's still any relevant
>> for current releases, when trying to
Hi,
On Fri, 18 May 2018 10:29:03 +0200
Moritz Mühlenhoff wrote:
> > Does it fail like in bug #858153 (which has a patch) or in a different way?
>
> That bug is a year old and for 0.19, not sure if it's still any relevant
> for current releases, when trying to run a bootstrap build with 0.25
Emilio Pozuelo Monfort schrieb:
> On 16/05/18 19:12, Moritz Mühlenhoff wrote:
>> I've started to look into this; I have created a llvm-4.0 build
>> for stretch and build a bootstrap build of rustc 1.24 against it.
>> Those two went fine.
>>
>> However cargo's bootstrap is
On 16/05/18 19:12, Moritz Mühlenhoff wrote:
> I've started to look into this; I have created a llvm-4.0 build
> for stretch and build a bootstrap build of rustc 1.24 against it.
> Those two went fine.
>
> However cargo's bootstrap is broken ATM which will need fixing (and
> it also requires a
Hi,
On 05/16/2018 07:12 PM, Moritz Mühlenhoff wrote:
> However cargo's bootstrap is broken ATM which will need fixing (and
> it also requires a more recent libgit than we have in stretch).
I'm backporting firefox to stretch since a while. rustc built fine with
llvm-3.9 so far.
On 05/16/2018 07:12 PM, Moritz Mühlenhoff wrote:
> Hideki Yamane schrieb:
>> Firefox60 needs rustc (>= 1.24) to be built but rustc in stretch is 1.14.
>> rustc (>= 1.24) needs llvm-4.0 and cargo but it is not in stretch...
>>
>> - add llvm-4.0 and cargo to stretch
>> -
Hideki Yamane schrieb:
> Firefox60 needs rustc (>= 1.24) to be built but rustc in stretch is 1.14.
> rustc (>= 1.24) needs llvm-4.0 and cargo but it is not in stretch...
>
> - add llvm-4.0 and cargo to stretch
> - backport rustc
> - rebuild build-depends: rustc
Hi,
On Thu, 3 May 2018 21:31:35 +0900
Mike Hommey wrote:
> > I expect nothing much different from previous ESR cycles: stretch will move
> > to 60 after 52 goes EOL in September.
>
> ... as long as we get the required compilers in stretch in time...
Firefox60 needs rustc
On Thu, 10 May 2018, Jonathan Dowland wrote:
> On Wed, May 09, 2018 at 08:27:32PM +0200, Moritz Muehlenhoff wrote:
> > It would be nice to move away from using RC bugs as testing blockers,
> > but instead declare a source package as not suitable for stable (e.g.
> > in some meta data on ftp-master
* Thomas Goirand [2018-05-10 17:36:19 +0200]:
> On 05/08/2018 03:01 AM, Paul Wise wrote:
> > On Thu, May 3, 2018 at 8:29 PM, Julien Cristau wrote:
> >
> >> I expect nothing much different from previous ESR cycles: stretch will move
> >> to 60 after 52 goes EOL in September.
> >
On 05/08/2018 03:01 AM, Paul Wise wrote:
> On Thu, May 3, 2018 at 8:29 PM, Julien Cristau wrote:
>
>> I expect nothing much different from previous ESR cycles: stretch will move
>> to 60 after 52 goes EOL in September.
>
> Does anyone know when firefox-esr in unstable will switch to 60?
It's
On Wed, May 09, 2018 at 08:27:32PM +0200, Moritz Muehlenhoff wrote:
It would be nice to move away from using RC bugs as testing blockers,
but instead declare a source package as not suitable for stable (e.g.
in some meta data on ftp-master or in whatever tooling involved) and
then have a
On Wed, May 09, 2018 at 11:10:23AM +0200, Raphael Hertzog wrote:
> While I understand the need to keep them out of stable, keeping them out
> of testing would annoy testing users and all users of "rolling" derivatives
> based on testing (where the packages are not a problem since new upstream
>
On Fri, 04 May 2018, Moritz Mühlenhoff wrote:
> We should make it easy for administrators of bigger desktop
> deployments to easily create debs for local deployments, but
> keeping all those extensions in a stable release is just
> broken and we should block them from testing migration.
While I
On Tue, May 08, 2018 at 09:01:20AM +0800, Paul Wise wrote:
> On Thu, May 3, 2018 at 8:29 PM, Julien Cristau wrote:
>
> > I expect nothing much different from previous ESR cycles: stretch will move
> > to 60 after 52 goes EOL in September.
>
> Does anyone know when firefox-esr in unstable will
On Thu, May 3, 2018 at 8:29 PM, Julien Cristau wrote:
> I expect nothing much different from previous ESR cycles: stretch will move
> to 60 after 52 goes EOL in September.
Does anyone know when firefox-esr in unstable will switch to 60?
Personally I would prefer it stay with 52 until it is EOL.
> - 2 don't mention it in the BTS (ublock-origin, debianbuttons)
Just for the record, the ublock-origin migration to webext is
underways, I simply ran out of time.
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot
Vincent Bernat wrote:
WebExtensions are backed by a standard draft:
https://browserext.github.io/browserext/. So, situation is expected to
improve in the future.
Mozilla have explicitly said that "Extensions created with the new
standard[...]won’t break in new Firefox releases." [0]
It has
On 2018-05-04 21:04, Holger Levsen wrote:
> because this is what the modern web has become in 2018. go gopher go!
Modern web? I don't use Mosaic anymore! :~)
On 2018-05-04 23:22, Moritz Mühlenhoff wrote:
> W. Martin Borgert schrieb:
> > If a software is not in Debian, I just don't use it.
>
> Your call. Don't use the extensions, then.
Alternatively: Do what is possible for me, to keep the software
I like to use in Debian. (It's
❦ 4 mai 2018 23:22 +0200, Moritz Mühlenhoff :
>> Why? We have now a huge breakage for all XUL extensions, but
>> were there problems of a similar scale before? Do we have to
>> expect similar breakages in the future with the new API?
>
> Sure, plenty of addons needed updates
On Fr, Mai 04, 2018 at 09:12:39 +0200, Moritz Mühlenhoff wrote:
Same as all previous extension breakages incurred by ESR transitions;
not at all. Apart from enigmail those are all not updated along
in stable, this doesn't scale at all. If you want your extensions
to be kept compatible, get them
Hello,
On Fri, May 04 2018, Moritz Mühlenhoff wrote:
> Same as all previous extension breakages incurred by ESR transitions;
> not at all. Apart from enigmail those are all not updated along in
> stable, this doesn't scale at all. If you want your extensions to be
> kept compatible, get them
W. Martin Borgert schrieb:
> On 2018-05-04 21:12, Moritz Mühlenhoff wrote:
>> Same as all previous extension breakages incurred by ESR transitions;
>> not at all. Apart from enigmail those are all not updated along
>> in stable, this doesn't scale at all. If you want your
On Fri, May 04, 2018 at 10:52:26PM +0200, W. Martin Borgert wrote:
> On 2018-05-04 21:12, Moritz Mühlenhoff wrote:
> > Same as all previous extension breakages incurred by ESR transitions;
> Why?
because this is what the modern web has become in 2018. go gopher go!
--
cheers,
Holger,
On 2018-05-04 21:12, Moritz Mühlenhoff wrote:
> Same as all previous extension breakages incurred by ESR transitions;
> not at all. Apart from enigmail those are all not updated along
> in stable, this doesn't scale at all. If you want your extensions
> to be kept compatible, get them from the
W. Martin Borgert schrieb:
> Quoting Moritz Mühlenhoff :
>> Julien Cristau schrieb:
>>> I expect nothing much different from previous ESR cycles: stretch will
>>> move to 60 after 52 goes EOL in September.
>>
>> Exactly.
>
> How will we
Hi,
Am 04.05.18 um 18:38 schrieb The Wanderer:
...
>> I guess so, yes. There's not much we can do if there is no support
>> for newer versions.
>
> Though please do take note of other applications which may still work
> with them.
>
> Even leaving other Mozilla-based browsers aside, ISTR there
On 2018-05-04 at 12:22, Emilio Pozuelo Monfort wrote:
> On 04/05/18 17:42, W. Martin Borgert wrote:
>> How will we deal with breaking extensions?
>>
>> E.g. I'm using xul-ext-scrapbook a lot. AFAIK, upstream does not
>> provide a post-XUL version. Probably other extensions will face the
>> same
On 04/05/18 17:42, W. Martin Borgert wrote:
> Quoting Moritz Mühlenhoff :
>> Julien Cristau schrieb:
>>> I expect nothing much different from previous ESR cycles: stretch will
>>> move to 60 after 52 goes EOL in September.
>>
>> Exactly.
>
> How will we deal
Quoting Moritz Mühlenhoff :
Julien Cristau schrieb:
I expect nothing much different from previous ESR cycles: stretch will
move to 60 after 52 goes EOL in September.
Exactly.
How will we deal with breaking extensions?
E.g. I'm using xul-ext-scrapbook
Julien Cristau schrieb:
> I expect nothing much different from previous ESR cycles: stretch will
> move to 60 after 52 goes EOL in September.
Exactly.
Cheers,
Moritz
在 2018年5月4日星期五 CST 上午3:56:30,Jeremy Bicha 写道:
> On Thu, May 3, 2018 at 3:32 PM, Adam Borowski wrote:
> > On Thu, May 03, 2018 at 02:29:59PM +0200, Julien Cristau wrote:
> >> I expect nothing much different from previous ESR cycles: stretch will
> >> move
> >> to 60 after 52
On Thu, May 3, 2018 at 3:32 PM, Adam Borowski wrote:
> On Thu, May 03, 2018 at 02:29:59PM +0200, Julien Cristau wrote:
>> I expect nothing much different from previous ESR cycles: stretch will move
>> to 60 after 52 goes EOL in September.
>
> That's really, really out of what
On Thu, May 03, 2018 at 02:29:59PM +0200, Julien Cristau wrote:
> On 05/03/2018 02:09 PM, Julien Aubin wrote:
> > Firefox 60esr is due for next week.
> >
> > As of now Debian Stretch is bound to Firefox ESR 52 which reaches EOL
> > soon. The problem is that it becomes less and less usable as more
On 2018-05-03 14:09:51 +0200 (+0200), Julien Aubin wrote:
> As of now Debian Stretch is bound to Firefox ESR 52 which reaches
> EOL soon. The problem is that it becomes less and less usable as
> more and more extensions are becoming incompatible with it.
>
> On the other hand team
El jue., 3 de may. de 2018 a la(s) 11:06, Julien Aubin <
julien.au...@gmail.com> escribió:
>
>
> Le jeu. 3 mai 2018 à 14:41, eamanu15 a écrit :
>
>> Hello Julien,
>>
>> Maybe this question need to be made on debian-metors or
>> pkg-mozilla-maintainer list.
>>
>> I
On Thu, May 03, 2018 at 02:29:59PM +0200, Julien Cristau wrote:
> On 05/03/2018 02:09 PM, Julien Aubin wrote:
> > Hi
> >
> > Firefox 60esr is due for next week.
> >
> > As of now Debian Stretch is bound to Firefox ESR 52 which reaches EOL
> > soon. The problem is that it becomes less and less
Hello Julien,
Maybe this question need to be made on debian-metors or
pkg-mozilla-maintainer list.
I think will be good wait until EOL before change to 60. I think that the
first months of 60ers will be a little unstable.
Regards!
El jue., 3 de may. de 2018 a la(s) 10:30, Julien Cristau <
On 05/03/2018 02:09 PM, Julien Aubin wrote:
Hi
Firefox 60esr is due for next week.
As of now Debian Stretch is bound to Firefox ESR 52 which reaches EOL
soon. The problem is that it becomes less and less usable as more and
more extensions are becoming incompatible with it.
On the other hand
Hi
Firefox 60esr is due for next week.
As of now Debian Stretch is bound to Firefox ESR 52 which reaches EOL
soon. The problem is that it becomes less and less usable as more and
more extensions are becoming incompatible with it.
On the other hand team mozilla.debian.net clearly states that
41 matches
Mail list logo