Discussion:
Can someone update lib32-p11-kit?
(too old to reply)
DR via arch-general
2017-05-10 19:33:59 UTC
Permalink
Raw Message
It's breaking 32bit chrome and other stuffs.

Regards.
Eli Schwartz via arch-general
2017-05-10 20:05:37 UTC
Permalink
Raw Message
Post by DR via arch-general
It's breaking 32bit chrome and other stuffs.
It's already flagged as out-of-date, no need to go complaining on the
mailing list though.

While it may be disappointing that a package actually goes a whole 2
weeks without getting updated, these things do occasionally happen, even
in Arch Linux. :)

In the meantime, breaking 32-bit-applications-on-64-bit-Arch-Linux
binary artifacts that don't even seem to be packaged in the AUR is not
really sufficient justification IMHO to already be bugging the
maintainer about it, especially since AFAIK Google stopped providing new
32-bit Chrome versions a while ago, on account of they provide 64-bit
builds and feel that that is sufficient in this day and age...
--
Eli Schwartz
Doug Newgard
2017-05-10 20:14:36 UTC
Permalink
Raw Message
On Wed, 10 May 2017 15:33:59 -0400
Post by DR via arch-general
It's breaking 32bit chrome and other stuffs.
Regards.
There is no 32 bit Chrome anymore. What "other stuffs"?
DR via arch-general
2017-05-10 21:24:46 UTC
Permalink
Raw Message
Post by Doug Newgard
On Wed, 10 May 2017 15:33:59 -0400
Post by DR via arch-general
It's breaking 32bit chrome and other stuffs.
Regards.
There is no 32 bit Chrome anymore. What "other stuffs"?
There's if I build it myself. Maybe I should've said chromium.

Other things like Vivaldi 32bit. Basically any 32bit application that uses
nss.

Regards
Rafael Fontenelle
2017-05-11 03:25:43 UTC
Permalink
Raw Message
Post by Doug Newgard
On Wed, 10 May 2017 15:33:59 -0400
Post by DR via arch-general
It's breaking 32bit chrome and other stuffs.
Regards.
There is no 32 bit Chrome anymore. What "other stuffs"?
There's if I build it myself.


Did you try building it in a clean chroot?

Regards,
Rafael Fontenelle

Loading...