Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 9 Sep 2013 15:29:30 +0200
From:      Baptiste Daroussin <bapt@FreeBSD.org>
To:        Adam McDougall <mcdouga9@egr.msu.edu>
Cc:        freebsd-chromium@freebsd.org
Subject:   Re: Problems with pkgng (pkg upgrade)
Message-ID:  <20130909132930.GD40186@ithaqua.etoilebsd.net>
In-Reply-To: <522DC5CD.3060006@egr.msu.edu>
References:  <l0kf3b$fka$1@ger.gmane.org> <522DC5CD.3060006@egr.msu.edu>

next in thread | previous in thread | raw e-mail | index | archive | help

--lc9FT7cWel8HagAv
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Sep 09, 2013 at 08:57:49AM -0400, Adam McDougall wrote:
> On 09/09/13 08:31, Lapo Luchini wrote:
> > Hi!
> >=20
> > I'm wondering why the chrome process has the habit of crashing when I do
> > "pkg upgrade" (last time, it was a signal 11).
> >=20
> > I certainly expect something like this during a "pkg upgrade" that
> > involves "chromium" package itself, but this also happens with updating
> > something totally unrelated, such as when "pkg upgrade" only upgrades
> > "pkg" (in the first run); or maybe upgrading "nano", or stuff like that.
> >=20
> > Is it expected?
> > Is it only me?
> > In that case, I can probably help with debug.
> >=20
>=20
> It is not only you, it happens on pretty much all my installs.  It can
> happen even if you pkg install something small and unrelated to
> chromium.  Last week I was shocked when I ran pkg upgrade and it did NOT
> cause chromium to crash; it had even replaced chromium itself!  I don't
> think it crashes 100% of the time, but most.  I don't have time to debug
> it.  Just in case it got fixed, be sure to test using the latest
> chromium version from ports.
> _______________________________________________
> freebsd-chromium@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-chromium
> To unsubscribe, send any mail to "freebsd-chromium-unsubscribe@freebsd.or=
g"

That is because pkgng overwrite the binaries during an upgrade instead of f=
irst
unlinking them then extract the new one.

This is planned to be fixed soon.

regards,
Bapt

--lc9FT7cWel8HagAv
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)

iEYEARECAAYFAlItzToACgkQ8kTtMUmk6Ez7sgCfWB+g+p+N5giYkK1HOH9Xkf/N
xJwAniA2H6QCrvPraPCKkqwwJD2+OE+g
=HBjy
-----END PGP SIGNATURE-----

--lc9FT7cWel8HagAv--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130909132930.GD40186>