On Sat, 25 Apr 2015 10:01:57 +0200, Rodrigo Rivas wrote:
>[snip] The "libvpx.so" symbolic link [snip] is not needed in
>runtime.
Thank you :).
On Fri, Apr 24, 2015 at 8:06 AM, Ralf Mardorf
wrote:
> On Fri, 24 Apr 2015 06:41:27 +0200, Ralf Mardorf wrote:
>>On Thu, 23 Apr 2015 22:56:56 +0300, Jesse Jaara wrote:
>>>What you need to do is to create a custom package for the specific
>>>version of libvpx that doesn't conflict with the one from
On Fri, 24 Apr 2015 06:41:27 +0200, Ralf Mardorf wrote:
>On Thu, 23 Apr 2015 22:56:56 +0300, Jesse Jaara wrote:
>>What you need to do is to create a custom package for the specific
>>version of libvpx that doesn't conflict with the one from repo, so you
>>can have both the new version for repo pack
On Thu, 23 Apr 2015 22:56:56 +0300, Jesse Jaara wrote:
>What you need to do is to create a custom package for the specific
>version of libvpx that doesn't conflict with the one from repo, so you
>can have both the new version for repo packages and the old version
>for whatever reason
Yes, I was th
What you need to do is to create a custom package for the specific version
of libvpx that doesn't conflict with the one from repo, so you can have
both the new version for repo packages and the old version for whatever
reason
On Thu, 23 Apr 2015 21:01:21 +0200, Aaron Caffrey wrote:
>Maybe you should specify which packages to be ignored via 'IgnorePkg'
Hi Aaron,
the problem is that a user first needs to test which software depends
on a dedicated version of a dependency and wich version doesn't.
$ pacman -Qi libvpx | g
On 23/04/15 at 04:18pm, Ralf Mardorf wrote:
Hi :)
if a dedicated version of a dependency is needed, some packages
mention it, others don't.
Firefox does not explicitly mention a version of libvpx
$ pacman -Si firefox | grep On
Depends On : [snip] libvpx [snip]
but it needs a dedicated ver
On 23-04-2015 16:57, Ralf Mardorf wrote:
> On Thu, 23 Apr 2015 17:42:44 +0200, G. Schlisio wrote:
>> arch does not support partial upgrades. it is simply to much of a
>> hassle, to keep track of every versioned dependency. so, if you choose
>> to update partially, you have to deal with it on your o
On Thu, 23 Apr 2015 17:42:44 +0200, G. Schlisio wrote:
>arch does not support partial upgrades. it is simply to much of a
>hassle, to keep track of every versioned dependency. so, if you choose
>to update partially, you have to deal with it on your own (as you
>already do).
>i think there have been
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
> I didn't notice that Firefox needs the up to date version of
> libvpx too. I wonder if there's a way to list all packages that
> depend on a dedicated version of another package.
arch does not support partial upgrades. it is simply to much of a
ha
On Thu, 23 Apr 2015 17:06:39 +0200, Simon Hanna wrote:
>are you sure everything is updated and you aren't using testing?!
Hi,
I'm aware that libvpx isn't up to date on my machine. I need to keep an
outdated version of Virtualmachine and to run it, I need the outdated
version of libvpx.
$ pacman
It's working fine for me...
% pacman -Qs libvp
local/libvpx 1.4.0-2
VP8 and VP9 codec
% pacman -Qs firefox
local/firefox 37.0.2-1
Standalone web browser from mozilla.org
% pacman -Qs ffmpeg
local/ffmpeg 1:2.6.2-1
Complete and free Internet live audio and video broadcasting solution
ar
Hi :)
if a dedicated version of a dependency is needed, some packages
mention it, others don't.
Firefox does not explicitly mention a version of libvpx
$ pacman -Si firefox | grep On
Depends On : [snip] libvpx [snip]
but it needs a dedicated version
$ firefox
XPCOMGlueLoad error for file /
13 matches
Mail list logo
