Hi
The old nss version will be available in wheezy. The new version is
available in wheezy+security only. So it should be available already now
without me doing any changes.
This actually look like a problem for jessie too. See this post here:
Hello all,
Ola Lundqvist:
> As I can see it there are the following options:
> 1) Do nothing. Let it be like this. We have a regression problem but only
> for software that fork and use nss in several threads.
> 2) Try to reverse the library split. This is a non-trivial task.
> 3) Try to fix the
On Fri, Nov 04, 2016 at 01:17:36PM +0100, Ola Lundqvist wrote:
> Hi all
>
> I have now analyzed the problem and the problem is that libfreebl3.so have
> been split into a libfreebl3.so that is pre-loaded and a libfreeblpriv3.so
> that is dynamically loaded by libfreebl3.so. This works well in
Hi Ola,
On Fri, Nov 04, 2016 at 01:17:36PM +0100, Ola Lundqvist wrote:
[..snip analysis..]
> As I can see it there are the following options:
> 1) Do nothing. Let it be like this. We have a regression problem but only
> for software that fork and use nss in several threads.
> 2) Try to reverse
Hi all
I have now analyzed the problem and the problem is that libfreebl3.so have
been split into a libfreebl3.so that is pre-loaded and a libfreeblpriv3.so
that is dynamically loaded by libfreebl3.so. This works well in many
situations but apparently not in google chrome. I guess this is because
On Wed, 2016-11-02 at 20:41 +0100, Jiří Jánský wrote:
> Hello all,
> there is still one thing, that is unclear for me. Chromium is security
> unsupported package. But does it also mean, that it is unsupported at all
> (can be non-function after install by apt-get install chromium)?
[...]
I don't
Hi Jiri
As I understand it is not supported at all. It does not mean that it will
break automatically (as in the ruby-rails-2.3 example you gave) but we can
not maintain it in a good way. One of the main reason for it not being
supported is that the later versions do not even build on wheezy and
Hello all,
there is still one thing, that is unclear for me. Chromium is security
unsupported package. But does it also mean, that it is unsupported at all
(can be non-function after install by apt-get install chromium)?
I am aware, that wheezy chromium package is quite outdated for today web.
Hi Holger and Ben
Thanks for the feedback. I'll check whether upstream chrome or chromium can
be installed and is usable on wheezy.
If chrome or chromium is uninstallable on wheezy, then is this an issue? I
would see it as that, but maybe outside LTS scope.
// Ola
On 2 November 2016 at 00:50,
On Tue, Nov 01, 2016 at 05:18:45PM -0600, Ben Hutchings wrote:
> I like that the outdated Debian package of chromium for wheezy is now
> unusable. If the current upstream version of Chromium (or Chrome) is
> also broken then that *is* a problem
seconded. (and thanks for wording this so well,
On Tue, 2016-11-01 at 23:37 +0100, Ola Lundqvist wrote:
> Hi Ben, Balint and others
>
> I'd like to have some advice on this regression.
>
> 1) Is this worth investigating?
> - Chrome is not supported, however we have now made it to crash. Ben
> obviously like that but maybe others do not have
On Tue, Nov 01, 2016 at 11:37:29PM +0100, Ola Lundqvist wrote:
> Hi Ben, Balint and others
>
> I'd like to have some advice on this regression.
>
> 1) Is this worth investigating?
> - Chrome is not supported, however we have now made it to crash. Ben
> obviously like that but maybe others do
Hi Ben, Balint and others
I'd like to have some advice on this regression.
1) Is this worth investigating?
- Chrome is not supported, however we have now made it to crash. Ben
obviously like that but maybe others do not have the same opinion.
2) Is this severe enough for me to revert the nss
13 matches
Mail list logo
