On Sun, 2016-07-31 at 08:15 +, nord-stream wrote:
> Any progress on this?
>
> **Please support user choice.**
Updates to stable are _not_ about "user choice".
> If 20% of firefox-esr users want Iceweasel back, that's still a large
> number of users.
It's not /that/ large. I'm also still not
Any progress on this?
**Please support user choice.**
If 20% of firefox-esr users want Iceweasel back, that's still a large
number of users.
Thank you for understanding...
nord-stream
signature.asc
Description: OpenPGP digital signature
Hi,
>(I assume it's not bringing back /etc/iceweasel and /usr/share/iceweasel
>(and probably a bunch of others). For Debian Edu the changed look is not
>so much the problem as are changed pathes.)
maybe you can ask as a feature to have symlinks :)
(not sure if it works)
Gianfranco
On Wed, Jul 20, 2016 at 02:47:18PM +, Gianfranco Costamagna wrote:
> maybe you can ask as a feature to have symlinks :)
we're switching to firefox-esr for good.
--
cheers,
Holger
signature.asc
Description: Digital signature
Hi Gianfranco,
On Wed, Jul 20, 2016 at 12:49:56PM +, Gianfranco Costamagna wrote:
> >> [...] And I also saw Debian Edu
> >> stable break because of this… and we're still fixing it, waiting for
> >> 8.6 to bring these fixes to our users.
> is firefox-branding-iceweasel able to mitigate this iss
Hi Antonio and Holger,
>> And while I applaud and understand why firefox-esr has replaced
>> iceweasel in stable, I was also surprised. And I also saw Debian Edu
>> stable break because of this… and we're still fixing it, waiting for
>> 8.6 to bring these fixes to our users.
>>
>> (The latter i
On Wed, Jul 20, 2016 at 10:59:01AM +, Holger Levsen wrote:
> On Wed, Jul 20, 2016 at 07:44:54AM -0300, Antonio Terceiro wrote:
> > To me not having firefox proper was a long-standing bug, and now that it
> > has been finally fixed, you want to provide a way for people who got
> > used to the bu
On Wed, Jul 20, 2016 at 07:44:54AM -0300, Antonio Terceiro wrote:
> To me not having firefox proper was a long-standing bug, and now that it
> has been finally fixed, you want to provide a way for people who got
> used to the bug to have it back. That's very weird to me.
That might seem weird to y
On Tue, Jul 19, 2016 at 04:56:05PM +, Gianfranco Costamagna wrote:
> there might be users that wants their name back, not sure who they
> are, I don't want to have to answer here, but I still think giving
> users the choice is something sane that might avoid troubles or
> complains.
To me not
Hi Adam!
>You're answering a different question, namely "why". I was asking for
>some information / pointers as to how you know they're being confused.
>Presumably there are several mailing list posts, IRC conversations, etc.
I didn't say the original statement, so I leave nord-stream answeri
On Tue, 2016-07-19 at 16:56 +, Gianfranco Costamagna wrote:
> >Who are these "quite a few users"? Where are they being confused?
>
>
> because they used to have an iceweasel package, and now they have a firefox
> instead
> (different desktop file, different branding)
You're answering a diff
Hi,
>If they're interested, they can follow the bug. They don't all need to
>be CCed on every message.
Indeed, I follow the bug :)
and I propose to drop the cc in the next message
>Who are these "quite a few users"? Where are they being confused?
because they used to have an iceweasel packa
[forgot to CC release]
On 2016-07-19 16:47, nord-stream wrote:
With this in stable, we can say to anyone who wants to keep Iceweasel:
"Run this command:
sudo apt-get install xul-ext-iceweasel-branding"
Why is the compatibility symlink shipped in the iceweasel package
insufficient? If this is
On 2016-07-19 16:47, nord-stream wrote:
With this in stable, we can say to anyone who wants to keep Iceweasel:
"Run this command:
sudo apt-get install xul-ext-iceweasel-branding"
Why is the compatibility symlink shipped in the iceweasel package
insufficient? If this is just about the title of
On 2016-07-19 16:47, nord-stream wrote:
On 18/07/16 17:57, Adam D. Barratt wrote:
[Why is this CCed to quite so many places / people?]
Sponsor, reviewer, related package maintainers...
If they're interested, they can follow the bug. They don't all need to
be CCed on every message.
[...]
On 18/07/16 17:57, Adam D. Barratt wrote:
> [Why is this CCed to quite so many places / people?]
Sponsor, reviewer, related package maintainers...
> A debdiff between two versions of the package is not that helpful to
> convince anyone that the new version should be added to stable, given
> tha
On Mon, Jul 18, 2016 at 06:57:47PM +0100, Adam D. Barratt wrote:
> [Why is this CCed to quite so many places / people?]
I've tried to cut it down now that this is just about the stable update.
> On Mon, 2016-07-18 at 14:48 +, nord-stream wrote:
> > See the attached files.
> >
> > nord-stream
[Why is this CCed to quite so many places / people?]
On Mon, 2016-07-18 at 14:48 +, nord-stream wrote:
> See the attached files.
>
> nord-stream
A debdiff between two versions of the package is not that helpful to
convince anyone that the new version should be added to stable, given
that no
18 matches
Mail list logo
