[gentoo-user] Dependency conflict. openjpeg ffmpeg

[gentoo-user] Dependency conflict. openjpeg ffmpeg

[Dale]

Howdy,

I can't figure out a way around this one.  Usually keywording, maybe
that should be unkeywording, a newer version works but doesn't seem to
in this case.   This started as part of a emerge -uvaDN world. 

Error I get:

WARNING: One or more updates/rebuilds have been skipped due to a
dependency conflict:

media-libs/openjpeg:0

  (media-libs/openjpeg-1.5.1:0/0::gentoo, ebuild scheduled for merge)
conflicts with
    >=media-libs/openjpeg-1.3-r2:0[abi_x86_64(-)] required by
(media-video/ffmpeg-2.2.3-r1:0/52.55.55::gentoo, ebuild scheduled for merge)

Little more info:

root@fireball / # equery list -p openjpeg ffmpeg
 * Searching for openjpeg ...
[IP-] [  ] media-libs/openjpeg-1.4-r1:0
[-P-] [  ] media-libs/openjpeg-1.5.0:0
[-P-] [  ] media-libs/openjpeg-1.5.1:0
[-P-] [ ~] media-libs/openjpeg-1.5.1-r1:0
[IP-] [  ] media-libs/openjpeg-2.0.0:2
[-P-] [ -] media-libs/openjpeg-9999:2

 * Searching for ffmpeg ...
[-P-] [  ] media-video/ffmpeg-0.10.12:0.10
[-P-] [  ] media-video/ffmpeg-1.0.8:0
[-P-] [  ] media-video/ffmpeg-1.0.9:0
[-P-] [  ] media-video/ffmpeg-1.2.6:0
[-P-] [  ] media-video/ffmpeg-2.2.2:0/52.55.55
[-P-] [  ] media-video/ffmpeg-2.2.3:0/52.55.55
[IP-] [  ] media-video/ffmpeg-2.2.3-r1:0/52.55.55
[-P-] [ -] media-video/ffmpeg-9999:0/52.55.55
root@fireball / #

I try not to use the 9999 versions.  I don't think I ever have.  I tried
unmerging openjpeg and ffmpeg, doing the preserved-rebuild thing and I
still get this error when I try to update again.  I have also synced
twice just in case I got a mixed version of the tree.  I also tried to
do a emerge -e system as well but it spits that error out first thing.

Anyone shed some light on this? 

Thanks.

Dale

:-)  :-) 

-- 
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!

Re: [gentoo-user] Dependency conflict. openjpeg ffmpeg

[Alan McKinnon]

On 14/06/2014 23:23, Dale wrote:
> Howdy,
> 
> I can't figure out a way around this one.  Usually keywording, maybe
> that should be unkeywording, a newer version works but doesn't seem to
> in this case.   This started as part of a emerge -uvaDN world. 
> 
> Error I get:
> 
> WARNING: One or more updates/rebuilds have been skipped due to a
> dependency conflict:
> 
> media-libs/openjpeg:0
> 
>   (media-libs/openjpeg-1.5.1:0/0::gentoo, ebuild scheduled for merge)
> conflicts with
>     >=media-libs/openjpeg-1.3-r2:0[abi_x86_64(-)] required by
> (media-video/ffmpeg-2.2.3-r1:0/52.55.55::gentoo, ebuild scheduled for merge)
> 
> Little more info:
> 
> root@fireball / # equery list -p openjpeg ffmpeg
>  * Searching for openjpeg ...
> [IP-] [  ] media-libs/openjpeg-1.4-r1:0
> [-P-] [  ] media-libs/openjpeg-1.5.0:0
> [-P-] [  ] media-libs/openjpeg-1.5.1:0
> [-P-] [ ~] media-libs/openjpeg-1.5.1-r1:0
> [IP-] [  ] media-libs/openjpeg-2.0.0:2
> [-P-] [ -] media-libs/openjpeg-9999:2
> 
>  * Searching for ffmpeg ...
> [-P-] [  ] media-video/ffmpeg-0.10.12:0.10
> [-P-] [  ] media-video/ffmpeg-1.0.8:0
> [-P-] [  ] media-video/ffmpeg-1.0.9:0
> [-P-] [  ] media-video/ffmpeg-1.2.6:0
> [-P-] [  ] media-video/ffmpeg-2.2.2:0/52.55.55
> [-P-] [  ] media-video/ffmpeg-2.2.3:0/52.55.55
> [IP-] [  ] media-video/ffmpeg-2.2.3-r1:0/52.55.55
> [-P-] [ -] media-video/ffmpeg-9999:0/52.55.55
> root@fireball / #
> 
> I try not to use the 9999 versions.  I don't think I ever have.  I tried
> unmerging openjpeg and ffmpeg, doing the preserved-rebuild thing and I
> still get this error when I try to update again.  I have also synced
> twice just in case I got a mixed version of the tree.  I also tried to
> do a emerge -e system as well but it spits that error out first thing.
> 
> Anyone shed some light on this? 

Look closely at the deps. You don't have a blocker, you have a conflict.

Your version of openjpeg is OK, the sub-slot operators are not.

What's the result of "eix openjpeg"?


-- 
Alan McKinnon
alan.mckinnon@gmail.com

Re: [gentoo-user] Dependency conflict. openjpeg ffmpeg

[Dale]

Alan McKinnon wrote:
> Look closely at the deps. You don't have a blocker, you have a
> conflict. Your version of openjpeg is OK, the sub-slot operators are
> not. What's the result of "eix openjpeg"? 

I get this:

root@fireball / # eix openjpeg
[U] media-libs/openjpeg
     Available versions: 
     (0)    1.4-r1{tbz2} 1.5.0^t 1.5.1^t{tbz2} ~1.5.1-r1^t
     (2)    2.0.0^t{tbz2} **9999^t
       {doc static-libs test +vanilla ABI_MIPS="n32 n64 o32" ABI_X86="32
64 x32"}
     Installed versions:  1.4-r1{tbz2}(11:00:53 AM 06/14/2014)(-doc
-test) 2.0.0(2)^t{tbz2}(02:27:04 PM 06/13/2014)(-doc -static-libs -test)
     Homepage:            http://code.google.com/p/openjpeg/
     Description:         An open-source JPEG 2000 library

root@fireball / #
 

This is all portage gives me for a error.  It ain't much.

root@fireball / # emerge -uvaDN world

These are the packages that would be merged, in order:

Calculating dependencies... done!

Total: 0 packages, Size of downloads: 0 kB

WARNING: One or more updates/rebuilds have been skipped due to a
dependency conflict:

media-libs/openjpeg:0

  (media-libs/openjpeg-1.5.1:0/0::gentoo, ebuild scheduled for merge)
conflicts with
    >=media-libs/openjpeg-1.3-r2:0[abi_x86_64(-)] required by
(media-video/ffmpeg-2.2.3-r1:0/52.55.55::gentoo, installed)
                                                


Nothing to merge; quitting.

root@fireball / #

Dale

:-)  :-) 

-- 
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!

Re: [gentoo-user] Dependency conflict. openjpeg ffmpeg

[John Campbell]

On 06/14/2014 05:12 PM, Dale wrote:
>
> media-libs/openjpeg:0
>
>    (media-libs/openjpeg-1.5.1:0/0::gentoo, ebuild scheduled for merge)
> conflicts with
>      >=media-libs/openjpeg-1.3-r2:0[abi_x86_64(-)] required by
> (media-video/ffmpeg-2.2.3-r1:0/52.55.55::gentoo, installed)

The multilib stuff is a work in progress...  You have two 64bit ABIs set 
up, and ffmpeg wants the x32 rather than the 64.  It needs it's 
libraries to match.  Looks like openjpeg chose the 64 ABI to compile.

Just set ABI_X86="32 x32" for openjpeg.  It's in 
/etc/portage/env/media-libs/openjpeg-1.3-r2

Re: [gentoo-user] Dependency conflict. openjpeg ffmpeg

[Dale]

John Campbell wrote:
> On 06/14/2014 05:12 PM, Dale wrote:
>>
>> media-libs/openjpeg:0
>>
>>    (media-libs/openjpeg-1.5.1:0/0::gentoo, ebuild scheduled for merge)
>> conflicts with
>>      >=media-libs/openjpeg-1.3-r2:0[abi_x86_64(-)] required by
>> (media-video/ffmpeg-2.2.3-r1:0/52.55.55::gentoo, installed)
>
> The multilib stuff is a work in progress...  You have two 64bit ABIs
> set up, and ffmpeg wants the x32 rather than the 64.  It needs it's
> libraries to match.  Looks like openjpeg chose the 64 ABI to compile.
>
> Just set ABI_X86="32 x32" for openjpeg.  It's in
> /etc/portage/env/media-libs/openjpeg-1.3-r2
>
>
>

I don't have a env directory in /etc/portage and there is no
openjpeg-1.3-r2 available in the tree.  I sort of think I know what you
are talking about tho.  I need to create that directory structure for
openjpeg-1.4-r1 and put ABI_X86="32 x32" in the file.  My question is,
will this eventually be fixed in the tree and the error go away?  I've
never put anything in the env directory before and would prefer to keep
it that way because I will forget it is there and it will come back and
bite me some day.  Ask anyone here.  lol 

Now I see why the error didn't make any sense to me.  I usually look for
something like a USE flag conflict or something.  I don't recall ever
running into a 64/32 bit thingy before.  O_O  

Thanks.  Muddy water is starting to clear up, a little bit anyway.

Dale

:-)  :-) 

-- 
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!

Re: [gentoo-user] Dependency conflict. openjpeg ffmpeg

[John Campbell]

On 06/14/2014 07:10 PM, Dale wrote:

> I don't have a env directory in /etc/portage and there is no
> openjpeg-1.3-r2 available in the tree.  I sort of think I know what you
> are talking about tho.  I need to create that directory structure for
> openjpeg-1.4-r1 and put ABI_X86="32 x32" in the file.

Sorry, I mistyped the version number.

> My question is,
> will this eventually be fixed in the tree and the error go away?  I've
> never put anything in the env directory before and would prefer to keep
> it that way because I will forget it is there and it will come back and
> bite me some day.  Ask anyone here.  lol

I doubt it.  Having two different 64bit ABIs isn't a normal use case.  I 
have 8gig of memory, on my system, so I have set it globally as 
ABI_X64="32 64" in /etc/make.conf.  It just wasn't worth the hassle for 
the smaller memory footprint x32 provides.

> Now I see why the error didn't make any sense to me.  I usually look for
> something like a USE flag conflict or something.  I don't recall ever
> running into a 64/32 bit thingy before.  O_O

There seems to be an upheaval in the emul-linux-x32 libraries going on, 
and a lot of packages are adding/subtracting the ABI_X86 options.  It's 
going to be a mess for a while.

Re: [gentoo-user] Dependency conflict. openjpeg ffmpeg

[Dale]

John Campbell wrote:
> On 06/14/2014 07:10 PM, Dale wrote:
>
>> I don't have a env directory in /etc/portage and there is no
>> openjpeg-1.3-r2 available in the tree.  I sort of think I know what you
>> are talking about tho.  I need to create that directory structure for
>> openjpeg-1.4-r1 and put ABI_X86="32 x32" in the file.
>
> Sorry, I mistyped the version number.

Ahh.  I was curious and thought about that.  That version is mentioned
in the error tho so I wasn't sure.  I wonder tho, can I add that file
and not have a version at all?   Sort of like I do in package.keywords
etc etc.


>
>> My question is,
>> will this eventually be fixed in the tree and the error go away?  I've
>> never put anything in the env directory before and would prefer to keep
>> it that way because I will forget it is there and it will come back and
>> bite me some day.  Ask anyone here.  lol
>
> I doubt it.  Having two different 64bit ABIs isn't a normal use case. 
> I have 8gig of memory, on my system, so I have set it globally as
> ABI_X64="32 64" in /etc/make.conf.  It just wasn't worth the hassle
> for the smaller memory footprint x32 provides.

Well, I have 16Gbs here.  I'm not lacking for memory.  If memory prices
were to drop a bit, I could upgrade some more.  I'd have to swap out
what I have tho.  Old mobo would only take 4GB sticks and this new one
will take 8GB sticks.


>
>> Now I see why the error didn't make any sense to me.  I usually look for
>> something like a USE flag conflict or something.  I don't recall ever
>> running into a 64/32 bit thingy before.  O_O
>
> There seems to be an upheaval in the emul-linux-x32 libraries going
> on, and a lot of packages are adding/subtracting the ABI_X86 options. 
> It's going to be a mess for a while.
>
>

Yeppie.  Not!!

Thanks.

Dale

:-)  :-) 

-- 
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!

Re: [gentoo-user] Dependency conflict. openjpeg ffmpeg

[John Campbell]

On 06/14/2014 10:10 PM, Dale wrote:
> John Campbell wrote:
>> On 06/14/2014 07:10 PM, Dale wrote:
>>
>>> I don't have a env directory in /etc/portage and there is no
>>> openjpeg-1.3-r2 available in the tree.  I sort of think I know what you
>>> are talking about tho.  I need to create that directory structure for
>>> openjpeg-1.4-r1 and put ABI_X86="32 x32" in the file.
>>
>> Sorry, I mistyped the version number.
>
> Ahh.  I was curious and thought about that.  That version is mentioned
> in the error tho so I wasn't sure.  I wonder tho, can I add that file
> and not have a version at all?   Sort of like I do in package.keywords
> etc etc.

Yes, you can skip the version number.  It should be just like the 
package.* directories but for env(ironment) variables.  It wouldn't 
suprise me if someone renamed it to package.env someday like they did 
from package.keywords to package.accept_keywords.

> Well, I have 16Gbs here.  I'm not lacking for memory.  If memory prices
> were to drop a bit, I could upgrade some more.  I'd have to swap out
> what I have tho.  Old mobo would only take 4GB sticks and this new one
> will take 8GB sticks.

Unless you have a specific reason for keeping both x32 and 64 ABIs I'd 
suggest changing to ABI_X86="32 64" globally in /etc/make.conf (or 
/etc/portage/make.conf).  It's a lot easier than waiting for the next 
conflict.  Then do "emerge --new-use --deep @world" and you're done. 
There shouldn't bee too many packages that need rebuilding.

Re: [gentoo-user] Dependency conflict. openjpeg ffmpeg

[wraeth]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 15/06/14 16:13, John Campbell wrote:
> On 06/14/2014 10:10 PM, Dale wrote: Yes, you can skip the version number. 
> It should be just like the package.* directories but for env(ironment) 
> variables.  It wouldn't suprise me if someone renamed it to package.env 
> someday like they did from package.keywords to package.accept_keywords.

*I* could be wrong, but this looks wrong.

The way I understand the environment overrides to work is:

You create a file in /etc/portage/env with your environment overrides:

file /etc/portage/env/notmpfs.conf:
PORTAGE_TMPDIR="/var/tmp/portage-notmp"

You then instruct which packages are to use a given environment override using
package.env:

file /etc/portage/package.env:
mail-client/thunderbird notmpfs.conf

When emerge begins work on a given atom, it will look at package.env to see if
there are any environment override directives given, and if so, use the
variables defined in the specified environment file to override those in
make.conf (or the default value if not specified).

At least, this is how I use /etc/portage/{,package.}env, and afaik is *how*
it's supposed to be used (as far as I understand man portage(5)).

Please, feel free to correct me if i'm wrong.

- -wraeth
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iF4EAREIAAYFAlOdP+wACgkQXcRKerLZ91mPygD/QNgEvnYIwnenijsM1ekj/2Hj
MvvHHojrdWHg4JudKAMA+wexTE9z9JEAYQRZARQS1NSd2sQj637cTpVl18NDE2BD
=vWhf
-----END PGP SIGNATURE-----

Re: [gentoo-user] Dependency conflict. openjpeg ffmpeg

[wraeth]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 15/06/14 16:40, wraeth wrote:
> Please, feel free to correct me if i'm wrong.

Looks like I *was* wrong - i was testing with something that seemingly wasn't
being overridden.  Actually testing with PORTAGE_TMPDIR (something more global
to portage than what I was testing with) *does* override that variable using
the '/etc/portage/env/<category>/<pkg-vers>' structure.

Don't mind me :)

- -wraeth


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iF4EAREIAAYFAlOdQ6IACgkQXcRKerLZ91kiRgD/WS1YO2d9JOviTINSIsFoe7jX
NYEHLbX5a99nb1k4BVkA/3E+LSH2Iu5det0PuDF5gW8NxomEf7/PQr6wKOwkovE8
=Bc4d
-----END PGP SIGNATURE-----

Re: [gentoo-user] Dependency conflict. openjpeg ffmpeg

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 910 bytes --]

On Sun, 15 Jun 2014 00:10:41 -0500, Dale wrote:

> Ahh.  I was curious and thought about that.  That version is mentioned
> in the error tho so I wasn't sure.  I wonder tho, can I add that file
> and not have a version at all?   Sort of like I do in package.keywords
> etc etc.

You can, but you just said.

> I've
> never put anything in the env directory before and would prefer to keep
> it that way because I will forget it is there and it will come back and
> bite me some day.  

Using the version number means the setting will "expire" when the
package is upgraded, meaning it won;t be able to bite you later on.

Though I would prefix the atom with ~ instead of = to cover patch level
updates.


-- 
Neil Bothwick

An infinite number of monkeys pounding away on keyboards will
eventually produce a report showing that Windows is more secure,
and has a lower TCO, than linux.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

Re: [gentoo-user] Dependency conflict. openjpeg ffmpeg

[Dale]

John Campbell wrote:
> On 06/14/2014 10:10 PM, Dale wrote:
>
>> Well, I have 16Gbs here.  I'm not lacking for memory.  If memory prices
>> were to drop a bit, I could upgrade some more.  I'd have to swap out
>> what I have tho.  Old mobo would only take 4GB sticks and this new one
>> will take 8GB sticks.
>
> Unless you have a specific reason for keeping both x32 and 64 ABIs I'd
> suggest changing to ABI_X86="32 64" globally in /etc/make.conf (or
> /etc/portage/make.conf).  It's a lot easier than waiting for the next
> conflict.  Then do "emerge --new-use --deep @world" and you're done.
> There shouldn't bee too many packages that need rebuilding.
>
>

I put that in make.conf and get this:

# required by sys-fs/eudev-1.7[gudev]
# required by @selected
# required by @world (argument)
=dev-libs/glib-2.40.0 ~amd64
 
Does it make sense to keyword that?  Isn't that the package that once
upgraded you can't go backward?  I'm just double checking that this all
makes sense.  < scratches head > 

Dale

:-)  :-) 

-- 
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!

Re: [gentoo-user] Dependency conflict. openjpeg ffmpeg

[Dale]

[-- Attachment #1: Type: text/plain, Size: 1318 bytes --]

Neil Bothwick wrote:
> On Sun, 15 Jun 2014 00:10:41 -0500, Dale wrote:
>
>> Ahh.  I was curious and thought about that.  That version is mentioned
>> in the error tho so I wasn't sure.  I wonder tho, can I add that file
>> and not have a version at all?   Sort of like I do in package.keywords
>> etc etc.
>
> You can, but you just said.
>
>> I've
>> never put anything in the env directory before and would prefer to keep
>> it that way because I will forget it is there and it will come back and
>> bite me some day. 
>
> Using the version number means the setting will "expire" when the
> package is upgraded, meaning it won;t be able to bite you later on.
>
> Though I would prefix the atom with ~ instead of = to cover patch level
> updates.
>
>

I have looked for a place where it is documented how to do that.  I know
there is a lot of ways to add packages to those files with <=> and such
in front of the package names.  Do you have a link to some docs on
that?   If not, some examples would be cool.

Well, I was going to try adding the variable to make.conf as posted in
another email.  I think that may be better since this seems to be a
issue that is "in flux" at the moment.  ;-)

Dale

:-)  :-)

-- 
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!


[-- Attachment #2: Type: text/html, Size: 2012 bytes --]

Re: [gentoo-user] Dependency conflict. openjpeg ffmpeg

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 1001 bytes --]

On Sun, 15 Jun 2014 03:59:25 -0500, Dale wrote:

> > Though I would prefix the atom with ~ instead of = to cover patch
> > level updates.

> I have looked for a place where it is documented how to do that.  I know
> there is a lot of ways to add packages to those files with <=> and such
> in front of the package names.  Do you have a link to some docs on
> that?   If not, some examples would be cool.

man portage
man 5 ebuild

The latter has more detail.

> Well, I was going to try adding the variable to make.conf as posted in
> another email.  I think that may be better since this seems to be a
> issue that is "in flux" at the moment.  ;-) 

I think the very fluxiness of it would put me off enabling it globally
and set it case by case until things had settled down.

BTW eix-test-obsolete is a good tool for cleaning up /etc/portage,
finding all sorts of per-package settings you set and forgot about.


-- 
Neil Bothwick

But I thought YOU did the backups...

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

Re: [gentoo-user] Dependency conflict. openjpeg ffmpeg

[Dale]

Neil Bothwick wrote:
> On Sun, 15 Jun 2014 03:59:25 -0500, Dale wrote:
>
>>> Though I would prefix the atom with ~ instead of = to cover patch
>>> level updates.
>> I have looked for a place where it is documented how to do that.  I know
>> there is a lot of ways to add packages to those files with <=> and such
>> in front of the package names.  Do you have a link to some docs on
>> that?   If not, some examples would be cool.
> man portage
> man 5 ebuild
>
> The latter has more detail.

Gold mine.  I knew it had to be somewhere but never could find it. 
Thank you!!


>
>> Well, I was going to try adding the variable to make.conf as posted in
>> another email.  I think that may be better since this seems to be a
>> issue that is "in flux" at the moment.  ;-) 
> I think the very fluxiness of it would put me off enabling it globally
> and set it case by case until things had settled down.
>
> BTW eix-test-obsolete is a good tool for cleaning up /etc/portage,
> finding all sorts of per-package settings you set and forgot about.
>
>


Yea, may try that.  I dunno.  To sleepy right now. 

I tend to forget to run that until the list gets HUGE then it is like,
that takes to long so oh well.  I really need to spend a few hours
working on that tho.  I'm sure it is a nightmare by now. 

Dale

:-)  :-) 

-- 
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!

[gentoo-user] Re: Dependency conflict. openjpeg ffmpeg

[Jonathan Callen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 06/15/2014 04:47 AM, Dale wrote:
> John Campbell wrote:
>> On 06/14/2014 10:10 PM, Dale wrote:
>> 
>>> Well, I have 16Gbs here.  I'm not lacking for memory.  If
>>> memory prices were to drop a bit, I could upgrade some more.
>>> I'd have to swap out what I have tho.  Old mobo would only take
>>> 4GB sticks and this new one will take 8GB sticks.
>> 
>> Unless you have a specific reason for keeping both x32 and 64
>> ABIs I'd suggest changing to ABI_X86="32 64" globally in
>> /etc/make.conf (or /etc/portage/make.conf).  It's a lot easier
>> than waiting for the next conflict.  Then do "emerge --new-use
>> --deep @world" and you're done. There shouldn't bee too many
>> packages that need rebuilding.
>> 
>> 
> 
> I put that in make.conf and get this:
> 
> # required by sys-fs/eudev-1.7[gudev] # required by @selected #
> required by @world (argument) =dev-libs/glib-2.40.0 ~amd64
> 
> Does it make sense to keyword that?  Isn't that the package that
> once upgraded you can't go backward?  I'm just double checking that
> this all makes sense.  < scratches head >
> 
> Dale
> 
> :-)  :-)
> 

The package you are thinking of that is a one-way upgrade is glibc,
not glib.  Glibc is the C Runtime Environment, absolutely everything
written in C and C++ ends up linking against it (and things that
aren't tend either to be compiled using something that is or
interpreted by something that is).  If glibc is downgraded, anything
that uses something from a newer version (or something that *changed*
in a newer version, due to how symbol versions work) will fail to run
against the older version.

For example, any program linked against glibc 2.14 or greater that
uses memcpy ends up linking against the symbol "memcpy@@GLIBC_2.14",
which is only in newer versions of glibc.  Programs linked against
older versions of glibc use "memcpy@GLIBC_2.2.5", which differs in
some way (specifically in this case, the old memcpy always went in a
particular direction, the new memcpy may be faster on some CPUs, but
this broke old Adobe Flash).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCgAGBQJTnqAdAAoJELHSF2kinlg4RwIQAIBA/fnW7hq6GUK3fQimcEIo
RdeXK3RXy750T6XP5vo71NFhrJJmaROaNzSksKXfAtfJZt3PnpbIxFxtvKep7Xp3
bJnAOXHej+EndkSDXEoZTAepzEmqIj8V+Y4blSmRE25w+NLTe2Wgkjd92Y6ugroW
Hk1A/nrGRNO5pBepSvIUOIn5GIoTMMH4485HBnwUdtt6+EQja50cfSMbTUoXqF38
GgkJkik28TOYSivn6b6VdzCvl+X8ZqFY0M+BhWSLLaN+7/BR1S5dI1Th1QNDaHSX
KcCbtSIwqB1V5w5jSLb4JtU+Noi5nqXyy4ZnwR0wCN/MkhBFFQlRYE/sgOeYrOgw
mxCj7442q0Ml1nv+4ASHdOsQ/M8VCoBR3TZhCYDU5wZB6Wb4AVY/tSxopDL54aqi
4iutCTBn9fh7NIfasVjhvSdNMdglF/SHnHfiS9C94odFGvbZjHJd7ICwshSh9eNG
/jwRRSrmdMK9IiqK9IkTYDXlCYkre2CtIt8urlypoWaQwD5IrkEIeE9PvXEUcDNU
jw8S+3hhNkQ5/3MKErBwGOshdhoogTM03afbSg/M3DRn+B3GAo8Zi9i26wUPTMJo
Y6Nm3xhPd5K5h9hmh4bTkG+eqIshtTpqC9cdzQ/xf1dA2X1yxvBdXt6B3cGQg/+1
kUyTwlCW3O11b9l0LzeH
=C+Xr
-----END PGP SIGNATURE-----

Re: [gentoo-user] Dependency conflict. openjpeg ffmpeg

[thegeezer]

On 06/14/2014 10:23 PM, Dale wrote:
> Howdy,
>
> I can't figure out a way around this one.  Usually keywording, maybe
> that should be unkeywording, a newer version works but doesn't seem to
> in this case.   This started as part of a emerge -uvaDN world. 
>
> Error I get:
>
> WARNING: One or more updates/rebuilds have been skipped due to a
> dependency conflict:
>
> media-libs/openjpeg:0
>
>   (media-libs/openjpeg-1.5.1:0/0::gentoo, ebuild scheduled for merge)
> conflicts with
>     >=media-libs/openjpeg-1.3-r2:0[abi_x86_64(-)] required by
> (media-video/ffmpeg-2.2.3-r1:0/52.55.55::gentoo, ebuild scheduled for merge)
>
> Little more info:
>
> root@fireball / # equery list -p openjpeg ffmpeg
>  * Searching for openjpeg ...
> [IP-] [  ] media-libs/openjpeg-1.4-r1:0
> [-P-] [  ] media-libs/openjpeg-1.5.0:0
> [-P-] [  ] media-libs/openjpeg-1.5.1:0
> [-P-] [ ~] media-libs/openjpeg-1.5.1-r1:0
> [IP-] [  ] media-libs/openjpeg-2.0.0:2
> [-P-] [ -] media-libs/openjpeg-9999:2
>
>  * Searching for ffmpeg ...
> [-P-] [  ] media-video/ffmpeg-0.10.12:0.10
> [-P-] [  ] media-video/ffmpeg-1.0.8:0
> [-P-] [  ] media-video/ffmpeg-1.0.9:0
> [-P-] [  ] media-video/ffmpeg-1.2.6:0
> [-P-] [  ] media-video/ffmpeg-2.2.2:0/52.55.55
> [-P-] [  ] media-video/ffmpeg-2.2.3:0/52.55.55
> [IP-] [  ] media-video/ffmpeg-2.2.3-r1:0/52.55.55
> [-P-] [ -] media-video/ffmpeg-9999:0/52.55.55
> root@fireball / #
>
> I try not to use the 9999 versions.  I don't think I ever have.  I tried
> unmerging openjpeg and ffmpeg, doing the preserved-rebuild thing and I
> still get this error when I try to update again.  I have also synced
> twice just in case I got a mixed version of the tree.  I also tried to
> do a emerge -e system as well but it spits that error out first thing.
>
> Anyone shed some light on this? 
>
> Thanks.
>
> Dale
>
> :-)  :-) 
>
yay i just had the same thing happen
i tried the ABI keyword as suggested further in the thread but it just
made the error shorter and odder.
in the end i just emerge -C ffmpeg openjpeg then add them all back one
at a time.
it's a bit of a pita but otherwise not really had too may issue with
portage of late.

Re: [gentoo-user] Dependency conflict. openjpeg ffmpeg

[Dale]

thegeezer wrote:
>
> yay i just had the same thing happen
> i tried the ABI keyword as suggested further in the thread but it just
> made the error shorter and odder.
> in the end i just emerge -C ffmpeg openjpeg then add them all back one
> at a time.
> it's a bit of a pita but otherwise not really had too may issue with
> portage of late.
>

Yea, I tried adding it to make.conf and got one error so commented it
out.  When I tried it again later, different error but still a error. 

I tried unmerging and adding back but no joy yet.  At least portage can
skip it tho.

Dale

:-)  :-) 

-- 
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!

Re: [gentoo-user] Dependency conflict. openjpeg ffmpeg

[Dale]

John Campbell wrote:
> On 06/14/2014 05:12 PM, Dale wrote:
>>
>> media-libs/openjpeg:0
>>
>>    (media-libs/openjpeg-1.5.1:0/0::gentoo, ebuild scheduled for merge)
>> conflicts with
>>      >=media-libs/openjpeg-1.3-r2:0[abi_x86_64(-)] required by
>> (media-video/ffmpeg-2.2.3-r1:0/52.55.55::gentoo, installed)
>
> The multilib stuff is a work in progress...  You have two 64bit ABIs
> set up, and ffmpeg wants the x32 rather than the 64.  It needs it's
> libraries to match.  Looks like openjpeg chose the 64 ABI to compile.
>
> Just set ABI_X86="32 x32" for openjpeg.  It's in
> /etc/portage/env/media-libs/openjpeg-1.3-r2
>
>
>

OK.  First, corrected the version and then tried with no version at all
as shown below.  Going to start here since well, this is where this
suggestion started.  I created the files in env and deeper but either it
isn't seeing it for some reason OR it isn't a option to change.  I'm
leaning toward the first since most likely I didn't do something right. 
;-)  It wouldn't be the first time but it is the first time I put
anything in the env directory, which I had to create by the way. 

Current paths to file:

/etc/portage/env/media-libs
/etc/portage/env/media-video

File names:

openjpeg
ffmpeg

Contents of both files:

ABI_X86="32 64"

So, what am I missing there?  Output of emerge:

root@fireball / # emerge -va =media-libs/openjpeg-1.4-r1
=media-libs/openjpeg-2.0.0 media-video/ffmpeg

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R    ] media-libs/openjpeg-1.4-r1  USE="-doc {-test}" 0 kB
[ebuild   R    ] media-libs/openjpeg-2.0.0:2  USE="-doc -static-libs
{-test}" 0 kB
[ebuild   R   ~] media-video/ffmpeg-2.2.3-r1:0/52.55.55  USE="3dnow
3dnowext X aac alsa bzip2 encode faac fontconfig frei0r hardcoded-tables
iconv jpeg2k mmx mmxext mp3 network opengl sdl sse sse2 theora threads
truetype vorbis x264 xvid zlib -aacplus (-altivec) -amr -amrenc
(-armv5te) (-armv6) (-armv6t2) (-armvfp) -avx -avx2 -bindist -bluray
-cdio -celt -cpudetection -debug -doc -examples -fdk -flite -fma3 -fma4
-gme -gnutls -gsm -iec61883 -ieee1394 -jack -ladspa -libass -libcaca
-libsoxr -libv4l (-mips32r2) (-mipsdspr1) (-mipsdspr2) (-mipsfpu)
-modplug (-neon) -openal -openssl -opus -oss -pic -pulseaudio -quvi
-rtmp -schroedinger -speex -sse3 -sse4 -sse4_2 -ssh -ssse3 -static-libs
{-test} -twolame -v4l -vaapi -vdpau -vpx -wavpack -webp -x265 -zvbi"
ABI_X86="(64) -32 (-x32)" FFTOOLS="aviocat cws2fws ffescape ffeval
ffhash fourcc2pixfmt graph2dot ismindex pktdumper qt-faststart trasher" 0 kB

Total: 3 packages (3 reinstalls), Size of downloads: 0 kB

Would you like to merge these packages? [Yes/No] n

Quitting.

root@fireball / #



Note the ABI part isn't changing.  Could it be because of some USE flag
combo I have set?  I do something . . . wrong??  Just for giggles, going
to post the original error again.



WARNING: One or more updates/rebuilds have been skipped due to a
dependency conflict:

media-libs/openjpeg:0

  (media-libs/openjpeg-1.5.1:0/0::gentoo, ebuild scheduled for merge)
conflicts with
    >=media-libs/openjpeg-1.3-r2:0[abi_x86_64(-)] required by
(media-video/ffmpeg-2.2.3-r1:0/52.55.55::gentoo, installed)
                                                


Nothing to merge; quitting.
 

< Dale scratches his head >

Thanks.

Dale

:-)  :-)

-- 
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!

Re: [gentoo-user] Dependency conflict. openjpeg ffmpeg

[Dale]

Dale wrote:
> OK.  First, corrected the version and then tried with no version at all
> as shown below.  Going to start here since well, this is where this
> suggestion started.  I created the files in env and deeper but either it
> isn't seeing it for some reason OR it isn't a option to change.  I'm
> leaning toward the first since most likely I didn't do something right. 
> ;-)  It wouldn't be the first time but it is the first time I put
> anything in the env directory, which I had to create by the way. 
>
> Current paths to file:
>
> /etc/portage/env/media-libs
> /etc/portage/env/media-video
>
> File names:
>
> openjpeg
> ffmpeg
>
> Contents of both files:
>
> ABI_X86="32 64"
>
> So, what am I missing there?  Output of emerge:
>
> root@fireball / # emerge -va =media-libs/openjpeg-1.4-r1
> =media-libs/openjpeg-2.0.0 media-video/ffmpeg
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
> [ebuild   R    ] media-libs/openjpeg-1.4-r1  USE="-doc {-test}" 0 kB
> [ebuild   R    ] media-libs/openjpeg-2.0.0:2  USE="-doc -static-libs
> {-test}" 0 kB
> [ebuild   R   ~] media-video/ffmpeg-2.2.3-r1:0/52.55.55  USE="3dnow
> 3dnowext X aac alsa bzip2 encode faac fontconfig frei0r hardcoded-tables
> iconv jpeg2k mmx mmxext mp3 network opengl sdl sse sse2 theora threads
> truetype vorbis x264 xvid zlib -aacplus (-altivec) -amr -amrenc
> (-armv5te) (-armv6) (-armv6t2) (-armvfp) -avx -avx2 -bindist -bluray
> -cdio -celt -cpudetection -debug -doc -examples -fdk -flite -fma3 -fma4
> -gme -gnutls -gsm -iec61883 -ieee1394 -jack -ladspa -libass -libcaca
> -libsoxr -libv4l (-mips32r2) (-mipsdspr1) (-mipsdspr2) (-mipsfpu)
> -modplug (-neon) -openal -openssl -opus -oss -pic -pulseaudio -quvi
> -rtmp -schroedinger -speex -sse3 -sse4 -sse4_2 -ssh -ssse3 -static-libs
> {-test} -twolame -v4l -vaapi -vdpau -vpx -wavpack -webp -x265 -zvbi"
> ABI_X86="(64) -32 (-x32)" FFTOOLS="aviocat cws2fws ffescape ffeval
> ffhash fourcc2pixfmt graph2dot ismindex pktdumper qt-faststart trasher" 0 kB
>
> Total: 3 packages (3 reinstalls), Size of downloads: 0 kB
>
> Would you like to merge these packages? [Yes/No] n
>
> Quitting.
>
> root@fireball / #
>
>
>
> Note the ABI part isn't changing.  Could it be because of some USE flag
> combo I have set?  I do something . . . wrong??  Just for giggles, going
> to post the original error again.
>
>
>
> WARNING: One or more updates/rebuilds have been skipped due to a
> dependency conflict:
>
> media-libs/openjpeg:0
>
>   (media-libs/openjpeg-1.5.1:0/0::gentoo, ebuild scheduled for merge)
> conflicts with
>     >=media-libs/openjpeg-1.3-r2:0[abi_x86_64(-)] required by
> (media-video/ffmpeg-2.2.3-r1:0/52.55.55::gentoo, installed)
>                                                 
>
>
> Nothing to merge; quitting.
>  
>
> < Dale scratches his head >
>
> Thanks.
>
> Dale
>
> :-)  :-)
>


OK.  This seemed to have fixed the problem. 

USE="-jpeg2k"

If everything still works then I guess I no longer need that USE flag. 
;-)  Now to go undo the other stuff I tried.

Dale

:-)  :-) 

-- 
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!